test(intent): cover calculatedActionOnCreate on a to-one relation

[delchev]

Pays back the coverage owed by #6681. engine-intent/CLAUDE.md requires every new keyword to extend IntentEmissionCoverageIT in the same PR; that one merged without it, and the doc recorded the debt.

What it covers

The fixture gains Tariff + Quote, where Quote.Tariff declares calculatedActionOnCreate: QuoteTariffAction, plus the hand-written custom/QuoteTariffAction.java the contract requires.

The class is written into the emission-test project by the IT itself. That coupling is exactly why the case was deferred: a generated repository referencing a missing class fails the whole client-Java batch and with it every REST assertion in this gate. Carrying the class as part of the fixture is what makes it safe.

Three layers, because no one of them alone catches this keyword's regression:

layer	assertion
.model	the relation property carries "calculatedActionOnCreate": "QuoteTariffAction"
generated code	entity.Tariff = Beans.get(QuoteTariffAction.class).calculate(entity); in the repository, plus the decoded imports: line
runtime	a create that OMITS the FK returns the base-flagged tariff; one that SUPPLIES a tariff keeps it

The middle row is the regression. A relation is an ordinary property in the .model, but only fields used to carry the calculated attributes into it — so the keyword parsed, validated and reached the .intent while the emitted repository contained no assignment at all, and the create stored null with every pipeline step green. Asserting the .model alone would not have caught it: that layer was already fine.

The base tariff is seeded as row 2, not row 1, so the runtime assertion cannot be satisfied by a first row or a stray column default — only by the action having run and matched on base.

Why the runtime layer is not redundant

It earned its place while this was being written. Annotating the action with org.springframework.stereotype.Component instead of the SDK's org.eclipse.dirigible.sdk.component.Component compiles cleanly and then fails every create with No qualifying bean of type 'custom.QuoteTariffAction' available. An emission-only case — the cheaper option — would have passed while the feature was dead at runtime.

Verification

IntentEmissionCoverageIT green: Tests run: 1, Failures: 0, Errors: 0.

Both new assertion groups were also observed failing first, so neither passes vacuously:

• the emission group, on a wrong model filename (app.model vs emission.model);
• the runtime group, on the 500 described above.

Re-run after rebasing onto current master, and the installed 15.0.0-SNAPSHOT template jars were diffed against the working tree to confirm the run used current Repository.java.template, EntityController.java.template and document-page.js.template rather than stale artifacts.

🤖 Generated with Claude Code