Skip to content

Bridge 1c: the book page's About shows a generated description - #111

Merged
KodeStar merged 3 commits into
mainfrom
feat/bridge-1c
Oct 17, 2026
Merged

KodeStar merged 3 commits into
mainfrom
feat/bridge-1c

Conversation

@KodeStar

@KodeStar KodeStar commented Oct 16, 2026 •

Copy link
Copy Markdown
Owner

Bridge Phase 1c (BRIDGE-PLAN.md): the book page's About shows a description generated on this server.

What it does

  • Types: BookMetaWork.generated_description?: {text}, BookMetaGenerated.description? (optional: a 1a/1b server sends neither), plus the 1c estimate and result fields mirrored.
  • aboutContent(book, work, recording, t): the community description, else the book's own description, else the work's core description, else the generated one (with the "Generated on this server" chip, no attribution, no "Improve this"), else the fallback sentence. It is fed the bookMetaWork value, so an unmatched book's generated work counts. BookAbout takes work as a required prop (the React Compiler memoises it again).
  • The Bridge's describing stage is worded (six locales); a finished sidecars.describe job refreshes the book's /meta.

Older servers send none of it, and the About card reads as before. Pairs with KodeStar/audiosilo-server#148, KodeStar/audiosilo-bridge#4, KodeStar/audiosilo-docs#141 and KodeStar/audiosilo#62.

Quality passes

  • /simplify: one source per work field (applied); the client pass-through test kept per the workspace rule.
  • /code-review max --fix: 15 findings, 13 fixed (the compiler bailout, the stage word, the /meta refresh, the shared chip test id, mirrored fields, stale docs, the offline harness). Two need the server to say which generated parts a book has: noted in the plan.

Test plan

  • npx tsc --noEmit && npm run lint && npm run format && npm test (409 suites, 4907 tests), npx expo export -p web
  • Real stack: the web player's About in headless Chromium showing a generated description with its mark.

The /meta work gains generated_description ({text}) and generated.description,
both optional (a 1a/1b server sends neither). aboutContent orders the text:
community > the book's own > the work's core > generated > the fallback
sentence, and says when the generated one is shown. BookAbout then wears the
"Generated on this server" mark under its eyebrow, with no community credit
or Improve this. The book page passes bookMetaWork, so an unmatched book's
generated description shows too. The offline companion keeps the field.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant