refactor(replay): move target classification into replay-port (#2663) - #3016
Conversation
Size Report
Startup median (7 runs, lower is better):
|
|
There was a problem hiding this comment.
All reported issues were addressed across 6 files (changes from recent commits).
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
|
Temporarily reopening to trigger the required CI workflows on the repaired head. |
50a5a5a to
614fbd0
Compare
|
Reviewed at 50a5a5a, and checked again at 614fbd0, which rebases onto main and resolves the
CI: checks on 614fbd0 are still running. |
There was a problem hiding this comment.
All reported issues were addressed across 2 files (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Fix all with cubic | Re-trigger cubic
|
Reviewed at 779f121. The fix for the finding at 614fbd0 is in, the classification move into replay-port looks correct, and I have no new findings. This is ready for human review. CI: the test jobs were still running when I checked. The only non-passing check was the automated review bot, which runs no tests. |
779f121 to
15a8f49
Compare
Summary
Moves replay target classification and its 17-case test into
@agent-device/replay-port. The recorded target tree fixture also moves to a package subpath used by the package test and two daemon replay regression suites. The daemon verifier imports the classifier from its owning package. Runtime decisions and wire responses are unchanged.12 files touched; three source/test/fixture moves. This is an independent staged move toward #2663's PR B, alongside #3007.
Validation
Tested rebased commit
15a8f497eonorigin/main4bbbfb702after review fixes to the base-tree readability predicate and rename regression assertion.pnpm install --frozen-lockfile && pnpm build && pnpm check:affected --run: all runnable checks passed, including related tests, layering, typecheck, lint, build, package, fallow, export, and provider integration checks. The manifest and lockfile change selected the full local gate set.scripts/*.tsto package-source case now asserts the rename map entry before the null result, so the test cannot pass without detecting the rename.pnpm typecheckand tracked-file layering scan passed. The closure gate now treats a fixture moved out of__tests__as a new package export and loads its selector calculation on demand, keeping it within the new-entry budget.No live device replay was run for this location-only move. The remaining replay runtime and Maestro adapter move needs the issue's live
.adand Maestro characterization.Part of #2663.