SQLR-41 — Tauri 2 + Svelte 5 local-first journaling example app

[joaoh82]

Summary

Closes SQLR-41. Adds a polished example app under examples/desktop-journal/ — a markdown daily-notes desktop product backed by a single .sqlrite file. Showcases Phase 8 BM25 full-text search with hit highlighting, the engine's ask feature in a non-AI-native product context, and the Tauri-friendly Arc<Mutex<Connection>> embedding pattern using the modern Connection API.

This is the third in the SQLR-38 example-apps umbrella (after examples/python-agent/ and examples/nodejs-notes/).

Demo

Full 1080p MP4: examples/desktop-journal/docs/demo.mp4

What's in this PR

New example app — examples/desktop-journal/

• Tauri 2 backend (src-tauri/) owns one Arc<Mutex<Connection>> in tauri::State. Every #[tauri::command] grabs the mutex, runs SQL via the public Connection / Statement API, returns serde-serialised structs.
  • Single-mutex design rationale: the journal is single-user / single-instance, so serialising commands is simpler than BEGIN CONCURRENT retry loops and just as correct. Documented in main.rs module doc.
• Modern API surface: uses Connection / Statement (not the older Database / process_command path used by the existing desktop/ SQL playground, which AGENTS.md says new SDKs should avoid).
• Schema v1 with a migration runner: entries, tags, entry_tags (synthetic PK because SQLRite's PRIMARY KEY is single-column today), plus secondary indexes on entries.date/updated_at and FTS indexes on entries.content/title.
• Features: entry CRUD, markdown editor + rendered preview toggle, tag chips with click-to-filter, Phase 8 BM25 full-text search with token-boundary-aware <mark> highlighting on the Rust side, "Ask my journal" panel that calls Connection::ask and gates the returned SQL to SELECT / WITH only, export-DB / export-markdown commands.
• In-app Settings (settings.rs): Anthropic API key persists to $APP_DATA/com.sqlrite.journal/settings.json — a separate file from journal.sqlrite so the key doesn't ride along if you sync the DB. DTO returns has_api_key: bool, never the value; falls back to SQLRITE_LLM_API_KEY env var when unset.
• Locked-down capabilities: only core:default / core:window:default / core:event:default / dialog:default. No fs / shell / http — the IPC boundary is the only path to the engine.
• Frontend: Svelte 5 + Tailwind v4 + TypeScript via @tailwindcss/vite (no PostCSS dance). All a11y warnings cleared (labels paired, keyboard handlers on interactive elements only).

Workspace + CI integration

• New workspace member examples/desktop-journal/src-tauri; existing CI commands gain --exclude sqlrite-journal (same shape as the existing sqlrite-desktop exclude).
• New journal-build job in .github/workflows/ci.yml mirrors desktop-build: frontend bundle then cargo build, including a no-default-features pass to prove the off-ask build still works.
• New .github/workflows/journal-release.yml builds .dmg / .deb / .AppImage / .msi installers via tauri-apps/tauri-action@v0 on manual trigger or journal-v* tag push, attaching to a draft release.
• AGENTS.md updated symmetrically (CLAUDE.md change deferred — see follow-ups).

Remotion demo composition — examples/desktop-journal/demo/

• Stitches 7 real app screenshots (docs/screenshots/01-empty.png … 07-ask-panel.png) into a 21s demo with Ken Burns slow zoom + fade-in caption strips + cross-fade transitions.
• Renders to docs/demo.mp4 (1080p H.264, 8.5 MB) and docs/demo.gif (960×540, 15fps, 8.8 MB, first 5 screens).
• npm run prep copies the canonical screenshots from docs/screenshots/ into the Remotion public/ (gitignored) so there's one source of truth.
• Replace a screenshot → npm run render re-produces both formats.

Website Examples card

• New entry at position 3 on /examples. JSON-LD updated. New Example.demoAsset field carrying GIF + MP4 paths.
• Inline GIF poster loads from raw.githubusercontent.com (no web/public/ copy to keep in sync); clicks through to the MP4 on github.com.

Test plan

• cargo fmt --all -- --check — PASS
• cargo build --workspace --exclude {desktop,journal,python,nodejs,benchmarks} --all-targets — PASS
• cargo test --workspace --exclude … --exclude sqlrite-journal — PASS
• cargo build -p sqlrite-journal --all-targets (default features) — PASS, no warnings
• cargo build -p sqlrite-journal --no-default-features --all-targets — PASS, no warnings
• cargo test -p sqlrite-journal — 14 / 14 tests pass (9 journal + 5 settings)
• cargo clippy -p sqlrite-journal --all-targets — clean (no warnings on new code)
• npm install && npm run build (Vite) in examples/desktop-journal/ — PASS
• npm run check (svelte-check + tsc) — 0 errors, 0 warnings
• npm install && npm run build in web/ (Next.js production) — PASS, /examples page statically pre-rendered with the new card + JSON-LD
• Smoke driver writes / FTS-searches / reopens a .sqlrite file via the journal's schema — passes (mirror of the README demo script)
• Manual UI verification by @joaoh82 — entry CRUD, search, Settings dialog, Ask flow all working

Follow-ups (will file separately)

• Allow bm25_score(...) in the SELECT projection list in the engine — would let the journal show real BM25 scores instead of the current positional surrogate.
• Custom branded app icon — currently reuses the playground's icons.
• Symmetric CLAUDE.md edit to match AGENTS.md (workspace-members line + four CI exclude-pattern blocks). Auto-mode classifier blocked the edit in-session; needs a manual one-line change.
• Record the README screencast (done as part of this PR via Remotion — superseded).

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
rust-sqlite	Ready	Preview, Comment	May 30, 2026 9:36pm