warden-sweep: create_issue.py renders empty findings table because verified.jsonl lacks full finding data

[dcramer]

Bug

scripts/create_issue.py in the warden-sweep skill renders an empty findings table in the tracking issue because verified.jsonl only contains verdict metadata, not the full finding details needed for display.

Expected

The tracking issue should show severity, skill, file path, and title for each verified finding.

Actual

The table rows render as:

| info |  | `` |  |
| info |  | `` |  |

All fields are empty because build_issue_body() reads f.get("severity"), f.get("skill"), f.get("file"), f.get("title") from verified entries, but verified.jsonl only has:

{"findingId":"sentry-security-83c8eadd","verdict":"verified","confidence":"high"}

Root Cause

During Phase 2 (Verify), the skill instructions tell the agent to append findings to verified.jsonl with just the verdict data. The create_issue.py script then reads verified.jsonl expecting full finding details (severity, skill, file, title, location) that were never written there.

Fix Options

1. In create_issue.py: Cross-reference verified.jsonl with all-findings.jsonl to merge in the full finding data before rendering the table.
2. In the skill instructions: Tell the agent to write full finding details (merged from all-findings.jsonl) into verified.jsonl during Phase 2.

Option 1 is probably the more robust fix since it keeps the script self-sufficient regardless of what the agent writes.

Workaround

Manually update the issue body after creation using gh issue edit with a body that cross-references both files. This is what I did during sweep run 7d5ea73d.