Add issue forms, a light PR template, and an Alpha banner - #10
Merged
Conversation
Why: Strangers landing on the public repo had no install-failure, bug, or feature form, and no pull-request checklist. The Alpha, macOS, and Xcode limits were easy to miss on the first screen. Changed: Issue forms now cover install failure, bug, and feature. The chooser disables blank issues and points security reports at GitHub Security Advisories. The pull-request template is a public-patch checklist and does not require agent:context or a task session directory. README, getting-started, CONTRIBUTING, and status state the Alpha banner and link the issue forms. Specs and the specs manifest record the new .github community paths. Front-door tests pin the forms, the PR template, and the banner. Verification: npm run agent:verify -- --profile spec-only --paths .agents/manifests/specs.yaml,.github/ISSUE_TEMPLATE/config.yml,.github/ISSUE_TEMPLATE/install-failure.yml,.github/ISSUE_TEMPLATE/bug.yml,.github/ISSUE_TEMPLATE/feature.yml,.github/pull_request_template.md,README.md,CONTRIBUTING.md,docs/getting-started.md,docs/status.md,docs/test/front-door.test.mjs,spec/project-structure.md,spec/README.md,spec/build-and-test.md --session-dir task-sessions/20260819-github-community-hygiene node --test docs/test/front-door.test.mjs npm run verify:public-surface Affected: .agents/manifests/specs.yaml .github/ISSUE_TEMPLATE/config.yml .github/ISSUE_TEMPLATE/install-failure.yml .github/ISSUE_TEMPLATE/bug.yml .github/ISSUE_TEMPLATE/feature.yml .github/pull_request_template.md CONTRIBUTING.md README.md docs/getting-started.md docs/status.md docs/test/front-door.test.mjs spec/README.md spec/build-and-test.md spec/project-structure.md Refs: https://github.com/fiveonecode/simulator-broker spec/project-structure.md Session: task-sessions/20260819-github-community-hygiene
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.
Strangers could read the README, but GitHub had no install-failure, bug, or feature form, no pull-request checklist, and no starter issues. The Alpha / macOS / Xcode limits were easy to miss.
This is the GitHub community-hygiene slice only. It does not add Homebrew, a notarized app, or npm. It does not change the self-hosted OpenCodeReview workflow.
What landed
agent:contextor a task session directory.Starter issues
These are real leftovers, not placeholders:
bash_profilewhen a bash login already has itdocs/testfront-door checks as a public npm scriptpackage_distributiontestsOut of scope
Homebrew formula/cask, notarized app, npm publish, OpenCodeReview workflow edits, broker runtime changes.
Verification
npm run agent:verify -- --profile spec-only— passnode --test docs/test/front-door.test.mjs— 13/13 passnpm run verify:public-surface— pass (250 files)npm run agent:complete— passHead:
170244b72e6dcffc67b5fd87af48f2f36a57292dSession:
task-sessions/20260819-github-community-hygiene