feat(tools): /install crawlproof installs CrawlProof - #491
Merged
Conversation
`/install crawlproof` printed "unknown engine or tool". The command existed on a box only as part of the `cli-tools` set, so getting it meant knowing that it travels with seven other commands, which is not something the pit should expect anyone to know. It is its own entry because `/install crawlproof` should install CrawlProof. Reachable two ways on purpose: the `cli-tools` set symlinks a wrapper of the same name, and this installs the package that wrapper vendors. Having both is safe, because the wrapper hands over to a `crawlproof` on PATH that is not its own and refuses to follow one that is, which would be an exec loop. An ordinary global npm package, so `npm install -g` is idempotent and the install is also the upgrade, the same as bo and railway. No upgrade key. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvWJ4336pxTFRdRbvsTQeD
ThreatCrush Security Scan0 finding(s) in the 2 file(s) this pull request changes. Nothing in the files this pull request changes. 91 pre-existing finding(s) elsewhere in the repository — **HIGH/CRITICAL**: 8 | **MEDIUM**: 73 | **LOW**: 10Not introduced by this pull request. The full set is in the Security tab.
…and 71 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CrawlProof reached a box only as part of the
cli-toolsset, so installing it meant knowing that it travels with seven other commands. The pit should not expect anyone to know that.Now it has its own entry:
Two install paths, deliberately
The
cli-toolsset symlinks a wrapper namedcrawlproof, and this entry installs the package that wrapper vendors. Having both on a box is safe rather than merely tolerated: the wrapper hands over to acrawlproofon PATH that is not its own, and refuses to follow one that is, which would be an exec loop. That refusal is tested upstream in cli-tools.Shape
An ordinary global npm package with no
upgradekey, becausenpm install -gis idempotent and the install is also the upgrade, the same asboandrailway. Modeled on theboentry throughout.The dashboard is a TUI and wants Node 22.6+;
statsand--jsonrun anywhere. Noted in the comment and the README rather than enforced, since nothing else in TOOLS declares a Node floor.Verified
toolList()now prints the row, and/install crawlproofresolves instead of erroring. Tests: 106 passing acrosstools,helpandtui— the structural test that walks every TOOLS entry covers the new one.🤖 Generated with Claude Code
https://claude.ai/code/session_01HvWJ4336pxTFRdRbvsTQeD