Complete native operator recovery capture and publication #782
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
toasterson/Anima!782
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/plan14-recovery-publication-20261006"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Native operator recovery could prepare a runnable checkout but could not complete the ordinary durable handoff. Snapshot verification rejected the recovery descriptor and twelve bootstrap receipts; publication targeted the preserved old branch; PR migration refused the resulting source branch.
Validate the exact assigned recovery checkout and twelve unique nonempty receipts, preserving the strict seven-receipt ordinary contract. Under existing work-item/owner locks, bind the destination to the single consumed operator intent and exact recorded source head/branch. Publish to a deterministic sibling branch
<WI>-recovery-<intent>and a per-intent PR marker in the configured namespace. A sibling can coexist with the original branch in both loose and packed Git refs. Preserve the old branch, PR and Change history; recheck authority before remote effects and canonical ingestion. Ordinary continuation keeps its owned branch and marker. Native Git ancestry, leases and unknown-outcome guards remain unchanged.Validation: the real bare-remote Git push regression fails with the old child-ref name and passes with sibling refs, verifying both loose and packed original refs are unchanged. All four disposable-PostgreSQL production-path fixtures pass: clean port, conflict recovery, ordinary continuation and completed follow-up. They cover malformed receipts, authority/source/strategy races, duplicate requests, uncertain sends, audit rollback and preserved PR history. HTTP peers are fault-injecting transaction fixtures. Server library tests: 524 passed, two existing isolated-RabbitMQ tests ignored. Strict server library/integration Clippy and diff checks pass. Previously recorded native snapshot client tests and CI fixture enrollment remain intact.
Plan14 WI-914: 01a11227-2d1c-72f1-8ac8-00a0eb4695a3, based on merged WI845/PR781. Requires fresh native exact-head reviews/CI, deployed native-bootstrap companion WI531, and real witnessed snapshot/Git/PR acceptance. No gate override or budget reset.