refactor(daemon): cut daemon test edges into root data fixtures and fakes [11a-3]

[thymikee]

Plan step 11a-3: daemon test files stop importing the root src/__tests__/test-utils/ data fixtures, and the review's copied-fake findings are resolved with one owner each.

Targeted root modules (scan edges now 0): device-inventory-gateways, replay-script-source, android-ui-hierarchy-fixtures, android-snapshot-capture, plugin.fixtures. Total daemon→root scan residue after the cut: 23 edges, all into the platform-runtime cluster owned by step 11a-2 (the only remaining 11a-1 residue).

Review resolutions:

1. Inventory fake — one owner: packages/device-selection/src/inventory-gateways.fixtures.ts, exported as @agent-device/device-selection/inventory-gateways-fixtures, with findInstalledApp in options, createTestDeviceInventoryGateways exported, and the nullable-provider bridge (withTestDeviceInventoryProvider) extracted once. Daemon (37 files under src/daemon), root composition, device-selection's own tests, and test/integration all import it. The root wrapper and its pin are deleted: the wrapper's fail-closed pin duplicated the real composer's pin already at src/platform-runtime-device-inventory.test.ts, and the real adapter has its own direct tests. test-kit was not viable: the fake needs the root composition's createDeviceInventoryContext (device-selection's production entry), which would make test-kit→device-selection while device-selection's tests need test-kit — a tsc -b project-reference cycle — so the package's own test-only subpath (the fallback) is the one owner.
2. Replay collector — no second implementation: the real client collector moved into replay-port (script-source-bundle, source-discovery, byte-pure moves with their own test suites), and the bundle helpers live once in replay-port/src/daemon-port/replay-script-source.fixtures.ts (./replay-script-source-fixtures), typed on DaemonWireRequest so it serves both trees without a production seam. Both test trees exercise the same globs, size cap, not-found AppErrors and ranking through it. The root src/__tests__/test-utils/replay-script-source.ts is deleted (its exports move with it; nothing suppressed via .fallowrc).
3. Android captures: snapshot-capture-fixtures and ui-hierarchy-fixtures are test-only entries on @agent-device/platform-android (the Apple runner requests-fixtures pattern), with the archived raw JSONs under packages/platform-android/src/fixtures/ where own:package-capture owns them. Contract comments kept to one line.
4. plugin.fixtures stays in @agent-device/test-kit/plugin.fixtures (package vocabulary over the filesystem install, no platform adapters).
5. createTestDeviceInventoryGatewaysFromProvider is used (lock-policy test + integration harness), so it stays exported; the daemon-side copy that fallow flagged is deleted. pnpm format run repo-wide.
6. Base delta is test-side only: the moved collector modules are byte-identical and the only production root edit is the two import lines in src/commands/replay/index.ts; everything else is test/fixture moves, import retargets, and gate wiring. No limrun/CONTRIBUTING/coverage/website files in the delta against the current base.

Gates (on the pushed commit, under the host gate lock): check:affected --run clean across all selected lanes; check:quick, check:layering, check:di-seams, check:gate-manifest, check:fallow, the eager-closure budgets table (three APPROVED_OVER_CEILING rows + the mechanics-facet exception for the Android fixture entries), the R13 export-pin tests, and the test-file-size ratchet green. Targeted full runs: src/daemon, src/__tests__, packages, scripts with zero failures; vitest list src parity vs base is exact modulo the moved test files' path keys and one intentionally deleted duplicate pin (the root inventory wrapper's fail-closed case, already owned root-side).

Risk: no production behavior change (CLI startup import-closure guard green through the replay move). Eager-require weight: daemon suites now pull replay-port's real collector instead of the local test twin.

NO DOCS — test topology and fixture ownership only; no user-facing behavior or CLI surface changes.

Follow-up commit (bd49bf8, second review round): assertProviderOutcome/assertSourceFamily moved from the root composer into @agent-device/contracts/device; the fake now calls the shared assertProviderOutcome instead of restating the flow (a malformed provider outcome fails closed with provider_inventory_contract_violation in both paths, pinned by a new fixture test). The fake's local path keeps its per-family filter because the local option is a flat whole-inventory discoverer fanned out per family — that filter is the adapter to the per-family source contract, not a restated assertion site.

Design answers at e4eee6b (review follow-up round):

1. Composer home (Q1): yes, moved. The composed-gateways flow now lives in @agent-device/device-selection/composed-inventory-gateways with the installed-app probe injected instead of hardcoded; src/platform-runtime-device-inventory.ts stays as the production wiring that attaches the Apple probe (function-scoped import keeps the composition root's eager closure flat; the hub no-growth gate is green). The test fake composes through the real composer with fake registry sources — the root, daemon-composition, and integration consumers exercise the production flow, not a restatement. No root-side wrapper is needed anymore: the one owner is the package entry both trees build on.
2. Collector home (Q2): moved out of the daemon port. script-source-bundle, source-discovery, and the request fixture now sit at packages/replay-port/src/ (client-side replay vocabulary, like session-replay-vars), outside the daemon-port/ engine-prefix zone; the ./script-source-bundle, ./source-discovery, and ./replay-script-source-fixtures subpaths keep their names. Caller filesystem reads stay out of the daemon's dispatch vocabulary.

[github-actions]

Size Report

Metric	Base	Current	Diff
Installed (including dependencies)	5.20 MB	5.20 MB	+282 B
Package (unpacked)	5.20 MB	5.20 MB	+282 B
Package (download)	1.56 MB	1.56 MB	+181 B

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	26.8 ms	30.2 ms	+3.4 ms
CLI --help	78.0 ms	81.2 ms	+3.2 ms

[thymikee]

I reviewed e51dff5 and found two problems to fix before merge. Both are copied test fakes, and one shared owner should replace each.

The new device-inventory-gateways.ts is about 110 lines copied from the existing device-selection fake. It also re-states the discover/providerFirst flow of the real createComposedDeviceInventoryGateways, without its assertProviderOutcome and assertSourceFamily checks. There are now three versions of this flow. The 43 migrated daemon tests no longer cover the real composition, so a change to provider-outcome checks, family assertions or scoping will not reach them. The copy also drops findInstalledApp, and the inline bridge in withTestDeviceInventoryProvider duplicates createTestDeviceInventoryGatewaysFromProvider in the same file. The rule: one fake owns this logic, and every test tree imports it. The daemon helper can re-export it, or the package fake can move behind a single importable test-support owner. Please add findInstalledApp to its options and delete the inline bridge.

The new replay-script-source.ts copies replayScriptSourceBundleFor, maestroScriptSourceBundleFor, noMaestroIncludeSources, withClientReplayScriptSources and withFlags from src/__tests__/test-utils/replay-script-source.ts, which still has 8 or more root importers. It also re-implements loadReplayScriptSourceBundle and the file discovery in a weaker form: no glob support, no bundle size cap, no not-found AppError, and no extension-ranked ordering. Two helpers now define what a request looks like when it reaches the daemon, and they can drift apart. A change in the real client collector would not fail the daemon or replay-suite tests. The rule: one helper module owns the bundle helpers, and the collector and discovery functions are passed in. Root passes the real ones. Alternatively, give the real collector a package-owned home that both trees import, so no second implementation exists.

Not blocking, and you can take or leave these: the Android archived captures and walker builders in android-ui-hierarchy-fixtures.ts are platform fixtures, and they have several non-daemon consumers (core interactor tests, snapshot-chrome tests, src/__tests__, scripts/check-affected/device-lanes.test.ts), so a platform-android test-fixtures subpath may fit better if the eager-closure rule allows it; and the header comments in the new support files narrate the root modules they replace, so please drop them or keep one line stating the contract.

Could the daemon avoid new fakes altogether? Export the existing inventory fake through one test-support owner, or move it into test-kit with an injected context wrapper, and point the 43 daemon importers and the root importers at it. That removes about 150 lines. Keep one replay-source helper module with the collector passed in. Keep plugin.fixtures in test-kit, as you have it. Put the Android captures with platform-android if the eager-closure rule allows, or leave them at the root and accept those few edges explicitly instead of inverting core to daemon. The first decision is which module owns the inventory fake: a device-selection test-support subpath or a test-kit dependency edge. The test-kit rejection from ADR-0019 applies only to the Android pieces.

The changes are test-only, so I ran no tests or gates here. I relied on your reported 433 files and 3305 tests green, and on the green layering, DI-seams and eager-closure checks. Smoke Tests is still queued, not failed, and this diff does not touch the runtime code that run exercises. There are no conflicts. The next step before merge is to replace the two copied fakes with one shared owner each.

[thymikee]

The code still has two copied test fakes and two failing checks at 93356dc, so it is not ready to merge. The earlier review at e51dff5 raised the same two copies. The inline bridge is now an in-file helper, but both copies are still there, and the Required evidence is satisfied.

First, src/daemon/tests/support/device-inventory-gateways.ts is still a roughly 110-line copy of the fake in packages/device-selection/src/__tests__/test-utils/device-inventory-gateways.ts. It re-states the discover/providerFirst flow without the assertProviderOutcome and assertSourceFamily checks from the real createComposedDeviceInventoryGateways, and it has no findInstalledApp. So there are now three versions of this flow, and the 43 migrated daemon tests no longer reach the real composition checks. A change to provider-outcome checks or family assertions will not fail them. The rule: one fake owns the inventory-gateway logic and every test tree imports it. Please expose the device-selection fake through a test-support subpath, or move it to test-kit with an injected context wrapper. Then point the daemon and root importers at it and delete this copy. If you keep a daemon wrapper, add findInstalledApp.

Second, src/daemon/tests/support/replay-script-source.ts is a second implementation of the bundle helpers and collector. It has no glob support, no bundle size cap, no not-found AppError and no extension-ranked ordering. The root src/__tests__/test-utils/replay-script-source.ts still has the real client collector, and this file was not touched in the delta. The daemon and replay-suite tests now build bundles with a weaker collector, so drift in the real one goes unnoticed. The rule: one helper module owns the bundle helpers and takes the collector and discovery functions as parameters. Root passes the real ones. Alternatively, give the real collector a package-owned home that both trees import.

Third, createTestDeviceInventoryGatewaysFromProvider is exported but has no outside consumer. Fallow reports it as an unused export, so the Compatibility & Provenance (fallow) check fails. Routing the bridge through it in this delta created that state. Fixing the first point removes the copy and the export with it. Otherwise, please remove the export.

Fourth, oxfmt --check flags provider-device-admission-fixture.ts, which is new in this delta, and it also names src/daemon/handlers/__tests__/lease.test.ts. The delta stat shows 212 lines deleted from that second file, so I could not tell whether it is still at head. The Lint & Format check fails because of this, while oxlint itself reported 0 errors. Please run pnpm format repository-wide and commit the result.

Not blocking, and you can take or leave these: the delta stat lists limrun, CONTRIBUTING, coverage and website-docs changes, which are probably base movement from the rebase, so please confirm the diff against 2c7a8d0 is test-side only (the PR body says 83 files and I count 84), and the header comments in the new support files narrate the root modules they replace, so drop them or keep one line stating the contract.

Could both daemon copies be deleted, with the device-selection fake exposed through one test-support subpath or moved to test-kit, and a single replay-source helper that takes the collector as a parameter? That would remove about 250 lines and keep the edge count at 0 for src/daemon. You would first need to decide which module owns the inventory fake: a device-selection test-support subpath or a test-kit dependency edge. The ADR-0019 eager-closure rule that rejected test-kit applies only to the Android pieces.

On checks, the fallow and Lint & Format failures look related to this diff. I did not read the Coverage failure log, and Smoke Tests is still queued. I did not run tests or gates, and I did not grep the head to confirm 0 src/daemon edges to the five root modules. After the two fakes have one owner each and pnpm format is committed, the checks need to pass before merge.

[thymikee]

Rework pushed at c61535e (rebased onto the refreshed base 57b6b9b; findings → fixes):

• Copied inventory fake → one owner: @agent-device/device-selection/inventory-gateways-fixtures (the moved device-selection fake, findInstalledApp in options, provider bridge extracted once). test-kit was impossible without a test-kit↔device-selection project-reference cycle, so the package subpath (the stated fallback) is the owner. The daemon copy, the root wrapper, and its pin are deleted — the wrapper's fail-closed pin duplicated the real composer's pin already at src/__tests__/platform-runtime-device-inventory.test.ts:104. createTestDeviceInventoryGatewaysFromProvider stays exported: it has two consumers (lock-policy test, integration harness), and the copy fallow flagged is gone.
• Copied replay collector → your preferred option: the real script-source-bundle/source-discovery moved into replay-port byte-pure (own subpaths + their suites); one helper module replay-port/src/daemon-port/replay-script-source.fixtures.ts (./replay-script-source-fixtures) typed on DaemonWireRequest. Both trees exercise the same globs, size cap, not-found AppErrors and ranking. Root test-utils/replay-script-source.ts deleted outright — no .fallowrc suppression, no unused exports left behind.
• Android captures → test-only entries ./snapshot-capture-fixtures and ./ui-hierarchy-fixtures on @agent-device/platform-android (eager-closure allows it with the mechanics-facet exception + three approved budget rows); archived JSONs live under packages/platform-android/src/fixtures/ where own:package-capture owns them. Header comments are one-line contract statements.
• Format: pnpm format run repo-wide (the two files you saw were already fixed by the base refresh); base delta is test-side only — the collector moves are byte-identical and the only production root edit is two import lines in src/commands/replay/index.ts; the limrun/CONTRIBUTING/coverage/website noise is gone against the refreshed base and the body's file count now matches git diff --name-only origin/refactor/daemon-test-fakes...HEAD (124).
• Parity: vitest list src vs base differs only by the two moved test files' path keys and the one intentionally deleted duplicate pin. Gates green on the pushed commit (check:affected --run, layering, di-seams, gate-manifest, fallow, eager-closure, ratchet).

[thymikee]

The PR is ready at c61535e. Both earlier problems from the 93356dc review are fixed: the fallow findings sat on the copied fakes, and the Lint & Format failure sat on the unformatted fixture, so both are gone or formatted. All 36 checks pass, and the review found no code problems. Not blocking, and you can take or leave these: the single fake in packages/device-selection/src/inventory-gateways.fixtures.ts (https://github.com/callstack/agent-device/blob/c61535e/packages/device-selection/src/inventory-gateways.fixtures.ts#L77) restates createComposedDeviceInventoryGateways without assertProviderOutcome and assertSourceFamily, so a malformed provider outcome in root tests would fail with a TypeError or pass instead of the typed provider_inventory_contract_violation, and the composer pin already owns that contract; the three new APPROVED_OVER_CEILING rows and the mechanics-facet exceptions in scripts/tests/eager-closure-budgets.ts (https://github.com/callstack/agent-device/blob/c61535e/scripts/__tests__/eager-closure-budgets.ts#L135) could be dropped once 11a-2 settles and the Android fixture subpaths can live in test-kit; and the PR body names the inventory pin as src/tests/platform-runtime-device-inventory.test.ts when the file is src/platform-runtime-device-inventory.test.ts. I did not run tests or gates myself, so the parity and gate results rest on the PR body and green CI. I also did not check that moving the collector adds no CLI startup import-closure weight beyond the passing guard, or that the 43-file count in the body matches the 37 files I counted under src/daemon. The total of 60 importers does confirm one owner. Nothing else needs to happen before merge.

[thymikee]

Non-blocking items taken; pushed as bd49bf8 (normal push):

• Fake restating the composer flow: assertProviderOutcome/assertSourceFamily moved from src/platform-runtime-device-inventory.ts into @agent-device/contracts/device (both sides already import that subpath; the fake can't import the root composer). The fake's provider path now calls the shared assertProviderOutcome, so a malformed outcome fails closed with provider_inventory_contract_violation in both paths — pinned by a new fixture test. Composing through createComposedDeviceInventoryGateways itself wasn't possible: it needs the root's platform-module registry/host and hardcodes the Apple findInstalledApp probe, which the fake must supply or omit. The fake's local per-family filter stays: local is a flat whole-inventory discoverer fanned out per family, so filtering there is the adapter to the per-family source contract, not a restated assertion (asserting instead broke three tests that deliberately hand the fake mixed-family inventories).
• PR body: pin path corrected to src/platform-runtime-device-inventory.test.ts; the 43 was all daemon+daemon-composition importers — corrected to the 37 under src/daemon.
• APPROVED_OVER_CEILING rows left as-is for the post-11a-2 follow-up.

Gates: 11,030 tests green across src/daemon/src/__tests__/packages, typecheck and layering clean, check:affected --run fully green under the gate lock.

[thymikee]

Coordinator: rebased onto the current tip of the PR below (stack sync, no content changes).

[thymikee]

This PR is ready at 1159838. The earlier clean review at c61535e still stands, and the new commit adds a contracts export, device-selection fixture, root composer and one daemon test change that I found correct when reading the diff. All 36 checks are green, and they cover those routes. I did not run the tests locally, and I did not execute a check that the new fixture test fails without assertProviderOutcome; I reasoned that from the code. I also did not confirm beyond green CI that the export-pin and eager-closure gates account for the two new contracts facade exports. Not blocking, and you can take or leave these: the rebase comment says "stack sync, no content changes" and the body cites bd49bf8, but this head adds a real contracts export and test changes, so a corrected comment and hash would help; and the web-close teardown test change in daemon-runtime-web-close-teardown.test.ts (installFakeManagedAgentBrowser plus a stderr assertion) is a separate concern from the contracts inventory work, so it is worth keeping out of the stated scope. No conflicts are known. The PR is still a draft with the ready-for-human label, so nothing else stands between this delta and merge.

[thymikee]

Coordinator correction to my earlier sync comment: the sync itself changed nothing. It only rebased the branch's existing commits onto #3519's new tip, 773f78b. 1159838 is bd49bf8 (the worker's contracts-export and inventory-assertion commit) rebased; the hash changed but the content didn't. The web-close teardown test change (installFakeManagedAgentBrowser plus the stderr assertion) belongs to #3519 (773f78b), not this PR. It only appears here when the diff is taken against an older #3519 head.

[thymikee]

Coordinator: rebased onto #3519's new head 8f501eb (#3519 was rebased onto main; see its comment). The rebase applied cleanly and none of this PR's commits changed. check:quick passes.

[thymikee]

The earlier review at 1159838 found no problems, and the rebase onto the new #3519 head (2354fd0) changed only the base. Your patch is the same apart from hunk offsets, and all 41 checks pass. Not blocking, take or leave: createTestDeviceInventoryGateways in https://github.com/callstack/agent-device/blob/2354fd0/packages/device-selection/src/inventory-gateways.fixtures.ts#L88 restates the real createComposedDeviceInventoryGateways in https://github.com/callstack/agent-device/blob/2354fd0/src/platform-runtime-device-inventory.ts#L38-L125 (provider-first discovery, declined-to-local fallback, provider projection, and per-family fan-out that swallows errors). The deleted root helper built its gateways through the real composer, and about 57 root, daemon-composition and integration test files now use the copy, so they could pass while production behavior drifts. A root-side wrapper over the real composer for src/__tests__ and test/integration would keep those tests honest, and the package fake could stay for the daemon tree only.

Two questions. First, the fake exists only because the daemon test tree cannot import the root module. Could the composer move into @agent-device/device-selection, with findInstalledApp and the host loader injected, so the fixture builds on the real one? Second, source-discovery.ts says it runs on the caller (#1802: the daemon opens no caller path), yet it now sits in packages/replay-port/src/daemon-port, and nothing stops daemon code from importing it. Is there a client-owned home the fixture could import, such as a client subpath, so caller filesystem reads stay out of the daemon port?

I did not run the tests or check:quick locally and relied on the CI results. I judged the 70-file delta from the range-diff and a full-diff comparison, not line by line, since it is almost all upstream main and #3519 content. No other reviewer has looked at this head, and there are no review threads. There are no conflicts. The two design questions above are the open item for this head.

[thymikee]

Both design questions taken; pushed at e4eee6b (stack of two commits on the fresh 11a-2f base — force-with-lease was needed because the base moved under the previous push; content of the earlier commits unchanged):

• Q1 (composer home): yes — the flow moved into @agent-device/device-selection/composed-inventory-gateways with the findInstalledApp probe injected instead of hardcoded, as a production subpath. src/platform-runtime-device-inventory.ts keeps its path as the production wiring that attaches the Apple simulator probe; the composer hop is function-scoped so the composition-root hub stays flat (hub no-growth gate green). The fake now builds its gateways through the real composer with fake registry sources — the restated flow is deleted, so root/daemon/integration consumers exercise production behavior, which also retires the wrapper suggestion: the one owner is the package entry both trees build on. The probe-attachment pin stays root-side (platform-runtime-device-inventory.test.ts, mocking the tool-provider as before); the package suite pins the injected-probe path.
• Q2 (collector home): moved — script-source-bundle, source-discovery, and the request fixture now sit at packages/replay-port/src/ (client-side replay vocabulary, next to session-replay-vars), outside the daemon-port/ engine zone; subpath names unchanged, so consumers retarget by path only. Caller filesystem reads are out of the daemon dispatch port.

Gates on the pushed head: typecheck, layering (incl. enumeration + eager-closure hub budgets), quick, di-seams, gate-manifest, fallow green; full src scripts packages unit sweep 14,230 tests green pre-rebase, targeted clusters green post-rebase.

[thymikee]

Coordinator: rebased onto #3519's new head af6925d20 (#3519 was rebased onto main again). This PR's 13 commits, including the design-question answers at 9dc0bb5cb, replayed without conflicts and their content is unchanged. Verified: check:quick passes; the device-selection, replay-port, platform-android, contracts, daemon, composition and layering lanes pass (678 files, 5044 tests). New head 3bdeef3fe.

[thymikee]

Coverage was red on the size ratchet: scripts/layering/package-boundaries.test.ts is over the 1,000-line tripwire (961 at the merge-base), and this PR's consumer-gate pins grew it to 1,005. Fixed at the cause in 1ae90cfd8 — the fixture-subpath pins moved to their own test module instead of trimming anything:

• New scripts/layering/test-only-fixture-subpaths.test.ts holds the test-only fixture subpath inventory owned by package-boundaries.ts: R11's TEST_ONLY_FIXTURE_SUBPATHS accept/deny gate (moved byte-identical, incl. the independent set pin and the package-test/ accept case) plus the platform-android manifest's fixture export entries, which were two lines added inside the real-tree key-list test. The new file mirrors the R13-side pin's placement next to its owner (platform-package-policy.test.ts), following the facade-surface.test.ts split precedent.
• The manifest assertion keeps its full sorted key list; it now calls readWorkspacePackages itself rather than riding the real-tree test's package list — same assertion, same tree.
• package-boundaries.test.ts ends at 955 lines (≤ 961); nothing else was touched.

Verified: ratchet test green, check:layering green (R11/R13 messages unchanged), check:quick (lint+typecheck) green, format:check green, and the three affected test modules pass (46 tests). New head: 1ae90cfd8.

[thymikee]

Took the two remaining notes from your earlier reviews; both are new commits, pushed as a fast-forward:

• Duplicate host stub (11:23 review): src/platform-runtime-device-inventory.test.ts no longer redeclares a DeviceInventoryHost. It imports testInventoryHost, now exported from @agent-device/device-selection/inventory-gateways-fixtures (775c0068e).
• Daemon importing the caller-side collector (12:38 review): R11 now denies @agent-device/replay-port/source-discovery and @agent-device/replay-port/script-source-bundle to daemon production files; the daemon receives the client's source bundle in the request (ff30a0c4b). Accept/deny cases are in scripts/layering/client-only-subpaths.test.ts. A planted daemon import fails with the new R11 message. The test-consumer predicate is extracted into isTestConsumerFile, so both R11 subpath gates share it.
• The header comment you flagged already names only the probe.

Verified at ff30a0c4b: check:quick, check:layering (317 tests), the size ratchet, check:fallow (no issues in the 4 changed files), check:affected --run (all runnable checks passed).

[cubic-dev-ai]

All reported issues were addressed across 4 files (changes from recent commits).

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

View guided diff | Turn on auto-fix | Re-trigger cubic</sub>

[thymikee]

The earlier duplicate-host question is resolved, and I see no code defect at 196452d. The change is still pending evidence: only the Mutants shards are still running (kernel-errors-1, daemon-ref-frame, scroll-edge-state, selectors-2/7/8, target-annotation-serde, snapshot-occlusion), and none has failed. This delta touches scripts/layering, one device-selection fixture export and one root test, so none of it sits on the routes those shards mutate. There are no conflicts. I read the code but did not run the layering gate or client-only-subpaths.test.ts locally, so the regression checks rest on reading, and I did not check whether the closure walker in eager-closure-budgets can express a per-hub deny set without new plumbing.

Before merge, the Mutants shards need to finish green. Please also answer one design question: does the src/daemon.ts hub closure own the client-only rule, or does a hand-listed path set own it? Today the gate defines the daemon by the DAEMON_SOURCE_FILE regex plus the two DAEMON_PROCESS_ROOT_FILES. A static import of the replay-port collector from src/platform-runtime-daemon-services.ts, from any src/platform-runtime-.ts, or from a workspace package the daemon imports would still pass R11. The rule to satisfy is that the src/daemon.ts closure never contains packages/replay-port/src/script-source-bundle.ts or source-discovery.ts. Could you delete DAEMON_PROCESS_ROOT_FILES and the daemon-path regex, and give the src/daemon.ts hub entry in eager-closure-budgets a deny set for those two files, enforced like denyPlatformImplementations? That one check would cover daemon/, the root entry, the composition root, every platform-runtime- module and every package the daemon reaches, with no hand edits. The hub closure already exists, so nothing needs to change first. Dynamic imports would stay outside it, which is the limit the platform-implementation rule already accepts. If you keep the path gate instead, please note in its comment that it covers direct imports only.

Not blocking, and you can take or leave it: the local scope in platform-runtime-device-inventory.test.ts is the same frozen literal as the fixture's private testRequestScope, so exporting testRequestScope next to testInventoryHost and importing it would remove the copy.

On the open inline threads from the other reviewer, all seven are fixed at this head, so please resolve them: client-only denies for src/daemon.ts and src/daemon-composition.ts (the wider transitive gap is the question above), isTestConsumerFile recognizes packages//test/, literal lists pinning the fixture and client-only sets, platform-package-policy, retired-paths-policy.ts, device-lanes.test.ts fixture path, and test-only fixture paths gated by the consumer predicate.