do-investigation-issuelisted

# Post Investigation Issue Creates a GitHub issue that captures an unverified finding and hands it off to a future investigator with enough context to start immediately. The issue does NOT require a confirmed defect — it exists to trigger investigation. ## Label Policy - **Always add:** `investigation` - **Never add:** `bug`, `feature`, or any other label unless the finding already confirms it - `bug` is added later by the investigator if root-cause analysis confirms a defect ## Title Format ``` Reliability risk: {component} — {brief one-line description} ``` Use `Reliability risk:` for session/agent reliability findings. Use `Integration failure:` for observed (not hypothetical) integration outages. Use `Gap:` for missing capabilities surfaced by research or audits. The component is the system area (e.g., `worker`, `nudge loop`, `session executor`, `bridge`). ## Body Template Load [TEMPLATE.md](TEMPLATE.md) as the body skeleton. Fill every section — leave no section empty or as a placeholder. If a section genuinely has no content, write one sentence explaining why (e.g., "None — proactive investigation, no remediation attempted yet."). ## Quick Start ### Step 1: Collect the finding Identify: - **Component** — which part of the system is affected - **Symptoms** — what was observed or what the research describes - **Evidence** — raw output, error strings, quotes from source material, or code references - **Impact** — what breaks or degrades if this is a real defect