feat: add SUPPORT.md to community-health and sync

[wcmchenry3-stack]

Context

No SUPPORT.md exists in any org repo. GitHub uses this file to display a support notice when users open issues. Without it, contributors don't know where to get help or how to report security issues vs regular bugs.

Implementation

1. Create community-health/SUPPORT.md

Content should cover:

Security issues
→ Do NOT open a public issue. Use GitHub's private vulnerability reporting (see SECURITY.md).

Bug reports
→ Open a GitHub Issue using the bug_report template. Include reproduction steps, expected vs actual behavior, and environment details.

Feature requests
→ Open a GitHub Issue using the feature_request template.

General questions
→ This is a small org with no dedicated support channel (no Slack, Discord, or email list). Open a GitHub Discussion (if enabled) or a GitHub Issue tagged question.

Response SLA
→ Best-effort by org maintainers. No guaranteed response time.

2. Add to sync-community-health.yml FILE_MAP

- src: community-health/SUPPORT.md
  dst: SUPPORT.md

Acceptance Criteria

• community-health/SUPPORT.md created covering security, bugs, features, and general questions
• Security section clearly directs to private vulnerability reporting (not public issues)
• File passes markdownlint
• FILE_MAP entry added to sync-community-health.yml
• GitHub community standards checklist shows Support as complete

Dependencies

None — can be worked in parallel with all other Phase 2 issues.

Part of Epic

#77

[wcmchenry3-stack]

Implemented in PR #99 and #106 (both merged). Closing.