test - Verification Stage

Invariants

• Verify against the task document acceptance criteria.
• Use the best available project verification path.
• Do not require one specific browser automation tool in core workflow.
• Always write one final report to docs/testing/.
• When tests pass and the user approves, update TASKS.md to Approved and re-read the tracker to confirm the row moved. A stale tracker blocks downstream and headless sessions.

Runtime adapters may expose this stage as a slash command, menu action, or natural-language skill invocation. The portable stage name is test.

Workflow