spec-review

# Spec review Independently review a feature specification as a formal contract gate. Produce durable evidence or report blocked recording. Explicit feedback requesting no formal status, readiness, record, or lifecycle use belongs outside `spec-review`. ## Workflow role - role_name: spec-review - stage: review - upstream: feature spec, linked proposal, exploration, research, local contracts, and workflow evidence - downstream: spec revision, review-resolution, architecture, plan, no handoff, and eventual test-spec readiness assessment - summary: Review the feature spec and record approval, changes requested, blockers, or inconclusive state. - ownership: Write formal review evidence and, with exact governed authority, settle only the matching spec entry. Workflow owns routing and continuation. - must_not_claim: architecture completion, plan completion, test-spec completion, implementation readiness, verification, branch readiness, or PR readiness Do not edit the specification unless explicitly asked for combined review and revision. Record first-pass review before any authorized correction. ## Invocation classification Classify before conditional loading or mutation. Settlement mode is exactly `isolated` or `governed-spec-entry`; governed mode requires one current `stage-owned-change-local-v1` change, specification, and matching reviewable entry. Recording and direct wording never grant governed authority. Automation mode is exactly `manual` or `workflow-managed-automat...