Apply ground-game's rulings: mastery in points, four boards, and a

vendor tool that covers what the gate checks

They ruled on all seven items the same day. Two were actionable here.

F28 RULED: points. Modes.csv MODE_COOP clarified upstream to say
"penalties apply to points, not card count"; mastery is now
total - blame - denied. A recorded scenario went red on it --
gr-e02-shared-ground pinned 0 (2 claimed CARDS - 1 - 1) and now expects
2 (4 POINTS - 1 - 1). The number moved because the rule was decided, not
because the engine drifted, and the scenario records both rulings; its
schema has no field for a second one, so both live in ruled_note with
`ruled` carrying the LATEST date.

F29 RULED not-intended and APPLIED upstream: SCN_02's suits re-tuned the
same day. The characterisation test is how we found out -- it pinned the
duplication, went red on the re-tune, and that red WAS the notification.
It now asserts every pair distinct, the stronger statement the
duplication had made unavailable. SCN_02 re-measures at 73 at 2p, not
67: its own board now.

F26/F30 ruled and recorded. F30's ruling incidentally confirms our
reading -- they name priority-2's suit as the first lever, which is the
difference we identified without having measured causation.

vendor-editions grew twice, both times because it covered less than the
gate it exists to satisfy:

  - It refused to touch ground-darvo-r0/ on the reasoning that the
    baseline is "a separate record". That was wrong within the hour:
    ground-game clarified Modes.csv and `make vendor` reported a clean
    sync while edition-check went red. A sync tool that covers less than
    its check reports success into a red gate.
  - Its two-block rewrite DETECTED which fence held which set and
    preserved the arrangement -- faithfully preserving a swap an earlier
    write had introduced, leaving each fence under a heading describing
    the other. edition-check reads every sha256 line flat and passed
    throughout: a document can be self-consistently wrong and green.
    Order is now asserted, with a control that goes red on a swap.

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

editions/catalog.yaml

@@ -4,6 +4,7 @@
 
 schema_version: 2
 # terminology: aspect (human) = former axis; modules remain module_id
+# packages declare files consumers must read (consumed_files / data_overlays)
 updated: "2026-08-08"
 default_baseline: ground-darvo-r0
 default_profile: baseline
@@ -97,6 +98,12 @@ modules:
     status: measured
     rules_delta: editions/modules/problem_stress/scoped/rules_delta.yaml
     data_overlays: [Problems.csv, Rules_Text.csv]
+    # files a consumer must open to implement this module (RPT-0006 §5b)
+    consumed_files:
+      - editions/modules/problem_stress/scoped/rules_delta.yaml
+      - editions/modules/problem_stress/scoped/Problems.csv
+      - editions/modules/problem_stress/scoped/Rules_Text.csv
+      - editions/modules/problem_stress/scoped/MODULE.md
     legacy_experiment_ids: [h2-scoped-problem-stress]
     measurement_ref: reports/260808-clay-borg-h2-measured.md
     hypothesis_ref: history/260808-h2-scoped-problem-stress.md