Repository navigation
[NO-TICKET] Tell the agent how to finish the map-link lines setup leaves - #446
Merged
Merged
Conversation
Setup can end with "Some attacks are only reported, not blocked yet" and "Could not confirm whether rules for this app are ready". Both mean the map setup uploaded could not be linked to the guard, and nothing told the agent how to finish that, so it passed the lines on to the person. AGENT-INSTALL.md now says to run setup --verbose, read the reason on the "could not bind this map" line, and fix it, with the fix for each reason, then rerun setup until the line is gone. It also says how to answer "is my app protected?": installed, blocking only once the site is connected to an account that includes protection, and live only after publishing again. The setup hints point at --verbose, and the readiness line says it follows the link when there is none. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
🎯 Elite quality (95%) — Docs and CLI hints now point agents to the exact verbose reason and its fixes. 📦 Small |
Contributor
Author
|
/review |
daniloradovic
approved these changes
Oct 26, 2026
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
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.
What changed
Setup can end with two
To dolines:Some attacks are only reported, not blocked yetCould not confirm whether rules for this app are readyBoth mean the same thing: the app's map was uploaded but could not be linked to the guard, so rules written for this app's own inputs can only report. The guide says
To dolines are the agent's to finish, but nothing told the agent how to finish these two. In a recent Lovable install it passed them on to the person, who was left asking whether the app was protected.AGENT-INSTALL.mdnpx @patchstack/connect setup --verbose, read the reason on thecould not bind this map to the runtime guard — <reason>line, fix it, then rerun setup until the line is gone. It gives the fix for each reason the code can report:dry-runenforcement until then);Setup output (
src/cli.ts)setup --verbose. It used to say "Finish adding protection, then run setup again."Tests
npm run typecheckandnpm run buildare green, as are the disclosure, capability and install-prompt checks.npm test: 4603 passed. 4 failed under full-suite load and all pass when run on their own: three timing tests and the plain-wording setup test, which hit its 5s timeout.Rollout
Both
AGENT-INSTALL.mdand the setup output change, and agents read the published tarball. So the hostile field test is owed after the release that carries this, plusstandardorlovablefor doc accuracy.🤖 Generated with Claude Code