test: enforce declared launches for daemon fixtures

Merged
TH
5d ago
+1178-256

Summary

Follow up on #4416 with declared daemon-fixture launch plans and teardown joins. Eighteen files; test infrastructure, fixture consumers and Vitest discovery. Production daemon behavior and gate thresholds are unchanged.

Review corrections cover module resolution, wrapped/typed launchers, namespace destructuring, bound plans, duplicate observer diagnostics and no-daemon teardown. Guard tests run directly in Vitest. The guard remains bounded syntactic enforcement; assignment/container aliases are outside its coverage. Design answer and receipt.

Validation

Exact head: 18fad61f628ce7744b672b880d94a8da5d3d6002; previous head: a2dc6558ade4598585d1dd6d8dc56ac6a4ccfb60.

  • Fresh frozen install/build and exact-head check:affected --run --head passed, receipt run-7tAruR: 42 runnable passes, 25 skips, no failed/unrun checks; clean unchanged checkout. Unit: 19,080 Vitest/76 Node passed, three/six skipped.
  • Guard inputs: before 14 failed/14 passed; corrected 28 passed. Observer: before 1 failed/5 passed; corrected 6 passed. Focused: 38 passed. Planted no-daemon teardown omission fails only with the correction.
  • Earlier run-Z5Avmu failed a release-publish timeout; unchanged-base unit passed. That receipt remains failed, cause unproven. No source or timeout changes preceded this clean rerun.
  • Previous hosted merge-ref CI and requested mutation shards passed. Ready-for-review CI/review remain required. No device-facing change. Cold self-review of the follow-up; no fresh independent source review.

Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.