Development record
commands/launch.md documents a top-level files count in launch --dry-run --json, but DryRunReport has no such key; the file list is bundle.files, an array; the bullet violates the file's own dotted-path convention
issueresolvednitpickiss-367
commands/launch.md documents a top-level files count in launch --dry-run --json, but DryRunReport has no such key; the file list is bundle.files, an array; the bullet violates the file's own dotted-path convention
Evidence
commands/launch.md:30— "-files— how many files the bundle would include."internal/core/launch/dryrun.go:38-48—DryRunReporttop-level keys are version, bundle, scan, lockstep, retention, smoke, gates, would_publish, would_refuse_on; nofiles.- The file list is
bundle.files(array of objects). Thefiles intcount lives onPayloadRenderResult(render.go), which--dry-runnever emits. - Surrounding bullets use dotted paths (
scan.hard_fails,smoke.ok), so barefilesreads as a nonexistent top-level key.
Adversarial verdict
CONFIRMED (nitpick). Datum recoverable from bundle.files; violates the file's own dotted-path convention. Fix: reword the bullet to bundle.files (count the array).
Frontmatter
| id | iss-367 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | nitpick |
.abcd/work/issues/resolved/iss-367-commands-launch-md-documents-a-top-level.md
open on GitHub ↗ · commit history ↗
mentions1
- dcn-26082000000000052026-08-20 — bughunt round 3 (branch bughunt-a/round-3): captured twelve findings (iss-360..iss-369, plus two renumbered to iss-373/iss-374 after round 2's own collision re-mint landed inside this round's block — the week's fourth collision,