Repository navigation
chore: reconcile published coherent 0.114.4 - #5260
Merged
Merged
Conversation
EHotwagner
marked this pull request as ready for review
November 2, 2026 19:19
This was referenced Nov 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reconcile the registry and canonical CLI pin with accepted coherent 0.114.4, published from immutable source
c914942cd0094179e07f12f0a2971f7daf059ff4. The owning registry history records release 431788123, original candidate/archive/content ID, final manifest/channel hashes and both-feed acceptance. Ordinary forward 41504251592 completed all 16 effects at journal generation 33; all seven assets authenticate and all three public payloads match the original candidate. Prior failures and the visibility checkpoint remain retained.This ten-file reconciliation advances only the three coord-engine registry fields and source-distributed CLI pin to 0.114.4, with generated documentation, skill inventory and census hashes. All 56 lockfiles and every other tracked blob remain unchanged. It does not rebuild or replace the published archives or tag.
Validation:
prepare-registry --checkreports all projections/manifests current; registry changelog protocol and coherent version checks pass;git diff --checkpasses. Structural census prints:v1-writer-census: PASS (structural; 54 command roots: 20 always, 6 conditional, 28 never; 9 out-of-catalogue arms; 75 source identities; 345 tracked executables). Independent source review approved exact head7d709fe1e438fdcd9306168c59b8c323fa180b37. No product tests were rerun for this metadata-only delta; actual PR gates remain required.Architecture map: the maintained version row is regenerated; repository boundaries and contract shape are unchanged.
architecture-map: unaffected
Delivery 5253 continues after this merge: merged-main feed verification, exact supplier/receiver-owner recording for SDD, Governance, Rendering and Game, and their separately owned source/qualification acceptance remain. Governance must pair FCS 43.12.403 with Core 10.1.403. Installed reconciler adoption, recovery and native reconciliation retain separate acceptance; this PR does not establish fleet adoption.
Refs #5253