qualify

# /qualify - Inspect an issue for build readiness Inspect an issue before handing it to build, and return whether to hand it over or fix it first. The conditions that stop build at Load live in build.js, so read them from there at run time. Findings that need a decision come back to the user as questions with a hypothesis attached. ## Input `$ARGUMENTS` is an issue number or URL. If empty, ask for the target via AskUserQuestion. ## Phase 1: Fetch Take the body and labels with `gh issue view <ref> --json number,title,body,labels,url`. If the fetch fails, report the ref and stop. Take the local repository with `gh repo view --json nameWithOwner` and match it against the owner/repo in the url. ## Phase 2: Inspect the plan contract With no `## Plan` section, set the verdict to needs-plan, inspect Verifiable criteria alone among Phase 3's axes, and go to Phase 4. A plan-less issue carries no contract, so Creation collision and Displayed field enumeration have nothing to judge against. The remaining axes are advice, so they leave the next step as it is. Criteria sent on to `/think` while unverifiable become what the plan gets designed against. Under needs-plan the decision to pick it up does not change, while the next step depends on the issue's content. When the acceptance criteria are unverifiable, set the next step to "rewrite the criteria as verifiable before drafting the plan". When the title is `[Bug]` and the body states no root cause, set the next step to "pin down ...