Runs every data-contract/rendering-legibility check this engine has
against system and returns one combined, tagged list — the single
entry point a host app calls once per loaded system (e.g. right after
fetching it, or from a dev-mode overlay) rather than wiring up each
individual finder itself. None of these are hard failures (this engine
has no concept of "refuse to render") — they're warnings for a human or
a test to look at, same spirit as a data pipeline's own build-time
validators, just scoped to what's checkable from the engine's own data
contract and geometry rather than upstream source data.
Runs every data-contract/rendering-legibility check this engine has against
systemand returns one combined, tagged list — the single entry point a host app calls once per loaded system (e.g. right after fetching it, or from a dev-mode overlay) rather than wiring up each individual finder itself. None of these are hard failures (this engine has no concept of "refuse to render") — they're warnings for a human or a test to look at, same spirit as a data pipeline's own build-time validators, just scoped to what's checkable from the engine's own data contract and geometry rather than upstream source data.