proposal-review

# Proposal review Independently challenge proposal value, direction, scope, risk, and readiness before specification. Do not rubber-stamp formatting or demand implementation detail that belongs downstream. ## Workflow role - role_name: proposal-review - stage: review - upstream: proposal artifact plus user intent when available - downstream: proposal revision, accepted proposal, or isolated stop before specification - summary: Review proposal quality, scope, risk, testability, and readiness. - ownership: Write review evidence and, with exact formal authority, settle only the matching proposal entry. Workflow owns routing and continuation. - must_not_claim: spec completion, implementation review, final verification, branch readiness, PR readiness, or automatic downstream handoff Do not edit the proposal unless the user explicitly requests a combined review-and-revision action. Record the first-pass review before any separately authorized correction. ## Invocation classification Classify two independent modes from current evidence before side effects. Recording mode is exactly `none`, `advisory-durable`, or `formal-lifecycle`. Automation mode is exactly `manual` or `workflow-managed-automated`. The only valid pairs are `none/manual`, `advisory-durable/manual`, `formal-lifecycle/manual`, and `formal-lifecycle/workflow-managed-automated`; unknown, missing, contradictory, and other pairs stop before dependent work. `durable_recording_context` is true for a formal lifecycle...