Bundle 48B: Tauri host and opaque library capability proof

[nulleimy]

Goal

Implement the minimum React/Tauri host proof on top of merged Bundle 48A without starting product screens or exposing renderer access to the Python sidecar.

Schema Tree

minimal React renderer
  -> typed invoke-only bridge
  -> named Rust commands
      -> desktop status
      -> native folder selection
          -> canonical directory validation
          -> in-memory opaque capability registry
          -> capability ID + display name only

Deliverables

• pinned React 19 / TypeScript / Vite / Tauri 2 workspace
• committed npm and Cargo lockfiles before final merge
• renderer bridge exposing only named commands
• no direct dialog, shell, filesystem, HTTP or sidecar access in renderer
• Rust desktop status command
• Rust-owned native folder picker
• in-memory opaque library-root capability registry
• capability IDs generated from cryptographic randomness
• renderer response excludes absolute host path
• strict Tauri capability file and CSP
• Rust unit tests for registry isolation, lookup and revocation
• frontend type/build/security-contract checks
• Linux Tauri compile proof and macOS app-bundle proof
• schema tree, operator guide and rollback

Isolation

• no product library table or import execution
• no MIR, composition, export or database change
• no Rust-to-Python sidecar supervision yet; that remains Bundle 48C
• no updater, signing or notarization claim
• no generic shell/fs/http plugin

Parent

Issue #78

Base

464b70cc86314a6a4abc024c9a216c863d1c9b2e

Rollback

Revert one isolated squash commit.

[nulleimy]

Bundle 48B implementation update

Current feature head: 6bc0528a5858e16452b318b5f5fddc5459e4328a

Completed:

• React/Tauri host proof
• typed two-command renderer bridge
• Rust-owned native folder picker
• opaque in-memory library-root capabilities
• committed npm and Cargo lockfiles
• committed 512×512 PNG icon
• read-only locked Linux/macOS workflow
• strict production CSP with separate constrained devCsp
• renderer security contract v2 enforcing a single IPC file and literal allow-listed commands
• schema tree and final operator guide

Evidence already observed before final lock:

• TypeScript/Vite/security build passed
• Rust fmt/clippy/tests/release build passed
• macOS APPLAYLIST.app bundle proof passed
• Python 3.11/3.12 regression passed on the preceding implementation head
• no review threads, reviews or PR comments
• PR is mergeable

Additional local proof:

• renderer security contract v2 passed against the exact renderer source
• a negative direct/dynamic invoke test was rejected

Fail-closed blocker

On final committed heads, Desktop Host Locked Proof, Python CI and PR Guard all failed before runner assignment with steps=[]; retry produced the same result. No build/test command executed. Public GitHub status reported Actions operational, so this is recorded as a repository/account runner-start condition rather than code-test evidence.

PR #84 remains draft and must not merge until all required workflows start and pass on the exact final head.