docs(v1): define evidence-backed production contract

req: client_local/005\nreq: sync/009\nreq: accessibility/001\nreq: operations/001\nreq: security/001\nreq: performance/001\nreq: v1_release/001

AGENTS.md

@@ -9,6 +9,7 @@ Keep it stable. Prefer pointers to canonical sources over copied structure, file
 ## Agent workflow
 
 - Start from product intent and requirements; inspect code only after the target behavior is clear.
+- For v1 work, read `docs/v1-product-evidence.md`, then `REQUIREMENTS.md`; use `PLAN.md` only as the mutable implementation cursor.
 - Read `REQUIREMENTS.md` before changing behavior.
 - If behavior changes, update `REQUIREMENTS.md` in the same change.
 - If implementation work does not change durable product obligations, acceptance, safety/recovery behavior, or verification duties, say `REQUIREMENT IMPACT: none` in the handoff and why.
@@ -25,7 +26,7 @@ Keep it stable. Prefer pointers to canonical sources over copied structure, file
 - Every behavior-changing or requirement-changing commit should cite relevant requirement IDs in the commit body or trailers using `req: <component>/001`.
 - Use commit history for evolution: `git log --grep 'req: parser/012'` should find the commits that changed that behavior.
 - Use the current tree for state: `REQUIREMENTS.md`, citations, tests, and `redgate health` describe what is true now.
-- Before committing requirement or behavior changes, run relevant tests and `redgate health --strict`.
+- Before committing requirement or behavior changes, run relevant tests and the strongest `redgate health` mode supported by the installed tool. Do not invent an unsupported `--strict` flag; report a tool/format mismatch explicitly.
 
 ## Requirements-first TDD