jevqueue 0.5.0: explain the plugin to the agent that is using it

A plugin whose only artefact is a README has already failed. The agent does not read READMEs -- it reads what is in its context.

The awareness document. A \SessionStart\ hook (Claude Code, Codex) and a \BeforeAgent\ hook (Gemini) now inject a short document into the session: what the queue is, when to ask it, what to do when it says no, and why it costs no generated tokens. It is short on purpose -- it is paid for in every conversation, including the ones where the queue has nothing to do.

The docs the site was missing. \docs/install.md\ covers installing, enabling, testing and how it gets used, for every agent in the matrix. \docs/benefits.md\ is for the owner of the agent rather than the agent itself: the control-flow problem being solved, what changes, what it costs, and what it saves.

The token numbers are measured, not asserted. On the benchmark's eight-tool corpus:

	Input	Output
A generative router choosing a tool	~674 (schemas + state)	the reasoning tokens to emit a name
The decision layer	215 (state only)	0
A step served from \static_tools\	--	0 -- no model is called

The 460-token gap is the tool schemas: a generative router has to receive every tool definition to choose between them, while the decision layer scores criteria against them so they never enter the context. That gap grows with the size of the toolset.

357 tests, offline.