ADR 0080: the development cycle is checked, not trusted

The flow the process overview draws — idea/symptom -> decision -> to-be design -> code ->
as-is — was enforced by nothing. cycle.py now refuses a to-be design naming no decision, an
in-progress/implemented design naming no owning code, a located/fixed issue with no owner,
a fixed/resolved issue with no fix, and a graduated research overview that does not say what
it became. AGENTS.md carries the cycle and a where-to-look table so a fresh session (or a
cleared context) finds the chain in frontmatter instead of assuming it. Grounding the check
surfaced two real gaps, fixed here: the work-ahead design named no owning code, and research
003 listed one became target twice.

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

00-META/process/00-overview.md

@@ -52,6 +52,17 @@ the expensive half.
 | [06](06-writing-a-module.md) | Writing a module | Something that runs today must run on the mesh |
 | [07](07-feature-branches.md) | Feature branches across repos | Work that changes code, in one repo or several at once |
 
+## The cycle is checked
+
+The flow above is a rule, and a rule states how it is checked:
+[`00-META/checks/cycle.py`](../checks/cycle.py) refuses a to-be design that names no
+decision, an `in-progress`/`implemented` design that names no owning code, an issue marked
+`located`/`fixed` with no owner or `fixed`/`resolved` with no fix, and a `graduated`
+research overview that does not say what it became. Run it with `records.py` and `index.py`
+before any HQ merge. What the checks cannot see — that code work actually started from a
+handoff — is held by playbooks [04](04-build-handoff.md) and [07](07-feature-branches.md):
+a feature branch exists because a design or an issue sent it.
+
 ## Status lives in frontmatter
 
 Research overviews, design docs, issue reports and decision records each carry their status as