Files
FredApps 7f96ae5f1e engine: one typed parameter schema for dispatch, value checks and filter dialogs
The registry's `params` doc strings were read by three hand-written scanners
(param_check, filters/validation, the filter dialog), each with its own idea
of the grammar. This adds `param_schema`: one parser of the documented
grammar into owned types, and a renderer a test holds to reproduce every
registry doc byte for byte.

- Dispatch rejects unknown keys for every command whose doc is complete
  (#7596). Docs that are not yet complete are listed in `INCOMPLETE`, which
  may only shrink; `coalesce` and `target` stay universal.
- Filter and adjustment values are checked against the ranges and choices
  in their docs; the hand-synced `fields()`/`choices()` tables are gone, and
  a test checks every documented range is enforced and never clamped
  narrower on the run path (#7597).
- The filter dialog builds its fields from the engine schema instead of its
  own parser (#7598).
- Docs that the tests and UI showed to be incomplete or wrong are fixed, and
  UI callers stop sending keys their command does not take.

Design after #7599 by @SckraT. The schema is cached in a OnceLock, so
nothing is leaked.

Closes #7596
Closes #7597
Closes #7598
2026-11-16 00:24:18 +01:00
..
…
…
…
…