- A targeted `npm test` run whose files are all unit suites now runs in the test manager's unit lane, beside the browser slot, so it starts as soon as admission allows instead of waiting behind another worktree's browser job. `npm test -- --status` lists the slot holder as `active` and the unit lane as `unit`. The manager's fingerprint now covers what a run can read: code and config, the selected suites, and any other top-level path those suites or the modules and scripts they load name. A changelog fragment, a note or a doc no selected suite reads no longer voids a queued or running job (Issue #1666, Issue #1677).