Roadmap: full Managed Agents surface alignment

[yanpgwang]

Objective

Track broad, trustworthy alignment beyond the core single-agent milestone in #58.

The official Go SDK v1.61.0 exposes 90 HTTP operations across the Managed Agents surface and its required Files/Skills dependencies. This is the concrete interpretation of the approximate “100 endpoints” target; generated auto-pagers and local SDK helpers are not counted as separate HTTP operations.

Current operation inventory

Surface	Operations
Agents and Agent Versions	6
Environments	6
Sessions and Session Events	9
Environment Work	8
Session Resources	5
Session Threads and Thread Events	5
Deployments and Deployment Runs	10
Vaults and Credentials	13
Memory Stores, Memories, and Memory Versions	14
Files	5
Skills and Skill Versions	9
Total	90

The inventory must be rechecked on every SDK upgrade because these APIs remain beta.

Progress

Slice	Operations	Status	Tracking
Core single-agent contract	21	Complete	#58
Files	5	Complete	#93, #94
File-backed Session Resources	5	Complete	#95, #96

The completed compatibility evidence currently covers 31 of 90 HTTP operations. Operation counts are credited only after the SDK, durability, and documentation gates for a slice pass.

Delivery order

1. Close the core single-agent contract and durability gate in Roadmap: core Managed Agents API alignment #58.
2. Add Files and File-backed Session Resources.
3. Complete the self-hosted Environment Work API.
4. Add Skills and immutable Skill Versions with real runtime materialization.
5. Add Memory Stores, Memories, and Memory Versions, including Memory-backed Session Resources and cross-Session retrieval.
6. Add Vaults and Credentials with explicit isolation and redaction guarantees.
7. Add Deployments and Deployment Runs with durable scheduling and pause/run behavior.
8. Add Multi-agent Session Threads and orchestration on top of the stable Skills and Memory layers.
9. Run a full SDK and live differential conformance release gate.

Skills and Memory are single-agent capabilities first: they provide reusable behavior and cross-Session continuity before they become shared foundations for multi-agent orchestration.

Exit criteria

• Every operation is callable through the official Go SDK.
• Every accepted field is either honored by the runtime or rejected explicitly.
• Pagination, validation, errors, timestamps, archive/delete behavior, and beta headers have black-box coverage.
• Durable operations have PostgreSQL/Temporal restart and replay coverage.
• Compatibility and provenance documentation records every remaining limitation.

This issue tracks broad parity; #58 remains the focused core milestone.