test(runtime-host): parallelize execution host integration coverage

[M4n5ter]

English

Summary

• split the 2,995-line Runtime Host execution integration suite into four behavior-focused test files
• move the shared real-Host fixture and helpers into a dedicated fixture module
• preserve all 29 existing test cases, names, assertions, and production boundaries

Why

Node's test runner schedules test files in parallel, but the former monolithic file serialized every execution-host scenario. That single file dominated the Runtime Host suite even though its cases use independent temporary roots.

The new files group authority/interactions, queue/admission, recovery, and message lifecycle coverage. They can run concurrently without changing production code or weakening coverage.

Impact

• focused execution-host coverage: about 33.1s → 12.2s locally
• complete Runtime Host package test after the split: 27.3s locally
• production behavior and public APIs are unchanged

Validation

• npm run build:test
• focused execution-host suite: 29 passed
• npm --workspace @maka/runtime-host test: 568 passed
• npm run lint
• npm run format:check
• test-name set compared with upstream/main: no additions or omissions

中文

概要

• 将 2,995 行的 Runtime Host execution 集成测试拆分为四个按行为聚合的测试文件
• 将共用的真实 Host fixture 与辅助函数移入独立 fixture 模块
• 完整保留原有 29 个测试用例、名称、断言及生产边界

原因

Node 测试运行器会并行调度测试文件，但原有单体文件会串行执行其中所有 execution-host 场景。尽管这些场景使用相互独立的临时 root，这个文件仍长期占据 Runtime Host 测试的主要耗时。

拆分后的文件分别覆盖 authority/interactions、queue/admission、recovery 和 message lifecycle，可以并行运行，且不改动生产代码或削弱覆盖范围。

影响

• execution-host 聚焦测试本地耗时：约 33.1 秒 → 12.2 秒
• 拆分后完整 Runtime Host package test 本地耗时：27.3 秒
• 生产行为与公共 API 不变

验证

• npm run build:test
• execution-host 聚焦测试：29 个通过
• npm --workspace @maka/runtime-host test：568 个通过
• npm run lint
• npm run format:check
• 与 upstream/main 比较测试名称集合：无新增或遗漏