一起把她养大的人The people who raised her
dsh-auto-memory 从一个人的实验，长成了有人在用的工具。这页记录所有提过 issue、交过 PR、以及赞助过开发资源的人——名字和贡献都在这里。
dsh-auto-memory grew from a solo experiment into something people actually use. This page credits everyone who filed an issue, sent a pull request, or sponsored the development resources.
突出贡献者Top contributors
按贡献条目数排序。每条都指向原始的 issue / PR。
Sorted by number of contributions. Every entry links back to the original issue or PR.
贡献量最大。工作区概览日志日期锚定修复（未锚定子串正则误纳恢复候选 ⇒ 排序被污染、概览可能为空）、自动续跑宿主加固、恢复候选生命周期与幂等重放。
The most prolific contributor. Anchored workspace-overview log-date matching (an unanchored substring regex admitted recovery candidates, polluting ranking and sometimes emptying the overview), auto-continuation host hardening, and recovery-candidate lifecycle / idempotent replay.
持续的问题反馈者，覆盖面板行为、召回质量与配置边界等场景。
A persistent reporter covering panel behaviour, recall quality, and configuration edge cases.
关于记忆召回与注入行为的连续反馈。
Successive reports on memory recall and injection behaviour.
DSH Desktop 增强模式（透明 / Mica 材质）下的面板可读性修复，以及入口按钮防遮挡与外点 / Esc 关闭。
Panel readability fix for DSH Desktop enhanced mode (transparent / Mica materials), plus entry-button anti-occlusion and outside-click / Esc dismissal.
无人值守 / 批处理场景的加固反馈——直接推动了欢迎向导与逐功能开关化。
Unattended / batch-workflow hardening feedback that directly drove the welcome tour and per-feature switches.
早期问题反馈，帮助校准了最初的行为预期。
Early feedback that helped calibrate the initial behaviour expectations.
其他贡献者Also contributed
每一位的第一个反馈都算数——很多修复就是从这些 issue 开始的。
Every first report counts — many of these fixes started right here.
@Architectxz#1
@ALuoXue#2
@lhbsaa#3
@alexchenzl#6
@zjj871114037#7
@eclgo#13
@moonltppt#14
@swtseaman#21
@xiaochaZ#38
@jeffsui#39
@cuohua#40
资源赞助Resource sponsors
本项目不接广告、不做付费墙。以下赞助方提供的是开发本身要烧掉的东西——API 额度。
No ads, no paywall. These sponsors provide what development actually burns: API quota.
DSH API · api.dshapi.icu
API 中转站，为本项目的开发、回归测试，以及 M 系列语义引擎的选型与激活策略研究提供模型端点。没有这些额度，那些基准实验根本跑不起来。
An API relay station providing the model endpoints used for development, regression testing, and the M-series semantic-engine selection / activation research. Without that quota, those benchmark runs simply would not have happened.
如何参与How to contribute
不需要先成为"核心贡献者"。一个能复现的 issue 就是有效贡献。
You do not need to be a "core contributor" first. A reproducible issue is a real contribution.
带上 DSH 版本、插件版本、复现步骤和实际 vs 预期。这一步比什么都重要。
Include DSH version, plugin version, steps, and actual vs expected. This matters more than anything else.
小步、单一目的、带上验证结果。回归套件是绿的才算完成。
Small, single-purpose, with verification results. It counts as done only when the regression suite is green.
问题反馈、使用技巧交流，响应通常比 issue 更快。
Feedback and usage tips — usually faster than issues.
提供 API 额度或其他开发资源。开个 issue 说明来意即可。
Provide API quota or other development resources. Just open an issue.