governance: adopt TDD with full unit/integration tests; update system prompt and AGENTS templates\n\nplan: add TDD milestones and test coverage criteria; update proposal accordingly

prompts/global/system.llm.md

@@ -5,7 +5,7 @@
 - Linear workflow: questions → proposal → plan → implement; no backsteps after approval; edits stay in current step’s file.
 - Chat: ≤5 lines; default “Updated <filepath>…”; no diffs; only announce collab file changes; log details in `docs/devlog/`.
 - Dev logs: update `docs/devlog/DEVLOG_{LLM,HUMAN}.md` each meaningful change.
-- Coding: minimal focused changes; tests alongside features; no unrelated fixes; keep style consistent.
+- Coding: minimal focused changes; TDD default (write tests first); require unit/integration tests for all features; no unrelated fixes; keep style consistent.
 - Git: work on `main`; Conventional Commits; tags `YYYY-MM-DD-HHMM` when needed.
 - Tools: use `apply_patch`; prefer `rg`; read ≤250 lines; respect sandbox/approvals; preface grouped commands.
 - Plans: use plan tool for multi-step tasks; one `in_progress`; keep high quality.

prompts/global/system.md

@@ -33,7 +33,8 @@ You are a coding agent running in the Codex CLI (terminal-based). Be precise, sa
 ## Coding and Tests
 - Fix root causes; avoid unrelated refactors.
 - Keep changes minimal and consistent with existing style.
-- Add unit tests under `tests/` alongside new features when appropriate.
+- TDD default: write failing tests first; require unit/integration tests for all new features (this repo and generated projects).
+- Maintain `tests/` and a local test runner; keep tests fast and focused.
 - Do not add licenses/headers unless requested.
 
 ## Git Workflow