slang-packlisted

# Build the slang pack You are rebuilding `data/pack.json` — the vocabulary layer every other skill in this plugin reads. Quality here determines quality everywhere else. This is a maintainer tool: run it from a checkout of the repository, not from an installed copy. Every path below is relative to the repository root, and `data/SCHEMA.md` plus `scripts/validate_pack.py` should both be visible from there. If they aren't, stop and say so — you cannot write the pack without knowing where it lives. Read `data/SCHEMA.md` before starting, and [`reference.md`](reference.md) for the source playbook and the search angles. **Default scope:** refresh the English pack (`data/pack.json`) and add what's new. If the user names a locale, work on that pack instead — German lives in `data/pack.de.json` and has its own source playbook in [`reference.md`](reference.md). A new locale means a new `data/pack.<locale>.json`; the validator picks it up automatically. ## The core idea A term's status is not one value. It has two, and they diverge: - **`youth_status`** — do young people still actually say this? - **`adult_read`** — does it still sound modern to someone over 30? The gap between them is the entire product. A term young people abandoned last year but adults still hear as cutting-edge is the funniest possible output, because it's the exact sound of someone trying too hard. That's the `cringe-zone` band, and it's the default for `/slangify`. So: **you are not filtering for freshnes