Migrate combat and grounded pipeline integration tests to native execution

This commit is contained in:
2026-11-22 04:54:27 +00:00
parent 562dfad5cd
commit 572b267c5d
4 changed files with 191 additions and 516 deletions

View File

@@ -1666,64 +1666,34 @@ publication then capture failure, useful exit categories, and no reporting sidec
prompt filesystem/mount helpers, copied completion/correction/debug contracts,
old checkpoint/chunk-plan source packages, and reporting-only module fingerprint
methods. No runtime output/cache/debug files were removed. Preserved typed
validation-result checks and intrinsic artifact-schema compatibility; migrated
D&D tests away from retired metadata and intermediate-output surfaces without
relaxing domain codecs. Corrected stale source/JSON fixture expectations and the
configuration NUL/resolved-control assertions. The production executable builds;
the real executable route and text/JSON/YAML/fallback tests now pass with a local
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.
Dependency tidy/old-path removal,
notice reconciliation, remaining fixture migration, and full validation are not
complete; this stage is not marked finished.
validation-result checks, intrinsic artifact schemas, domain codecs, reference
compatibility, and source/identity rules. Corrected stale source/JSON fixture
expectations and the configuration NUL/resolved-control assertions.
All framework package tests and vet checks now pass; the complete pipeline
package also passes race checks. Migrated resolution, construction, reference materialization,
generated handoff, codec, source/annotation isolation, diagnostics, and session
coverage to the current contracts. Removed tests tied solely to superseded
outer retries, checkpoint provenance, manifests, and attempt-debug wrappers;
native producer, cache, assessment, and capture tests retain their replacement
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.
All framework, module (including the complete integration package), and
configuration tests now compile and pass. Migrated retained resolution,
construction, reference materialization, typed handoff, codec, source/annotation
isolation, diagnostics, and session coverage. Cross-family contracts live in the
black-box module integration package and use real production registration and
native provider fakes; the unchanged import-boundary tests pass. Published domain
and evidence files replace retired manifests and intermediate-output ledgers.
Spell, NPC, location, occurrence, combat, and grounded-pipeline fixtures retain
canonical identity, contextual selection, source chronology, scene eligibility,
complete correction/revalidation, and evidence-union behavior. Invalid combat
enums fail at the native structural boundary rather than bypassing its schema.
Removed tests tied solely to superseded outer retries, checkpoint provenance,
manifests, and attempt-debug wrappers; native producer/cache/assessment/capture
tests own the replacement behavior. Complete pipeline and integration repeated
race checks pass, as do framework/integration vet checks.
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.
Migrated the older spell and NPC registry integration fixtures to native
provider requests, real JSON lane publication, and version 6 test configurations.
Kept source ordering/identity, capability failures, reference inputs, malformed
candidate rejection, and consolidation coverage. NPC reconciliation now tests
explicit strict failure, permissive final safe groups with one qualified fallback,
and correction to a complete proposal. Shared production registries remain real;
test providers classify the selected native response contract rather than
recreating completion requests or manually decoding model output into modules.
These selected integration tests, vet/race checks, all framework/configuration
tests, and import-boundary tests pass. Remaining combat, location, occurrence,
and grounded-pipeline fixtures still block full integration compilation.
NPC-occurrence and location handoff tests now run through native providers and
published lane/evidence files. Retained contextual same-name location selection,
names-only NPC projection, deterministic durable IDs, source chronology, earlier-
producer requirements, and no consumer execution after strict producer rejection.
The multi-chunk semantic NPC fixture now derives evidence from the actual rendered
chunk rather than completion order, and verifies both downstream chunks with the
canonical registry identity under ordinary parallel workers. Removed only the old
generated-reference checkpoint assertion; existing native cache/eligibility tests
own its replacement behavior. Updated occurrence test configurations to version 6
and made temporary config cleanup test-owned. These selected integration tests,
vet/repeated race checks, framework/configuration tests, and import-boundary tests
pass. Only combat and grounded-pipeline legacy fixtures remain as integration
compile blockers; CLI/dependency cleanup and complete validation are still pending.
The production executable builds. Real executable route and text/JSON/YAML/
fallback checks passed with a local fake HTTP provider after removal of the old
runtime wrapper. Focused native CLI tests pass, but the full CLI suite and
whole-tree compilation remain blocked by legacy CLI fixtures/imports; the current
setup failure is old-path ConfigKit importing the removed YAML `plugin/limit`.
Remaining CLI test migration, dependency tidy/old-path removal, notice
reconciliation, and whole-tree validation are required before completion.
This stage is not marked finished.
**Goal:** delete the old architecture rather than leave dormant alternatives.