Repository navigation
Support authenticated legacy owner PR continuations - #5270
Conversation
# Conflicts: # .agents/skills/atlas/assets/seed/catalog.json # .claude/skills/atlas/assets/seed/catalog.json # docs/atlas/catalog.json # registry/driver-skill-manifest.json
|
Root selects one fresh ordinary same-journal forward invocation for coherent0.117.0, following original publisher41782925473/a1 and original forward41783682191/a1. The latter ended at a bounded checkpoint (failure=null), generation14: all three GitHub Packages and public Coord.Cli verified, public Kit intent pending; no further package sends are inferred. Independent maintained journal read validates generation14, logical34ac29fc810edf6107c2944bae5bd2927db41420, physical38b4a9ebe75d2c267c6b7194a805d6b32ac756d1, stateSHA256df2b00a5f3b2aeeab40537d00cc9d0210c3ec8b1aec832db402067a61cce4aee. Fresh public Kit0.117.0 is now listed and its served archive b708ba897ae9c77fbe588c6102b2ae5ce4d460cddad9f657b0781e91d0a2c096 matches every original producer entry; only the service signature differs. The read-only observer ended after one index read. Original failures, bounds, intents and archives remain immutable. Admission: ONE new workflow_dispatch of release-successor-publish.yml, publish=true, on held main9c0a1551d29d6d733b997ab9f33d8ea4852a45f1, with SAME candidate41778982096, artifact13298970087, raw archiveSHA2569698196056fb057aa4e1ed30d596e57f6e29439fb8933874c56630756018bd11 and contentsha256:632cf870362d21a9706c265cf4a32fae4a90a5541a2f168a66954294e3bee7da. All historical/install/recovery flags remain false. Reuse the original coherent-set-v0.117.0 journal. First independently observe and settle the original Kit intent; no duplicate Kit/tag/draft or verified-package send is authorized. Remaining not-yet-attempted effects may proceed only through unchanged fresh source, native, environment, org-writer, candidate, journal and provider guards. Unknown/mismatch stops; no rerun, candidate replacement, repack, journal reset or original-clock renewal. This separate forward invocation retains the existing90-minute job plus10-minute queue and2-minute readback bound (6120seconds). The previous operation remains a checkpoint, not retroactively complete. All16 verified effects, both-feed readback and exact promoted seven assets remain required. Registry/pin integration and main feed green are required afterward; installation, enrollment, archive and Game effects remain separate. This admission is recorded on the accepted source PR while the owning metadata intake keeps its issue/comment/field quiet window. It changes no Project field or selected intake issue. |
Continue an already-owned legacy PR through one authenticated body/title update while preserving its source, ownership and complete native roster. The maintained route binds a Root-authored operation declaration, previous/current source ancestry, exact deciding preimages, possible-send custody and independent readback. Existing reservation and new-PR limits remain enforced.
Refs #5269
Drivers ships the lazy legacy helper with the canonical Root rules and their shared identity-policy data. Inspection, intent and custody identify the selected rule and policy hashes; receiver-local shadows and determining drift are refused. The existing draft-creation flag and native readback behavior remain intact.
Plan and body inputs use one bounded opened-file reader: no-follow/nonblocking open, regular-file and byte limits, UTF-8 decoding and opened-file stability checks. The original no-writer FIFO hang and missing packaged-policy failure remain retained. Empty-file and universal-newline behavior is preserved; closed plan and owning-reference checks continue to govern accepted inputs.
Prepare coherent source version 0.117.0 for the additive legacy operation and accepted archive guidance. The four reviewed retention references, Kit manifest and standing advisories remain exact. Actual protected archive merge 3363aae is an ancestor; the complete candidate tree is byte/mode-identical to Root-reviewed 0cccdda. Published registry/default pins stay at their observed accepted values pending normal coherent publication and readback.
Validation: 77 admission/package controls pass; removing the policy recheck, legacy/draft exclusivity or FIFO nonblocking guard causes the intended control failure, with restored controls passing. Existing pure normal-consumer/source-axis controls pass 7 tests and release-source closure passes 26. Atlas passes 18 controls with all 546 protected baseline records retained (551 total); generation, manifests, census, coherent-version/release-note, Wizard surface and whitespace checks pass. Fixtures use isolated temporary plans/bodies and inert provider responses; package/version checks use declared source metadata and observed public feed/tag state. Original failures, semantic timeout history and unavailable historical Atlas objects remain explicit.
The complete Delivery continues through exact-head required CI/protected merge, coherent publication and materialized adoption, then one separately Root-bound real Game PR continuation with complete native before/after evidence. Source preparation and fixture success establish those scoped checks only.
Prepared with OpenAI Codex assistance.