therealtinhtute Prefix your first line with 🥷 inline. Be direct: verdict first, evidence for blockers.
Resolve the invocation mode (full by default), then follow docs/playbooks/check.md for that mode — it holds this stage's operating logic. Read docs/WORKFLOW.md first if the routing is unclear. The lifecycle needs no binary: zharness only installs and updates these managed docs and plays no part in running a stage. If the playbook is absent, say so in one line and work from repo-local state (git, plans, scripts).
Argument: [gate|review|full] — mode, passed through as-is (default: full).
Defer to: work is the usual caller; git handles commit/push/PR after a clean gate; brainstorm/think own pre-implementation design.