A field report from bootstrapping Services/Vault: ~20 CLI calls produced
three productive writes, and four of those calls were deliberate failures
sent only to discover a vocabulary.
The worst of it was self-inflicted and new. `repoctl skills install` is the
documented way to make the bootstrap skill reachable, and it writes the
three skill files -- which `init` then reported as INIT_PATH_COLLISION and
redirected to `adopt`. Every skill-driven bootstrap of an empty repository
was pushed onto the adoption path. The collision check exists to protect
content the tool did not author, and identical bytes are nothing to
protect: a path already holding exactly what the plan would write is no
longer a collision, at plan time or at write time, while a file whose
content differs still is. `init` reports only the files it actually wrote.
`--lifecycle` advertised no choices, so its vocabulary was reachable only
by sending a wrong value and reading the refusal; it now carries `choices`
like `--type` does.
`--answers-template` prints a commented answers file naming every key, its
allowed values and its default. The answers keys are not the flag names
(`--type` sets `repositoryType`) and nothing printed the mapping. It lists
`summary` and `namespace` too, which are cheap to answer once and otherwise
survive as generated placeholders in the contract.
`--repo .` proposed the name `adopted-repository`: `Path(".").name` is the
empty string, so the ordinary way to name the current repository fell
through to the generic fallback. Resolve before deriving.
Both skills gained what the report had to discover by hand: that `--plan`
already unwraps a saved result envelope, and that sibling repositories are
where a naming convention comes from.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
32 lines
1.6 KiB
Markdown
32 lines
1.6 KiB
Markdown
---
|
|
name: repository-bootstrap
|
|
description: Bootstrap a new repository into Repository Stewardship using repoctl init. Use when creating a new repository or scaffolding ops/contract.yaml, kdb/kdb.yaml and agent entrypoints from scratch.
|
|
---
|
|
|
|
# repository-bootstrap
|
|
|
|
Thin wrapper around `repoctl init`. Do not reimplement classification, template
|
|
rendering or validation here - call the CLI and explain its output.
|
|
|
|
## Procedure
|
|
|
|
1. Run `repoctl init --answers-template > answers.yaml`. It names every key, its
|
|
allowed values and its default; the answers keys are not the flag names
|
|
(`--type` sets `repositoryType`). Fill it in with the user.
|
|
Answer `summary` and `namespace` too: they are cheap now and otherwise stay
|
|
as placeholders in the contract.
|
|
All values are refused rather than guessed -- `name` must match
|
|
`^[a-z][a-z0-9]*(?:[.-][a-z0-9]+)*$`, `owners` must be non-empty -- and before
|
|
choosing a name, look at the sibling repositories and follow their convention.
|
|
If the target already holds `ops/contract.yaml`, this is an existing
|
|
repository: use `repository-adoption`, not `init`. Skill files left by
|
|
`repoctl skills install` are not a collision.
|
|
2. Run `repoctl init --repo <path> --answers answers.yaml --output json` to obtain a
|
|
`BootstrapPlan` (this performs no writes).
|
|
3. Show the user the planned files and the `planHash`.
|
|
4. Only after explicit approval, run
|
|
`repoctl init --repo <path> --apply --plan <plan-file> --approve <planHash>`.
|
|
5. Report the resulting `repoctl validate --repo <path>` findings.
|
|
|
|
Never invent files outside the plan and never skip the approval step.
|