Entry point into skills/foreman/references/. SKILL.md's own "References"
section is the authoritative per-file pointer list for the skill body; this
index is the cross-linked map for readers arriving from
README.md or docs/USAGE.md
who want the operator-facing detail behind a specific claim.
| Stage | What to read | File |
|---|---|---|
| Setup & Environment | Windows + WSL inventory, bootstrap, profiles, .wslconfig tuning, clock-sync |
reference-environment.md |
| Setup & Environment | foreman-setup.sh/foreman-cleanup.sh requirements (EARS) |
../../../openspec/changes/archive/2026-07-18-lifecycle-three-stage/specs/lifecycle/spec.md |
| Use — routing | Exact registered model/transport roles and admission | lanes.md |
| Use — specs | The five-part spec template + EARS phrasing | five-part-spec.md |
| Use — roles | Orchestrator / worker / advisor / auditor contracts | roles.md |
| Use — parallelism | Worktree-isolated search/plan/audit fan-out | parallel-worktrees.md |
| Use — durable rounds | Existing journal, immutable checkpoints, owner recovery and legacy refusal | durable-lanes.md |
| Use — v0.2.5/v0.2.7.5 hardening | Current host controls and retained historical obligations | orchestration-hardening.md |
| Use — audit | Audit dimensions + verdict schema | audit-checklist.md |
| Use — release reporting | Metric definitions (M1–M13), companions, sigma-before-claim, linter | release-metrics.md |
| Use — regression tiers | Runtime/cost budgets, cadence, and the fixed 20% review margin | regression-tier-budgets.md |
| Cleanup | Retain owners and run evidence; use confirmed cancellation before worktree cleanup | — |
| Security (all stages) | Threats and enforcement map | security-model.md |
../../../openspec/changes/archive/2026-07-18-t5b-concurrency-verdict/and../../../docs/research/vendor-concurrency-results.md— the destructive concurrency test that keeps thegrok/codexpueue caps at 1 until a real authenticated green row is recorded.
skills/foreman/scripts/maintenance.sh and skills/VENDORED.md are
documented inline in SKILL.md §12 and the README's "Repo understanding and
maintenance" section rather than in a dedicated reference file.