[Copilot]

Summary

This PR adds the repository’s missing community health baseline: pull request and issue templates, a security policy, and contributor/accessibility guidance. It standardizes how users report bugs/features, how contributors submit changes, and how security issues are disclosed privately.

Changes

• GitHub intake templates

  • Added .github/pull_request_template.md with structured sections for scope, validation, and reviewer checklist.
  • Added issue forms:
    • .github/ISSUE_TEMPLATE/bug_report.yml
    • .github/ISSUE_TEMPLATE/feature_request.yml
    • .github/ISSUE_TEMPLATE/config.yml (disables blank issues, routes security reports to private advisory flow).

• Security policy

  • Added SECURITY.md with supported-version policy and private vulnerability reporting path.

• Contributor guidance

  • Added CONTRIBUTING.md with local dev checks, PR expectations, and contribution standards.
  • Added ACCESSIBILITY.md with documentation/UI accessibility guidelines and reporting expectations.

• Repository discoverability

  • Updated README.md with a dedicated Community & Security section linking the new docs.

# .github/ISSUE_TEMPLATE/config.yml
blank_issues_enabled: false
contact_links:
  - name: Security vulnerability report
    url: https://github.com/Penivera/Bridge/security/advisories/new

Validation

Describe how you validated these changes.

• cargo test
• cargo clippy --all-targets --all-features
• Other (describe below)

Verified rendered markdown/template structure and repository links; confirmed issue template routing and security contact path.

Checklist

• I have tested my changes locally
• I have updated documentation where relevant
• I have considered security and backward compatibility impact

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
bridge-website	Ready	Preview	Oct 11, 2026 11:04am UTC