0.0.71

AgentCore Launchpad 0.0.71 adds a governed COA context layer and improves Runtime canaries, trace message visibility, and dependency build reliability.

Highlights

• COA context layer: connect a Context Ontology Accelerator deployment, authorize access as the signed-in member, and attach governed context to Harness or Strands agents. The V2 Context Layer page includes namespace sources, metrics, ontology classes, deployment health, and a conversational playground.
• Runtime canaries: dataset replay sends each question to both arms, and verdicts require the minimum sample count in each arm. Runtime canaries can start at 50/50 and complete early from an eligible paired verdict. Custom evaluator scores also appear in per-case run comparisons.
• Trace messages: show recorded model inputs, completions, MCP arguments/results, and embedded Strands tool results on their own spans, with deduplication and session privacy boundaries preserved.
• Gateway user identity: logged-in Harness chat can forward the member's token to additional CUSTOM_JWT Gateways that meet the workspace trust checks, enabling tools that act as the user.
• Runtime rebuilds: converted Harness agents can recover from stale dependency pins when lock compilation fails. Rebuilding legacy Studio code removes obsolete generated mem0_memory imports and tool-list entries that otherwise prevent startup.
• Dependency validation: reject requirements-file option injection hidden after environment markers before resolving pins or compiling a lock, while retaining ordinary markers and supported URL/VCS pins.

Upgrade notes

• COA integration requires a compatible COA deployment, registration of each environment's Connection callback, and member consent. COA-attached agents currently require console user identity; the public API, evaluation replay, experiments, canaries, and Harness-to-Runtime conversion are unsupported for these agents.
• Additional Gateways must satisfy the workspace Cognito trust checks to receive a member token. Public API and evaluation invocations continue to use their service identity.
• Existing converted Runtime and legacy Studio agents receive the build fixes on their next redeploy or canary build.
• Follow the production runbook for ledger backup, in-flight work checks, and deployment.

Validation

Release target: 40f10c938175a885dc9c9fcc1647d575960a553b from main.

The full make verify gate passed in an isolated checkout with locked dependencies:

• 6,782 backend tests and 48 infrastructure tests.
• 653 frontend tests across 60 files, ESLint, TypeScript checks, and the Vite production build.
• Local lifecycle lint/syntax checks, English/Chinese translation parity (8,261 keys), and Chinese punctuation checks.

GitHub's Python and JavaScript/TypeScript CodeQL checks also passed. The existing non-blocking React Hooks lint warning in EvaluationExperiment.tsx remains.

What's Changed

• Forward the user token to other Gateways that trust the workspace pool by @xiehust in #296
• Show model and tool messages on trace spans by @xiehust in #297
• Let a Runtime canary complete with Dataset replay by @xiehust in #299
• Let agents use COA as a governed context layer, acting as the signed-in member by @xiehust in #302
• Browse and try COA context from the V2 Context Layer page by @xiehust in #303
• Drop mem0_memory from Studio code generated before 0b38065 (#301) by @xiehust in #304
• Re-resolve a converted Runtime's stale requirement pins when its lock fails (#300) by @xiehust in #305
• Reject requirements-file option injection in pinned dependencies by @xiehust in #308

Full Changelog: v0.0.7...0.0.71