file-tech-debtlisted

# File a tech-debt issue This skill is the single source of truth for turning one out-of-scope finding (a real problem spotted while reviewing something else, and therefore not fixed in place) into a durable, deduplicated GitHub issue. It covers building the key, checking for a prior match, filing when there is none, and nudging the debt-count display to refresh. It does not decide *which* findings are out-of-scope, does not classify security-sensitivity, and does not fix anything, it only files. **Callers own their own bookkeeping around this recipe.** Some callers record their own disposition-ledger entry and gate their own downstream state on it after filing succeeds; others file and stop. That bookkeeping is caller-specific and lives in the caller, not here. Follow the steps below exactly as written; do not invent a bookkeeping record, a completion flag, or a run-tracking step of your own on top of them, that would duplicate (or fight with) whatever the caller already does. ## 1. Build the dedup key Every filed issue's body carries exactly one dedup-key line: a single HTML comment, byte-for-byte in this form: ``` <!-- gaia-debt-key: v1 class=<finding_class> path=<repo-relative-posix-path> line=<integer> --> ``` - `v1` is the schema version. Bump it only for a breaking change to the key's shape, not for routine use. - `<finding_class>` is the finding's seeded class, or `holistic/unclassified` when the finding maps to no seeded class. - `<path>` is a repo-relative POS