melech-debug-mode

# Debug Mode Follow this protocol for the user's requested workflow: ```text choose browser driver → attach if autopilot → define one complete attempt → start collector → add probes → prove probes loaded → run E2E → read evidence → act on evidence → rerun E2E if code changed → clean up ``` The E2E boundary is the local UI in a browser. A unit, integration, AI, or test-harness run never counts as E2E, even when it uses a real model, tool, sandbox, filesystem, or backend. Neither does a direct call, script, synthetic request, or isolated endpoint. Do not create or run a test harness before the first browser attempt. Tests and direct calls are supplemental diagnostics only after browser reproduction. If the requested behavior cannot be exercised through a local UI, say this skill does not provide its E2E path; do not relabel a harness as E2E. ## 1. Choose The Driver - Use **autopilot** by default for every local UI workflow. - User explicitly says they will drive, hold the wheel, or use `proceed` → **manual**. - The user denies browser control, the target tab is ambiguous or unsafe, the target appears to be production, or attach remains unavailable after retry → **manual**. Do not ask the user to choose for an ordinary local UI. For autopilot, read the installed `melech-live-browser/SKILL.md`, show its Chrome consent notice, and begin its attach flow before any diagnostic shortcut. If it is missing, offer: ```bash npx skills add https://github.com/AdirD/agent-shel...