feat(validator,generate,run): an identifier a proposal builds on must be in the input, or the verdict falls [skip-docs]

P6 (økt 108) ended in ValidatedProposal (verdict 5fd6272e3725fe68) on two cost
codes -- M-04-01 / M-04-03 -- that appear in NO prompt of that run. Measured
here first, verbatim: validate_proposal(p, baseline=None) validates it; the same
proposal against any non-empty CostBaseline is rejected naming both codes.

So the hole was never "fabrication goes uncaught" -- _reconcile_against_baseline
exists and is right -- but that the falsifier is reached only through
`if baseline is not None`. The input always exists; the baseline does not.

New stage 0b (_ground_against_input), OUTSIDE the baseline branch, after stage 0
so an anchored run's message is byte-identical to before. ONE Rejection, the
validator's own type, naming EVERY ungrounded identifier "; "-joined in the
proposal's own order (økt 94's completeness reason).

The rule has NO pattern -- `code in grounding`, exact substring -- and that is a
measurement: over the delivered corpora (K2 1108 files / 2 005 561 chars, the
three N payloads 8 excerpts each) the identifier forms are heterogeneous, and a
pattern chosen to cover them would be a rule about shapes. Bare numerals are the
one inert class (46 394 occurrences / 2 117 distinct in K2); the rule fails OPEN
there, never closed.

Evidence is three non-model-authored sources: what run_project DELIVERED (the
rendered cut/pointer/chunks plus the base's context_files -- never files, which
would make the type: verdict layer evidence), the project's own cost lines, and
the baseline's codes when anchored. The rendered PROMPT is deliberately NOT
evidence, on two measurements: gen_context IS the debate output on the S2c path,
and from attempt 2 the prompt carries the previous Rejection.reason verbatim --
which for this stage QUOTES the identifier it just refused. Grounding in the
prompt would let the gate's own refusal disarm it on its second round.

Prose scanning was chosen against WITH THE NUMBERS: a typed gate catches 2/2
(P6) and 2/2 (S7c) -- 100% of what reached a verdict. What stays uncaught, said
plainly: an ungrounded identifier that lives only in agent/debate prose and never
becomes an affected_item code (2 of 4 P6, 2 of 4 S7c, 1 of 2 P4).

Iron Law: 9 red / 2 green before the rule existed. Ten mutations all red against
the whole suite, green control 1558 passed / 5 skipped (from 1543/5, superset,
0 removed), golden demo-transcript.stdout BYTE-UNCHANGED (shasum -a 1 of the
CONTENT = ea8c534773acdbe41ae68f2c55724d69aaf8be4f).

Three existing fixtures changed, no gate weakened -- most of all
test_pre_amendment_bundle_runs_unchanged, which sent the SAME FABRICATED code and
asserted it validated: the økt-108 hole written down as an expectation.

No paid run. Order 20260909T113641Z-38938691-from-.claude.

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

tests/test_s40_cost_baseline_loadbearing.py

@@ -250,16 +250,23 @@ async def test_bundle_path_anchors_when_the_bundle_declares_a_baseline(fresh_sto
 
 
 async def test_pre_amendment_bundle_runs_unchanged(fresh_store) -> None:
-    """Control + backward compatibility: the SAME fabricated reply validates against a bundle with
-    no ``cost-baseline.json``. Anchoring is opt-in per bundle, so every pre-S4.0 bundle (including
-    the commons-owned goldens) runs byte-identically to before."""
+    """Control + backward compatibility: an unanchored bundle still runs to a VALIDATED outcome, so
+    anchoring stays opt-in per bundle and every pre-S4.0 bundle (including the commons-owned
+    goldens) is unaffected.
+
+    **NARROWED BY P7, deliberately.** This arm used to send the SAME FABRICATED code and assert
+    that it validated — which was, stated plainly, the økt-108 hole written down as an expectation:
+    with no baseline there was no falsifier for an invented cost line at all. The reply now carries
+    a code the delivered base actually names, so the arm proves what it claims (an unanchored run
+    still reaches a verdict) without also promising that fabrication clears it. The fabricated half
+    lives in ``test_identifier_grounding_loadbearing``."""
     result = await run_project(
         "BYGG-ENERGI-MIKRO-A",
         "local",
         docs_dir=str(PRE_AMENDMENT_BUNDLE),
         bundle_dir=str(PRE_AMENDMENT_BUNDLE),
         verdict_input=_VERDICT_INPUT,
-        client_factory=_factory(_reply(_FAKE_CODE, 1.0, 300000.0, 90000.0)),
+        client_factory=_factory(_reply("ENERGI-TOTAL-EL", 1.0, 300000.0, 90000.0)),
         store=fresh_store,
     )
     assert isinstance(result.outcome, ValidatedProposal)