github-paper-review-workflowlisted

# GitHub Paper Review Workflow Use GitHub as the source of truth for paper revisions. Maintain two authoring surfaces: - a Chinese semantic Markdown file for claims, logic, and author instructions; - a formal English LaTeX file for the submission text. Keep both synchronized, but treat the Chinese file as semantic authority unless a newer human review comment overrides it. ## Non-negotiable rules 1. Apply this priority order: newest unresolved human review instruction, Chinese semantic source, English LaTeX, agent judgment. 2. Never merge, resolve a human thread, or force-push without explicit author approval. 3. Never edit the Overleaf copy concurrently with an active GitHub PR. GitHub is authoritative until the PR closes. 4. Never silently weaken a mathematical claim or ignore contradictory evidence. Explain the conflict and block when needed. 5. Mark every AI-created PR body, issue comment, review reply, and status message with the reserved marker `<!-- academic-writing-ai:`. Never post an unmarked AI comment. 6. Treat an unmarked comment from an authorized author login as human instruction, even when `gh` uses the same login. 7. Default to private repositories. Fail closed on a public repository unless the author explicitly permits it. Read [references/review-protocol.md](references/review-protocol.md) before creating or processing a PR. Read [references/github-commands.md](references/github-commands.md) when issuing GitHub API commands. ## Workflow ### 1. Establi