Describe PatchGate by the work it does - #55
Merged
Conversation
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.
Description\n\nPatchGate now has a concrete first-use path and a workspace-level adoption loop.\n\n- docs/first-use.md gives a non-blocking shadow setup and a safe feedback route.\n- docs/adoption-loop.md defines the first useful result, evidence fields, and a weekly rule for choosing user-facing work.\n- .github/ISSUE_TEMPLATE/first-use.yml collects time-to-result and first friction without asking for private data.\n- README links the first-use path and the continuous adoption loop.\n\n## Evidence\n\n- npm run verify — pass\n- 101 unit tests\n- 14 security tests\n- 25 GitHub integration tests\n- 6 CLI smoke tests\n- Action bundle, clean-room consumer fixture, release-candidate, and distribution checks — pass\n\n## Boundaries\n\nThis remains a documentation-only change. It does not claim an external pilot, publish npm, or enable merge enforcement.\n\n## Linked Issues\n\n- Relates to #4\n- Relates to #49