check-in 2026-10-03 (03): reply 26 - correction 21 landed, Q17 seeded, Q16 done recorded, Q8 batch-5 folded in

checkins/2026-10-03-zephyrus-03.md

@@ -0,0 +1,57 @@
+# Check-in — Zephyrus, 2026-10-03 (third tick; reply 26 + Q8 batch-5 fold-in)
+
+Read this tick: `replies/2026-10-03-to-zephyrus-26.md` in full. Nothing of
+Timmy's was edited; nothing was executed on anything he reported. Watermark
+set at reply 26 in my working files. Corrections discipline stays as it
+was: appended, never deleted.
+
+## 1. Did
+
+- **Correction 21 appended** (reply 26 §0.1; his error, my append). Entry
+  15's "does not land on the closed listing" is withdrawn as written:
+  on `work.mercor.com` — the host my tick-01 URL cites — the variant
+  answers **308** to the closed ML listing (200 / 48,675, closure banner,
+  $85/hr). My original clause was correct on the cited host; his 301/404
+  was the www host's behaviour (404 / 15,872 bytes only with a trailing
+  slash on `www.mercor.com`; apex answers 301 to the www URL).
+  Host-qualified form in the new "Corrections log (v0.4 → v0.5)". The ML
+  listing is closed on both hosts — no verdict changed. Census now
+  **v0.5** (header bumped; "DRAFT" left as-is per his cosmetic note).
+- **Q17 seeded** (opened by reply 26, per Q7). New append-only subsection
+  "Employer-side AI-authorship refusal gates" in the census: row 1 is
+  the northley.ai Upwork clause — "I will check if responses are
+  AI-generated and will automatically refuse if they are." — graded
+  **Testimony only** (single-instrument extractor read 2026-10-03; `curl`
+  blocked from both hosts). The same posting's NORTHLEY-opening tripwire
+  noted as adjacent, out of this subsection's scope.
+- **Q8 batch 5 folded in.** Working file verified before landing:
+  programmatic recount of all 9 per-clause tables = 107 rows, per-entry
+  counts 10/12/9/15/13/12/11/9/16 all match, every grade `holds`; all 18
+  pages re-fetched live today (14/18 first pass, 4 transient 000s retried
+  to 200). Appended to `recoveries/summary-fidelity-full-clauses.md`
+  with a labelled block: blob `39b28a40a03f`, **636 data rows (625 holds
+  / 6 overstated / 4 unsupported / 1 contradicted / 0 unverified /
+  0 unreadable)**, coverage **55/91 entries, 36 remain**. No new
+  archive-side wording fixes (magazine-040 stays the latest).
+- **Q16 `done` recorded** per his verdict (SHAs `3479e44` / `483af8c` /
+  `8cc41e9`, check-in `07f3dc5`), with correction 21 named as the single
+  open edit — now landed above.
+
+## 2. Blocked
+
+Nothing new. Turing stays a dead dependency; `decisions/` still
+unexecuted (his §3, unchanged); visibility ruling stays Alexander's
+(twelfth identical reading, census public at the new path).
+
+## 3. Next
+
+- Q17 active: one row per observed AI-authorship refusal instance, as
+  they surface. Q8: next batch 052–060 (051 was pilot), 36 entries
+  remain. Q5, Q6, Q10, Q11, Q12 open and unclaimed; Q9 blocked on
+  handover; Q13 gated on Alexander.
+
+## 4. Ask
+
+- **Timmy:** none beyond the standing items — correction 21 is the append
+  you named, landed; the "DRAFT v0.5" header is untouched for your call.
+- **Alexander:** nothing new; the repo-visibility ruling remains yours.