CB-WP-0042 T01-T04: H2's scoped stress, with the named defects caught

H2 is ground-game's answer to our H1 reading — that a flat +1 to every
seat is a solve-rate tax scaling with the number of Problems. Unclaimed
Problems now tick only the seats in scope: global (all), personal (the
owner), bond (the owner's Bond network over Bond edges only, degree 0
falling back to personal), assigned by hidden priority so 2p never has the
bond card in play.

T01: the package is vendored with digests, and H2's Problems.csv is r0's
with one column added and NOTHING else changed — checked, not assumed,
because the delta claims deal_and_thresholds unchanged and a silent
difference would make every H2-vs-baseline comparison a comparison of two
boards as well as two rule sets. Scopes are read from the column, not
derived from the priority in Rust: F25 exists because we hardcoded numbers
the edition already carried.

T02: owner and scope are new ProblemState fields, both Option and both
skipped when None, so a baseline state serialises without them and every
recorded scenario's hash is untouched — asserted on the JSON, not assumed.
with_variant() replaces the bare field write, because state.variant = v
would leave owners unassigned: a silently wrong game rather than a failing
one.

T03: every named defect is mutation-proven — traversing Rivalry edges,
applying stacking once, a degree-0 owner ticking everyone, personal
hitting everyone. The degree-0 mutation MISSED first: the fallback lives
inside bond_network and the mutation broke the None-owner arm instead, a
different branch. It stayed green until aimed at the path the test
exercises. A mutation that misses is not evidence the test works.

T04: ownership is not a permission. Filtering SOLVE to the owner turns it
red, which is the regression this task exists for — the engine had no
owner concept before T02 added one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

editions/ground-darvo-r0/PROVENANCE.md

@@ -59,6 +59,11 @@ reported it unverified and it was a real gap.
 
 ```
 sha256  c469f984c3147861815e8fbd67cf1254de73368fad1654f4177f740c0c280499  ../catalog.yaml
+sha256  4c81bae21d2ecb70c7424fa17445246a9b551b10e258d448634816c564e28f09  ../experiments/h2-scoped-problem-stress/Problems.csv
+sha256  8ed8deb7ad142de1bda70dc11add339f742e8c12ac1f02d5f7c7ec8f17f77b1d  ../experiments/h2-scoped-problem-stress/Rules_Text.csv
+sha256  b2db91edc6798efca1ccf0b048bb0d7cb324e808e01d636ebca813527bcd0db2  ../experiments/h2-scoped-problem-stress/VARIANT.md
+sha256  abf994f585fdfa9b2822614a7961e98141cded6a91c446916ff7fd48642de0a7  ../experiments/h2-scoped-problem-stress/metadata.json
+sha256  8dc569b2ae62f88f7f64e282bc6bba3dbcc3ffcad276591baafbdd24cb6c16b7  ../experiments/h2-scoped-problem-stress/rules_delta.yaml
 sha256  f58e81f84ea2b0d16e39932261eb3f3d9890345cdf37ad6f0b3abc00636840be  ../experiments/h1-problem-stress/rules_delta.yaml
 sha256  7b1cc0149122b855e827bc930576ed165bf7dd8d62707e845a9e514ce3521f8e  ../experiments/h1-problem-stress/Actions.csv
 sha256  62785f5e7e245c60171624d15de2f40187a44fec54f93c7d9705cf52584b1078  ../experiments/h1-problem-stress/Rules_Text.csv
@@ -66,6 +71,13 @@ sha256  b2714210c142f1d6d5bed8f9a795019e51829c627f9599ac0ebfa04ef60a37a5  ../exp
 sha256  443199db94601cc889557e5e86823f374dbfdf875962fc84f95c01865605101c  ../experiments/h1-problem-stress/metadata.json
 ```
 
+**H2 vendored 2026-08-08** (CB-WP-0042). Its `Problems.csv` is r0's with
+**one column added** — `stress_scope` — and **nothing else changed**: same
+rows, same `point_value`, `required_solution`, `visibility` and
+`hidden_priority`. That is checked, not assumed, because the delta's
+`unchanged:` list claims `deal_and_thresholds` and a silent change there
+would move every baseline hash.
+
 **`rules_delta.yaml` is the load-bearing one**: it is the executable
 statement of H1, and the kernel implements it. A silent change there is a
 silent change to what we measured.