Description
Maintainer-local gate, before any other SKT-0168 child lands. The requirements behind SKT-0168 come from a private engagement and name a customer, programme, internal systems, app names, brokers and people. Add those terms to the gitignored scripts/forbidden-words.local (the hosted guard is blind locally without it; see the forbidden-words guard). The term list stays in that ignored file and the maintainer’s private notes, never in a task, commit message or doc here.
Acceptance Criteria
- #1 scripts/forbidden-words.local holds the term list and stays untracked
- #2 A planted term in a scratch tracked file fails the local hygiene leg (red), and removing it passes (green)
Implementation Notes
loop52 (root-only): 54 engagement terms appended to gitignored scripts/forbidden-words.local (backup in session scratch; still git-ignored). Each term pre-scanned against all tracked files with ripgrep (control check proved the scan detects hits) and against decompressed .gz assets: zero hits beyond binary false positives the guard skips; generic vendor words kept as whole-word patterns. Red: scripts/forbidden-words.sh on a scratch file with a planted term exits 1 (two terms tested). Green: full-tree scan exits 0 after removal. No term appears in any task, commit or doc.