[KodeStar]

Bridge Phase 1c: own-words descriptions. Pairs with KodeStar/audiosilo-bridge#4, KodeStar/audiosilo-server#148, KodeStar/audiosilo-frontend#111 and the workspace PR (docs/bridge-1c).

User Guide

• Generating characters and recaps: a new "A description for the book" section (spoiler-free, own words, kept on this server, never holding up the job, where it shows) and "Writing a description for an older book" (when the console offers it, the kept notes, no new transcription, the small cost, the failure reasons). The files list gains description.json, the progress gains "Writing the description", the notifications gain "Description ready".
• The book page: the About order (community, the book's own, the work's, generated with its mark, the fallback sentence), with a new screenshot. The old line saying a description can come from tags was wrong (the server reads none from tags) and is reworded.
• Small updates to Books, The Bridge, Notifications and Recaps and characters.

Developer Docs

• The .audiosilo folder: description.json (format, checks, signature order, migration 0050), bridge.json's description object, the second save, a kept description's provenance, the rescan answer.
• Generating: the description step (the opening-notes spoiler bound, chapter_positions.json, the voice rules, the n-gram check and checked_against, running at contributing so an ebook is checked against its text) and sidecars.describe.
• API reference: /meta's work.generated_description and generated.description, the unmatched description-only answer, sidecars.describe and 409 generate_open, the estimate's can_describe and has.*.description, the admin book detail's generated_description, the rescan answer.
• Data model (0050), scanner, web UI (the console's Description part), notifications, the player's book page and data flow, the cross-repo contract, and the change-to-page map.

Screenshots

• New: admin/book-description.png (the Community card's Description part) and web-player/book-about-generated.png (About with the "Generated on this server" chip). run.sh seeds a fixture description.json for The Call of the Wild (step 2b), which no other shot uses.

Test plan

• npm run build