mb-verify — Verifier loop (acceptance → evidence → verdict)

• What it does: checks a completed task against acceptance criteria and records the result with evidence.
• Use it when: implementation is done and you want an explicit PASS, FAIL, or partial verdict.
• Input: TASK_ID, acceptance criteria sources, and the task protocol files.
• Output: verification.md, evidence artifacts, updated task state, and follow-up bugs when criteria fail.

Goal

Independent-ish verification so we don’t “trust without verify”.

Inputs

• TASK_ID (e.g. TASK-123)
• Links to acceptance criteria:
  • .memory-bank/features/FT-* and/or
  • .memory-bank/requirements.md (REQ IDs)
• Link to protocol plan: .protocols/<TASK_ID>/plan.md

Preconditions

• Implementation is done and gates were run (or failures recorded).