Repository navigation
Expose read-only App audio settings - #376
Merged
Merged
Conversation
Let headless players inspect saved levels or first-run defaults through the same bounded core reader used by the App. Keep provenance explicit, preserve legacy files, and refuse damaged preferences without reading progression. Explain protected install-root recovery in both installers and document the packaged command, its boundaries, and the latest playtest observations.
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
1 participant
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.
Headless players could not inspect the App's Master, Radio, Room Sound,
Effects, or mute.
numinous settingsandnuminous settings --jsonnow readthose launch preferences through the App's shared bounded core reader,
distinguishing missing/default values from a valid saved document. Legacy
defaults are preserved; damaged or unreadable files fail without mutation.
Inspection stays independent of Journey and scores and makes no live-device
or hearing claim.
Both installers retain their protected unmarked-root refusal and now name a
fresh archive or separate empty installation directory as recovery. Packaged
guides, owner docs, playtest evidence, changelog, and alpha 3 release notes
describe the resulting behavior.
Validation: four CLI process regressions cover defaults, distinct saved
levels, legacy schemas, malformed and oversized files, damaged progression,
and unchanged files. Core persistence and both installer self-tests passed.
The ordinary all-target run passed 4,847 cases with four diagnostic exclusions.
The full Windows release gate passed without optional skips: strict Clippy,
rustdoc, MSRV, coverage, flash and CPU/GPU checks, play and creation harnesses,
goldens, packaging, interoperability, supply-chain checks, and the complete
3,065-frame App matrix. Coverage retained 95.13% regions and rose to 95.00%
lines under unchanged exclusions. No live-device or hearing claim is made.