Albums in the Rust edge, and the batch-counter rule (design 3)

A release the window closed on with one file named by its stem or post, the
name with a number and no archive, volume, sidecar or random name, waits in
the album of its poster and template (the name's digit runs as #, the
extension apart) posted within the window of the album's first file; the
album closes a window after that span and is written as one release
(source album, no file total) named by the members' shared numbers, a lone
member as the release it was. The batch store writes an album's member
names as release_texts kind 6 (member). A counter total of 100 or more under
which one poster started 20 or more releases is a batch counter: those
releases get no file total.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

REBUILD.md

@@ -448,6 +448,23 @@ releases, a third of them one poster's image dump (27.7 M rows, LOG.md
    poster. A counter total shared by many stems of one poster within the
    window is a batch counter, not a file count (Yenc-PP-A&A's [n/68067]):
    `file_total` null for them, not 68,067 incomplete singles.
+   **Built 2026-10-26** (edge/src/indexer.rs, LOG.md (113)): a release the
+   window closed on with one file named by its stem or post, the name with
+   a number and no archive, volume, sidecar or random name, waits in the
+   album of its poster and template (the name's digit runs as `#`, the
+   extension apart: `#_#.jpg.data`) posted within WINDOW_MS of the album's
+   first file, at most ALBUM_MAX_FILES (1,000) a album; the album closes a
+   window after that span and is written as one release (`source: album`,
+   no file total) named by the members' shared numbers (`1481439079025_#
+   .jpg.data`), a lone member as the release it was. The batch store writes
+   the members' names as `release_texts` kind 6 (`member`, the first 20).
+   The directory-like prefix variant is not built (no case seen in the
+   corpus samples). The batch counter: a total ≥ 100 under which one poster
+   started 20+ releases within 100 batches gives none of them a file
+   total. On six a.b.ath ranges of 2016: 46 albums of 790 files among
+   2,099 chunks, most of them a subject parser miss (`[n/60] Shogun I
+   (1980) Shogun I (1980).avi.012`: the counter text taken into the name,
+   a volume each) that the album rule glues back together.
 
 4. **A slimmer catalog.** `releases` loses its text copies: `poster_id` →
    `posters(id)` (the table gets an id; 33 B → 4), `group_set_id` →
@@ -665,9 +682,10 @@ until the window is done (LOG.md 2026-10-26 (111) has the first local
 numbers, (112) the homelab run).
 
 Next: the replay on homelab over the 2016 window (the NVMe bytes per
-header for real), albums in the edge (design 3), the ordered range leases
-with the carried window in the edge-node and its snapshot (design 1 and
-5), the prober writing `release_texts` kind 2. Gone from the list: block
+header for real), the ordered range leases with the carried window in
+the edge-node and its snapshot (design 1 and 5), the prober writing
+`release_texts` kind 2, random-named singles without a chunk (decision f:
+2.3 M of the first replay's 4.0 M singles are "Bob"'s 32-hex posts). Gone from the list: block
 leases, the planner and the block merger (design 1, amended).
 
 ## Decisions