docs: direct community support to the Discussions hub

[Jammy2211]

Overview

Update README Community & Support and existing docs support pages with the exact policy paragraph. Add .github/ISSUE_TEMPLATE/config.yml with question, feature idea and implementation proposal links, blank issues enabled; add bug_report.md requesting reproducer, traceback, versions and expected/actual behavior. Preserve collaborator Slack details; remove invitations to file support questions as issues.

Plan

• Implement the approved PyAutoArray portion of the community-surface handoff.
• Validate the changed behavior or public documentation, then obtain independent review.
• Open a separate PR; category creation and thread migration remain human actions.

Detailed implementation plan

Affected Repositories

• PyAutoArray (primary)

Branch Survey

Canonical checkouts are on main. PyAutoMind has an unrelated deletion of draft/maintenance/pyautobrain/workspace_resolver_fanout.md, which will be preserved. No overlapping worktree claims were found.

Suggested branch: feature/community-surface (approved)
Worktree root: /home/jammy/Code/PyAutoLabs/.worktrees/community-surface/
Work classification: docs; no scientific library API changes.

Implementation Steps

Update README Community & Support and existing docs support pages with the exact policy paragraph. Add .github/ISSUE_TEMPLATE/config.yml with question, feature idea and implementation proposal links, blank issues enabled; add bug_report.md requesting reproducer, traceback, versions and expected/actual behavior. Preserve collaborator Slack details; remove invitations to file support questions as issues.

Validation

Focused scan/triage tests for Brain; Markdown, YAML, contact-link and exact policy-paragraph checks for support docs; HTML and visual review for the static website; independent diff review. Heart STALE on 2026-09-19: release validation incomplete: no rehearsal for current source; no red/yellow reasons.

Original Prompt

Approved handoff supplied by the maintainer, with approval recorded as "I approve" on 2026-09-19. The verbatim request is retained in PyAutoMind's community-surface-policy.md; this member's prompt is community-surface-pyautoarray.md.

[Jammy2211]

Implemented and independently reviewed CLEAN: #563

Validation: documentation/template checks, canonical policy wording and git diff --check. No scientific runtime API changes.

PR remains draft pending manual answerable Proposals category setup (slug proposals). Current Proposal category is singular and non-answerable. Scientific Analysis should also be made answerable per the migration instructions.

Full cross-repo handoff: PyAutoLabs/PyAutoBrain#405 (comment)

[Jammy2211]

Completed: PyAutoArray community surface

Merged: 2026-09-19
Issue: #562
PR: #563

Shipped

Updated Community & Support documentation and issue templates to route community questions, proposals, and suspected errors to the shared Discussions hub; confirmed reproducible bugs retain repository issues.

Uses the human-approved five categories: Announcements, Help & Questions, Ideas & Proposals, Bugs & Errors, and Show and tell.

Validation and close-out

All workflows and jobs for the exact PR head were audited before merging; required jobs passed, with only conditional skips inside successful workflows. Independent review was CLEAN. Git ancestry confirms the feature head is contained in origin/main with zero unmerged commits. Human authorized merging all PRs on 2026-09-19.

• pending-release: PyAutoArray@docs: direct community support to the Discussions hub #563

Only this repository member is complete. The shared community-surface worktree remains because Mind, Lens workspace, website, and organization-profile PRs are still open. The policy and migration umbrella tasks remain active.