Centralize cross-platform storage paths - #115
Closed
brxs wants to merge 1 commit into
Closed
Conversation
brxs
marked this pull request as ready for review
August 8, 2026 20:19
This was referenced Aug 8, 2026
Collaborator
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #107.
What changed
AppPathscontract with distinct config, durable-data, cache, downloaded-asset, and staging rootsWhy
The app and Python services previously reconstructed macOS-specific locations independently. Linux and Windows support need one authoritative path policy so large assets, settings, caches, staging, and child-service paths cannot drift.
Validation
cargo clippy --workspace --all-targets -- -D warningsgit diff --checkThis PR intentionally excludes process supervision, secure runtime installation, audio sample formats, platform packaging, and release CI.