Integrate retired allocation path removal on staging

[adrianwebb]

Outcome

Integrate existing retired allocation-authoring/client-path removal into protected staging. No redesign, new runtime or release.

Work authority

• Work item / Issue: Integrate retired allocation client removal into staging #114; Platform #520.
• Proposal / decision: Existing DO decision unchanged; integration repair only.
• Assignment / checkpoint: September 30 user instruction to integrate all work before automated acceptance.
• Actor: Codex.
• Human authority: @adrianwebb.
• Agent / capacity provider: N/A — local integration, not a generated assignment.
• Exact base ref: staging 9d6fbc5.
• Exact head ref: codex/agent-retire-allocation-authoring bf62a93.

Contributor mode (select one):

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

Plan

Review existing work, verify in the owning package, merge only after required Actions, return checkout to staging and resume one automated acceptance process.

Changes and commits

Preserves existing commits and generated artifacts. Removes the retired capacity-plan/allocation-save path and consumes the canonical living-graph/allocation contract.

Verification

184 tests/37 files and source ownership passed. CI now installs the exact merged UI artifact (staging b0c9a2bdf1eed181950c1202a24ab3d9af012833, Verify run 36729378278) before the normal strict build; no RC, compatibility fields or type bypass. Prior CI passed strict compilation and 183 tests; the sole remaining asset-test module-runner failure is repaired with createRequire, with the existing brand-assets test passing locally. Current required Actions pending. No model/cap changes, manual assignment durations or golden pass claimed.

Risk and rollback

Revert these commits through a checked staging PR and rebuild the existing development selection. No data migration, credentials, production cutover or tags.

Completion summary

Existing work ready for checked integration; golden release/Reporter frontier remains open.

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.