Clarify verbosity and collection discovery for migration handoff

This commit is contained in:
2026-11-20 03:28:54 +00:00
parent 69d2ba7038
commit 83d33777e7
2 changed files with 9 additions and 1 deletions

View File

@@ -219,6 +219,9 @@ and CLI application-loading/source-selector helpers.
through `promptkit.DirectoryInputs`, no implicit main, existing schema base
and engine retry setting, and the default upstream bundle. Do not change
collection traversal, peer composition, or whole-record replacement.
`DirectoryInputs` retains explicit directory-selector support; collection
discovery continues through the file source's ConfigKit import globs for
`collection.yml` and `collection.yaml`.
6. Use fresh application input per comparison side and invocation-owned state
under the native factory lifecycle; comparison may share that state without
sharing either side's selected values. Start without an engine/config cache:
@@ -366,6 +369,9 @@ qualified IDs and independent namespaces, raw byte output, native structured
serialization, completed invalid content/status 4, and resultless operational
failure/status 1. Include a small typed-error mapping table rather than parsing
error prose. Use native config classification for representative load failures.
Verify `--verbose` leaves artifact stdout unchanged and routes emitted Info and
Warning messages to stderr under native visibility rules, without fixing their
wording or requiring a particular generation summary.
## Stage 6: Add Separate Native Report Delivery