Implement positional prompt execution with native reporting and outcomes

This commit is contained in:
2026-11-20 04:42:59 +00:00
parent f9b5121432
commit 6f39bca841
6 changed files with 437 additions and 5 deletions

View File

@@ -445,6 +445,26 @@ upstream analysis or rendering suite.
## Stage 5: Implement Positional Generation, Request Mapping, And Outcomes
**Status: Complete.** `run PROMPT_ID` uses native resource/input/execution
bindings and equivalent command-scoped aliases, typed namespace strings and
public engine views, and one `Engine.Run` dispatch with the invocation context.
Operation durations pass through unchanged. Main results use the native reporter
with the artifact-only byte-preserving text template; structured modes retain
the native result. Completed content-validation failure is domain status 4;
resultless operational failures remain status 1 with preserved typed causes and
safe explanations. Configuration classification uses native diagnostic evidence.
Verified on Go 1.27.4 with focused controlled-provider integration tests, race
checks, and vet: canonical/preferred aliases, input file/literal precedence,
commas and additional equals signs, explicit numeric zero and empty reasoning,
service tier and extra parameters, independent namespaces and exact qualified
IDs, session context, raw stdout, native JSON/YAML results, verbose diagnostic
stream separation, invalid-content delivery/status 4, and operational failures
without a result or provider-payload disclosure. Typed-error/nil-result checks
and the shared Narratio discovery/preparation/generation fixture cover mapping
and context consistency. Actual timeout/cancellation lifecycle checks follow in
Stage 7; full-package compilation still awaits Stage 8 legacy removal.
**Primary files:** the new application `run` declaration, request/outcome
helpers in `internal/adapter/cli`, and run integration tests.