Repository navigation
Keep local test app builds isolated and clean up managed bundles - #19
Merged
Merged
Conversation
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.
Default local builds now use one managed .build/local-app.noindex bundle named LeftOpen Test with a separate bundle identifier. Explicit LEFTOPEN_OUTPUT_DIR builds retain the release packaging path.
Add dev-app.py build/run/clean commands. Cleanup is limited to marked output, rejects symlinks and active bundled processes, and unregisters the exact test app. User data and fixed-address services are preserved. Update both READMEs.
Validation: all 7 Python lifecycle/safety tests passed; zsh syntax and diff checks passed. No new packaged-app UI or lifecycle run was performed during this branch split.