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:** Kubernetes manifests + Helm values, Bash Make targets
+- **Key deps:** CloudNative-PG (cnpg) clusters, Valkey, OpenBao, 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 (db-*, apps-pg-*, pg-*, valkey-*, openbao-*)
+make db-status         # gitea-db cnpg cluster health (read-only)
+make apps-pg-status    # shared apps-pg cluster health (read-only)
+make pg-status         # standalone PostgreSQL HA pod status (read-only)
+make valkey-status     # Valkey pod status (read-only)
+make db-deploy | apps-pg-deploy | pg-deploy | valkey-deploy   # production-touching
 ```
+
+`*-deploy` targets change production platform services — operator approval
+required. `*-status` / `*-logs` targets are read-only and safe.