Repository navigation
Correct canonical skill routes and qualify their selected SDD adoption #4789
Description
Owner: Programme/root owns acceptance, exact source/effect admission and distribution coordination. Existing /root/knowledge_fable_receiver owns this complete Delivery through review, repair and selected SDD receiver qualification; canonical skill, publication and SDD owners retain their actual domains.
Done when: Correct the current sealed release recipe, legacy product intake/replay exposure, inspect-versus-repair discovery and compatibility/recovery authority in canonical FS-GG skills. Establish explicit FS-GG routing that excludes the hazardous managed merge recipe without editing vendored global files. Protect reviewed source and required generated mirrors/manifests, then deliver the changed distributed skills through an ordinary fresh coherent publication and the existing FS.GG.SDD Kit receiver. Verify actual public package identities, complete materialized bytes/modes and both declared roots, actual existing Codex runtime-discovered instruction paths/content and causal one-line mismatch refusal/restoration. Operator-only skills remain hub-only and require their own hub discovery checks. Preserve all original failures/Unknowns and explicit unselected-consumer exceptions. Source merge/package availability alone is not adoption. Parent4785 keeps its entire Done when; deterministic controller conversion remains exclusively4647.
Current deliverable: Root accepted the complete selected canonical-skill correction and SDD adoption. Canonical PR4793 protected d5af6a9; ordinary coherent0.112.0 publication and run39639020615 completed all16 journal effects and promotion; registry PR4794 protected 5b5f939. SDD PR1117 merged normally as c26d641b57ab1531374f3979b93509527cad9804, exact reviewed tree171b64a47eea2e77526817bdb46cb62129a1be0c, after all six required checks passed at reviewed6c5df488b02bf6adbf9be174d481179877f465f2.
Next action: Reconcile this accepted Delivery to native completed and guarded board Done, then separately audit the whole parent4785 promise before any parent closure. No further selected source, publication, consumer runtime or knowledge capture operation remains.
Blocked on: None for this selected Delivery. Explicit retained scope: Audio/Game/Governance/Net/Rendering/Templates are unselected framework exceptions; Coordination remains a nonparticipant under ADR0078; Claude execution is unselected. The global cross-repo-coordination duplicate remains an explicit precedence exception; runtime enforcement of the hub local implicit-invocation policy is Unknown. Local organization-feed403Unknown remains alongside independently accepted provider evidence. Domain/vendor API currency and other Drivers/product/provider consumers are not blanket-certified. Future controller conversion remains exclusively4647; broader4730/2965 and accepted4701/4712/2852 scopes remain unchanged. Original unrelated runtime/custody holds are not released.
Acceptance evidence: Complete acceptance against the governing plan: canonical obsolete release/legacy intake/read-only inspection/compatibility/recovery/routing corrections and generated closure passed review and controls; both-feed promoted receipts and normalized payload equality accepted. Public Kit0.112.0 SHA256 a669699ead74fc241dc39a1a2a4c37542405b98c12f6c5531ff3660bb3ddf0eb materialized through the existing receiver. All39 managed outputs plus32 generated views were authenticated with bytes/modes/realpaths; protected merge independently matches all39 package hashes and the reviewed full tree/pin. Existing Codex actual skills/list discovery was joined to the exact package and both roots; a one-line mutation at the actual discovered check-board path was refused, then exact restoration passed and rediscovery succeeded. Hub cut-nuget-release actual discovery, maintained redirect and local explicit-invocation policy were inspected. The Fable launcher repair passed independent review,21 focused controls and the required full offline/package acceptance gate. Nonrequired kit-bump-mechanical refusal correctly required reviewed normal merge for the receiver repair; no bypass or rerun was used. Atlas platform/skill-roots and platform/skill-delivery-authority remain accurate; new stable sdd/provisioned-tool-launcher-identity was captured in the same protected SDD PR. Root full acceptance receipt SHA256 2ef30c75c2d18ba7dd26b1adf27aa0c1442c5df8fc952a44def33acc6712c9c8. Original failed gates, early metadata propagation, collector/assertion failures, missing short-child birth samples and scoped diagnostic gaps remain retained; later accepted evidence does not relabel those originals or authorize replay.
Activity
EHotwagner commentedon Oct 21, 2026
Programme/root selects prospective SOURCE 0.112.0, predecessor 0.111.0, and the fresh proposed journal identity
coord112-skill-routing-20261021-01: logical refrefs/heads/fsgg/v2/journal/release/coord112-skill-routing-20261021-01and protected-main directorystate/releases/coord112-skill-routing-20261021-01.The genuine promoted predecessor is coherent111, source
bd60a97a422c8fc8ca0c17b2a9dea4e504b708d2, contentsha256:ea0b66a325ef425510a362e189469c5c6e6936880f455898e78520076737298b. Its accepted generation33/all16 effects, original failed/continued attempts, archives and journals remain immutable. This decision authorizes reversible source composition only: no namespace allocation, candidate, publisher, protected-main hold or installation. Final candidate source/run/artifact/archive are not yet known.Additional source scope for the same #4789 owner
/root/knowledge_fable_receiver:Directory.Build.propsscalar and matching CLI release notes; the sixCURRENT_RELEASEfields inscripts/release_successor_journal.py.coherent-0112-absence, including only that selector’s literals inscripts/telemetry-host-published-org-read.pyandtests/telemetry-host-published-org-read/run.py. The accepted Host0.8 branch, immutable pins and behavior remain unchanged.Use pipeline-preflight, the selected pure candidate/recovery/selector and skill controls, independent exact-source review and normal required CI. The full Delivery still includes genuine coherent publication and selected SDD materialization/discovery acceptance; source merge alone does not complete it.
Preparation-time public indexes showed111 latest/112 absent and proposed tags/release/journal paths absent. All three local org-feed index reads returned403: org occupancy remains Unknown. These observations are not future availability guarantees. The existing authenticated candidate feed gate must freshly resolve all coordinates and predecessor before tests/build/pack; preserve actual refusals without automatic retry. No new provider, token or credential grant is selected.
EHotwagner commentedon Oct 21, 2026
Root selects prospective source custody for the already approved #4789 correction scope, following the user’s instruction to add #4785 to the active workload.
The earlier overlapping source domains are: enrollment43’s six registry paths; #4723’s driver manifest; #4731’s CLI project release notes; and #4733’s two canonical
pnext-item/SKILL.mdfiles. Root assigns only these future source-path claims to the existing #4789 owner in its new isolated branch/worktree. This is a new root decision, not an inferred confirmation from absent former owners. The earlier four-path feedback handoff is not widened.The original worktrees/branches and private outputs remain preserved and must not be reused or changed. Current protected preimages are verified at the #4792 carrier tree; they must be refreshed beside implementation. Stop and reconcile any drift or actual competing writer. Root serializes shared generated outputs. Subsequent delivery still requires independent source review, exact-head required CI and the normal protected merge route.
Retain every historical reservation row and receipt, all unlisted paths, runtime effects and Unknowns, including the 439 inherited and 46 later reservations. A source merge or clean worktree does not establish runtime retirement. The three UTEL source-path returns are separately supported by the original custodian and original retirement evidence.
The full #4789 promise remains canonical corrections, fresh coherent publication and selected SDD/Codex adoption. This disposition resolves these source-domain overlaps only; actual implementation still awaits the qualified installed selection and its bounded source admission. No publication, installation or old runtime retry is selected.
EHotwagner commentedon Oct 21, 2026
Root source-scope decision: include the one-line
docs/architecture.mdprojection produced by the maintainedprepare-registrycommand for SOURCE 0.112.0 / published package 0.111.0 in the current #4789 source operation. The original UTEL source custodian verified both retained worktrees clean, exact tracked/working bytes, and no continuing source writer or pending push, and returned only this completed-source path. Root accepts that return fromutel4707-hostand returns the same path from its completedroot-observe-utel4707-final-deliverysource reservation. Every other path, runtime/effect reservation and historical Unknown remains unchanged. This is a necessary generated consequence of the approved version composition; unrelated architecture prose is unchanged. The same owner, isolated worktree and original source window continue. This selects no publication, installed update, new operation clock or whole-row release.EHotwagner commentedon Oct 21, 2026
Root selects the narrow registry repair exposed by PR #4793 feed-coherence run 39616085390: FS.GG.Telemetry.Host is already published at 0.8.0 on both feeds, while its registry package-version/tag still report 0.7.0. Root independently accepted the original 0.8.0 publication on 2026-10-21 at 11:31 UTC (original publisher 39580298871; independent org-feed read 39591087147); this is not a republish. The same #4789 owner may reconcile only that published package-version/tag, the existing registry changelog and maintained generated projections/manifests in the same PR. Preserve Host implementation, immutable package/source/runtime pins, the independent Host workflow branch, all original failures and every remaining #4707/#4640 installed-consumer requirement. Run relevant existing pure coherence checks, obtain the same reviewer’s exact repair review, and let normal new-head CI validate it. No package, installed service, journal, runtime or credential effect is selected.
EHotwagner commentedon Oct 21, 2026
Root selects the two-file source closure repair exposed by PR #4793 required CI run 39617936255:
scripts/creator_source_qualification.pyandtests/new-sdd-workspace-successor/run.py. The existing Creator 0.21 normal project-reference route packages current CLI 0.112, but its qualification constants still expect 0.111. Update only that current-source binding and its meaningful stale-0.111 rejection control. Preserve historical Creator 0.20/CLI 0.110, frozen 0.108 and published-consumer routes; no project-reference, provider or workflow variant is added. Root checked the 17 current source reservations and found neither path claimed. The same #4789 owner, isolated branch and remaining original operation budget continue. Obtain the same reviewer’s repair review, run relevant existing pure closure controls, and let normal new-head CI supply compiled qualification. This grants no local CLR, publication or consumer effect.Narrow amendment: the caller sweep also found the current-source PackageReleaseNotes sentence in
scripts/NewSddWorkspace/NewSddWorkspace.fsprojstill says coherent 0.111. Root includes only that prose literal correction to 0.112. Its project reference, version, dependencies and historical/published routes remain unchanged. The third path has no current source-reservation overlap; the same owner and original remaining budget apply.EHotwagner commentedon Oct 21, 2026
Root accepts the source milestone for #4789 / parent #4785: PR #4793 merged at 15:35:48 UTC to
d5af6a987e915bd0a1b572bcc09ad0d4b2e798b5. Independent native PR, commit, main and CI reads verify tree84ad8499022c4608760a83eaf5b810155d751580, exactly matching reviewed head681a659fbd13a98064f0e47068c0419ef43408e5, with 97 passing and 4 skipped checks. Full Delivery and parent remain open / In progress; publication and installed adoption are not accepted by this source milestone.Root selects the existing ordinary coherent 0.112.0 candidate route, with promoted 0.111.0 predecessor/source
bd60a97a422c8fc8ca0c17b2a9dea4e504b708d2and prospective journalcoord112-skill-routing-20261021-01. Same knowledge_fable_receiver owner carries the entire Delivery. Before the one candidate dispatch, bind the reviewed private composition to this actual source, fresh native authority/namespace/run census, the exact existing operator and a fresh 3300-second original (one CPU, 512 MiB local sampled memory, 512 MiB evidence; 120-second final reserve). Candidate workflow keeps its existing 45-minute hosted limit. Source selection does not allocate a journal or authorize a replay, publisher, install or consumer operation. Any uncertain send is reconciled as its original, never resent.Root reserves only
.github/mainat this exact source from 15:38:46 UTC until 18:58:46 UTC on 2026-10-21, a finite 200-minute horizon: 55 minutes candidate, 65 minutes separately admitted preflight, 65 minutes separately admitted first publication, and 15 minutes combined review allowance. This is a cooperative source-ref reservation, not server CAS or permission for all later effects. Root must disposition any drift or unfinished operation at expiry; no automatic extension, retry or hold release follows. Other repositories and disjoint PROC/LEARN/UTEL work remain available.Next: authenticate the genuine successful original candidate and its original archive bytes; only then separately admit ordinary
publish=false, followed by separately admittedpublish=trueif eligible. Accept all 16 durable effects and both feeds before the existing SDD Kit receiver and actual Codex/hub discovery/mismatch/restoration work. Operator-only withholding, unselected consumers, Coordination nonparticipation, source/installed distinctions and every original failure/Unknown remain unchanged. Root retains acceptance authority.EHotwagner commentedon Oct 21, 2026
Root accepted coherent112 publication from ordinary forward39639020615/a1 after independent final readback: all16 effects at generation33, promoted release419781177, seven release assets and normalized both-feed package payloads. Original publisher39633207670 remains the retained generation14 checkpoint. Publication source is d5af6a9; https://github.com/FS-GG/.github/actions/runs/39639020615 and https://github.com/FS-GG/.github/releases/tag/coherent-set/v0.112.0 . Root released its cooperative hub source hold. This accepts publication only; selected SDD materialization, actual Codex/hub discovery and full4789/4785 acceptance remain open.