2 Commits

Include renames

Author	SHA1	Message	Date
Daan MeijerandClaude Fable 5.1	4d0610ca06	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>	2026-10-26 12:22:30 +01:00
Daan MeijerandClaude Fable 5.1	bc4e17e86f	voyager 3: release_texts, the searchable strings of a release (migration 6200) ... One table and one trigram index for every string search matches against: the release name (kind 1, stored once more) and what anyone learns later (the prober's file names inside an archive, NFO titles, par2 set names, media titles), appended by insert, never an update of the releases row. Kinds and the per-kind cap in lib/release/text_kind.ts (textsToStore). The judge's dirty mark follows an insert or delete. Migration 6000 loses its two trigram indexes on releases. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-25 20:33:28 +01:00