docs(detention): forced-entry rule; close the ten open flag items

Owner's decisions of 2026-09-07 applied:
- Rule sharpened in README "Definitions": forced entry into the victim's
  space (home, office, hotel room, car) followed by beating or holding them
  there to take what is wanted is detention, however short.
- 354, 355 (null) and 124 set to 0. 242, 273, 413, 422, 423, 215, 298 stay 1;
  the set-to-0 proposals for them are withdrawn under the rule.
- corrections-approved.md, detention-flag-review.md and the corrections JSON
  carry the decisions; the worklist item says no open items remain.
- Summaries 242 and 273 relabelled "Detention" with the forced-entry wording.

verify_all.py PASSES.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GZZENdTLzNGsbNy4DyF1yt

merge-output/sofia-worklist.md

@@ -251,7 +251,8 @@ row 252 wrong URL / Phuket case). Additional items found during the summary pass
   `detention` and the sheet column "Kidnappings" to "Detention"; the scenario name "Kidnapping" stays.
   Full rule: README-START-HERE.md, "Definitions". Per-case proposals with evidence:
   `detention-flag-review.md` / `detention-flag-corrections.json` (40 records; on 2026-09-06 the owner ACCEPTED all 30 set-to-1 proposals (rule clarified: detention of
-  anyone, guards or staff included, counts); the 10 set-to-0 items incl. the two nulls and 2 checks are still open). This REPLACES the earlier item
+  anyone, guards or staff included, counts); on 2026-09-07 the owner set 354, 355 and 124 to 0 and
+  withdrew the other set-to-0 proposals under the forced-entry rule; no open items). This REPLACES the earlier item
   "`kidnappings` = 1 but no abduction: 293, 271, 273, 298" — under the detention rule 293 and 271 stay 1
   (held at gunpoint / forced back inside), 273 goes to 0 (stabbed, not held), 298 needs a source check.
 - **Case 237** — `violence_torture` = 0 but the source says he was beaten; `theft` = 1 though nothing was