[Codename-11]

Summary

• derive Workstream execution provenance from the concrete run connection instead of inheriting Agent Profile runtime configuration
• describe MCP/runtime connection presence as endpoint reachability, separate from AgentRun activity and Delivery state
• auto-transition explicit MCP EXECUTE runs to configured In Progress / In Review statuses with audit and activity evidence
• configure lifecycle targets for new workspaces and document the contract
• add regression coverage proving MCP presence does not block Ready to Close

Root cause

The Workstream UI mixed profile configuration with run evidence, so direct Codex Desktop MCP work could appear to have run on the configured Codex app server. Separately, explicit MCP runs did not apply the workspace lifecycle targets, leaving issues in Backlog even after execution began. Connection reachability language also read like active execution even though readiness correctly uses AgentRun state.

Validation

• pnpm prisma:generate
• pnpm lint (passes with existing warnings)
• pnpm typecheck
• pnpm vitest run tests/unit/run-provenance.test.ts (4/4)
• git diff --check

Local Postgres integration tests are blocked because Docker Desktop is not responding. The local production build reached webpack but the workstation C: drive is full (ENOSPC). Clean GitHub CI runners are therefore the authoritative integration, build, and Playwright gates for this PR.

Release

Authorized single-PR patch release: v0.29.3. Merge, tag, production deployment, targeted Axiom-Labs lifecycle-target configuration, and live verification remain distinct recorded steps.