ADR-006/014: clear two stale labels

Review O5/O6: ADR-006 mislabeled backend.tf as "Forgejo state backend" (its own
State-backend section chooses local state — Forgejo's API is read-only); ADR-014
called plugin reproducibility open though TODO 10.7 is done.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
sjat 2026-06-05 18:55:17 +02:00
parent d8afa94c4b
commit 8e4bf3dd88
2 changed files with 6 additions and 5 deletions

View file

@ -75,7 +75,7 @@ isolation — no risk of accidentally applying the wrong state.
Each environment directory contains: Each environment directory contains:
- `providers.tf` — provider version pins and configuration - `providers.tf` — provider version pins and configuration
- `backend.tf`Forgejo state backend (environment-specific path) - `backend.tf`backend configuration (local state on the control node; no remote backend — see "State backend" above)
- `variables.tf` — input declarations - `variables.tf` — input declarations
- `terraform.tfvars.example` — tracked template; copy to `terraform.tfvars` for actual values - `terraform.tfvars.example` — tracked template; copy to `terraform.tfvars` for actual values
- `main.tf``local.vms` map and module calls (no DNS resources) - `main.tf``local.vms` map and module calls (no DNS resources)

View file

@ -85,10 +85,11 @@ The accelerators this policy prefers (`context7`, `deep-research`, `superpowers`
`claude-code-guide`) are **plugins under `~/.claude/`** — local per machine, **not** `claude-code-guide`) are **plugins under `~/.claude/`** — local per machine, **not**
synced by Claude account and **not** carried by the git repo (only `.claude/commands`, synced by Claude account and **not** carried by the git repo (only `.claude/commands`,
`.claude/hooks`, `.claude/settings.json` travel). A fresh clone therefore lacks the `.claude/hooks`, `.claude/settings.json` travel). A fresh clone therefore lacks the
plugin toolchain until it is reinstalled. Making it reproducible from the repo plugin toolchain until it is reinstalled. Making it reproducible from the repo is
(`extraKnownMarketplaces` + `enabledPlugins` in `.claude/settings.json`, plus a **done** (TODO 10.7): `.claude/settings.json` declares `extraKnownMarketplaces` +
bootstrap step) is tracked in `docs/TODO.md` and tied to control-node/AI setup. Until `enabledPlugins`, and `docs/runbooks/claude-code-setup.md` documents the per-machine
then, the graceful-degradation fallback above keeps the policy working. bootstrap. Until a fresh clone runs that bootstrap, the graceful-degradation fallback
above keeps the policy working.
## Decision ## Decision