Problem
In a linked worktree, the pre-push hook can fall back to the primary checkout's Python interpreter, but Pyright still reads the linked worktree's pyproject.toml and expects a local .venv path. Without a worktree-local .venv, Pyright reports missing imports even though the hook is running from the primary checkout's venv.
Observed during PR #25:
- first push failed in pre-push Pyright with missing imports for mcp, tiktoken, pytest, etc.
- creating an ignored .venv symlink in the linked worktree to the primary checkout's .venv made Pyright pass
Expected
Either the workflow should document the required linked-worktree .venv symlink, or the hook/wrapper should make Pyright resolve the fallback venv without manual setup.
Scope
Light task follow-up after the deep research template change lands.
Problem
In a linked worktree, the pre-push hook can fall back to the primary checkout's Python interpreter, but Pyright still reads the linked worktree's pyproject.toml and expects a local .venv path. Without a worktree-local .venv, Pyright reports missing imports even though the hook is running from the primary checkout's venv.
Observed during PR #25:
Expected
Either the workflow should document the required linked-worktree .venv symlink, or the hook/wrapper should make Pyright resolve the fallback venv without manual setup.
Scope
Light task follow-up after the deep research template change lands.