Applied the two issue forms, then adjusted them so GitHub accepts the feature form. The 期望效果 textarea now has id expected-effect. The checkbox that told people not to tick it is gone from both forms. The feature checklist searches the lower-case bug label, the same spelling the bug form applies. No config.yml (blank issues stay available). The YAML does not create the bug or enhancement labels.
Checked with Ruby's YAML parser: both files parse, every non-markdown field has a unique id, and the labels are bug and enhancement. No project test covers these files.
- Node minimum is 22 in package.json engines, the start scripts, the service installer, setup and doctor,
matching the README, the release notes and the CI matrix (22 / 24).
- .gitattributes: CSS, HTML, JSON, Markdown and YAML check out with LF, so `node --test` on Windows matches the
CSS rules the UI tests read; the Windows test step is no longer continue-on-error.
- CI: actions/checkout@v7 and actions/setup-node@v7 (Node 24 runtime).
星闌