Repository navigation
Tools: start a development lab instance with one command - #240
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
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.
Base:
agents; tools and human instructions only. Code under test stays in a separatelab/...worktree. Runtime use requires merged #236 and device-ownership #237 in that integration branch.Starting a development app currently requires manually selecting a branch, building the correct profile, staging/signing it and keeping console ownership alive. Add
python3 lab/scripts/start_dev.py A(or B) after one-time slot configuration. It fetches/switches the clean dedicated worktree, fast-forwards a matching remote branch, builds with four workers, stages and verifies the package, copies runtime data beside the app, and supervises the actual GUI executable until exit. It retains the existing console-lock protocol throughout and serializes launcher builds. It never starts an automation program.Human setup and one-command usage, including local-only integration branches, profile/allowlist preparation and failure recovery. Native profile/device leases remain a separate prerequisite; no default settings, devices, certificates or permissions are configured automatically. Versioned deployment paths preserve prior artifacts; stable identity does not promise suppression of macOS permission prompts.
Validation: 17 offline tests pass, including temporary real Git updates, existing shell-lock interoperability, build/console exclusion, failure ordering, runtime-resource staging and interrupted child teardown. Harness/standing-rules/whitespace checks pass; Agents Check runs the new tests. No full application build, real signing, GUI launch or console access was performed.