examples/generated/ has a page for every agent agentseam can hook,
each showing the same situation — an agent about to write a secret into a file it will
read back later — in that vendor's own dialect: the config install writes, the normalized
event a handler sees, and what allow / deny / escalate / transform / warn / vouch
each turn into on the way back (aliases: ask for escalate, rewrite for transform),
including the ones that get reduced because the agent cannot express them.
There is a section for every hook each agent supports, in lifecycle order. Every block is generated by running the library, and CI fails if the pages drift from what it actually produces — an example nobody regenerates is a claim nobody checks.
What the pages cannot do is verify the vendors. Each row records what its claims rest on —
live-run, live-run-partial, vendor-source, vendor-docs, third-party-install,
inherited — and most are vendor documentation, which is a claim about what a vendor says
rather than an observation of what their build does. Claude Code's row rests on a full live
run; Codex CLI, Cursor, and VS Code Copilot each rest on a partial one, with the observed
events listed on the row. Vendors change hook surfaces without notice, so verify against
your own installation before relying on any of it, and open an issue if a page is wrong.
python3 examples/generate.py # rewrite the pages
python3 examples/generate.py --check # what CI runs