Verify an Angular Feature

Adapted from Vercel's dogfood: checks a bounded feature against acceptance criteria using available Chrome tools, replaces issue quotas with coverage, and preserves the user's browser and server sessions. Upstream license: references/LICENSE.txt.

1. Define what must work

Read the task, approved design, or relevant acceptance criteria and the project's browser rules. Identify the target route, changed behavior, and relevant user state. If criteria are implicit, derive a small list of observable outcomes and state those assumptions. Ask only when an unresolved choice would materially change what counts as correct.

Prepare a compact coverage table: criterion, action, expected result, observed result, status, evidence. Use pass, fail, blocked, or not tested; empty evidence is never a pass. Keep exploration within the feature and its directly affected flows.

Done when the target and observable acceptance criteria are explicit.