docs(remediation): RM-02 round-4 narrowing in review at e910a45a; D-48's failure mode now has a control

The wording ruling holds: the required sentence is verbatim in the baseline and its control, and every remaining use of "protected" refers to RM-60's external boundary rather than the local baseline. The history claim reads "structurally incapable of asserting history provenance". I verified the negative control by making the overclaim myself: clean exits 0, and injecting "protected, independently anchored" into the baseline purpose exits 84 with INVENTORY_CLAIM_OVERSTATED. D-48 was an overstated boundary claim that three of us approved; that exact failure mode is now caught mechanically rather than by attention. Review dispatched with N2 as the sharpest check: the overclaim control is itself PR-controlled, so can it be weakened or reworded so an overstatement passes? This PR's history is that every fix relocates the defect one level down, so the reviewer is asked to assume it did again. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
2026-08-01 15:28:52 -05:00
parent dde38717dd
commit 8fe14d8e1a
1 changed files with 1 additions and 1 deletions
@@ -20,7 +20,7 @@
 | ------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | RM-01 checkout      | —               | **MERGED** `f58b3699` (#1027)                                                                                                                                                                                                                          |
 | RM-03 queue guard   | Jason (re-sync) | ✅ **MERGED** `58b971ab` (#1032), #1019 closed. ⚠ **NOT DELIVERED**: installed guard still the broken one (291 lines / 0 `ASSERTED_NOT_READY` vs main 482 / 5). Re-sync via `mosaic upgrade`, then **prove it blocks a KNOWN-RED pipeline** — **D-51** |
-| RM-02 registry ★key | **coder-mos2**  | Round 4 @ `fbb61912`. Blocker 2 hit **RM-60 again (D-52, CWE-353)** — seat stopped, both orchestrator AND coordinator had authored the error. Ruled **(b) honest narrowing**; blocker 3 + (d)-strict unchanged. **2 anchors now need RM-60**           |
+| RM-02 registry ★key | rev-974         | **RE-REVIEW @ `e910a45a`** — (d)-strict history REMOVED + blocker 2 NARROWED (D-52) + blocker 3 + renderer. Overclaim control **fires at exit 84**, verified by orchestrator. CI 2201 **10/10**. ACs @ `dde38717`                                      |
 | RM-61 CI exemption  | —               | ✅ **MERGED** `f4fd5967` (#1033). #1034 closed; **#1000 stays OPEN** (retirement trigger). Exemption is on `main`                                                                                                                                      |
 | RM-59 / RM-60       | Jason (infra)   | tracked deps; RM-60 option **B**                                                                                                                                                                                                                       |
 | #1023 queue attempt | Jason           | SUPERSEDED-PENDING-JASON — live REQUEST_CHANGES, do **not** merge                                                                                                                                                                                      |