Product Documentation Refresh

Wiki manual chapters updated, both print PDFs re-rendered, verified, versioned, and published to the product docs folder

Inputs

    What BOB Does

    1. obsidian-markdown → when chapters were added/removed/renumbered, update the manual index note, the print-source cover TOCs, and the `getting-started` chapter picks in `docs/manual-assembly.yaml`
    2. branded-pdf (assemble-source) → `--check` for staleness, then rebuild both print sources from the wiki chapters, bumping `--set-version manual=X.Y` / `--set-version getting-started=X.Y` for each changed document
    3. branded-pdf (cover-pdf) → render both print sources to /tmp proofs
    4. branded-pdf (cover-pdf) → verify proofs against the route's acceptance criteria: sane page count, cover + doc-info, running `Page X of Y` footers, no `missing embed` markers, spot-read the changed chapters
    5. Review the proofs — especially chapters touched in step 1 — and approve
    6. vault-release → publish approved proofs to `20-COMPANY/40-PRODUCTS/thirdbrain-bob/docs/` as `-v{RELEASE}.pdf` — the **vault release version they ship with**, not a per-document version — and delete superseded version PDFs (close open viewers first — drvfs locks)

    Outputs

      Time Savings ~30-90 minutes depending on content changes manual → automated with agent assistance
      Try It "BOB features, skills, or workflows changed and the shipped User Manual / Getting Started Guide no longer match the product, or a release is being prepared"
      Compounding Each run refines templates and context — 5 automated steps improve with accumulated data