fi-deferlisted

<!-- loc-override: generated 1:1 from commands/defer.md by scripts/gen-codex-skills.sh; length is owned by the source command file --> The user wants to defer a `[open]` found-issue. Deferring means: keep the entry visible in `docs/found-issues.md` but suppress it from the statusline counter and exempt it from `[open]`-only checks. The entry stays in the file as a parking-lot record. ## Invocation ```bash found-issues defer <match> [--reason "<text>"] [--mute-until YYYY-MM-DD] ``` `<match>` is a substring matched case-insensitively against the entry's path or symptom. If the match is ambiguous (matches multiple `[open]` entries), the CLI lists all matches and exits 2 — surface them to the user and ask for a more specific match. ## Exit codes — what to tell the user - **0**: Deferred successfully. Print the CLI's stdout (it includes cycle + threshold info). - **1**: No match. The CLI prints the match string; suggest the user check `docs/found-issues.md` or run `$fi-status` for the current entry list. - **2**: Ambiguous match. The CLI lists all matches; ask the user for a more specific substring (e.g., line number, distinctive part of the symptom). - **3**: Already `[deferred]`. The CLI explains the re-defer-after-promote workflow. If the user actually wanted to promote it back, suggest `$fi-promote-deferred`. - **4**: Entry has an active `(PR: ...)` annotation. Deferring would silently drop the entry from both the `issues` and `in PR` counters. The CLI prints the two-opt