feat(registry): #68 stage 2 — local registry store + mu-setup skill - #76
Merged
Conversation
Part of #68 (implementation stage 2). Makes the case registry usable on the repository-backed local path, with no SaaS account and no database runtime. - project-registry/store.mjs: Git-reviewable local backend — registryPath, readKind (absent = empty, not error), atomic writeKind, idempotent initRegistry (existing kind files kept, not overwritten — UC-C5), and a non-mutating registryStatus. serializeRegistryFile now validates every asset and its kind before writing, so the store never persists garbage. - CLI gains init / status / read-kind / write-kind (repo-resolved paths). - plugin/skills/mu-setup: the discover -> propose -> approve -> init/migrate workflow, reusing project-context for identity/capability/authorization and the project-registry CLI for proposal + store. Idempotent, present-before- write, stores no credentials (UC-C3/C5/C6/C7). - Registered mu-setup as an on-demand skill: build ui map, both runtimes vendored, platform-compat roster, README(+CN) inventory, bootstrap routing and on-demand list, CONTEXT.md example. - 5 store tests (init idempotency, no-overwrite rerun, empty/valid, status, invalid-asset rejection). test:project-registry now covers the directory. Regenerated adapters (13 skills). Deferred to stage 3: a reference provider adapter with fake-provider tests. Relates to #68 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KwyFyRC6pepaK6DuMK7YeT
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.
Part of #68 — implementation stage 2
Makes the case registry usable on the repository-backed local path — fully functional with no SaaS account and no database runtime (UC-C2).
project-registry/store.mjs— Git-reviewable local backend:readKind(absent = empty, not error), atomicwriteKind, idempotentinitRegistry(existing kind files kept, never overwritten — UC-C5), non-mutatingregistryStatus.serializeRegistryFilenow validates each asset + its kind, so the store never persists garbage.init/status/read-kind/write-kind.plugin/skills/mu-setup(new on-demand skill) — the discover → propose → approve → init/migrate workflow, reusing project-context for identity/capability/authorization and the project-registry CLI for the proposal + store. Idempotent, present-before-write, stores no credentials (UC-C3/C5/C6/C7). Registered per the maintenance contract: build ui map, both runtimes vendored, platform-compat roster, README(+CN), bootstrap routing + on-demand list, CONTEXT.md example.Verification
npm run test:project-registry— 8 contract + 5 store tests (init idempotency, no-overwrite rerun, empty/valid, status, invalid-asset rejection)test:skills/test:platforms/test:generated(13 skills) /test:release— passNext: stage 3 (one reference provider adapter with fake-provider tests), stage 4 (skill wiring + UC-ID traceability).
Relates to #68