[lion24]

Scope gate (required)

• This PR closes an issue that carries the good-first-issue, help-wanted, or scope:approved label. (Issue opened, waiting for a maintainer to label it.)
• I confirmed the scope with a maintainer on the issue before writing code.
• This PR is from a topic branch (not main on my fork).
• This PR makes one logical change. It does not bundle unrelated fixes.
• I did not run Black / autopep8 / isort / clang-format / Prettier on files I did not otherwise modify.
• Diff is minimal — no reformatting of surrounding lines that are unrelated to the change.

Linked issue (required — use Closes #NNN or Fixes #NNN):

Closes #404

What does this PR do?

It fixes first-time setup on macOS, which currently always fails at Analytics Core with uv exited with code 2, so Analytics Full never runs.

The install dir is ~/Library/Application Support/com.fincept.terminal. The pinned uv 0.7.12 can't open a lock file passed by a path containing a space (error: File not found: '/Users/<me>/Library/Application'). --python and pip compile -o paths with the same space are fine, and the arguments already go to uv as a QStringList. The issue has a minimal repro.

The install steps now run uv from the venv directory and pass requirements.lock as a bare file name, so the space never reaches uv. uv is pinned with checksums, so this avoids a uv bump.

Type of change

• Bug fix
• New feature / screen
• Performance improvement
• Refactoring (with linked issue)
• Documentation (see CONTRIBUTING — docs-only PRs allowed only for genuine errors)
• Build / config change

Changes made

fincept-qt/src/python/PythonSetupManager.cpp (+11 / -2):

• StepOptions: new optional working_dir. start_step calls QProcess::setWorkingDirectory only when it's set, so every other step is unchanged.
• lane_install_core: runs from the venv dir and passes -c requirements.lock.
• lane_install_full: runs from the venv dir and passes -r requirements.lock when not in fallback mode. The fallback still uses the bundled requirements file.

How to test

1. On macOS, start with an install dir where setup has failed at Analytics Core, or a fresh one.
2. Build (cmake --build --preset macos-release) and launch, or click Retry Setup.
3. Analytics Core and Analytics Full complete. The log shows uv pip install ... -c requirements.lock finishing OK.

Architecture / code-quality checklist

• Builds without errors on my target platform (Windows / macOS / Linux) — state which below
• UI thread is never blocked (no waitForFinished() on main thread) — see CLAUDE.md P1
• Timers start/stop in showEvent() / hideEvent() — see P3 (n/a)
• No raw QProcess for Python — used PythonRunner::instance().run() — see P4 (uses the existing start_step path)
• No print() in Python scripts — used logger.info / logger.warning — see P14 (n/a)
• No sensitive data (API keys, credentials) committed
• DataHub rules (D1–D5) respected if touching data flow (n/a)
• Tested manually on: macOS (Apple Silicon). Not tested on Windows or Linux.

Screenshots / logs

Before:

[PythonSetup] uv failed after 12 ms (kind=1 exit=2): error: File not found: `/Users/<me>/Library/Application`
[PythonSetup] [venv-numpy2] Installing the analytics core — uv exited with code 2.

After: setup completes, with Analytics Core and Analytics Full installed.

[github-actions]

Hi @lion24 — thanks for the PR!

Our automated scope gate flagged the following:

❌ No scope-approved linked issue. This PR must close an issue that carries one of: good-first-issue, help-wanted, scope:approved. Link it in the PR body with Closes #NNN or via GitHub's "Linked issues" sidebar.

Please read CONTRIBUTING.md. Once an issue with the appropriate label exists and is linked here, re-run this check by pushing an empty commit or editing the PR description. A maintainer can also bypass this gate by adding the scope:approved label to this PR.

PRs that remain unresolved for 7 days will be closed automatically.