Repo hygiene: fill stack-and-commands, normalize workplan statuses

- Fill .claude/rules/stack-and-commands.md (was an empty TODO template)
- Normalize workplan frontmatter statuses to canonical vocabulary
  (completed/done -> finished) per ADR-001

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

.claude/rules/stack-and-commands.md

@@ -1,19 +1,18 @@
 ## Stack
 
-<!-- TODO: Fill in language, frameworks, and key dependencies -->
-- **Language:**
-- **Key deps:**
+- **Language:** Helm values + Kubernetes manifests, Bash Make targets
+- **Key deps:** Gitea (current forge runtime), Actions runner substrate, SOPS/age; runs against the S2 cluster on railiance01
 
 ## Dev Commands
 
 ```bash
-# TODO: Fill in the standard commands for this repo
-
-# Install dependencies
-
-# Run tests
-
-# Lint / type check
-
-# Build / package (if applicable)
+make help              # list all targets
+make check-tools && make check-sops   # preflight (read-only)
+make gitea-status      # forge runtime + database state (read-only)
+make runner-status     # Actions runner / registry probes (read-only)
+make registry-docs | evidence-docs | runner-docs   # print canonical docs
+make gitea-deploy | gitea-ingress-deploy           # production-touching
 ```
+
+`gitea-deploy` / `gitea-ingress-deploy` change the production forge —
+operator approval required. Status and docs targets are read-only.