fix: preserve conversation project scope in allocation admission

[adrianwebb]

Outcome

Preserve standalone chat admission through canonical allocation project scope.

Work authority

• Work item / Issue: Implement the minimal AgentKernel, profile, and workday architecture platform#520
• Proposal / decision: N/A — operator-requested allocation acceptance repair, not a golden deliverable.
• Assignment / checkpoint: Fresh SDK refreeze preflight; API Count shared graph work in allocation readiness and retain source transport diagnostics #378
• Actor: Codex
• Human authority: @adrianwebb
• Agent / capacity provider: operator Codex task; dev2 managed acceptance
• Exact base ref: staging 48553fe
• Exact head ref: bc73878

Contributor mode (select one):

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

Plan

Repair the observed acceptance failure through the existing runtime path. Local verification complete; merge after required Actions, then verify managed local recovery. No tags or releases.

Changes and commits

bc73878: Standalone conversation run creation records its selected project IDs; tests enforce the canonical field.

Verification

11 focused tests pass; file length and architecture checks pass. Strict build passes.

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

Risk and rollback

No database, credential or contract migration. Revert bc73878 through a PR and rebuild the same managed live target. No purge or bootstrap reinstall.

Completion summary

Bounded repair verified locally. Integrated golden lifecycles remain unproven and are not claimed as complete by this PR.

AGPL committer authorization

Base-owned workflow retains provider-authenticated author authorization.

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.