π¬ A browser extension and desktop app that turns your clicks into step-by-step guides with annotated screenshots π
TypeScript browser-extensionchrome-extensiondocumentationfirefox-extensionguide-generatorlocal-firstmanifest-v3privacy-firstproductivityreactscreenshotstep-by-step-guidetutorialtypescriptworkflowwxt
docs: record the single-line title invariant
davbiof09e06172874
diff --git a/AGENTS.md b/AGENTS.mdindex 77e5527..07cb113 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -49,7 +49,7 @@ src/β β βββ scrub.ts # scrubValues (removes typed values from prose)β β βββ bundle.ts # exportGuideAsBundle (zip via fflate)β β βββ parse.ts # readBundle (unzip + validate)-β βββ guides/ # Data layer: types, Dexie DB, CRUD service+β βββ guides/ # Data layer: types, Dexie DB, CRUD service, title rulesβββ entrypoints/ # Chrome extension entry points (WXT)β βββ background/ # Service worker: state machine, message handlers, tab managementβ βββ content.ts # Content script: CaptureSession, event listeners@@ -274,4 +274,5 @@ Font: Poppins (loaded via `@fontsource/poppins`).- **Font loading** uses `@fontsource/poppins` (CSP-safe, no CDN dependency)- **Cross-context sync** via BroadcastChannel β star/delete events update other views without full reload- **Bundle export flattens before it ships** β `redact` annotations are drawn at render time, so `screenshot.blob` still holds the unblurred capture. `flattenScreenshot` burns redactions into the pixels and drops the annotation, and bakes an *explicit* crop (rebasing annotations and resolving `bounds` into an explicit target). The automatic zoom-to-target crop stays as data. Anything that ships a screenshot outside the browser must go through the renderer+- **Guide titles are single-line**, normalised by `sanitizeGuideTitle` on every write path: `updateGuideTitle`, `importGuide`, `revertToSnapshot` and the AI meta path. Each renderer downstream already assumed it. The HTML and PDF covers clamp to `MAX_TITLE_LINES`, their running headers to one line, the video cover card wraps to two, the sidepanel truncates, and Markdown writes `# <title>`, where a newline ends the heading and spills the rest into the body. A fifth write path needs the same call. The 70-character cap is a UI affordance only and is deliberately *not* applied on write, so a title recorded before the cap keeps its full text instead of losing its tail to a focus and a blur- **Imports re-mint every id** β `importGuide` mints new guide/step/screenshot ids in one Dexie transaction. Reusing the ids in the file would let a shared guide overwrite one the recipient recorded. It also clears `aiPending`, which no background job will ever resolve for an imported step