promote-remediationlisted

# Promote Remediation to Feature The `bug2feature` skill creates `remediation-*` feature.json files for `kind: 'bug'` submissions. Sometimes a submission was filed as a bug but is really a feature request: the affected code doesn't exist yet, the spec describes a new capability rather than a defect. The triage-time gate in `bug2feature` (section 3a-bis) catches most of these at ingest. This skill handles the residuals: cases discovered later, after the remediation directory already exists. A promotion has four mechanical effects: 1. The directory is renamed from `remediation-{YYYYMMDD}-{slug}` to `{slug}` (a clean descriptive slug: no prefix, no date stamp; or a new slug if you specify one via `--new-slug`) 2. The `id` field inside `feature.json` is updated to match the new directory name 3. The `title` field is reframed (the "Remediation:" prefix, if present, is dropped and replaced with a forward-looking name) 4. The `notes` field is appended with a provenance line so the original bug context isn't lost Cross-references in OTHER features' `dependencies` arrays are also updated so the promoted feature is still reachable by its new ID. The script also warns about (or applies) any cleanup the user should know about; e.g., if the remediation was PARTIAL (some of the original spec already landed in code), the agent suggests narrowing the scope to only the still-pending half. ## Usage ``` promote-remediation <app>/<remediation-slug> [--new-slug <feature-slug>]