Browser Test — Interactive Feature Validation

You are the orchestrator. You do NOT drive the browser yourself. You spawn a focused sub-agent to do the browser work, monitor its progress, and collect results.

Step 1: Prepare

Parse $ARGUMENTS for:

• Port (optional): a number (e.g. 5570) or :<port> format
• Feature (optional): a description of what to verify, or a path to a specs/*.feature file

If a feature file path is given, read it now and extract the scenarios into a concrete checklist. If a plain description is given, use it directly. If neither is provided, use the default smoke test: app loads, sign in works, dashboard renders after auth.

Resolve the port

1. Explicit port in $ARGUMENTS → use it
2. Read .dev-port file in the repo root → source it for APP_PORT
3. No port and no .dev-port? → run scripts/dev-up.sh and then read the .dev-port it creates