fix: slim CLI package and enforce clean linting - #14
Conversation
Repair the Umami proxy worker’s request handling while aligning the CLI gate commands, range flow, and test coverage with the updated behavior. Clean up Biome findings by replacing unsafe non-null assertions with explicit validated narrowing and removing stale imports and bindings. Validation: npm run lint -- --max-diagnostics=100 Know-Code-Verified: 9cfe4be37591656fc9d85d26a540ec901f37f9cbb9a043db6a127a693f7e35f9
Know-Code-Verified: d69b59b1a5efa389338aa2202576ab814cfe6f05014e0e2ff99b5d35a057e090
PR SummaryLow Risk Overview
Adds Reviewed by Cursor Bugbot for commit ad7fee9. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8881a23. Configure here.
Know-Code-Verified: ca887796f3dcd7818755f17440456bdd47abf2793d69eae56f290f4a4938b6b0

Summary
This change makes the published
@chtnnh/know-codepackage materially leaner while adding a maintained lint gate for the repository.bin/, hooks, anddist/index.js) remain shipped while test-only output stays out.Why
npm pack --dry-runshowed that the published CLI artifact included compiled test files and test helpers that are never required by global installations. Keeping the package focused on runtime files reduces install/download overhead without changing the public CLI surface.Validation
npm run lint -- --max-diagnostics=100git diff --checkCloses #5