Hand checked processing selections to execution

This commit is contained in:
2026-11-16 14:18:38 +00:00
parent b1d1b8302c
commit e98e525b5c
19 changed files with 268 additions and 102 deletions

View File

@@ -41,5 +41,6 @@ only on explicit request.
Process stdout contains transcript JSON when no output file is selected. Ordinary
reports may record recoverable model failures even when processing completes.
Exit status `0` means success, `1` runtime or output failure, `2` invalid usage
or input, and native comparison may return `3` for differences. See the
or input, and native comparison may return `3` for differences. A missing
processing profile or required glossary selection is an input failure. See the
[output contract](integrations/output-files.md) and [subprocess contract](integrations/subprocess.md).

View File

@@ -31,6 +31,13 @@ stays independent of application runtime assembly. Preserve its behavior from
the [CLI contract](../cli.md) when changing the command; the
adoption decision is recorded in [ADR 0001](../adr/0001-releasekit.md).
Processing preflight checks glossary selections before inspecting proposal,
validation, and enabled repair profiles in pipeline order. The checked plan
carries the resolved module specs and glossary views into execution. It reuses
profile and backend inspections and equivalent glossary views within the
invocation. Native inspection commands continue to inspect configuration
without running processing readiness checks.
## Validating Examples
Keep complete copyable files in [examples](../../examples/) and link to them from

View File

@@ -16,7 +16,10 @@ Modules implement `contracts.TranscriptModule`:
Built-in modules also expose `RepairPromptID()` for the runner to select their
repair definitions; proposal-only callers retain the existing interface.
Runner resolves configured module specs to module instances through `internal/framework/modules`.
The CLI supplies the built-in factory from `internal/modules` to the runner.
The runner resolves checked module specs through that factory. Module instances
can receive concurrent proposal calls across sections. Request inputs are
borrowed for the call and must be copied before modification or retention.
## Built-In Modules
@@ -105,6 +108,6 @@ the selected default in the [configuration contract](../config.md#pipeline-and-g
## Key Tests
- `internal/modules/*/module_test.go`
- `internal/framework/modules/registry_test.go`
- `internal/modules/registry_test.go`
- `internal/framework/proposal_generation/*_test.go`
- `internal/cli/process_ordered_integration_test.go` (pipeline/report integration)

View File

@@ -26,7 +26,6 @@ Core deterministic components:
Framework orchestration and contracts:
- `internal/framework/contracts`
- `internal/framework/preflight`
- `internal/framework/modules`
- `internal/framework/proposal_generation`
- `internal/framework/proposals`
- `internal/framework/runner`
@@ -39,6 +38,7 @@ Framework orchestration and contracts:
- `internal/framework/stagename`
Domain implementations:
- `internal/modules` (built-in module composition)
- `internal/modules/*`
- `internal/validators/*`
- `internal/prompts`

View File

@@ -414,6 +414,14 @@ attribution, provider-free inspection, constructible catalog entries, and both
request precedence paths. Update [CLI/config internals](../internal/cli-config.md),
[module internals](../internal/modules.md), and configuration docs where affected.
**Complete.** Configuration uses common validation and role fallback after
composition. Preflight passes checked role and glossary selections to execution
and reuses inspection and glossary work within the invocation. The built-in
factory lives beside the modules. Processing and native inspection preserve
their respective variable precedence with one merge per request. The CLI build
and full offline suite passed, including status 2 for an unknown processing
profile before provider dispatch or output initialization.
## Stage 12 — Unify structured-call completion and failure facts
Audit #23, #25, #41, #44.