[adrianwebb]

Outcome

Coordinators can discuss exact draft and retained proposals through the same communications.send operation, including after approval. The real diagnostic question for accepted API proposal 12b52c0e was refused with communication_proposal_not_open, preventing recovery discussion with its Engineer.

Work authority

• Work item / Issue: Complete accounting transition observations for strict Agent acceptance #553 and Continue coached Atlas team delivery and persistent agent improvements from #428 sdk#429
• Proposal / decision: API 12b52c0e-05a8-48b6-91cd-c4898bd534aa v3, accepted Decision e6a4446b-2600-4764-99a4-c6b31e18e5a7.
• Assignment / checkpoint: Actual failed Engineer assignment_O7zvmOew_IG-K46ukcKTCZQ8ks9OafpJ; diagnostic send refused before invocation. Implementation failed due to uncommitted source/test changes and is not represented as a product.
• Actor: Codex coordinator
• Human authority: adrian; explicit instruction to repair native MCP workflow gaps through existing Issues.
• Agent / capacity provider: Coordinator boundary repair; original guest failure retained.
• Exact base ref: staging 41e51cd; supersedes Allow native coordinator MCP protocol clients #591–594; their bounded source changes and evidence are retained in this single complete MCP candidate.
• Exact head ref: b637ca2

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Consolidate the overlapping native-MCP repair heads into this exact candidate so the required complete verification and 996-step component scene run once for the current source. Prior PRs remain closed historical records; no test, assertion, gate or failed observation is removed.

Treat a proposal attachment as exact read-only context across its lifecycle. Retain team authorization, source verification and replay freezing; messages still admit only configured communication work, never acting authority.

Changes and commits

8747a50 removes only the transport-state gate. Exact proposal source and owning project/team still checked. Native recovery fixture now begins with draft context before the existing open transition; mutation/replay assertions remain.

Verification

Current final candidate b637ca2 adopts checked SDK440 merge f6073f78db38510297bed47700f1dcb2d37e843f in package, lock and exact Actions build input. It exposes governance.proposals.update through the same backend operation (77 tools/35 resources), allowing coordinators to revise structured work items and clear estimates deliberately after real scope changes. No new operation, runner, store or raw host/TreeDX surface.

On this SDK consumer candidate: nine focused MCP tests/three files passed (schema dialect, authorization/version/idempotency equivalence, stateless confirmation), strict build and length/architecture policies passed. Local npm9 install/ls rejected the Git comparator; existing hydrate-exact-dependency.ts succeeded with npm11.19.1, matching Node24 CI tooling. Local archive SHA256 e3d55bfef5db8a8a419da49dc91e22cb6247d3dde85e5583bd7fe5945ec16159 is a local exact-source pack, not a sealed release. Required Actions on the new candidate pending. Earlier b6 run39788732504 passed complete verify:direct and native PostgreSQL steps but remained in coded component scenes; it cannot count for the changed dependency candidate.

Real MCP observation on b6: native Inbox published Deployment proposal3385d505 v3 private simulation source ee2e9fc66b8e6ff9f745a8f0d20507820a7220d2 into v4 authoring60b0644f07d2d5d200d84f9518ced04a3709c941. Native execution.graph.show read back the retained work item and both genuine estimates under v4 authority; a fresh group workday18e8cece admitted four planning contributions. Structured estimate clearing still needs the newly exposed update tool; no fresh formal estimates, approval, review or release claimed for the changed scope.
Real accepted-proposal call reproduced rejection. Focused regression reproduced five rejected retained states before the repair. Four files / 35 focused checks pass, including unknown/foreign/missing-owner and exact-source failure denial. Strict build/declarations and file policies pass. Native PostgreSQL/TreeDX integration case strengthened but not run locally because explicit prerequisites are unavailable; required Actions pending. Local candidate8747a506 adopted through supported dev rebuild (provider left manual). The original unchanged native request recovered as send-52939adce05910b07905e9648625c8c2: API Engineer responded about the accepted proposal. Cross-project Agent Architect send-589fdaa605eef3a04cbb703c601d79e2 also responded using the same accepted API proposal context. Both are real diagnostic discussions, not implementation credit. A transient TreeDX network error during rebuild was retained; unchanged retry after readiness succeeded.

• I ran the narrowest relevant package verification and documented any checks that could not be run.

Risk and rollback

Authorized historical proposal context becomes discussable without changing its governance state or execution permissions. Revert 8747a50 to restore the old restriction; preserve messages, estimates, decisions and failed evidence.

Completion summary

Small real interaction repair so the coordinator can ask about approved implementation and failures. Original implementation/review/simulated release proof remains incomplete.

AGPL committer authorization

Existing trusted provider-authenticated approved-author workflow applies; no policy changes.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.

Real Inbox revision repair (b6b5038)

Native MCP publish_revision on actual Agent496 proposal e219d853 v3→v4 dropped its executionPlan. Group planning then had no estimating nodes. Partial revisions now retain plan, groups, objective/evidence links and discussion from the exact active source; reuse the existing exact reader for private simulation estimates. Explicit replacements/clears still apply. No new mutation path/store.

Regression reproduced (23 existing checks passed/one new failed); repaired candidate passes44focused checks/3files, strict build and file policies. Existing native TreeDX/PostgreSQL authoring case strengthened; local disposable prerequisites unavailable, not a claimed pass. Required Actions must pass on b6b5038; old-head evidence does not transfer. Native stop/Reporter ended affected dd8522dc workday, retained evidence preserved.