fix(evaluation): update stale Language Gate preamble to reflect tracking

04-job-evaluation.md still said the gate result "is not a field /scrape
or /rank track" - true when the gate was introduced, false since /rank
began persisting language_gate/language_note as shortlist veto fields
and /scrape began surfacing the flag. The authoritative framework file
taught agents the opposite of rank.md's own persistence rule. New
coupling test pins that the section names the tracked fields and never
reverts to the untracked claim. framework_version 1.2.3 -> 1.2.4.
Review finding F24 (2026-08-19).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

CHANGELOG.md

@@ -56,6 +56,14 @@ per-file diff commands.
 
 ### Fixed
 
+- **Language Gate preamble no longer claims the gate is untracked** (`framework_version`
+  1.2.3 -> 1.2.4 in `04-job-evaluation.md`) - the paragraph still said the result "is not
+  a field `/scrape` or `/rank` track", written before the gate was wired into both
+  consumers. An agent reading the authoritative framework file learned the opposite of
+  what `rank.md` itself insists on ("These veto fields are as important to persist as
+  the score itself"). The preamble now names `language_gate`/`language_note` and how each
+  consumer uses them; a coupling test in `tests/test_rank_command.py` keeps the framework
+  text honest about the tracking.
 - **`/reset documents` now clears `documents/postings/`** - the drop folder for
   hand-pasted job posting text was absent from the preview, the delete block, and the
   user-facing scope description, after which the command told the user "The `documents/`