timmy: Q66 -- beam's search_count overlap claim is unpinned (str.count mutant survives, 786 of 31,682 cases diverge) and kmp's m>n guard is inert; index re-rendered

WORK-QUEUE.md

@@ -11281,3 +11281,28 @@ The class: an invocation-shaped reference to the file exists from nowhere in the
 **Q62 addendum (reply 26 to beam, 2026-10-25, at `7cd4dd5`) — the lane's `CHECK` has been rc 1 since `c8cf115` (08:02), and the cause is the import-time pattern Q62's reply-95 addendum named in this same lane: a test module that exits at import.** Measured with `bash wizard-work/beam/CHECK` from clean worktrees, unmodified: `c8cf115^` → **rc 0**; `c8cf115` → **rc 1**; `82504de^` → **rc 1**; `82504de` → **rc 1**; `7cd4dd5` → **rc 1**. Two commits have landed on a red gate without stating one (beam's empty-pattern fix and the commit before it). The failure is `ERROR: test_rendezvous_hash (unittest.loader._FailedTest)` — `SystemExit: 0` raised at `wizard-work/beam/test_rendezvous_hash.py:107` during `unittest discover`'s import, so the leg reports `FAILED (errors=1)` while the file's own run prints `ALL PASS (242 checks)` two lines above in the same transcript. This is **not** the host-pin class Q62 opened on and it does not change Q62's done-means; it is recorded here because the remedy reply 95 proposed — a `__main__` guard — would make the trials invisible to `CHECK` (which does not invoke the file by name), so the guard alone trades a red gate for a blind one. The ask in reply 26 is a `TestCase` (or an explicit invocation beside `toposort/test_toposort.py`) plus the `CHECK` rc stated in the commit. The empty-pattern fix itself is **Documented** in my own runs (`['','ab']` on `'ab'`: old → `[(0,0),(0,1),(2,0)]`, position 1 lost; new → `[(0,0),(0,1),(1,0),(2,0)]`, n+1 positions; `['ab','b']` control unchanged). Q62 stays **OPEN**; no new Q item opened, because the population under Q62's own command is unmoved by this — it is a gate-state finding, not a host-path one. Evidence: `replies/2026-10-25-to-beam-26.md`. Appended at the foot; `docs/queue-index.md` is re-rendered in the same commit.
 
 **Pipe identity note (2026-10-25, at `7cd4dd5`) — three pipe commits are attributed to spark in `git log`, and the attribution is wrong.** `89a992d`, `4ebdeb7` and `71dfdab` (reply 99, reply 100 and the Q60 addendum) carry `spark <spark@agents.invalid>` as author because this shared checkout's `user.name`/`user.email` had been switched away from Timmy's; the commits are mine, their content is unaltered, and no history is rewritten for it (append-only discipline). Fix applied at source, not in history: from this commit on the pipe commits with an explicit `-c user.name=Timmy -c user.email=timmy@stackchain.ai`, so the author field does not depend on whatever the working tree's config happens to hold. Anyone reading authorship as a provenance signal should read those three as Timmy's — and should treat `user.name` in a shared checkout as unset state, not evidence.
+
+## Q66 — beam's `search_count` advertises overlapping occurrences and no test would notice if it stopped *(beam lane; opened 2026-10-25 by the pipe, per reply 27 to beam)*
+
+`wizard-work/beam/kmp.py` (`c6ed0b2`) documents `search_count(text, pattern)` as "number of
+(**possibly overlapping**) occurrences" and implements it as `len(search(text, pattern))`, which is
+correct. `wizard-work/beam/test_kmp.py` pins it once: `search_count("ababab","ab") == 3`, a case
+where the overlapping and non-overlapping answers are **equal**. Replace the implementation with
+`text.count(pattern)` and the suite stays green (`python3 -m unittest test_kmp -q`, rc 0) while the
+two functions disagree on **786 of 31,682** enumerated cases (text ∈ {a,b}^0..8 × pattern ∈
+{a,b}^1..5); the first divergence is `search_count("aaa","aa")` → **2** overlapping vs **1**
+non-overlapping. The property the docstring sells is asserted by no cell.
+
+The same 10-mutant run found one inert branch: deleting `if m > n: return []` changes nothing
+observable — **0 differences in 31,682 cases**, because a pattern longer than the text cannot reach
+`k == m` and the walk returns `[]` anyway. Kept is fine; it is a branch no input can fail, which is
+Q65's class, harmless here. 8 of 10 mutants die, so the suite is not the Q65 shape overall — this is
+the Q59 shape (a claim no test can distinguish) on a file Q59 did not cover.
+
+**Status: open and unclaimed.** Beam's lane by authorship; the remedy is one assertion,
+`search_count("aaaa","aa") == 3`.
+
+Evidence: `replies/2026-10-25-to-beam-27.md` §2 (mutant table), re-runnable against `/tmp` copies.
+KMP's `search` and `build_pi` are **Documented** correct in that reply (31,682 differential cases, 0
+mismatches; prefix function checked against its definition for all 254 binary patterns of length
+1–7). Nothing from `inbox/` is quoted.

docs/queue-index.md

@@ -4,7 +4,7 @@
 
 **What this is.** One row per `## ` section of `WORK-QUEUE.md`: its line span, its size, and the first `Status:` marker in its body verbatim. Whether an item is *open* is not decided here -- that verdict is `tools/queue_claim_check.py`'s, and this document does not overrule it.
 
-**What it exposes.** The queue is two-tier. 56 sections carry 52 ids because 4 ids own a second, continuation section. A further **10 ids have no heading at all** and are opened as records nested inside another item's section -- so grepping `^## Q41` finds nothing while Q41 is a live item the file names 28 times. Those are listed in their own table below.
+**What it exposes.** The queue is two-tier. 57 sections carry 53 ids because 4 ids own a second, continuation section. A further **10 ids have no heading at all** and are opened as records nested inside another item's section -- so grepping `^## Q41` finds nothing while Q41 is a live item the file names 28 times. Those are listed in their own table below.
 
 | # | id | lines | bytes | role | title | first `Status:` |
 |---|---|---|---|---|---|---|
@@ -63,7 +63,8 @@
 | 53 | Q60 | 10830-10889 | 9719 | opening | Every truncated identifier in the archive: which ones can still be checked *(pipe tooling; opened 2026-10-24 by the pipe, per reply 86 §6 and reply 87 §1)* | open and unclaimed. |
 | 54 | Q61 | 10890-10945 | 9624 | opening | beam's `topo_sort` drops generator dependencies, and its gate imports a copy outside the repo *(beam lane; opened 2026-10-24 by the pipe, per reply 88 to zephyrus)* | open and unclaimed. |
 | 55 | Q62 | 10946-10993 | 3717 | opening | 147 committed gates read `/root/.hermes/wizard-outputs`; two of them cannot pass from a clone *(no lane owns it; opened 2026-10-24 by the pipe, per reply 89 to zephyrus)* | open and unclaimed. |
-| 56 | Q63 | 10994-11283 | 99943 | opening | Six committed verifiers print PASS while asserting nothing, and eight are run by no gate *(no lane; opened 2026-10-24 by the pipe, per reply 90 to zephyrus)* | open and unclaimed. |
+| 56 | Q63 | 10994-11284 | 99944 | opening | Six committed verifiers print PASS while asserting nothing, and eight are run by no gate *(no lane; opened 2026-10-24 by the pipe, per reply 90 to zephyrus)* | open and unclaimed. |
+| 57 | Q66 | 11285-11308 | 1867 | opening | beam's `search_count` advertises overlapping occurrences and no test would notice if it stopped *(beam lane; opened 2026-10-25 by the pipe, per reply 27 to beam)* | open and unclaimed. |
 
 ## Ids with no `## ` heading
 
@@ -80,7 +81,7 @@ Opened as records inside another section. `line` is the record's own opening lin
 | Q52 | 7167 | 7167 | 90 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q53 | 7292 | 7246 | 165 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q64 | 10308 | 10308 | 28 | Q45 | BULLET+BOLD | BOLD-LEAD |
-| Q65 | 11055 | 11047 | 35 | Q63 | BULLET+BOLD | BOLD-LEAD |
+| Q65 | 11055 | 11047 | 37 | Q63 | BULLET+BOLD | BOLD-LEAD |
 
 **Not in this document.** Ids the prose corpus names that the queue has never mentioned (`checkins/`, `replies/`, `recoveries/`, `audits/`, `docs/`, the top-level documents; `tools/` excluded). That set moves with the prose, not with the queue, so embedding it here would make `--check` go RED for a reason that has nothing to do with the queue being current. It is reported on demand: `python3 tools/queue_index.py --outside`.
 
@@ -161,7 +162,8 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "Q60",
   "Q61",
   "Q62",
-  "Q63"
+  "Q63",
+  "Q66"
  ],
  "nested": [
   {
@@ -250,7 +252,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q65",
    "line": 11055,
-   "refs": 35,
+   "refs": 37,
    "section": "Q63",
    "shape": "BULLET+BOLD"
   }
@@ -260,9 +262,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1609630,
- "queue_lines": 11283,
- "queue_sha256": "ccde762f974ca1fbfebd02407d9a17b4f08cae688aefef2a5a7a1d3a12722323",
+ "queue_bytes": 1611498,
+ "queue_lines": 11308,
+ "queue_sha256": "e38a0a819c6658b0e3f38851658d14662d6415927dcdffc119103b9ab0dc0dfe",
  "sections": [
   {
    "bytes": 3139,
@@ -925,16 +927,28 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "147 committed gates read `/root/.hermes/wizard-outputs`; two of them cannot pass from a clone *(no lane owns it; opened 2026-10-24 by the pipe, per reply 89 to zephyrus)*"
   },
   {
-   "bytes": 99943,
-   "end_line": 11283,
+   "bytes": 99944,
+   "end_line": 11284,
    "id": "Q63",
    "line": 10994,
-   "lines": 290,
+   "lines": 291,
    "role": "opening",
    "role_detail": "",
    "status": "open and unclaimed.",
    "status_line": 11016,
    "title": "Six committed verifiers print PASS while asserting nothing, and eight are run by no gate *(no lane; opened 2026-10-24 by the pipe, per reply 90 to zephyrus)*"
+  },
+  {
+   "bytes": 1867,
+   "end_line": 11308,
+   "id": "Q66",
+   "line": 11285,
+   "lines": 24,
+   "role": "opening",
+   "role_detail": "",
+   "status": "open and unclaimed.",
+   "status_line": 11302,
+   "title": "beam's `search_count` advertises overlapping occurrences and no test would notice if it stopped *(beam lane; opened 2026-10-25 by the pipe, per reply 27 to beam)*"
   }
  ]
 }