[KodeStar]

Bridge Phase 1c (BRIDGE-PLAN.md): generated descriptions in .audiosilo/, /meta and the console.

What it does

• description.json as a known attachment (migration 0050): audiosilo-meta model.Description, text trimmed, 200-1500 code points (meta's schema bounds, with a drift test), no control character but a line break. A book without one keeps its stored signature byte for byte. A book with only a description has generated: true.
• /meta: a generated description rides in a NEW additive field, work.generated_description {text}, marked work.generated.description (generated now always carries the three booleans). It never goes into community_description: the shipped 2.0 app shows that first in About, over the book's own description, and credits the community; it ignores the new field. Community wins: filled only when the community work has no community_description. spoilers=hide keeps it; attribution never counts it; an unmatched book with only a description answers {matched:false, work:{..., generated_description}}. /meta now reads only the attachment parts it can fill.
• sidecars.describe (new kind): params {}, 409 generate_open while a generate job is open for the book, its own dedupe; a generate job queued later cancels an open describe job. An older Bridge doesn't advertise it (409 kind_unavailable).
• Estimate: can_describe, has.local.description, has.community.description (the community's community_description or its core description, either shown before a generated one). Admin book detail: generated_description {text, generated_at?}. Rescan answer: attachments.description.
• Console: the book page's Community card gains a Description part (the mark, the text behind Show more, a note when the player shows another description instead) and Write a description (offered only when the player would show it: writable, generated characters or recaps, no description on either side, no open job). Notifications say "Description ready" / "Description failed".

Pairs with KodeStar/audiosilo-bridge#4, KodeStar/audiosilo-frontend#111, KodeStar/audiosilo-docs#141 and KodeStar/audiosilo#62.

Quality passes

• /simplify (2 reviewers): 15 items applied (shared console job pieces, narrow catalog reads, the fill mask, one notification table); skipped a blockedBy kind field (the refusal is generate-specific).
• /code-review max --fix: 15 findings, all fixed with tests. The two it left for a decision were decided in the session: a generate job cancels an open describe job; a core description counts as the community having one.

Test plan

• scripts/build-admin.sh (874 tests), go build ./... && go vet ./... && go test -race ./... && golangci-lint run (0 issues)
• Real stack: /meta for an unmatched generated book (plain and spoilers=hide), the console's book page in headless Chromium showing the Description part.

Left open

• The player can't tell which generated parts a book has (generated is a bool), so a description-only book costs a /meta ask on surfaces that read only characters and recaps; a generated list is a follow-up.