Community Health

cl-weave keeps its GitHub intake surfaces intentionally small and aligned with the project policy documents. Use the templates under .github/ as the default entrypoints for bugs, feature proposals, and pull requests.

Intake Surfaces

• Bug reports use .github/ISSUE_TEMPLATE/bug_report.md and must include Summary, Reproduction, Expected Behavior, Actual Behavior, Validation, and Additional Context.
• Feature requests use .github/ISSUE_TEMPLATE/feature_request.md and must include Problem, Proposed Change, Validation Plan, Scope Check, and Public Surface Notes.
• Pull requests use .github/pull_request_template.md and must include Summary, Validation, Public Surface Impact, and Follow-up Risk.
• Issue chooser routing lives in .github/ISSUE_TEMPLATE/config.yml and should keep support, security, and reproduction guidance pointed at canonical policy documents.
• Review ownership lives in .github/CODEOWNERS and is the default routing source for repository-wide review responsibility.

Canonical References

• Bug intake is anchored to docs/src/issue-reporting.md.
• Feature intake is anchored to docs/src/project-scope.md and docs/src/support-policy.md.
• Security-sensitive reports are anchored to private GitHub security advisories.
• Pull request intake is anchored to docs/src/pull-request-template.md.
• Review ownership and process authority are anchored to docs/src/governance.md.

Keep these files synchronized with cl-weave metadata so agents can discover the same intake contract without scraping GitHub UI state.