fix(mobile): rebuild pending-move fixtures with the shared shell factory

[saphid]

Summary

Shared Test CI on t3code/codex-turn-mapping fails all five cases in apps/mobile/src/state/thread-order.test.ts with TypeError: Cannot read properties of undefined (reading 'relationshipToParent').

Root cause: d084be71eb ("fix: hide subagent threads from v2 lists") added a thread.lineage.relationshipToParent === "subagent" filter inside getThreadListV2OrderedSection and updated the threadListV2.test.ts fixtures, but the pending-move suite still hand-cast partial EnvironmentThreadShell rows without lineage. Every refresh through the coordinator then crashed.

Fix: build the fixture rows through makeThreadShellFixture, which produces a complete shell via presentThreadShell, so the fixtures track every field the shared section helper reads. Test assertions are unchanged — pinned/unpinned membership, activity order, deterministic ties, and reverse transitions are all still exercised.

This branch also carries the published shared-CI repairs so the full check suite can run green here:

• 82b753431d — knip unused-code repair, cherry-picked from fix(ci): register the live background verifier and drop dead v2 exports #11513 (cb0a26f5)
• 73a032f987 — expo-audio pin for the release-smoke patch, cherry-picked from fix(mobile): pin expo-audio so the release smoke patch stays in use #11518 (88301853)

Test plan

• vp test run apps/mobile/src/state/thread-order.test.ts — 5/5 pass (was 5/5 failures)
• vp test run apps/server/src/orchestration-v2/ThreadSettlementService.test.ts — 14/14 pass
• vp run knip:check — clean (was the Check CI failure)
• node scripts/release-smoke.ts — passes (was the Release Smoke CI failure: ERR_PNPM_UNUSED_PATCH expo-audio@57.0.4)
• vp run --filter @t3tools/mobile typecheck, vp lint, vp fmt --check — clean

Generated with Devin — SWE-2 High via T3 Code/Cursor harness. Coordination: T3 thread 29183fbb-98fc-48d3-9530-d46bbecf13c8, campaign issue saphid/t3code-personal#298.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The PR combines low-risk test and dead-code cleanup with a mobile dependency pin, but it also adds a Knip entry that suppresses an unused-file static-analysis diagnostic. That configuration override requires human review.

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

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

Dismissing prior approval to re-evaluate 73a032f

[saphid]

On the Macroscope eligibility flag for the knip entry: scripts/verify-background-live.ts is a standalone runnable script — it is invoked directly (node apps/server/scripts/verify-background-live.ts, documented in docs/operations/background-verification.md), so nothing imports it and knip's unused-file report on it is a false positive. Declaring it under entry alongside the other runnable scripts (scripts/cli.ts, scripts/probe-claude-fork-local-rollback-replay.ts) is knip's intended mechanism for this case, not diagnostic suppression — the file and its real dependencies remain fully analyzed.

This commit is cherry-picked from #11513 so this branch can demonstrate the repaired Check job; it lands via that PR.

[saphid]

@juliusmarminge this OV2 fix repairs the V2 thread-order regression suite and is ready for your review.

Latest head 73a032f98771 has green CI, is mergeable into t3code/codex-turn-mapping, and has no unresolved review threads. The PR description contains the focused regression evidence. We will keep babysitting it through landing.

One explicit human-review item: Macroscope flagged the runnable-script knip entry carried from #11513. The rationale is in the preceding comment; that dependency should land through #11513. This comment is a review request, not a claim that human approval is complete.

[saphid]

Closing: the full contents of this PR landed upstream via the squash merge of #11518 (a8cc38b95b on t3code/codex-turn-mapping), which carried this thread-order fixture repair alongside the knip and expo-audio shared-CI repairs. This branch is now patch-equivalent to the base (zero file diff), so there is nothing left to land here.

The original defect and focused evidence remain in this PR's description: apps/mobile/src/state/thread-order.test.ts now builds rows through makeThreadShellFixture, and all five pending-move cases pass in CI on the merged commit.