Behavioural conformance the pure checks can't reach: write a minimal settings
file in the adapter's declared settingsFormat (with a hook), load it through
the adapter's layout, and assert the hooks actually came back. This is what
catches a layout that points at the right file but in the wrong format (the
JSON-vs-TOML trap) — the pure checker would pass it, the agent would silently
run with zero hooks. Does filesystem IO, so it's a separate opt-in assert.
Behavioural conformance the pure checks can't reach: write a minimal settings file in the adapter's declared
settingsFormat(with a hook), load it through the adapter'slayout, and assert the hooks actually came back. This is what catches a layout that points at the right file but in the wrong format (the JSON-vs-TOML trap) — the pure checker would pass it, the agent would silently run with zero hooks. Does filesystem IO, so it's a separate opt-in assert.