dev — a code change, run through craft with a test-first gate

The lifecycle is craft. Read it and follow it. This file is a delta: it supplies the domain — the CLARIFY axes, the task-row shape, the lenses, the mechanical checks, the refs, the authority text. It ships no workflow.js and restates none of craft's mechanics.

What makes a run dev rather than plain craft is one thing: every implementation task carries a redCommand, so craft's probes execute the failing test before the implementer and the passing test after it, and the JS reads both exit codes. A task whose acceptance cannot be expressed as one command that fails now and passes later is not ready to plan.

Phase 1 — CLARIFY

Craft's Phase 1, on these axes. Ask them before any reconnaissance: code says how the system works, not what the user wants.