BloomBridge

Use when you need to SEE the result of a BloomBridge conversion in the real Bloom app — start Bloom from the Remote-Reload worktree, attach to its embedded WebView2 over CDP, select a converted book in the Collection-tab preview, screenshot individual pages, trigger a live reload of a re-converted book, and compare Bloom's rendering to the source PDF page images. This closes the loop: convert → view → compare → adjust the BloomBridge code → re-convert.

Use when you need to understand or verify the Bloom book file format — what a valid Bloom book is, its HTML structure, the data div, pages, translation groups, xMatter, origami (split-pane layout), canvas (images/overlays), the appearance system, how styles are defined, and the rule that text carries no inline styling. Points at the spec under docs/bloom-format/ and the `validate` CLI command. Consult it before changing anything that generates or inspects Bloom HTML.

Gmail operations through gog.

Cut a new app release. Commits and pushes any pending changes, then triggers the GitHub Actions release workflow (release.yml), which builds the Windows installer and publishes a GitHub Release — auto-bumping packages/app/package.json's patch version if the current version was already released. Use when the user says "release", "ship a new version", "commit and push a new version", or invokes /release.