You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prove the direct replacement works as one coherent Linux application and leave an auditable merge handoff. A maintainer can compare Tauri with the recorded Floem baseline, verify product parity and security, and merge without hidden cleanup work.
Acceptance criteria
Formatting, Clippy, Rust tests, generated-binding checks, TypeScript typecheck, Vitest, component tests, visual checks, and Linux Tauri smoke tests all pass from the integration worktree.
Manual Linux checks cover IME, keyboard, focus, titlebar, themes, Typeface loading/offline retry, selector, conflicts, close flush, App scale, localization, Spellcheck, and reduced motion.
A capability and CSP audit confirms the frontend has no direct filesystem, shell, network, remote-content, or undeclared window authority.
The Floem benchmark protocol is repeated for Tauri, including complete process-tree RSS/PSS, and differences are recorded without unsupported efficiency claims.
Current README, PRD, AGENTS, ADR, specification, and changelog text describe Tauri as the sole implementation and preserve macOS/Windows as architectural targets.
The handoff records validation evidence, remaining cross-platform limitations, the approved main-merge step, and post-merge worktree/branch cleanup commands.
What to build
Prove the direct replacement works as one coherent Linux application and leave an auditable merge handoff. A maintainer can compare Tauri with the recorded Floem baseline, verify product parity and security, and merge without hidden cleanup work.
Acceptance criteria
Blocked by
Workspace
feat/tauri-2-replatform/home/daniel/Projects/lettera/.worktrees/feat-tauri-2-replatformfeat/tauri-2-replatform