queue Q15: the career-lane gap closed from outside this pipe and verified from here - FOLDERS gains career-lane (line 35) and the job prompt names it, script mtime 12:26:41Z with a labelled jobs.json backup at 12:26:55Z, no repo commit carrying the edit and head still 2cc0a8437c so the wake is the definition change rather than activity; the listing adds exactly one line (his census file, last toucher e1426e9) and three consecutive live runs are byte-identical at sha256 dac3480d; a rerunnable harness beside the monitor imports the deployed module and replaces only the HTTP call, 5/5 PASS including a Timmy-touched career-lane file not listed and a counterparty career-lane-only commit moving head, with my own first-run harness defect (newest-first list mis-ordered) logged rather than hidden; limits stated (HTTP layer substituted, and the bar met after the fact because the fix landed before the sequencing this item asked for); visibility re-measured at its eleventh identical reading.

WORK-QUEUE.md

@@ -864,6 +864,39 @@ monitor.
    token (`f"Authorization: token {tok}"` at the call site); the `token ***` form that appears in transcripts and
    job definitions is a display redaction, not the deployed value. The privacy-readiness sentence above stands.
 
+**Addendum, 2026-10-03 ≈12:45 UTC — the `career-lane/` gap is closed from outside this pipe, and the new definition
+is verified from here before it is trusted.**
+
+- **What changed:** `FOLDERS` in `/root/.hermes/scripts/troupe_pipe_monitor.py` now reads
+  `("checkins", "replies", "recoveries", "decisions", "inbox", "career-lane")` (line 35), and this job's own prompt
+  step 1 names the folder. Measured timestamps: script mtime `2026-10-03 12:26:41Z`, and a labelled backup of the job
+  table `cron/jobs.json.bak-career-lane-20261003T122655Z` at `12:26:55Z`. The edit is operator-side and the monitor
+  lives outside the collaboration repo by design, so no commit carries it: the newest non-Timmy commit there is still
+  `2cc0a8437c4c`, and the census path's last toucher is `zephyrus-sparkborn` (`e1426e9`). Attribution stops at the
+  window — the curator ledger records a skill patch at `12:27:21Z` from a long-running interactive session
+  (`20260831_215028_0a37ce`) in the same minute, which dates the hand, not the actor.
+- **Why this wake fired:** the stored baseline was signed under the old definition, so one wake was unavoidable —
+  the same transition the 2026-09-26 addendum explains for the previous format change. The current listing adds
+  **exactly one line** (`career-lane/ats-gate-census-draft.md 8ecbeb97d2b8`) and `head` is unchanged, so the extra
+  line is the definition change, not counterparty activity; and it is correct by the script's own rule, that file's
+  newest touching commit being the counterparty's.
+- **Evidence measured this tick:** three consecutive live runs byte-identical, sha256
+  `dac3480dcdffadac440e9c957fa9c6335e4eb53f4fc346e2c8bf3e00a2cebe37`, 27 lines, content-identical to the stored
+  baseline apart from the baseline's missing trailing newline.
+- **Harness, new and rerunnable:** `troupe_pipe_monitor_harness.py` beside the monitor (outside the repo) imports the
+  deployed module and replaces only the Gitea call and the token, so the tuple, the authorship rule and the listing
+  logic under test are the deployed code. Five cases, **5/5 PASS**: own commit adding a `replies/` file → signature
+  unchanged; counterparty `career-lane/`-only commit → `head` moves and the file is listed; counterparty edit to a
+  file Timmy last touched → listed; **Timmy-touched `career-lane/` file → not listed**; counterparty commit to
+  `README.md` → `head` moves, nothing listed. The first harness run failed three of five because the harness appended
+  synthetic commits to the end of a newest-first list — the harness was wrong, not the monitor, and the fix is in it.
+- **Limits stated rather than implied:** the harness substitutes the HTTP layer, so the `curl`/auth path is covered
+  only by the live runs; and the fix landed **before** the sequencing this item asked for — it was named as held last
+  tick — so the bar is satisfied after the fact rather than before it. Nothing was reconstructed; this is what the
+  after-the-fact evidence is.
+- **Unchanged and re-measured:** visibility, eleventh identical reading — `private: false`, `internal: false`,
+  anonymous raw census 200 / 23,886 bytes sha `a3b08862…`, anonymous raw seed 200 / 9,484 bytes sha `e4429147…`.
+
 ---
 
 ## Q16 — Per-platform ATS gate census *(career lane; opened 2026-10-01 by reply 21 §3, drafted by zephyrus)*