The desktop replacement is an isolated static Svelte/Vite application with a Tauri 2 Rust shell. Flutter remains the existing application and is not part of desktop development commands.

F01 pins the foundation to:

• Node.js 24.15.0 and npm 11.12.1;
• Rust 1.92.0 for CI, with the Tauri crate version pinned in desktop/src-tauri/Cargo.toml and exact dependency resolution in Cargo.lock;
• Svelte 5.57.0, Vite 8.3.0, TypeScript 6.0.3, Tauri CLI 2.11.4, and Tauri Rust 2.11.5.

The package manager is npm. Run commands from desktop/ unless a command gives an explicit manifest path.

cd desktop
npm ci
npm run check
npm run test:unit
npm run test:contracts
npm run lint
npm run format:check
npm run build
cargo check --manifest-path src-tauri/Cargo.toml
cargo fmt --manifest-path src-tauri/Cargo.toml -- --check
cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings
cargo test --manifest-path src-tauri/Cargo.toml

Run the local Tauri window with npm run tauri -- dev. The application starts a Vite server on 127.0.0.1:1420 and loads only bundled local assets. The foundation window has an 800x600 minimum size and makes no Linkding requests.

For a native Linux build, install the Tauri/WebKit development prerequisites for the chosen distribution. On Debian/Ubuntu, the CI baseline installs:

sudo apt-get install \
  build-essential curl file libayatana-appindicator3-dev libssl-dev \
  libwebkit2gtk-4.1-dev libxdo-dev librsvg2-dev patchelf wget

A Secret Service daemon and user session are additionally required once the credential backend is implemented. CI foundation tests use a fake keyring and a loopback-only mock server; they never inspect the host keyring or network.

The Windows candidate job runs on windows-2022, targets x86_64-pc-windows-msvc, and builds only an unsigned NSIS installer. It compiles the Windows Credential Manager backend, uses the current-user installer mode, and downloads the Evergreen WebView2 bootstrapper only when WebView2 is absent. A clean Windows test host needs network access for that bootstrapper or a preinstalled supported WebView2 Runtime.

The local equivalent for package configuration is:

cd desktop
npm ci
npm run tauri -- build --ci --no-sign --bundles deb  # Linux config validation

Run the Windows workflow through workflow_dispatch for an NSIS candidate. The workflow uploads an installer, PE architecture/version evidence, signing status, keyring feature evidence, and a checksum. It does not publish a release or require signing secrets. Native install, uninstall, WebView2, Credential Manager, and restart/clear checks are Q08 gates.

• npm run test:unit uses Vitest, jsdom, Svelte Testing Library, fake timers, and the typed bridge mock in src/lib/testing/.
• npm run test:contracts checks the shared IPC fixture and the frozen Linkding unread field. It must fail if a test intentionally changes a required field name; revert such experiments before committing.
• Rust integration tests under src-tauri/tests/support/ use temporary preferences, failure-injectable fake storage, and a server bound to 127.0.0.1. No test accepts a real token or discovers real credentials.
• Browser/axe coverage uses the local in-memory bridge and is documented in evidence/accessibility-performance.md. Native screen-reader, native keyring, packaging, and cross-OS checks remain separate evidence gates; none is represented by a skipped green placeholder.

.github/workflows/desktop-ci.yml runs for desktop changes in pull requests or by explicit manual dispatch. It has contents: read, does not publish artifacts, does not need secrets, and does not alter the existing Flutter release workflow. It runs the same npm and Cargo checks listed above on a pinned Ubuntu/Node/Rust toolchain and caches only dependency/build paths keyed by lock file and toolchain.

The workflow intentionally does not claim Windows/macOS packaging or native keyring coverage. Those gates require their own OS evidence. macOS WebDriver availability and manual native alternatives are recorded in distribution.md.