Move the mobile E2E harness out to the kilo-workflow repo

[iscekic]

Symptom

A weekend of workflow runs left the machine overloaded: orphaned Appium servers and a simctl recordVideo process alive for over two days, plus simulators that nothing could power off.

Cause

dev/local/mobile-simulator.ts existed in both this repo and kilo-workflow, drifted by 152 lines, each copy carrying fixes the other lacked. Both wrote the same claim files in the same machine-global $TMPDIR/kilo-mobile-simulator-claims.

The leak itself: a claim whose worktree is gone was discarded without powering the device off. The next claim saw a Booted device, recorded bootedByClaim: false, and release never shut it down — the simulator stayed booted forever. Fixing that once meant fixing it twice, in two places that kept diverging.

Change

E2E is agent tooling, not app code, so it moves out. apps/mobile/e2e/ and the simulator CLI now live in the kilo-workflow repo as mobile_e2e/, which is the single owner. The leak fix itself lands in kilo-workflow, not here.

• Delete apps/mobile/e2e/ (22 files) and the duplicated mobile-simulator.ts + test.
• Drop the dev:mobile:simulator script, and the appium/webdriverio deps and catalog entries — nothing here imports them now.
• Split dev/local/mobile-workflow.test.ts: the 15 flow and preflight assertions move with the harness; the 7 app and dev-tooling assertions stay.
• apps/mobile/AGENTS.md no longer points at an e2e runbook.
• dev/seed/app/api-token.ts drops its path reference in an error message.

One deliberate coupling left

dev/local/mobile-ios-build.ts still reads the claim directory to prove a device belongs to this worktree. pnpm dev:mobile:ios build <udid> stays a cloud command that the harness calls, so the read is correct. The record shape is now a contract owned by kilo-workflow, and a comment says so.

Verification

• pnpm test:mobile-workflow — 100 pass, 0 fail
• pnpm test:dev-local — 184 pass, 0 fail
• Harness smoke-tested from this worktree after the move: mobile_e2e/appium.sh <device> server status resolves the cloud worktree, re-execs through the harness tsx/process-lock, and answers.

Review note

Merge this together with the kilo-workflow commit. Until both land, mobile_e2e/preflight.sh and the role definitions point at paths that only exist on one side.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

This is a deletion-only harness move plus small doc/comment edits; I verified the cloud repo retains no dangling references to the removed harness and that the dependency/catalog removals are internally consistent, with high confidence.

Verification performed

• No remaining references anywhere in the repo (excluding pnpm-lock.yaml) to apps/mobile/e2e, mobile-simulator.ts, dev:mobile:simulator, appium-wrapper, appium, or webdriverio. The only Appium mentions left are prose comments in apps/mobile/src/components/agents/chat-composer.tsx and message-bubble-a11y.test.ts, and the only kilo-mobile-simulator-claims use is the intentional read in dev/local/mobile-ios-build.ts.
• pnpm-lock.yaml no longer resolves appium/webdriverio, matching the removed root devDependencies and pnpm-workspace.yaml catalog, minimumReleaseAgeExclude, and allowBuilds entries. geckodriver: true is correctly retained for apps/extension Firefox e2e.
• test:mobile-workflow now lists only test files that still exist; test:dev-local uses a glob, so the deleted appium-wrapper.test.ts / mobile-simulator.test.ts do not break it. No CI workflow referenced the deleted paths or the removed script.
• The trimmed dev/local/mobile-workflow.test.ts drops exactly the assertions that read apps/mobile/e2e/** files; the remaining assertions read only files that still exist in this repo.
• No new imports, runtime code paths, or subscriptions were added, so there is no new memory-leak surface.

Assumptions / notes for the author

• validateSimulatorClaim in dev/local/mobile-ios-build.ts:663 still hard-fails when no claim record exists, and this repo no longer contains a writer for $TMPDIR/kilo-mobile-simulator-claims. So pnpm dev:mobile:ios build <udid> is now only usable when driven by the kilo-workflow harness. The PR description states this coupling is deliberate and the added comment documents the contract, so I did not flag it, but it does make the command unusable standalone from this repo.
• Per the PR's own review note, this must land together with the kilo-workflow commit; I could not verify the other side of the move.

Files Reviewed (32 files)

• apps/mobile/AGENTS.md
• dev/local/mobile-ios-build.ts
• dev/local/mobile-workflow.test.ts
• dev/seed/app/api-token.ts
• package.json
• pnpm-workspace.yaml
• pnpm-lock.yaml (generated)
• apps/mobile/e2e/** (22 files, deleted)
• dev/local/mobile-simulator.ts, dev/local/mobile-simulator.test.ts, dev/local/appium-wrapper.test.ts (deleted)

---

_{Reviewed by claude-opus-5 · Input: 50 · Output: 9.8K · Cached: 1.5M}

_{Review guidance: REVIEW.md from base branch main}