docs: self-host at L1 and ship the three Claude skill adapters

- Move ops/contract.yaml annotation from specification-only to l1-implemented and
  declare real content roots for repoctl source, schemas, tests and Claude adapters.
- Add repoctl-cli capability to provides[].
- Route repository.tooling.use and repository.handoff intents to the existing
  tooling-implementation KDB topic.
- Update README, AGENTS.md and CLAUDE.md to describe the implemented repoctl surface
  instead of a planned one, without claiming L2/L3/MCP capabilities that don't exist.
- Add .claude/skills/{repository-bootstrap,repository-adoption,repo-handoff}/SKILL.md,
  generated from the same stewardship.skills_content strings that ship inside every
  repoctl init bootstrap (no duplicated logic).

`repoctl validate --repo .` passes with zero findings after this change.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Alexander Baranov
2026-08-24 15:00:34 +03:00
co-authored by Claude Sonnet 5
parent 96d4d08230
commit 7286322c83
8 changed files with 141 additions and 12 deletions
+6 -1
View File
@@ -4,7 +4,10 @@
This repository defines Repository Stewardship: harness-neutral contracts, knowledge routing, templates and adoption practices for managing Git repositories with humans and AI agents.
It currently contains specifications and runbooks. `repoctl`, executable handlers and an MCP server are planned interfaces, not implemented tools in this repository.
It now ships an L1 implementation: the `repoctl` CLI (Python package
`repository-stewardship`, module `stewardship`, run via `uv run repoctl`) implements
`config`, `validate`, `discover`, `describe`, `context`, `init` and `adopt`. Executable
`ops/handlers/`, the L2 handler ABI and an MCP server remain planned, not implemented.
## Start here
@@ -12,6 +15,8 @@ It currently contains specifications and runbooks. `repoctl`, executable handler
2. Read the small index in `kdb/kdb.yaml`.
3. Match the task to an exact topic intent.
4. Open only the documents and headings named by that topic's `data.readHints`.
5. Prefer `uv run repoctl context --repo . --intent <intent> --output json` over reading
whole documents by hand once the CLI is available in your environment.
Do not load every design document by default.