fi-promote-deferredlisted

<!-- loc-override: generated 1:1 from commands/promote-deferred.md by scripts/gen-codex-skills.sh; length is owned by the source command file --> The user wants to promote a `[deferred]` found-issue back to `[open]`. This usually happens after the touch counter has triggered a nudge (3 touches in cycle 1; 6 in cycle 2; etc.) — the deferred entry has been bitten enough times that it warrants real attention. ## Invocation ```bash found-issues promote-deferred <match> # or found-issues promote-deferred --match <match> ``` `<match>` is a substring matched case-insensitively against the entry's path or symptom. Same matching rules as `defer`. ## Exit codes — what to tell the user - **0**: Promoted successfully. Print the CLI's stdout. All annotations (touch history, defer-cycle, reason) are preserved as evidence on the now-`[open]` entry. - **1**: No `[deferred]` match. The user might have already promoted it, or the substring doesn't hit anything. - **2**: Ambiguous match. List the matches and ask for a more specific substring. - **3**: Match hits an `[open]` entry, not `[deferred]`. The user may have meant to promote a different match — suggest `$fi-status` to see the current state. ## When to use promote-deferred - **Threshold nudge fired** in your `found-issues log` output: "Touched deferred entry (now Nx, threshold N)" → promote and address. - **Manual re-evaluation** during periodic review of the deferred parking lot. - **Critical [!] auto-promotion is reserved for t