Requested by Can · project thread

#What this changes

The GitHub community setup workflow (scripts/github-community.mjs) can now answer issues and discussions on the GitHub mirror as the mirror token's account (Codician), without a pull request per reply.

Replies wait as replies/<id>.md on the community-replies branch of this repository, which is never merged and never mirrored. Each file has a small header (target: issue 4 or discussion 2, optional labels and close) and the reply in Markdown. The script fetches that branch, posts each reply it hasn't posted before, and ends the comment with a <!-- diffinery-reply: <id> --> marker, so rerunning the workflow posts nothing twice. Closing happens only alongside the first posting, so an issue someone reopened stays open.

No workflow file changes: the existing workflow already runs this script with MIRROR_TOKEN.

#How it was tested

• node --check on the script.
• Ran replyFiles() and parseReply() against a local repository with a community-replies branch: a valid reply parsed with its labels and marker, and a bad target (pull 4) was reported with a clear message.
• The GitHub calls reuse the script's existing rest() and graphql() helpers; the first real run is the replies to issues #3, #4 and #5.

#Checklist

• pnpm -r typecheck and pnpm -r test pass (no TypeScript or test changes; script only)
• User- or admin-visible changes update the docs in apps/diffinery/docs (maintainer tooling only)
• New D1 migrations use the next free number in apps/diffinery/migrations (none)

🤖 Generated with Claude Code

https://claude.ai/code/session_015ALxdbMU5hpZXjGpL2jhC4