Repository navigation
Conversation
Design partners try bawbel-gate on a real agent setup and report what happened. Until now that had no home: blank issues are off and the other three forms are for bugs, design changes, and features. The form asks for the use case, environment, expected outcome, what was tested, and blockers, and has an optional checkbox to publish the results anonymously. It says plainly that no payment is implied and that vulnerabilities go through SECURITY.md. Closes #82 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015T9K217kxBqsUZ3omKYv9P Signed-off-by: chaksaray <chaksaray@gmail.com>
This branch has not been deployed
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.
Closes #82
What and why
Design partners are people who try bawbel-gate on a real agent setup and report what happened. That had no home:
blank_issues_enabledis false and the existing forms are for bugs, design changes, and features. This adds.github/ISSUE_TEMPLATE/design_partner.yml(BIZ-5).Fields: use case, environment, expected outcome (all required), what was tested, blockers (optional), and a checkbox for permission to publish the results anonymously (optional, never required). The top of the form says plainly:
It also asks reporters not to include secrets, credentials, customer data, or private hostnames, to redact manifests before pasting them, and to report vulnerabilities per SECURITY.md and never in a public issue.
Differences from the plan: the file is
design_partner.yml, with an underscore like the three existing forms, notdesign-partner.yml. No label is set, because adesign-partnerlabel does not exist in this repository and creating labels is a repository setting for the maintainer. If you want one, create it and addlabels: [design-partner]to the form.Governing spec
DESIGN.md section(s): none. This is a repository template, not behavior.
Output contract
Verification
The three existing forms validate the same way, as a baseline. Trial merges (
git merge) with #76, #78 and #81: clean.Not verified: how the form renders in the GitHub issue chooser. That needs the file on the default branch of the repository.
Checklist
git commit -s)tests/replay/if this blocks an attack class (not applicable)🤖 Generated with Claude Code
https://claude.ai/code/session_015T9K217kxBqsUZ3omKYv9P