Promote consolidated staging history to main (no tags)

[adrianwebb]

Outcome

Promote verified current staging into main by merge commit, preserving the integrated original commit histories. No tags or releases.

Work authority

• Work item / Issue: Consolidate feature branches into staging and main; clean preserved refs #118; central Consolidate project branches into staging and main; preserve work and verification gates platform#626

• Proposal / decision: N/A — human-requested branch cleanup.

• Assignment / checkpoint: Exact-ref inventories and staging receipts in the owning Issue.

• Actor: Codex in the owner's Platform workspace.

• Human authority: @adrianwebb; all relevant work through staging then main; preserve lineage; do not cut tags.

• Agent / capacity provider: Codex; no managed execution/SDK campaign here.

• Exact base ref: main 80cc038

• Exact head ref: staging 3367eb9

• Agent-assisted under human authority

Plan

Run the existing required PR Actions on exact staging; ordinary merge commit into main; independently read back the protected heads and ancestry; delete only exact redundant feature refs.

Changes and commits

Promotes existing protected staging history. The previous main head is its ancestor. No direct-main feature merge, squashing, rebasing, source rollback, Git tag or release dispatch. Truly unmerged/dirty/failing test work remains excluded and explicitly open in the owning Issue.

Verification

Fresh protected heads fetched and exact main-ancestor-of-staging verified natively. Relevant staging PR Actions passed as recorded in the Issue. Fresh current promotion PR checks still required; this promotion is not a full capacity/Agent/SDK golden acceptance receipt.

Risk and rollback

Normal branch merge does not change the selected runtime or cut a release. Preserve current branch protections and unrelated policies. If needed, revert a specific source change through a separately checked staging PR; never rewrite main or delete unpreserved commits.

Completion summary

Main promotion pending current required verification and independent merge readback.

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.