feat(event-script): f:minRange and f:maxRange - the bounds of a range typed by the notation; rangeLookup checks every band when it reads a table

[acn-ericlaw]

What

f:minRange(range, default) and f:maxRange(range, default), two simple plugins that read one range in the notation of f:rangeLookup's bands (min..max, min.., ..max) and return its lower or upper bound, typed by the notation: a numeric bound is a number (a whole number within the 64-bit range a long, any other number a double), a text bound is text as written, and an open end answers the optional default, or null when there is none. f:rangeLookup now checks every band when it reads a table, whatever the value, so a band that could never match (3..3, the upper bound being excluded) is refused by name on the table's first use. The three plugins share one notation reader, RangeNotation in com.accenture.util, allow-listed in the plugin loader's bytecode gate beside the decimal helper, so a range is refused by one of them exactly when the others refuse it; the gate test now names the three plugins.

Pinned by the shared range-bounds-vectors.json (34 vectors, byte-identical with the Rust twin Accenture/mercury#380, Increment 177), three new range-lookup-vectors.json entries, the fixture unit-test-range-bounds-1 (the band the lookup chose read back through a dynamic key; a graph.math IF/THEN/ELSE computing the distance to the next tier only when the band has an upper bound), the plugin tests and the gate test. Docs: the syntax guide's plugin table and The bounds of a band, the flow schema reference, the skills reference's Range tables, the command reference, the AI agent guide and help graph-data-mapper with the rebuilt bundle (index-DgBUB6YY.js; a rebuild of the unchanged sources reproduced the committed bundle byte for byte before the help edit). CHANGELOG Unreleased item 1.

Why

Eric's follow-up to f:rangeLookup: with the bounds encoded in the range text, a developer or an AI agent needs graph.math or graph.data.mapper to read a band's min and max back, typed as the number or text they are; and a range whose max is not above its min can never match, so the lookup must refuse it rather than carry it silently.

Verification

• mvn -o -q -pl system/event-script-engine test on the plugin, lookup and gate tests; mvn -o -pl system/minigraph-playground-engine test on the two vector tests and GraphTaskTest (23 tests, 0 failures); SkillSnapshotTest green.
• scripts/check-doc-canon.py, check-minigraph-grammar.py and check-rest-automation-grammar.py OK.
• The vector files, the fixture, the help page and the bundle are byte-identical in both repositories; the Rust vector test passed on its first run.

Upgrade note: a range table holding an empty or mixed band beyond the bands a run reached was accepted before and is refused now - fix the band; no other action.

Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com

🤖 Generated with Claude Code