refactor(test-kit): move the interaction-targeting node fixtures out of selectors

[thymikee]

What

The interaction-targeting node fixtures (nine RawSnapshotNode[] trees captured from live iOS and React Native snapshots) are used by selectors' own tests and by tests in replay-port and root. They were published from @agent-device/selectors/interaction-targeting-fixtures; they now live in @agent-device/test-kit as nine named exports.

• Commit 1: pure git mv of interaction-targeting.fixtures.ts from packages/selectors/src to packages/test-kit/src (the file imports only a kernel type, so it needs no edits).
• Commit 2: the five importers read the names from @agent-device/test-kit; selectors declares test-kit in devDependencies and tsconfig references (test-kit no longer reaches selectors after refactor(test-kit): drop the daemon-contracts dependency #3686/refactor(test-kit): drop command-registry by making the replay-script generator a root fixture #3687, so no reference cycle); the ./interaction-targeting-fixtures export and its line in the layering test are removed; one duplicate test-kit import in replay-port's test is merged.

Fixture decision

Fixture	Importers by package	Outcome	Reason
selectors/interaction-targeting-fixtures	selectors 2 tests, replay-port 1, root src 2 (test-utils/index.ts, selector-action-resolution.test.ts)	case 3: test-kit	shared by three packages' tests; plain node data over kernel types

Parity

vitest run <files> --reporter=json, origin/main against this branch, over the 4 direct importers plus every test that imports the root test-utils helper: 28 files, 265 / 265 -> 265 / 265. No test file moved; unit-core selects them as before. No vi.mock involved.

Surface

exports: selectors 18 -> 17 (./interaction-targeting-fixtures removed); test-kit stays one "." entry, +9 named exports; no barrels or export *. Selectors gains a test-kit devDependency + reference; the R83 isolation walk and tsc -b stay acyclic.

Gates

check:quick, check:layering, check:fallow, check:gate-manifest, pnpm format pass. check:affected --run (full set, since a package manifest changed) passes except one test, test/integration/smoke-web-platform.test.ts > web shutdown cleanup reaps the exact daemon that survived graceful shutdown. It fails identically on a clean origin/main (reproduced alone under the host lock on both), so it is a pre-existing, host-dependent failure unrelated to this diff.

The gates ran on the pre-rebase head; after rebasing onto #3704 I re-ran lint, format, install and the 265-test parity set.

🤖 Generated with Claude Code

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-10-16 11:40 UTC

[cubic-dev-ai]

No issues found across 11 files

_{View guided diff | Turn on auto-fix | Re-trigger cubic}

[github-actions]

Size Report

Metric	Base	Current	Diff
Installed (including dependencies)	5.29 MB	5.29 MB	0 B
Package (unpacked)	5.29 MB	5.29 MB	0 B
Package (download)	1.59 MB	1.59 MB	+8 B

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	26.7 ms	26.5 ms	-0.2 ms
CLI --help	77.6 ms	75.6 ms	-2.0 ms

[thymikee]

This PR is ready at 8084aa0. The move of the interaction-targeting node fixtures out of selectors looks correct. Not blocking: the description string in packages/selectors/package.json (line 7) now has a literal … where it had an escaped one, which is unrelated to the move, so you can revert that hunk or leave it. There are no conflicts. Smoke Tests is still running, and the other checks are not failing. The diff touches only test fixtures and package wiring, so I see no runtime route involved. I did not run the layering, fallow or ceiling gates or any tests. I also did not check whether the published package or build keeps test-kit out of the selectors production closure. Smoke Tests still needs to finish.