Repository navigation
Onboard FS.GG.Net to coordination-kit via the FS.GG.Kit package (FS-GG/.github#1291) - #9
Merged
Merged
Conversation
Net was rostered for `coordination-kit` at creation but wired for none of it (FS-GG/.github#1291): 0 kit skills, no `fsgg-coord`, no engine manifest. Onboard it DIRECTLY onto package delivery (ADR-0062) — skip the byte-copy step entirely — rather than byte-copying the kit in first. * `.config/kit/FS.GG.Kit.receiver.proj` references the versioned FS.GG.Kit package and materializes it to the repo root on demand (non-build-config, like audio/templates). * `FS.GG.Kit 0.1.0` pinned in Directory.Packages.props (CPM; Renovate-managed). * Materialized the full kit for the first time (10 files, `10 written`): the 4 coordination-kit skills in both roots (.claude/skills + .agents/skills), `scripts/fsgg-coord`, and `.config/dotnet-tools.json`. Byte-identical to canonical — `coordination-sync --check` OK — so coordination-coherence goes green. * Consume-side + coherence callers: kit-materialize.yml (re-materialize on a Renovate FS.GG.Kit bump), coordination-coherence.yml (guard the committed kit), lockfile-sync.yml (heal Renovate lockfile drift; restore-target FS.GG.Net.slnx). Supersedes the pending byte-copy sync PR #8. The roster flip to `kit-delivery: package` and the dispatch-App / contract-row follow-ups are tracked on FS-GG/.github#1291. Refs FS-GG/.github#1262, FS-GG/.github#1291. See ADR-0052, ADR-0062. FSGG-Worker: shrike-6417
The first materialize used FS.GG.Kit 0.1.0, which shipped a stale engine manifest (fs.gg.coord.cli 0.6.0) — canonical had advanced to 0.7.0 (#660) without a kit republish, so a from-scratch materialize drifted and coordination-coherence red. Root cause fixed in FS-GG/.github#1292 (republish 0.1.1 + kit-published-coherence gate). Re-pin to 0.1.1 and re-materialize: the engine manifest is now 0.7.0, byte-identical to canonical. Refs FS-GG/.github#1291, FS-GG/.github#1292. FSGG-Worker: shrike-6417
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
1 participant
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.
Onboard FS.GG.Net to the coordination fabric via the versioned
FS.GG.Kitpackage (ADR-0062), resolving the kit half of FS-GG/.github#1291.Why this is an onboarding, not a flip
Net was rostered for
coordination-kitat creation but wired for none of it — 0 kit skills, noscripts/fsgg-coord, no engine manifest. So unlike the other six receivers (a byte-copy→package flip,0 written), this materializes the full kit for the first time and setskit-delivery: packagedirectly, skipping the byte-copy step entirely.What landed
.config/kit/FS.GG.Kit.receiver.proj— referencesFS.GG.Kitand materializes it to the repo root on demand; non-build-config (like audio/templates), so it never touches Net's hand-authoredDirectory.Build.props.FS.GG.Kit 0.1.0inDirectory.Packages.props(CPM, Renovate-managed). Locked-mode restore ofFS.GG.Net.slnxstill passes — the pin is referenced only by the out-of-solution receiver project, so the committed lockfiles are unchanged.10 written) — the 4 coordination-kit skills in both roots (.claude/skills+.agents/skills),scripts/fsgg-coord,.config/dotnet-tools.json. Byte-identical to canonical (coordination-sync --check→ OK), socoordination-coherenceis green.kit-materialize.yml(re-materialize on a RenovateFS.GG.Kitbump),coordination-coherence.yml(guard the committed kit),lockfile-sync.yml(heal Renovate lockfile drift,restore-target: FS.GG.Net.slnx).Supersedes
The pending byte-copy sync #8 — Net goes straight to package delivery, so that PR is obsolete. It'll be closed once this merges.
Follow-ups (tracked on FS-GG/.github#1291)
kit-delivery: packageroster flip in.githubregistry/repos.yml(the Net analogue of #1290) — merges alongside this.contents: write+ org secrets visible) —kit-materialize/lockfile-syncpushes need it; only bites once arenovate/*PR exists.contract-coherencecaller — deferred: no repo wires it per-repo today, and Net has nodependencies.ymlcontract row yet (publish-before-flip / SDD#589).lockfile-syncis wired but Renovate isn't onboarded here yet (Configure Renovate - autoclosed #1) — inert until it is.Refs FS-GG/.github#1262, FS-GG/.github#1291. See ADR-0052, ADR-0062.