intent: a posts: set: constant renders as a Java string literal (#7246)

[delchev]

Fixes #7246

The defect

GlueIntentGenerator.postSetExpr tested a set: value against "[^"]*" for its string branch - it only fired while the value still carried its double quotes, which YAML strips long before the renderer sees it. An authored

set:
  Note: issued

reached the renderer as issued, missed every branch and fell through the final pass-through, so the template emitted

row.Note = issued;

and the whole generated module stopped compiling. PostIntent's own javadoc documented "a quoted string" as a supported form, and GluePostsTest asserted the item / negation / integer / source forms only, so nothing caught it.

The change

The value vocabulary moves into one place, PostSetSupport, shared by the renderer and a new parse-time refusal so the two cannot drift:

• a plain constant renders as an escaped Java string literal - the templates: a string defaultValue containing a quote or backslash breaks the generated repository's compile #7154 / templates: authored checks/guard/unique messages are interpolated into Java string literals unescaped - a quote in message: breaks the whole generated module (#7154's sibling, JavaLiterals unused there) #7241 family, so a value carrying a quote or a backslash cannot end the literal it is written into;
• a number, true / false / null, and a value the author quoted explicitly keep their non-text reading (the quoting is also the escape hatch for a constant that reads like an expression);
• a value that reads as an expression the renderer cannot compile - a dotted path off anything but item / source, or a negation of anything but a per-item copy - is refused at parse time, naming the rule and the field.

The refusal is the point of the third case. Rendering Receipt.Store as the string "Receipt.Store" would put the text of the path into the ledger cell instead of the value it names - silent in exactly the way passing it through was, and worse than a compile error. Refusing before anything is written is the honest outcome, and an author who really means that text quotes it.

The PostIntent example is corrected with it: it showed Store: Receipt.Store and GoodsReceipt: Receipt.Id, neither of which the renderer ever supported (the back-reference named by idempotentBy is written by the generated handler, not authored).

Tests

GluePostsTest gains the constant to the existing descriptor assertion (Note: issued -> "issued"), plus the escaping of a quote / backslash, the non-text forms, and the parse-time refusal naming the rule and the field. Full engine-intent suite green (1190 tests); formatter:validate and the release-profile javadoc clean on the module.

🤖 Generated with Claude Code