fix(skills): sync the distributed adoption skill and pin it to the repo copy

`init` writes .claude/skills/*/SKILL.md into every new repository from the
constants in skills_content, so each skill exists twice: once as the copy
this repository uses, once as the copy it ships. Editing one and not the
other went unnoticed by validate and by every test.

It had already happened. The shipped repository-adoption skill still told
its reader to use `--strategy normalize --recipe documents-to-content-root`
-- an operation the CLI does not offer and CLAUDE.md forbids claiming --
and said nothing about the owner requirement or acknowledged findings.
Every repository bootstrapped since would have received that copy.

Sync both, and add a test that compares each shipped skill against the
checked-in one so the next divergence fails instead of shipping.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Alexander Baranov
2026-08-25 18:11:13 +03:00
co-authored by Claude Opus 5
parent 1ab02a257c
commit 79ea43d5bf
4 changed files with 70 additions and 10 deletions
+8 -4
View File
@@ -14,8 +14,11 @@ with machine output, and explains findings. It must not duplicate the runbook lo
1. Run `repoctl adopt --repo <path> --mode assess --output json` (read-only).
2. Present the classification, detected content roots, and any `questions` that need
owner confirmation.
3. Run `repoctl adopt --repo <path> --mode plan --output json` once open questions are
resolved. This is still read-only and returns an `AdoptionPlan` with a `planHash`.
3. Run `repoctl adopt --repo <path> --mode plan --owner <owner> --output json` once open
questions are resolved. This is still read-only and returns an `AdoptionPlan` with a
`planHash`. `plan` refuses without a confirmed owner, and refuses while `assess` left
an error-severity finding; an owner who accepts one lists it under
`acknowledgedFindings` (with a `reason`) in the `--answers` file.
4. Show the full plan (files created, patched managed blocks, preserved paths,
forbidden changes) before asking for approval.
5. Only after explicit approval, run
@@ -23,5 +26,6 @@ with machine output, and explains findings. It must not duplicate the runbook lo
6. Run `repoctl adopt --repo <path> --mode verify --output json` and report the
`AdoptionReport`, including any `unresolvedFindings`.
Default strategy is `overlay`. Only use `--strategy normalize --recipe
documents-to-content-root` when the owner explicitly asks to reorganize root documents.
The only implemented strategy is `overlay`. Normalization recipes are specified in the
runbook but not implemented, and the CLI does not offer them: do not describe
`--strategy normalize` or `--recipe` as available.