v0.10.0 — cross-repo trap dual-write, green needs evidence, live demo

An external-evaluation-driven release: we surveyed the neighboring ecosystem (auto-capture memory, spec/task-first frameworks, markdown conventions), confirmed the retrospective × git-native × zero-dependency × hard-guard quadrant is still unoccupied, and closed the three real gaps the evaluation surfaced.

• health=green now needs evidence. The Stop hook (and --ci) gains a second check: STATE claiming health: green while the latest record carries no test evidence (empty tests: frontmatter) gets a nag — the "tests green before done" hard guard is now wired to the health color. Detection is frontmatter-presence only, no prose judgement; in CI it's a warning, never a gate.
• Cross-repo traps stop biting twice. fw-trap now judges a trap's scope: platform/language-layer traps (any project would step in them) are still registered in the repo's TRAPS — the registry must stay self-contained — and saved to your user-level memory so your other repos get the warning too. One copy per scope is division of labor, not duplication.
• Honest edges of the reminder net, documented in all four README editions: the lag check counts commits, so a session that commits nothing (research, ops) or a squash/rebase flow slips under it. The net catches forgetting; it doesn't replace the session-end obligation.
• README now opens with a live demo: a real ~30-second cold start recorded on this very repo — one command, two file reads, and a fresh session reports exactly where the last one left off.