[ronak-guliani]

Summary

Stack PR #444 on the finalized acceptance foundation in PR #443 without merging either PR.

• Reuse PR Add collaborative acceptance domain and persistence foundation #441's canonical CollaborativeAcceptanceCaseId, CollaborativeAcceptanceCandidateId, CollaborativeAcceptanceExchangeId, and CollaborativeAcceptanceRequestTransportContext; collaboration transport no longer owns a duplicate exchange lifecycle or budget state machine.
• Keep request identity, typed immutable case/candidate/finding-revision/exchange references, monitor provenance, authority bindings, producing execution generation, payload references, supersession, response correlation, and terminal outcomes durable in orchestration projections.
• Renumber the collaboration projection migration to 098, preserve canonical migrations 096 and 097, repair skipped projection prerequisites before ALTER TABLE, and add divergent-ledger coverage.
• Harden response, cancellation, supersession, response deletion/reopen, override, and consumption authorization with bound sender/recipient execution authorities and cross-thread rejection tests.
• Use notification-delivered plus a terminal outcome for nonblocking requests; schema invariants reject impossible response-ready states.
• Preserve the existing queued-turn reactor, task-scoped waits, user-authored priority, active-turn non-interruption, generation-fenced response consumption, direct-cycle escalation, and exactly-once queue/projection behavior.

Canonical stack and persistence proof

• PR Add collaborative acceptance domain and persistence foundation #441: feat/collaborative-acceptance-core, head 447088867abaa595eebf6ec329fa2fb4dac8b500, migration 096 (CollaborativeAcceptance).
• PR feat: add PR monitor acceptance review ledger primitives #443: feat/pr-acceptance-evidence, head 32e7d2d3da33e150af328efccf477c5415567378, migration 097 (PullRequestMonitorReviewDisputes).
• This PR: migration 098 (ProjectionThreadCollaborationRequests) with guarded ProjectionCore/RepairProjectionCore prerequisites and divergent-ledger/idempotency tests.

Validation

• pnpm fmt:check — passed.
• pnpm lint — passed with existing repository warnings only.
• pnpm typecheck — passed.
• pnpm test — passed: 291 test files passed, 2 skipped; 2,505 tests passed, 9 skipped; server serial suite 102/102 passed.
• Focused protocol/migration tests — passed: 7/7.
• Head: 9a06eb7209d88d29a87a9884121f7eec384b87ec.
• CI was queued/in progress at update time; follow-up CI results are authoritative.

Browser scenarios remain pending parent-owned integrated validation: busy-parent queued delivery, generation-fenced response continuation, retry/supersession/reopen recovery, and direct circular-wait handling. No browser/dev-server validation is claimed here.

Follow-on integration assumptions

• Coordinator/provider work must create or reference the canonical acceptance exchange before issuing a collaboration request and pass immutable monitor provenance from the PR-monitor adapter; request transport must not infer identity from mutable thread/PR state.
• Acceptance owns exchange budget/status transitions; request orchestration owns only correlated delivery, task-scoped waits, and generation-fenced consumption.
• Later automation/UI work should use the existing orchestration dispatch and QueuedTurnReactor, preserve user priority, and treat needs-human as an explicit escalation rather than a retryable wait.

[ronak-guliani]

Superseded by the single aggregate PR #447, which contains this PR's changes plus the complete collaborative-acceptance stack and is based directly on main.