name	issues-clarify
description	Re-derive and repair the ThreatForge GitHub board after roadmap or code drift

Issues clarify

Run as an explicit maintainer-requested board maintenance pass.

Record the current main commit and all open PRs for a reproducible snapshot.
Discover Project 2 fields/options dynamically.
Review every non-Done issue against current code, merged work, open PRs, parent initiatives, dependencies, and roadmap direction.
Identify obsolete, duplicate, compound, blocked, or wrongly prioritized work, and work whose Effort no longer matches the reasoning it actually needs. Raise an understated Effort before acting on the issue: cryptography, the IPC boundary, the .thf schema, and trust boundaries are High however small the diff looks.
Preserve Backlog for genuinely unshaped reports.
Split compound executable work into native sub-issues; a High issue stays the parent of the sub-issues it decomposes into.
Ensure exactly one autonomy label and explicit acceptance/dependency state.
Mutate one item at a time, read it back, and leave a concise reason for material changes.
Report the snapshot, changes, unresolved decisions, and remaining drift.

Do not alter repository code or invent product decisions.

name	issues-clarify
description	Re-derive and repair the ThreatForge GitHub board after roadmap or code drift

Run as an explicit maintainer-requested board maintenance pass.

Record the current main commit and all open PRs for a reproducible snapshot.
Discover Project 2 fields/options dynamically.
Review every non-Done issue against current code, merged work, open PRs, parent initiatives, dependencies, and roadmap direction.
Identify obsolete, duplicate, compound, blocked, or wrongly prioritized work, and work whose Effort no longer matches the reasoning it actually needs. Raise an understated Effort before acting on the issue: cryptography, the IPC boundary, the .thf schema, and trust boundaries are High however small the diff looks.
Preserve Backlog for genuinely unshaped reports.
Split compound executable work into native sub-issues; a High issue stays the parent of the sub-issues it decomposes into.
Ensure exactly one autonomy label and explicit acceptance/dependency state.
Mutate one item at a time, read it back, and leave a concise reason for material changes.
Report the snapshot, changes, unresolved decisions, and remaining drift.

Do not alter repository code or invent product decisions.

issues-clarify