Record detailed processing progress decision
This commit is contained in:
@@ -535,8 +535,12 @@ for inspection.
|
||||
|
||||
### 57. Clarify what the inherited progress flag does in processing
|
||||
|
||||
`process` advertises progress messages but supplies no producer. Define its
|
||||
behavior or clarify process help while preserving acceptance for existing scripts.
|
||||
`process` advertises progress messages but supplies no producer. **Resolved D7:**
|
||||
add processing progress through CommandKit's reporter. Operators selecting
|
||||
`--progress` want relatively detailed updates; expose meaningful stage/chunk,
|
||||
proposal, validation, and repair activity as available, rather than only coarse
|
||||
stage summaries. CommandKit owns mode precedence and stream routing; preserve
|
||||
transcript stdout. Exact wording and event granularity are implementation choices.
|
||||
[Dead code §10](12-deadcode.md#10-resolve-the-inherited-progress-flag-for-process)
|
||||
|
||||
## Test maintenance and dead code
|
||||
|
||||
Reference in New Issue
Block a user