triage-findingslisted

# Interactive Finding Triage Start an interactive triage session for review findings. The user classifies each finding in a browser UI, and decisions are written back to the report JSON. **Argument**: `$ARGUMENTS` — path to the `report.json` file produced by `grumpy-review` or `check-pr-comments`. ## Workflow 1. Validate the report JSON against the schema: ```bash python3 ${CLAUDE_SKILL_DIR}/../../scripts/validate_report.py "$ARGUMENTS" ``` Requires `python3-jsonschema` (`apt install python3-jsonschema`). If validation fails, fix the JSON and re-validate before proceeding. Do NOT start the triage server with invalid data. 2. Start the triage server (default port 8741): ```bash python3 ${CLAUDE_SKILL_DIR}/../../scripts/triage_server.py "$ARGUMENTS" [--port PORT] ``` The server auto-opens a browser. If that fails, it prints the URL for the user. 3. Wait for the user to complete triage in the browser and submit decisions. The server writes the `triage` field back into the report JSON and exits. ### Killing a stuck server The server normally shuts itself down when the user submits with `complete=true`. If it gets stuck, kill it by port — **never use `pkill -f`** (risks killing servers from other sessions): ```bash fuser -k 8741/tcp # kills whatever is bound to port 8741 ``` Replace `8741` with the actual port if `--port` was used. 4. Read the updated report JSON. Summarize the triage results: - How many findings were triaged -