End-to-end smoke testing of `init` and `adopt` (plan -> approve -> apply -> verify) via subprocess surfaced a real portability bug: on Windows, sys.stdout defaults to the console codepage rather than UTF-8 when not attached to a UTF-8 terminal, so machine YAML/JSON output containing non-ASCII characters (an em dash in generated skill/docstring text) could fail to decode for downstream consumers. repoctl now reconfigures stdout/stderr to UTF-8 unconditionally in main(), and the offending em dashes are replaced with ASCII hyphens so generated file content is unaffected either way. Verified via manual CLI smoke tests: full init and adopt flows (including baseline re-check, plan-hash approval, collision rejection on re-apply, and preservation of profiles-source/, profiles/ and legacy kdb.yaml) work end to end. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.0 KiB
1.0 KiB
name, description
| name | description |
|---|---|
| repository-bootstrap | 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
- Collect the missing decisions from the user: repository type
(
infrastructure-config|service-config|software|project),metadata.name,title,owners,lifecycle. - Run
repoctl init --repo <path> --answers <answers-file> --output jsonto obtain aBootstrapPlan(this performs no writes). - Show the user the planned files and the
planHash. - Only after explicit approval, run
repoctl init --repo <path> --apply --plan <plan-file> --approve <planHash>. - Report the resulting
repoctl validate --repo <path>findings.
Never invent files outside the plan and never skip the approval step.