refactor(move): complete replay port package extraction

[thymikee]

Summary

• Move the final 15 connected replay production modules unchanged into @agent-device/replay-port, route daemon callers through package exports, and remove src/daemon/replay/**.
• Update package ownership and source references. The original replay subtree held 108 files / 24,089 LOC and now has no tracked files. This layer touches 52 files; all 15 source moves are exact renames (git diff -M90%).
• Daemon coordinator, repair transaction, device selection, and handler adapters remain as specified by the issue’s retention scope.
• Closes refactor(replay): move the daemon-side replay port into packages/replay-port #2663 after the preceding stack layers merge.

Validation

• Head a4badbb72: fresh pnpm install --frozen-lockfile && pnpm build && pnpm format && pnpm check:affected --run passed, including related tests, package checks, Maestro conformance, and wire compatibility.
• Layering and depgraph: R4 0 value cycles, R5 0 back-edges, R6 3 type inversions, R11 zero root back-imports. Fallow and 753 eager-closure budget tests passed.
• Live iPhone 18 Pro simulator on a4badbb72: recorded .ad replay passed 2/2 steps, 0 heals; Maestro checkout form passed 17/17 steps, 0 heals. Baseline 3c1f51382 had the same 2/2 and 17/17 results. Both final sessions closed; session list and device claims are empty.
• Review fixes cover package-relative dynamic imports in the ownership test and move the native-command complexity baseline to its package path. GitHub CI is pending on this PR head.

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://callstack.github.io/agent-device/pr-preview/pr-3041/
Built to branch gh-pages at 2026-09-28 17:05 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[github-actions]

Size Report

Metric	Base	Current	Diff
Installed (including dependencies)	4.87 MB	4.87 MB	0 B
Package (unpacked)	4.87 MB	4.87 MB	0 B
Package (download)	1.46 MB	1.46 MB	-3 B

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	28.9 ms	27.0 ms	-1.8 ms
CLI --help	85.8 ms	79.5 ms	-6.3 ms

[cubic-dev-ai]

All reported issues were addressed across 52 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[thymikee]

Reviewed at fec8036. The move looks correct, but one fallow baseline entry did not move with its file. This PR renames src/daemon/replay/internal/native-command.ts to packages/replay-port/src/daemon-port/native-command.ts, but fallow-baselines/health.json#L566 still keys src/daemon/replay/internal/native-command.ts:complexity. Baselines are path-keyed, so the old entry no longer matches a file and the new path has no entry. Please move the entry to packages/replay-port/src/daemon-port/native-command.ts:complexity. The other moved files have no baseline entries.

Checks were still running at review time. If Repo Guards fails, check this entry first. The typecheck break from #3037 must also be fixed before this stack can go green.

[thymikee]

Reviewed at f77f9ee, following up on the earlier review at fec8036 (#3041 (comment)). The change at f77f9ee only touches src/daemon/tests/replay-coordinator-ownership.test.ts, so the baseline problem from the last round is still open.

fallow-baselines/health.json:566 still keys the complexity baseline as src/daemon/replay/internal/native-command.ts:complexity, and that path no longer exists after the move to packages/replay-port/src/daemon-port/native-command.ts (https://github.com/callstack/agent-device/blob/f77f9ee/fallow-baselines/health.json#L566). Baselines are path-keyed, so a stale key means the moved file has no complexity baseline of its own; whichever gate run reads this file next either skips enforcing that metric for the new path or fails on first exercise. Can you rename the key to packages/replay-port/src/daemon-port/native-command.ts:complexity so the baseline tracks the file it was measured against?

Smoke Tests is still queued, so there's no result to attribute to this delta; the only changed file is a self-contained ownership test, not part of the device-facing smoke route it covers. Once the health.json key is moved, this is ready for human review.

[thymikee]

CI follow-up: the iOS fixture-backed Smoke Tests job 108970206222 failed at step 11 (wait text Automation lab) with typed APP_NOT_RUNNING after the deep-link launch. The same step and error recurred on #3032's independent replay-test branch. Both artifacts showed the unanswered iOS “Open in Agent Device Tester?” confirmation. The shared harness correction is isolated in #3044, which handles the typed readiness-exhausted first wait and has a regression that fails with the old early return. All #3041 non-smoke checks passed; exact-head live .ad and Maestro replay passed before publication. This PR's iOS smoke should be rerun after #3044 is in its CI base.

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="fallow-baselines/health.json">

<violation number="1" location="fallow-baselines/health.json:566">
P2: This line fixes the `native-command.ts` baseline but two sibling entries in the same `target_keys` list were not moved with their renames: `src/daemon/replay/internal/session-replay-heal.ts` (line 539) and `src/daemon/replay/internal/session-test-infrastructure.ts` (line 579) still key paths that no longer exist, while the files now live at `packages/replay-port/src/daemon-port/`. Since fallow baselines are path-keyed and must move on rename, update both entries to the new package paths as well.</violation>
</file>

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: This line fixes the native-command.ts baseline but two sibling entries in the same target_keys list were not moved with their renames: src/daemon/replay/internal/session-replay-heal.ts (line 539) and src/daemon/replay/internal/session-test-infrastructure.ts (line 579) still key paths that no longer exist, while the files now live at packages/replay-port/src/daemon-port/. Since fallow baselines are path-keyed and must move on rename, update both entries to the new package paths as well.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At fallow-baselines/health.json, line 566:

<comment>This line fixes the `native-command.ts` baseline but two sibling entries in the same `target_keys` list were not moved with their renames: `src/daemon/replay/internal/session-replay-heal.ts` (line 539) and `src/daemon/replay/internal/session-test-infrastructure.ts` (line 579) still key paths that no longer exist, while the files now live at `packages/replay-port/src/daemon-port/`. Since fallow baselines are path-keyed and must move on rename, update both entries to the new package paths as well.</comment>

<file context>
@@ -563,7 +563,7 @@
     "packages/capture-kit/src/snapshot/snapshot-presentation/text-surface.ts:high impact",
     "src/daemon/handlers/session-test-sharding.ts:high impact",
-    "src/daemon/replay/internal/native-command.ts:complexity",
+    "packages/replay-port/src/daemon-port/native-command.ts:complexity",
     "packages/platform-apple/src/core/debug-symbols/utils.ts:high impact",
     "packages/platform-linux/src/snapshot.ts:high impact",
</file context>

[thymikee]

Reviewed at a4badbb. The new commit moves the complexity baseline key in fallow-baselines/health.json to packages/replay-port/src/daemon-port/native-command.ts, which resolves the stale-key finding from the last round. The rest of the branch is unchanged. Smoke Tests is still running, and this delta does not touch the route it covers. Ready for human review.