Repository navigation
Description
Drafted by an AI agent from an operator-confirmed interview (run 20260908-home-d1).
Parent
Parent: #4004. Refs #3352 (closed), which added the output-verbosity flag after ~63,000 tokens of children_rollup in one run.
Not a duplicate of #3352. That fix works: --quiet does suppress the inventory it was built to suppress. This is the residual gap it left, found by using the flag on a larger target than the one that motivated it.
Problem
--quiet does not suppress truncated_paths.
On the depth-2 home scan in this run, the truncated_paths list ran to roughly 140 lines under --quiet. For scale: the depth-1 frontier alone held 81 entries with 48 subtrees truncated at depth 1, and a home directory is exactly the shape that truncates — many top-level entries, most of them deep.
140 lines of path list is most of what --quiet exists to avoid, and it arrives in the mode the operator selected specifically to avoid it.
Proposed fix
Under --quiet, replace the list with a count:
truncated_paths: 48
Keep the full list in the JSON snapshot. That is where a consumer needing the paths already looks, and it is unaffected by a flag that governs console output.
The count is the part that is actionable at a glance — it tells the operator whether the scan saw a little or a lot it did not walk, which is the decision --quiet output should support.
Design constraints
- Snapshot content is unchanged. This is console output only.
- The count must be visible under
--quiet, not merely absent. A truncating scan that reports nothing about truncation would be worse than the current noise, because coverage gaps are the thing the component is careful to never present as clean. - Non-quiet output is unchanged.
Acceptance criteria
- Under
--quiet,truncated_pathsis emitted as a count rather than a list. - The count is present even when zero paths truncated, so a clean scan and a suppressed list are distinguishable.
- The full
truncated_pathslist remains in the JSON snapshot regardless of--quiet, demonstrated by a test. - Non-quiet output is byte-identical to today for the same input, demonstrated by a test.
-
scripts/affected-tests.sh --runselects and passes the suites mapped to the changed files.
Out of scope
- Any other
--quietsuppression not evidenced by this run. - Changing what truncates or at what depth.
Activity
kyle-sexton commentedon Sep 23, 2026
This was generated by AI during triage.
Agent Brief
Type: Bug
Summary:
--quietonscansuppresses the children rollup but leaves the fulltruncated_pathslist in console output, which can run to well over a hundred lines on a large scan — exactly the noise--quietexists to avoid.Current behavior:
The stdout-shaping function for
scanoutput drops thechildren_rollupfield under--quietbut passestruncated_pathsthrough unchanged as a full list of path strings.Desired behavior:
Under
--quiet,truncated_pathsis emitted to the console as a count of truncated paths rather than the full list, present even when the count is zero (so a clean scan is distinguishable from a suppressed list). The full list remains in the JSON snapshot file regardless of--quiet. Non-quiet console output is unchanged.Key interfaces:
scan_stdout_payload(): under quiet mode, replaces thetruncated_pathslist with a count in the console-facing payloadtruncated_pathsoutput field: the full list in the snapshot file always; a count under--quieton the console, the full list otherwiseAcceptance criteria:
scan --quietprintstruncated_pathsas a numeric count, not a list of path strings.scan --quietagainst a target with zero truncated paths still shows the count (0), not an absent field.truncated_pathslist regardless of--quiet, demonstrated by a test.scanwithout--quietproduces output identical to before this change for the same input, demonstrated by a test.Out of scope:
--quietsuppression not already covered by this issue.fix(disk-hygiene): quiet scan prints truncated_paths count, not the f…