Repository navigation
Prepare CLI 0.101 receiver and reconcile published Workspace 0.18.2 - #4366
Merged
Merged
Conversation
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.
Prepare coherent CLI/Kit/Drivers source0.101.0 for exact CI attribution and the additive immutable causal receiver, and reconcile independently published Workspace.Template0.18.2 inventory. Coord published package/tag0.100.0, predecessor source3ed8 and immutable journal18 remain unchanged; logical19 is source-only preparation.
The existing candidate gate requires the actual packed receiver to accept four synthetic declaration cases through generic receipts, reopen and replay them with the same canonical revision, terminally reject a fresh immutable-conflict receipt, and refuse unknown kinds before receipt creation. Original performance sampling and the seven-member candidate archive are unchanged. Packed qualification, publication and installed adoption remain pending.
Workspace0.18.2 binds protected20c009bc and original release38014935496/a1. Both feeds match480 signature-excluded payload entries; original/GitHub/release archive789254f5 and signed public496aad are distinct authenticated identities. Independent public direct A and bounded retained B preservation/apply/remove/recovery are accepted. One installed public SDD2.1 Portal provider C is accepted. B ordinary Server.Tests passed20/20 with original-file preservation. Global defaults, full Wizard adoption and whole P3/axis coherence remain pending. Historical0.18.1 source/public hashes are preserved. The Coord whole raw contract row and UTEL release/probe payload files are unchanged by this inventory join.
Generated compatibility, architecture, both mirrored publishing inventories and both component inventories now reflect their source registries. Exact source-owned manifest emission and catalog reconciliation propagate only the publishing skill row digest; Kit manifest is unchanged. A static sweep covers all20 renderers and39 generated regions across23 subjects with zero remaining delta. Prior6d fullcheck passed generated-current and16 disposable marker controls; its result does not qualify this new head. Local full source qualification passed at24ea6dd: generated-current and both manifests, all16 marker controls, the skill-registry fixture through77 plus catalog/trigger controls, pure projection40/40, and24 coherence ids/29 contract literals. Terminal exit0 and empty owned group; sampled peak102,502,400B. The inventory update after that fullcheck changed only five human prose clauses in three files to record B20/20 (receipt52d18d42). All39 generated regions, production executable producers and parsed contracts/repos remain unchanged; raw registry/compatibility bytes change. Fresh native final-head checks remain required. Facts-only projection checks do not qualify the packed receiver. The final six-line feed fixture correction updates current Workspace expectations to0.18.2 and retains its stale-comparator non-vacuity control. Offline feed fixture passed45/45 plus41 reader cases at exactfde15037, exit0/empty owned group (sampled48,910,336B); no live feed or CLR execution. The subsequent merge from protected2fe16e49 changes only the owning root v3 projection (3 inserted/3 removed lines); the22-path source patch is byte-identical to qualifiedfde and guards are unchanged. The originalfde eligibility event had the correct marker/head but stale base3d versus fetchededb; normal synchronize is supported and fresh native event acceptance remains required. Original native failures and the interrupted offline supervisor race remain retained.
No publisher activation, candidate, package acquisition, release, install or operational Store effect is included. Later release gates must freshly bind protected source, all six feed coordinates, predecessor channel and complete unused Authority path/protection facts.