melech-debug-modelisted

# Debug Mode Treat the current task as an active debugging session. Diagnose from runtime evidence before proposing a fix. Read [DEVELOPER_JOURNEY_EXAMPLE.md](references/DEVELOPER_JOURNEY_EXAMPLE.md) only for first-use guidance or when user-facing handoff examples are needed; routine runs follow this file directly. Autopilot reproduction composes with the separate `melech-live-browser` skill, which owns browser setup and operation. ## Guardrails - Keep the collector local. Do not enable Portless `--tailscale`, `--funnel`, `--ngrok`, LAN mode, or any other remote exposure. - Never collect credentials, tokens, cookies, authorization headers, personal data, full request bodies, or unrelated application state. Prefer booleans, counts, IDs already safe for development, enum values, and narrow summaries. - Add the fewest probes that distinguish the current hypotheses. Start with at most five unless the control flow genuinely requires more. - Make probes non-blocking and failure-isolated so collector failure cannot alter product behavior. - Mark every temporary edit with `DEBUG_MODE:<session-id>:<probe-id>` and keep a list of touched files for cleanup. - Do not fix the bug before the evidence identifies a cause, unless the user explicitly asks to skip diagnosis. - Stop only this session. Never run `portless proxy stop`, `portless clean`, or broad process-kill commands. - During autopilot, keep browser observations narrow enough to answer the current hypotheses.