Separate reconciliation preparation and proposal assessment from native execution

This commit is contained in:
2026-11-22 00:07:05 +00:00
parent 92c2382806
commit 2348730820
17 changed files with 327 additions and 1138 deletions

View File

@@ -582,6 +582,23 @@ test to a native provider fake, including catalog rejection and final correction
## Stage 13: Refactor The Shared Reconciliation Core
**Status:** Complete. Removed the reconciliation execution service and its
private completion/correction transport, retry classifications, asset/schema
registration, metadata, and fingerprints. The core now exposes fixed owned
preparation bytes, native initial/follow-up request builders, proposal decoding,
and the existing independent safety assessment/application functions. Candidate
handles, declared ranges, bounded source windows, group-safety rules, typed
application, and actionable issue prose remain; the follow-up asset owns the
replacement assignment rather than an application retry message builder.
Added the generic native correction pair with the unchanged response schema and
matching unset profile defaults, moving enduring protocol/policy into initial
system context. Retained domain-neutral regressions and added native provider/
preparation, structural-failure, fixed-material, and successive-proposal tests.
The complete reconciliation and asset tests, vet, race checks, and
`git diff --check` pass. Domain normalizer and central registration consumers of
the removed APIs remain assigned to Stages 14–15 and 24; no whole-tree compilation
claim is made at this intermediate boundary.
**Goal:** separate one-time evidence preparation from proposal interpretation.
**Inspect/change:** `internal/framework/semanticreconcile/{engine,preparation,