[adrianwebb]

Outcome

The real portfolio coordinator could not discuss the existing Admin chart proposal through the shared topic: communications.send returned communication_proposal_not_found because the proposal owner differed from the recipient project. Topic streams now retain the proposal's actual owning project, immutable source and version while each contributor keeps its own discussion workspace and source context.

Work authority

• Work item / Issue: Complete accounting transition observations for strict Agent acceptance #553; shared plan Continue coached Atlas team delivery and persistent agent improvements from #428 sdk#429.
• Proposal / decision: Real Admin proposal fbd7342a-dbb1-4ee3-84dd-bf7ffa1c3a1c v1; preceding UI proposal v7 accepted as 7fcf2c92-0c7d-44a9-b1c6-cba49a79ed45.
• Assignment / checkpoint: UI implementation assignment_1WOXUn7Kz1j845WHUKBGA2XK9Z-nsCHC, approved independent review assignment__wLBxQtOWs_do-1XCWCLTZDKgd9F0WCu; next real coordinator/Admin planning question exposed this boundary.
• Actor: Codex integrator repairing a public admission blocker.
• Human authority: @adrianwebb; standing approval for small shared-backend repairs and real group-driven work.
• Agent / capacity provider: portfolio-atlas; provider_-rcKRK8gG2NGnOU3yGu_CV3Wz7ACppTP.
• Exact base ref: dependency PR fix: restore group-driven proposal admission and discussion participation #585 branch codex/group-admission553 at 2a145d52586892e3f3e8ecec02bc056c4a42ae1a; protected staging freshly fetched at 0df73b38026c80a321abd428a7e78f33dddc72bb.
• Exact head ref: codex/group-discussion553 at 0daf6e36c1f17f651638f0e4efa43e67b09fc3ab.

Contributor mode (select one):

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

Plan

This is a small stacked slice on #585. Retarget to staging after #585 merges; do not merge it into the dependency branch. Pass required checks and exercise the same meaningful coordinator/Admin proposal question through the public boundary after the current UI simulation closes.

Changes and commits

• 1a6d69d1, 4f7b07b3, 17982511: reproduce cross-project admission, context compilation and unchanged-send replay denials before repair.
• 29795151: resolve shared proposal context using its owning project/library, retain exact committed context on replay, validate same-team ownership, and freeze contributor source using the existing resolver.
• 6d4e5d3e: include fix: restore group-driven proposal admission and discussion participation #585's native group/Reporter fixture correction.
• Preserve foreign-team and forged-project denials, immutable version/digest checks, changed-request conflicts, recipient workspace boundaries and every negative replay case.
• Extend the existing real PostgreSQL/TreeDX/MCP recovery case to both same-project and cross-project streams. No new runner, state model or execution path.

Verification

• 45 focused cases pass across ready-node, communication operations and replay files.
• Three source-context cases pass; the separate native PostgreSQL case was not run locally because its explicit disposable environment is unavailable.
• Strict build and unchanged file-length/architecture checks pass.
• Native PostgreSQL/TreeDX/MCP coverage is extended and awaits required Actions. The controlled native inputs are not claimed as real agent products.
• Real coordinator/Admin question failed at the old public boundary; successful retry is pending development adoption after UI workday closure.

Risk and rollback

Read context crosses same-team project streams; writes stay in the recipient's own project. Other foreign context kinds remain denied. Existing open-proposal requirement remains. Revert this slice if exact source or team custody cannot be proved; preserve prior sends and products.

Completion summary

Prepared the next small discussion slice while the meaningful UI implementation/review continued. No verification-only assignment was created.

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.

2026-10-21: inherit585's exact scene-binding repair (group selection and relocated workspace case), preserving original failed39467610835. Required checks on new head pending; no component pass or merge claimed.

Protected delivery: this exact slice head0daf6e36c1f17f651638f0e4efa43e67b09fc3ab is retained as an ancestor of cumulative API PR585's protected staging merged0d726be81701eb1b157b348697834b7358e3068. Required Verify39569564428 passed on cumulative head38892d88397e3bd577e30f3097dfa1afc40b1d5b; earlier failed/cancelled runs remain historical failures, not passing receipts. The stack was delivered together to avoid duplicate full campaigns. Fresh protected fetch and Git ancestry checks passed.