debug-instance

# Debug Running Kandev Instance Diagnose issues in a running kandev development instance by fetching structured logs and optionally inspecting the UI via an existing Playwright browser session. ## Immediately: Create Task Pipeline As soon as this skill is invoked, create a task list to track progress: 1. **Detect running instance** — probe health endpoint, determine ports 2. **Fetch & analyze backend logs** — get debug export, summarize errors 3. **Browser inspection** (if UI-related) — check for existing playwright session, inspect DOM/console 4. **Diagnose & report** — correlate findings, present root cause hypothesis Mark each task as `in_progress` when starting and `completed` when done. Skip task 3 if the issue is purely backend. --- ## Phase 1 — Detect Running Instance 1. Probe the default backend port: ```bash curl -sf http://localhost:38429/api/v1/system/health ``` 2. If that fails, try ports 38430–38435 (kandev auto-assigns nearby ports if default is busy). 3. If still not found, ask the user which port kandev is running on. 4. Derive the web port: typically `backend_port - 1000` (e.g., 38429 → 37429). ## Phase 2 — Fetch & Analyze Logs **IMPORTANT**: The debug export returns raw JSON. If output appears schema-converted (types instead of values), the response is being compressed by a proxy tool — use `curl` directly or check tool configuration. 1. Fetch the debug export: ```bash curl -s http://localhost:<backend_port>/api/v1/system/debug/expo...