Classify invalid artifact relations as input errors

This commit is contained in:
2026-11-20 13:48:55 +00:00
parent 672b7f0ebd
commit 7e45ffca43
5 changed files with 71 additions and 2 deletions

View File

@@ -72,6 +72,16 @@ Required remediation:
## 2. P2: Classify identifiable Narratio input errors consistently
Status: Domain-validation unit completed; native identity classification remains
pending upstream support. Catalog derivation now identifies invalid relations
with a typed input error, retaining its underlying cause. Native `artifacts list`
and `run --stage analyze` regressions return status 2 for an unknown dependency;
joined storage/cancellation errors retain status 1. ckconfig v0.9.0 and the current
upstream checkout classify native ConfigKit load errors only and expose no
consumer classification hook. An upstream extension and its adoption are still
needed for campaign/session assertions in native acquisition and comparison;
permission to modify that repository has been requested.
Stages: 1, 7–10, and 12; native outcome verification in Stage 21.
Locations: `internal/app/configuration_commands.go:75–96`,
@@ -497,3 +507,13 @@ test or application changes. Earlier full application verification remains
applicable to the unchanged source. Documentation checks and `git diff --check`
were repeated for this update. No live services or performance measurements were
used.
## Remediation verification
The completed Narratio units and domain-validation portion of finding 2 pass
`go test ./...`, `go test -race ./...`, `go vet ./...`, and `go build ./...`
with official Go 1.27.4. Documentation checks and `git diff --check` also pass.
Native regression coverage verifies equivalent-party resume, real roster changes,
source normalization, and typed domain-input outcomes. No upstream files,
dependencies, releases, tags, or remote repositories were changed. Finding 2's
native configuration identity classification remains outstanding as recorded above.