Finding
bin/autogen-markdown-doc.js is ~350 lines containing CLI parsing, marker detection, orchestration, error handling, and output formatting. DESIGN-PRINCIPLES.md states: "The bin file should remain as thin as possible — typically just a runCli call and a descriptor import. All real logic belongs in src/ as TypeScript."
There is no src/ directory. The project.json silently acknowledges "no build step," but DESIGN-PRINCIPLES does not document this exception for orchestrator packages.
Context
The no-TypeScript / no-src/ design may be intentional for autogen as a pure orchestrator (it spawns child plugins rather than implementing file-processing logic itself). If so, DESIGN-PRINCIPLES should be updated to carve out orchestrator packages explicitly.
Options
- Refactor into src/ — extract orchestration logic into TypeScript files under
src/, add a build step, make bin/ a thin launcher. High effort.
- Document the exception — add a note to DESIGN-PRINCIPLES acknowledging that orchestrator packages with no file-processing logic are exempt from the thin-bin rule. Low effort.
Severity
⚪ Design / convention alignment (no runtime impact)
Finding
bin/autogen-markdown-doc.jsis ~350 lines containing CLI parsing, marker detection, orchestration, error handling, and output formatting. DESIGN-PRINCIPLES.md states: "The bin file should remain as thin as possible — typically just arunClicall and a descriptor import. All real logic belongs insrc/as TypeScript."There is no
src/directory. Theproject.jsonsilently acknowledges "no build step," but DESIGN-PRINCIPLES does not document this exception for orchestrator packages.Context
The no-TypeScript / no-
src/design may be intentional for autogen as a pure orchestrator (it spawns child plugins rather than implementing file-processing logic itself). If so, DESIGN-PRINCIPLES should be updated to carve out orchestrator packages explicitly.Options
src/, add a build step, makebin/a thin launcher. High effort.Severity
⚪ Design / convention alignment (no runtime impact)