fix: surface new comments on closed and answered threads

[Jammy2211]

Summary

New comments on closed or answered community threads were being missed: settled Discussions had their response flag cleared, and closed issues were excluded. Ears now identifies external activity after settlement and brings it back for Community review without requiring contributors to reopen anything.

The dashboard labels it “Follow-up needs review,” preserves the closed/answered status, and links to the pending comment. This is an activity signal; Community judges whether the text is an actionable request, an acknowledgement or unclear. Reopening, unlocking and clearing an accepted answer remain separate authorized actions.

Scripts Changed

• ears/collect.py: collect recently updated closed issues/Discussions within the existing page budget; derive nullable follow-up evidence from closure/answer timestamps and ordered comments, including nested replies. Use a fixed read-only GraphQL query for Discussion closure time. Skip quiet closed issue history and closed PRs. Surface incomplete coverage explicitly.
• ears/board.py, ears/presentation.py: follow-up attention rows, comment links and permission-aware review prompts.
• REFERENCE.md, collector/presentation tests and browser fixture: document and exercise the optional v1 contract.

Validation

• 97 Ears tests passed; generated state.json validates.
• Chromium smoke passed at 390px and 1280px in light/dark themes, including copy success/failure and the new follow-up source link; no page errors.
• Live read-only verification catches Discussion Remove dashboard timestamp and usage prose #13 as closed, answered, awaiting review, with complete comment coverage.
• Brain community/adapter tests: 66 passed.

Integration and limits

Merge the companion Brain reader PyAutoLabs/PyAutoBrain#489 before this producer. Collection is bounded by the page budget; truncated closed history remains an explicit coverage gap. This does not automatically reopen or semantically classify threads. Discussion/issue comments are read transiently and are not published in snapshots.

Closes #19. Tier: judge; human merge.

Heart

The user explicitly acknowledged these exact Heart YELLOW reasons on 2026-10-07 and authorized pushing branches and opening PRs (no merge/release):

• manifest drift: shared-standards blocks (generated) — 2 mismatch(es) vs PyAutoMind/repos.yaml
• release validation stale: source moved since rehearsal (PyAutoNerves, PyAutoFit, PyAutoArray, PyAutoGalaxy, PyAutoLens)