Clarify progress and verbose reporting in the CommandKit roadmap

This commit is contained in:
2026-11-20 03:46:30 +00:00
parent e476c08ea4
commit bcbfc0fa4a

View File

@@ -245,6 +245,19 @@ verbose/debug; progress requires `--progress` or debug. Quiet suppresses success
results and progress while preserving failures. Material conditions also appear results and progress while preserving failures. Material conditions also appear
in the result, independent of diagnostic visibility. in the result, independent of diagnostic visibility.
Emit Progress for stage transitions and useful finer-grained activity, including
download starts/completions, individual speaker and artifact completions, and
reuse of prior work. These events are available with `--progress` alone and use
native streamed, unprefixed lines. Info supplies context: selected sources,
destinations, configuration, and reasons for decisions. For example, downloading
a speaker's audio is Progress; identifying the selected audio source is Info.
Keep the categories independent. `--verbose` enables informational messages and
warnings without enabling progress; `--progress` enables progress without
enabling informational messages or warnings. With both flags, stderr carries
both categories while stdout retains the final report. Do not introduce a
separate verbose-progress level or require both flags for finer-grained events.
Keep downstream streams in existing captured logs and provide concise console Keep downstream streams in existing captured logs and provide concise console
context and log locations without automatic replay. Quiet does not disable logs context and log locations without automatic replay. Quiet does not disable logs
or persistence; debug does not automatically enable downstream debug artifacts. or persistence; debug does not automatically enable downstream debug artifacts.
@@ -301,9 +314,10 @@ These work areas describe scope, not mandatory buildable milestones.
execution, add party-file selection, and remove the same-campaign diff execution, add party-file selection, and remove the same-campaign diff
restriction. Keep each comparison side independent and acquisition lazy. restriction. Keep each comparison side independent and acquisition lazy.
4. **Integrate presentation and lifecycle.** Define domain report values, route 4. **Integrate presentation and lifecycle.** Define domain report values, route
diagnostics through CommandKit, and replace ad hoc status handling. Propagate diagnostics and finer-grained progress through CommandKit, and replace ad hoc
signal cancellation and adapt runner failure/finalization paths to preserve status handling. Propagate signal cancellation and adapt runner
partial results and attempt terminal persistence. Add native completion. failure/finalization paths to preserve partial results and attempt terminal
persistence. Add native completion.
5. **Complete integration and migration.** Update behavioral tests, remove 5. **Complete integration and migration.** Update behavioral tests, remove
obsolete CLI machinery and expectations, review dependency attribution, and obsolete CLI machinery and expectations, review dependency attribution, and
update canonical documentation, examples, and affected scripts with the update canonical documentation, examples, and affected scripts with the
@@ -326,9 +340,12 @@ the integration risks without duplicating upstream parser/configuration tests:
runtime state. Party selection reaches each consumer, and diff sides remain runtime state. Party selection reaches each consumer, and diff sides remain
independent. App-only and aggregate override behavior follows ckconfig. independent. App-only and aggregate override behavior follows ckconfig.
- Structured results remain separate from diagnostics, retain meaningful partial - Structured results remain separate from diagnostics, retain meaningful partial
work, and use native outcomes. Lazy commands avoid configuration/services; work, and use native outcomes. Representative finer-grained progress events
cancellation reaches active work, preserves checkpoints, and permits terminal appear with `--progress` alone; informational context follows verbose mode,
persistence and lock release, including their failure reporting. and combining the flags exposes both without changing stdout reports.
- Lazy commands avoid configuration/services; cancellation reaches active work,
preserves checkpoints, and permits terminal persistence and lock release,
including their failure reporting.
- Existing consequential stage, resume, publication, restore, and cleanup - Existing consequential stage, resume, publication, restore, and cleanup
behavior remains protected. Safe inspection, diagnostics, and persistence behavior remains protected. Safe inspection, diagnostics, and persistence
preserve the established secret-handling boundary. preserve the established secret-handling boundary.