Add GETTING-STARTED.md: the install flow with agent-refusal fallbacks#51
Merged
Conversation
One shareable doc: paste the install prompt; if the agent refuses (expected behaviour for this request shape, likelier in strict sandboxes and right after a release), escalate through confirm → guide checklist → 3-command manual fallback, and report novel refusals back as field-test personas. Root doc, so it stays out of the npm tarball. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Focused getting-started guide clarifies AI install flow and refusal handling. 🎯 Quality: 97% Elite · 📦 Size: Small 📈 This month: Your 215th PR — above team average · Averaging Excellent |
mariojgt
approved these changes
Jul 14, 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
2 participants
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.
Summary
Adds a shareable teammate-facing doc with the simple flow: (1) paste the tested install prompt, (2) if the agent refuses — expected occasionally, since the request matches a supply-chain shape and is likelier in strict sandboxes or right after a release — escalate through replying with the vetting confirmation the agent asked for, re-running
npx @patchstack/connect guideto finish only the ✖ items, then (3) a three-command manual fallback, plus a "done when" checklist and an ask to report novel refusals so they become field-test personas. The README install-prompt section links to it, and CLAUDE.md's sync invariant now covers all three copies of the prompt (README, GETTING-STARTED, field-test/prompt.txt), verified identical. As a root doc it is not in the npmfileslist, so it adds no audit surface to the shipped tarball.🤖 Generated with Claude Code