fix(hooks): keep the heavy verify lanes off the push path

`orly gate pr` runs the whole declared verify set, so wiring it into pre-push
put `make memleak` and `make test-integration` back on every push — the two
lanes this hook's own header says were moved to Continuous Integration (CI)
because they held the Secure Shell (SSH) session open for 15-20 minutes and
github.com dropped the connection at pack-write time. A push spent nine
minutes inside the gate with `make memleak` still running before this was
caught.

Pre-push now runs `orly gate work`: branch shape, tree state, declared
commands, and nothing that executes a test. `orly gate pr` moves to
CHORE(close), immediately before `gh pr create`, which is the boundary it
grades and the point where paying for the full sweep is the whole idea.

Both hooks pass `--accept-dirty`. A commit hook's tree is dirty by
construction, and at push time the commits are what travel — a scratch file in
the working tree is not part of the push. The tree criterion still binds where
it means something, in `orly gate pr`.

AGENTS.md records the split, so the next session reads it as a rule rather
than rediscovering it from a stalled push.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>