Tauri directory resolution for fleet
State: open/verified · Kind: adapter · Audience: system
Summary
Section titled “Summary”- Bridges a Tauri
Apphandle into the fleet path SDK: one call resolves fleet’s vendor and suite directories plus Tauri’s per-productapp_data_dir(), and runs the vendor bundle-id assertion against the app’s real identifier. - Deliberately thin. Single-instance, window-state, deep-link and notification helpers wait for a second real consumer.
Statement
Section titled “Statement”C-0023’s fleet crate takes no Tauri dependency, so the Tauri-specific per-product directory
lives here. AppDirs::resolve(app) takes a Tauri App handle, runs
fleet::assert_vendor_bundle_id in debug builds against the app’s bundle identifier, and returns an
AppDirs exposing vendor() and suite(key) from fleet::Fleet alongside product(), Tauri’s
app_data_dir().
The debug assertion is a migration tracker, not a gate: it has no allowlist for the legacy
com.sksizer.* and com.agentzoo.app prefixes, so it surfaces non-conformant apps one at a time as
each adopts the SDK.
What it provides
Section titled “What it provides”AppDirs::resolve(app): one-call resolution of vendor, suite and product directories.vendor()andsuite(key): passthrough to thefleetcrate’s tiers.product(): Tauri’sapp_data_dir(), the tierfleetitself does not address.assert_vendor(): debug-only vendor bundle-id conformance check.
Underlying implementation
Section titled “Underlying implementation”packages/rust/fleet-tauri/src/lib.rs.
Locations
Section titled “Locations”packages/rust/fleet-tauri/packages/rust/fleet-tauri/src/lib.rs#AppDirs