intent: the gated requiredWhen check is proved at runtime, not in the generated source (#7238)

[delchev]

The gaps

Two, both from #7129 (checks: requiredWhen, #7094).

1. The assistant guide. Already fixed by #7414 (merged this morning), which added the kind's bullet. What was still missing there is the routing, the one thing an author has to decide: the status: gate is OPTIONAL, and its presence is what decides where the rule is enforced. Added as two sentences to that bullet.

2. The IT asserted source text only. IntentEmissionCoverageIT checked AccountRepository().findById(hop0Fk), java.util.Objects.equals(entity.Note, "audited") and the authored message over the rendered repository. Nothing drove a record to the gate status, so a guard that never fires would pass identically - which is precisely the failure mode of the sibling issue #7237 (Objects.equals(Long, int) is never true, so the rule looks authored and enforces nothing).

And it could not do more as it stood: the check read Account.name, which the fixture declares required: true. The value it guards is therefore always present, and no write could ever be refused - the reason this check stayed source-text-only while compare got a runtime block on the same day.

The change

• Account gains an optional taxCode, and the gated check reads Account.taxCode (message reworded accordingly). A rule over a REQUIRED column of the related row is unfalsifiable; the comment in the fixture says so.
• A runtime block in assertRuntimeEnforcement, all three outcomes over REST:
  • an entry with Note: "audited" against an account with no tax code, with balanced lines so the itemsMin / itemsSumEqual gates on the same status cannot be what refuses it → 400 carrying the authored message;
  • an entry with no note, same account, same status → 200 (the rule is a condition, not a required nobody declared);
  • the account amended to carry a tax code → the audited entry's same write is accepted. Amending the related row rather than the entry is what proves the gate reads the hop when the write is checked, not a copy taken at create time.

The ungated twin (Doc, the controller's 400) already had runtime coverage from #7237; this is the other routing.

Verification

• mvn -o -P integration-tests -pl tests/tests-integrations verify -Dit.test=IntentEmissionCoverageIT -Dit.groups= -Dit.excludedGroups= -Dselenide.headless=true → Tests run: 1, Failures: 0, Errors: 0 in 193 s, BUILD SUCCESS, against a full quick-build install of this branch in an isolated local repository.
• mvn -o -pl tests/tests-integrations formatter:validate with the formatter cache wiped first → BUILD SUCCESS.
• No production code changed: the guide is a resource read by the assistant prompt, the rest is the test fixture.

Fixes #7238

🤖 Generated with Claude Code