analyze-code-quality

Analyze the overall quality of the source code by running all available checks and looking for known anti-patterns. Generate a comprehensive quality report. ## Process ### 1. Run automated checks Run these commands and capture the results: ```bash # Unit tests with coverage npm test 2>&1 # Linter npm run lint 2>&1 # TypeScript type checking npm run typecheck 2>&1 # E2E tests (if server not already running) npm run test:e2e 2>&1 # Smoke tests — run the BUILT dist/cli.js, so they catch ESM-bundle-only # runtime failures the tsx-based e2e suite can't (e.g. a bundled CJS dep # calling require()). Requires a prior `npm run build`. npm run test:smoke 2>&1 ``` ### 2. Analyze test coverage — treat 100% as a floor, not a ceiling Read the coverage output from step 1. Identify: - Files with <50% line coverage (high risk) - Files with 0% coverage (untested) - Areas where unit tests exist but E2E tests don't (or vice versa) **Then explicitly state the limit of what this number proves.** Line/branch coverage shows every *line ran* — it does **not** show that every *behavior* or every *sequence of behaviors* is *asserted*. A stateful module can sit at 100% line/branch/function/statement coverage and still ship basic bugs, because each individual operation was tested from a clean initial state while the *transitions between internal states* were never exercised. So do **not** treat a high coverage number as a stopping point: a module at 100% coverage is exactly where the behaviora...