Define release-candidate balance acceptance targets

TODO.md

@@ -49,7 +49,7 @@ release-candidate foundation, not yet a 0.10.0 release candidate.
 refinement** and **0.9.6 integration** passes are complete (all moved to
 `DONE.md`). The **0.10.0 release candidate** is next: content lock, external
 playtest, balance, save migration and release/legal sign-off. The source version
-is 0.9.6; the v0.9.6 release is published.
+is 0.10.0-rc.1; the v0.9.6 release is published.
 
 ## Milestone 0.10.0 — Release candidate
 
@@ -79,12 +79,17 @@ verify every distribution path. This is the next minor release after the 0.9.x p
 
 ### Balance and fairness pass
 
-- [ ] Define measurable targets for routine compliance, access-decision accuracy, peaceful
+- [x] Define measurable targets for routine compliance, access-decision accuracy, peaceful
       resolution, justified emergency calls and false-positive/false-negative rates.
+      (`docs/balance-acceptance.md` defines cohorts, denominators, 36 matrix cells,
+      seeds, thresholds and matched emergency-first comparisons. Documentation verified;
+      targets are not measured results.)
 - [ ] Run scripted venue sweeps across easy/normal/hard and all four phases; compare outcomes and
       tune event weights, reaction tables, compliance and report strictness where targets fail.
 - [ ] Review emergency calls against actual danger: no routine behavior should make emergency the
-      dominant winning move, and genuine threats must remain answerable.
+      dominant winning move, and genuine threats must remain answerable. Include the
+      type-derived `_read_npc_truth()` mismatch with observed threats/forced entry;
+      use independently labelled behavior evidence, not the helper as its own oracle.
 - [ ] Verify the reputation grades, debrief explanations and campaign progression still communicate
       the de-escalation-first design after tuning.
 - [ ] Record the balance evidence and any deliberate exceptions in `docs/development-status.md`