文件最后提交记录最后更新时间
docs(issues): split off display/rendering template, collect terminal host (#412) (#413) Flicker reports keep landing without the one piece of info that discriminates the bug — the terminal host (VSCode/Cursor xterm.js vs standalone Windows Terminal / iTerm2 / etc.). The shell field on the generic bug template was the wrong axis. New template asks for host + version, env vars (TERM_PROGRAM/VSCODE_INJECTION/WT_SESSION), and ships copy-paste diagnostic snippets so users do not have to know how to introspect their own terminal.21 天前
chore: add Support section with PayPal + WeChat Pay donation channels (#1238) International donors can send via PayPal (paypal.me/yuhuahui); domestic users scan the WeChat Pay QR. README copy frames it as "coffee, not contract" — donations don't buy feature priority or change issue triage, which keeps the project's cheap-and-narrow positioning intact. Co-authored-by: reasonix <reasonix@deepseek.com>11 天前
fix(release): split macOS dmg by arch (#2050)2 天前
chore: add Support section with PayPal + WeChat Pay donation channels (#1238) International donors can send via PayPal (paypal.me/yuhuahui); domestic users scan the WeChat Pay QR. README copy frames it as "coffee, not contract" — donations don't buy feature priority or change issue triage, which keeps the project's cheap-and-narrow positioning intact. Co-authored-by: reasonix <reasonix@deepseek.com>11 天前
docs(contrib): drop CHANGELOG-per-PR rule (#94) Three coupled changes: - CONTRIBUTING.md: replace 'update CHANGELOG.md under [Unreleased]' with 'don't touch CHANGELOG.md'. Releasing section now says the maintainer writes the notes from git log at release time. - PULL_REQUEST_TEMPLATE.md: replace the 'CHANGELOG updated' checkbox with the inverse — 'no edits to CHANGELOG.md'. - CHANGELOG.md: drop the lingering [Unreleased] section. The --system-append feature it described will land in the next versioned section, written by the maintainer. Why: PR-time CHANGELOG entries had two failure modes — they piled up in [Unreleased] when releases didn't roll them forward, and they created soft conflicts between concurrent PRs. PR descriptions are the authoritative record while work is in flight; release notes are better written once with full context than in pieces during review.27 天前
fix(ci): use /pattern/i form in issue-labeler config (#637) github/issue-labeler@v3.4 compiles patterns with new RegExp(str), which doesn't accept the PCRE (?i) inline flag — it throws Invalid regular expression: Invalid group on the first pattern and the whole label job dies before tagging anything (run 25649833795). Switch every entry to the /pattern/i literal form the action parses out of slash-delimited strings. Behavior is unchanged (still case-insensitive); the YAML just speaks JS regex now. Validated locally: all 14 patterns compile, 17/17 realistic issue fixtures match the expected labels.18 天前