--- 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 --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 --apply --plan --approve `. 5. Report the resulting `repoctl validate --repo ` findings. Never invent files outside the plan and never skip the approval step.