fix(skill-builder): scaffold regenerates registry.json — the 5th one-shot-green surface (ag-ekyq #scaffold-registry-regen)#614
Merged
Conversation
…shot-green surface (ag-ekyq)
init.sh's new-skill plumbing wired 4 of the 5 derived surfaces (dispositions,
narrative counts, codex override-catalog) but NOT the registry.json SKU catalog.
A stale registry.json trips contracts-sync ("registry.json is stale") AND
correctness(ubuntu) ("SKU_CATALOG: DRIFT") together — it cost /burndown #600 a
2nd fix-and-repush (22a0af2) and was a manual step for /eval-outcomes (#613).
Adds generate-registry.sh as plumbing step 4, positioned LAST (it scans the
whole skills/ tree, so the skeleton + other 3 surfaces must exist first),
guarded with a WARN fallback like its siblings. A new skill is now one-shot-green
across all 5 surfaces with zero manual regen.
Closes-scenario: ag-ekyq#scaffold-registry-regen
Bounded-context: BC4-Factory
Evidence: tests/scripts/scaffold-registry-regen.bats (4/4 green; wiring + ordering contract)
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.
What
skill-builder's
init.shnew-skill plumbing (ag-cw2y) wired 4 of 5 derived surfaces — dispositions, narrative counts, codex override-catalog — but not theregistry.jsonSKU catalog. A staleregistry.jsontripscontracts-sync("registry.json is stale") ANDcorrectness(ubuntu)("SKU_CATALOG: DRIFT") together.This was the most-missed surface this session: it cost
/burndown#600 a 2nd fix-and-repush (22a0af2f) and was a manualgenerate-registry.shstep for/eval-outcomes(#613).How
Adds
generate-registry.shas plumbing step 4 ininit.sh, positioned last (it scans the wholeskills/tree, so the skeleton + the other 3 surfaces must exist on disk first), guarded with aWARNfallback like its siblings. A new skill is now one-shot-green across all 5 surfaces with zero manual regen.TDD
tests/scripts/scaffold-registry-regen.bats(4/4 green) locks the wiring + ordering contract: init.sh invokes the canonical generator, guarded, after the override-catalog step and before the final skeleton echo.generate-registry.shis not repo-root-injectable (it reads hooks/types.go/schedule across the tree), so the contract is the wiring+ordering; the end-to-end behavior was empirically validated this session runninggenerate-registry.shon the freshly-scaffolded/eval-outcomes(#613, registry included the new skill).Scope
Reverted the 7 pre-existing-main codex
.agentops-generated.jsondrifts thatregen-codex-hashesswept in; surgically rebuilt the manifest to skill-builder's hash delta only (changing init.sh refreshes skill-builder's codex twin hash — a real consequence of this diff).Closes-scenario: ag-ekyq#scaffold-registry-regen
Bounded-context: BC4-Factory
Evidence: tests/scripts/scaffold-registry-regen.bats