Repository navigation
PR03: Add project configuration and stable path resolution - #3
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.
Commands launched from a nested or unrelated directory previously depended on the process working directory. Add versioned
cua.tomlconfiguration and an immutable project context so CLI, HTTP, MCP, workflows, and worker processes consistently use the selected project's paths and environment.--root; preserve legacy cwd defaults. Explicit CLI files stay invocation-relative, while configured references are project-relative..env, let process values take precedence, and pass environment snapshots to providers and browser launches without changing cwd or process environment.Validation: GitHub CI passed, including quality/type checks, the full browser suite, deterministic benchmark gate, and security benchmark. Local verification also passed 886 non-browser tests and 16 selected browser regressions; an explicit-root benchmark from an unrelated directory completed six correct replays with zero model calls or commits. Live Windows UIA was not exercised.