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>

tests/unit/release/text_kind.spec.ts

@@ -10,7 +10,7 @@ import {
 
 test.group('release text kinds', () => {
   test('names and codes map both ways; the codes are fixed', ({ assert }) => {
-    assert.deepEqual(TEXT_KINDS, { name: 1, file: 2, nfo: 3, par2: 4, media: 5 })
+    assert.deepEqual(TEXT_KINDS, { name: 1, file: 2, nfo: 3, par2: 4, media: 5, member: 6 })
     for (const [name, code] of Object.entries(TEXT_KINDS)) {
       assert.equal(textKindCode(name), code)
       assert.equal(textKindName(code), name)