Skip to content

Retain superseded candidate histories without source rollback - #630

Merged
adrianwebb merged 2 commits into
stagingfrom
codex/cleanup-retired-candidate-lineage-626
Oct 5, 2026
Merged

adrianwebb merged 2 commits into
stagingfrom
codex/cleanup-retired-candidate-lineage-626

Conversation

@adrianwebb

Copy link
Copy Markdown
Contributor

Outcome

Retain obsolete candidate commits as protected ancestors without restoring superseded source or declaring failed observations successful.

Work authority

Plan

Fresh required Actions; merge commit to staging; update existing staging-to-main promotion; delete only exact protected ancestor refs after readback.

Changes and commits

Obsolete composition-only generation155/Agentrc39/Deploymentrc194 is superseded by current protected integration generation266/Deploymentrc320. Preserve the original commit as an inactive historical parent; do not roll back current exact integration locks. All original commits are parents of this history-only candidate. Exact unchanged staging tree ee5390e975153a5bed51bf99caa7d60b36686290. No source/test/manifest/config/dependency edits, tags/releases or rewritten commits.

Verification

Every selected original head is an ancestor of this candidate; exact tree equals the freshly fetched protected staging tree. Fresh PR verification pending. No golden/capacity acceptance claim, no invented successful historical output.

Risk and rollback

Keep original refs until protected ancestry and required checks are verified. Relevant unmerged and dirty work remains excluded. Do not roll back current locks, source or package versions. Any needed reversal follows another checked staging PR, not reset/rebase.

Completion summary

Candidate pushed with independent exact remote readback; protected merge and main promotion pending.

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.

@adrianwebb
adrianwebb merged commit e4c4cad into staging Oct 5, 2026
1 check passed
@adrianwebb
adrianwebb deleted the codex/cleanup-retired-candidate-lineage-626 branch October 5, 2026 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant