Add an issue-to-PR contribution workflow, templates and automated checks #9

User problem

Community contributors need a clear path from a bug or feature idea to a focused, reviewable pull request.

Acceptance criteria

• Add CONTRIBUTING.md explaining issue scope, feature branches, linked PRs and validation.
• Add bug-report and feature-request forms with actionable fields and sanitized examples.
• Add a pull-request template covering linked issues, changes, testing and screenshots where relevant.
• Run the existing dependency-free syntax and Node regression checks on GitHub pull requests.
• Use read-only workflow permissions and avoid installing unnecessary dependencies.
• Document the manual browser integration gate for network/storage changes.
• Link this guide from README and make issue-to-PR tracking the default repository workflow.
• Link the existing v1.1 upgrade feature issues to PR v1.1.0: expand Interceptor into a complete local HTTP workbench #1; leave them open pending merge.

Implementation status

Implemented and verified in PR #1 on feat/v1.1-workbench. PR #1 was merged into main on 2026-10-03, merge commit eeb65009fa6e343cf6dd1f67386be0afc5bbb3e5. GitHub automatically closed this issue as completed through the PR's closing reference. The source changes are now on main; the Chrome Web Store release remains pending.

Verification

All four YAML files parse. Issue-form IDs/types/required fields and workflow triggers/read-only permissions/Node 22/check commands were validated. npm run check, all 29 tests, and git diff --check pass. A separate review checked contributor setup and links. GitHub Actions ran the new workflow successfully on Node 22: https://github.com/user-github-me/interceptor/actions/runs/37097320891. The checks are attached to PR #1.

Relevant source

CONTRIBUTING.md, .github/, README.md, AGENTS.md

Related v1.1 work is tracked through PR #1. Follow-up improvements or bugs should use their own issue and PR.

Completion record

The implementation commits are 7b76001, 3ee1668, 4f1d89c, 504051e, and test follow-up 619736d. Relevant verification is described above and in PR #1. All 29 Node regressions and JavaScript syntax checks pass; GitHub CI passes on Node 22. The workbench/browser features were checked with isolated local HTTP/WebSocket fixtures; shortcut labels were also checked for Mac/Windows/Linux platforms. The maintainer merged PR #1, and GitHub closed this issue automatically; new bugs or follow-up scope should use a separate issue, or reopen this one if its original criteria fail.