Move cross-family runner contracts into module integration tests

This commit is contained in:
2026-11-22 04:33:28 +00:00
parent 93d94fdd0a
commit 20c0975d9d
7 changed files with 175 additions and 53 deletions

View File

@@ -1675,8 +1675,7 @@ fake HTTP provider, closing their earlier runtime-wrapper setup blocker. All D&D
module and configuration tests, their focused vet checks, contracts/shared/helper
tests, and focused native CLI tests pass. Whole-tree compilation remains pending:
CLI and integration fixtures still reference removed APIs and legacy imports.
Leaf-assembled module tests also need a proper integration-test home to
satisfy the existing import-boundary check. Dependency tidy/old-path removal,
Dependency tidy/old-path removal,
notice reconciliation, remaining fixture migration, and full validation are not
complete; this stage is not marked finished.
@@ -1690,6 +1689,16 @@ behavioral coverage. Whole-tree compile-only validation still fails at the old
ConfigKit YAML import in CLI tests and removed completion/checkpoint APIs in
module integration fixtures; those blockers remain required work.
Moved the cross-family spell, combat, enemy-event, and Seriatim runner contracts
into the black-box module integration package. They use public module APIs and
share a small native provider/embedded-engine fixture, preserving complete
assessment/history, strict/permissive outcomes, scene gating, intrinsic codec,
and transcript metadata/source-reference coverage. These selected integration
tests and their vet/repeated race checks pass, as do all D&D, generic, and
Seriatim package tests and the unchanged production import-boundary suite.
The remaining legacy integration files still prevent running that whole package;
their completion/checkpoint fixture migration is not finished.
**Goal:** delete the old architecture rather than leave dormant alternatives.
**Inspect/change:** all production/test callers of the feature roadmap's removal