[t3-code-bot]

problem

nine complete tests kept two obsolete helpers alive even though neither has a production caller. this is a focused run of the t3code useless test audit automation, not a human-authored change.

removed and evidence

base inspected: 8b44f42b14c8.

• deleted apps/mobile/src/state/use-selected-thread-worktree.test.ts in full: three tests and their mocked hook harness only called useThreadCwd. a tracked-source search on the pinned base finds that symbol only in its declaration and this test file. every production importer of use-selected-thread-worktree uses useSelectedThreadWorktree, which remains unchanged. testing the unused arbitrary-thread hook cannot protect the selected-thread path that the app actually runs.
• removed the entire six-test resolveOnboardingTargetEnvironment suite and its six environment fixtures from apps/web/src/onboarding/targetEnvironment.logic.test.ts. the pinned-base symbol search finds only the helper declaration and that suite, no callers or re-exports. the live wizard instead passes its explicit selection through resolveOnboardingSetup (WelcomeWizard.tsx:279,329), and uses isOnboardingRelayEnvironment at line 325. all three setup regression tests remain unchanged.
• deleted the two now-unreferenced helper implementations and imports used only by them. the first test-only pruning check exposed resolveOnboardingTargetEnvironment as an unused export in knip; retaining dead implementations solely to retain their tests would defeat the audit. no live helper logic changed.

this does not claim duplicate coverage: these tests exercised unreachable implementations. retained terminal launch, selected-thread git state/actions, setup, and layout tests exercise distinct live paths. the broader audit also inspected shared endpoint/text-direction re-exports, markdown streaming, and web/mobile timeline tests; those keep unique cases or separate implementations and were retained.

verification

• vp install --frozen-lockfile: passed to synchronize the existing checkout's dependencies.
• before removal: vp test run apps/web/src/onboarding/targetEnvironment.logic.test.ts apps/mobile/src/state/use-selected-thread-worktree.test.ts apps/mobile/src/features/terminal/terminalLaunchContext.test.ts: 3 files, 15 tests passed.
• after removal: vp test run apps/web/src/onboarding/targetEnvironment.logic.test.ts apps/mobile/src/features/terminal/terminalLaunchContext.test.ts apps/mobile/src/state/use-selected-thread-git-state.test.tsx apps/mobile/src/state/use-selected-thread-git-actions.test.ts apps/web/src/components/composerFooterLayout.test.ts: 5 files, 24 tests passed.
• final vp run check:changed: passed formatting, lint, both knip passes, mobile/web/scripts typechecks, 3 onboarding tests, and the targeted react-compiler checks (7 passed, 2324 unrelated cases skipped by its filter).
• git diff --check: passed. full diff reviewed for accidental changes and secrets.
• no repo-wide local checks or ui captures: no reachable product behavior changed. github ci/review must still pass before merging.

model: gpt-6.1-sol. harness: hermes agent.

[macroscopeapp]

Approvability

Verdict: Approved at 9133fb1

Macroscope's review found this PR approvable — Removes unused thread-directory and onboarding-target helpers without changing active behavior. Repository searches found no production callers, so the cleanup has limited exposure.

^{You can add or adjust custom eligibility rules. Learn more.}

[maria-rcks]

Note

Written by gpt-6.1-sol on behalf of Maria

Verified in a real dev environment

verified as-is at 9133fb1ef21ca731afb8a43a76f6729ce1853320 on a Linux Boat VM. installed dependencies and ran main (9e85538535) first in a separate worktree, stopped its captured process group, then ran the exact pr head with separate state. drove the real web client using repository Playwright and /usr/bin/google-chrome. no mocks or replay provider.

this is unreachable-code cleanup, so there is no user-facing bug to reproduce. both removed symbols occur only in their declarations and deleted tests on main. the live onboarding helpers and selected-thread hook remain unchanged.

• on main and the pr: deselecting the computer disabled continue; reselecting enabled it. the agents step detected codex, project scanning rendered results, and skipping import completed setup.
• added the same real git repository through the app, selected codex gpt-6.1-sol, and submitted real turns on both revisions. the rendered responses returned the correct working directory, git root, and readme contents.
• on the pr: a second turn resumed the same thread and returned the same path and readme. the terminal drawer also ran pwd in that project.
• blacksmith: 4 focused existing test files, 21 tests passed (onboarding setup, mobile terminal launch context, selected-thread git state and actions). existing github checks are green. no source changes or pushes needed.

short runtime transcript

main onboarding:

pr onboarding with matching selection:

Not verified

native ios/android selected-thread consumers were not exercised on this Linux VM; the web terminal does not prove the native hook. Electron shell integration, macOS/Windows, multi-computer relay/direct/ssh onboarding, importing conversations, and other providers were not exercised. no runtime verification claim for those paths.