v0.5.122

Team Agent 0.5.122

• Fix dynamic single-seat startup and team respawn losing the generated MCP configuration (Issue #345 / PR #346).
• Fail closed when a Provider requires MCP readiness but its configuration metadata is missing; defer without input or attempt consumption.
• Retain exact process/image/owner binding, add dynamic-start/resume regressions, and align controlled test observation with the existing image-computation budgets.

Official tagged Publish npm run 39537120683 completed all 8 jobs successfully. Verify workspace: 3,728 passed / 0 failed. Installer and three platform packages are published at 0.5.122.

Published-artifact smoke completed 103 primary CLI expected-exit checks (73 isolated help/configuration checks and 30 native lifecycle/collaboration commands across three workers). Leader CLI and native Worker to="*" broadcasts reached every other intended worker with native acknowledgements. Three same-session, no-hint recalls and a scoped stop with two zero-resource inventories passed. All model communication stayed on native MCP, without source searches or shell/script/RPC fallback.

Known observations are retained: the initial composite driver timed out on an unavailable Leader transcript-receipt projection even though the real Leader independently confirmed receipt; one post-restart native MCP client disconnection recovered through native directory refresh and retry. This is functional finite acceptance with those explicit warnings, not a zero-error or all-provider/platform guarantee. Installing the release does not automatically replace running teams.