Rule it an accepted disclosed residual — operator g0's ruling, 2026-09-11, selected from a presented decision after being shown the finding, both independent rounds, and the reviewer's refusal to close it. (Operator words are the ruling phrase; the characterization that follows is the agent's, grounded in session evidence.) Finding req-03-unowned-content-mutation-gap against REQ-0.35.0-06-03 is REAL and is NOT discharged by repair: an independent spec reviewer raised it (receipt arb-step-specreview-3c195166fc7c432789ca49635c910a54), a repair was attempted that added a genuinely mutation-killed in-module guard witness (verify_candidate_against_declaration's `declared != _OWNED` continue; observed AssertionError naming the dead entry id; production module restored byte-identically), and a second focused independent round REFUSED to close it (receipt arb-step-specreview-09feec6798f146fa8b5db3cc7059466a) on the correct ground that the repair "closes a distinct sub-claim, not the one named". The residue: the drift/textual comparison in _owned_drift that would catch arbitrary hand-authored prose inside an unowned section is structurally unwitnessable from within rendition_lineage.py alone, because composer.py's generate_candidate — a Denied Path belonging to the already-landed OBPI-0.35.0-05 — carries unowned bytes forward byte-verbatim from the same committed-rendition file _owned_drift compares, so the filter's discriminating power depends on code this OBPI may neither touch nor mutate. The reviewer's own disposition was "Disclosed, non-fatal, but not discharged." Two rounds named the same root, triggering the design-escalation rule (operator ruling 2026-09-03: stop dispatching, escalate the design). REQ-03's behavior is correct and its in-module half is now witnessed by two killed mutations at input_digest 49a411c1345247a4f8d1410f9b08e5f392b042d0ff03978a2f91e956df462a8b; the cross-module half is accepted as a disclosed residual of this OBPI's allowed-path boundary rather than laundered as proven. Both reviewer rounds and the finding remain in the ledger as history, not erased.
