v0.5.6

Per-deployment scenarios menu

The built-in scenarios tool now returns text from a scenarios: block in the config (with {user} substituted for the caller), so each deployment names the tools it actually exposes instead of a fixed list. When scenarios: is unset, the tool points people at aggrete__check. The demo menu moved into proxy.config.yaml.

Follows 0.5.5, which added check and scenarios and broadened the demo to every rule type. No change to enforcement behavior.