Migrate NPC and location normalization to native correction and explicit fallback handling

This commit is contained in:
2026-11-22 00:27:34 +00:00
parent 772b8619c1
commit 4f82d01534
16 changed files with 1062 additions and 732 deletions

View File

@@ -673,6 +673,27 @@ preservation, unchanged-candidate reassessment, and cancellation.
## Stage 15: Migrate NPC And Location Registry Normalization
**Status:** Complete. Both normalizers now use the shared native producer helper
and fixed one-time reconciliation preparation. Each response applies its own safe
groups afresh to the original records, before typed operation assessment. Added
same-schema/default-profile correction prompts and static dependencies; removed
retry transport, schema/policy fingerprints, and manifest-only asset registration.
Name-based NPC identity, evidence-anchored location identity, canonical naming,
source ordering, and domain application rules remain unchanged. Strict handling
does not silently fall back; permissive output uses only the final safe candidate
or the supplied merged artifact, with codec/identity/source construction checks.
Retained domain regressions and added native provider coverage for correction,
unchanged reassessment, final-only safe groups, failed continuation without prior
proposal recovery, structural failure, overrides/history, cancellation, and
unusable fallbacks. Native prompt-pair checks run in the content package without
depending on legacy module helpers.
Asset/reconciliation tests, vet/race checks, focused pipeline producer/runner
tests, production framework builds, and `git diff --check` pass. Both normalizer
package tests remain blocked at setup by shared legacy asset helpers importing
old ConfigKit's removed YAML `plugin/limit`; their new tests are not claimed
passing. Scheduled dependency cleanup and final whole-tree validation must run
them and close that blocker.
**Goal:** apply the proven normalizer path without domain-policy drift.
**Inspect/change:** `internal/modules/dnd/normalize/{npcregistry,locationregistry}`