deepseek-foreman 0.4.3 → 0.4.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -52,6 +52,10 @@ Everything is plain Markdown in your repo: tickets, receipts, review reports. **
|
|
|
52
52
|
|
|
53
53
|
Cost ledger per receipt, budget caps for unattended runs. Model roles & field data: [metrics](docs/metrics-2026-10-01.md).
|
|
54
54
|
|
|
55
|
+
## 📈 Built from real usage
|
|
56
|
+
|
|
57
|
+
Every ticket you run feeds an anonymized local ledger (`~/.dsh/foreman-insights/`); every 10 tickets (or weekly) the data turns into the next version's requirements. This project's own roadmap came from exactly that loop.
|
|
58
|
+
|
|
55
59
|
## Acknowledgements
|
|
56
60
|
|
|
57
61
|
Ported from [yanauto/opus-manager](https://github.com/yanauto/opus-manager) (MIT, © 2026 yanauto) — the ticket/receipt contract and the "re-run acceptance, cross-vendor review, verify every finding" playbook were proven there over 8 weeks / 13 repos / 360 tickets. Dual copyright in [LICENSE](LICENSE).
|
package/README.zh-CN.md
CHANGED
|
@@ -50,6 +50,10 @@
|
|
|
50
50
|
|
|
51
51
|
每张回执带成本台账，无人托管有预算闸。模型分工与实测：[可量化数据](docs/metrics-2026-10-01.md)。
|
|
52
52
|
|
|
53
|
+
## 📈 由真实使用驱动迭代
|
|
54
|
+
|
|
55
|
+
你跑的每张工单都会进本地台账（`~/.dsh/foreman-insights/`，仅本机）；每 10 张单或每周，数据自动分析成下一版需求。本项目自己的路线图就是这么来的。
|
|
56
|
+
|
|
53
57
|
## 致谢
|
|
54
58
|
|
|
55
59
|
移植自 [yanauto/opus-manager](https://github.com/yanauto/opus-manager)（MIT，© 2026 yanauto）——工单/回执契约与「重跑验收、异族审查、逐条核实」打法在上游经 8 周 13 仓库 360 单验证。双版权声明见 [LICENSE](LICENSE)。
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "deepseek-foreman",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.5",
|
|
4
4
|
"description": "Foreman for DeepSeek Harness: your best model leads, cheaper models build, a rival vendor reviews. Role-to-route adjudication with peak-window, vision, output-size and cross-vendor-review constraints.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "lib/index.js",
|
|
@@ -141,6 +141,12 @@ _receipts/ 回执、审查报告、进度、报告
|
|
|
141
141
|
|
|
142
142
|
核实结论追加在审查报告末尾。
|
|
143
143
|
|
|
144
|
+
## 七点五、使用数据回收（跨项目，每次收尾必做）
|
|
145
|
+
|
|
146
|
+
每收尾一张单，**追加一行**到 `~/.dsh/foreman-insights/usage/<当天日期>-<项目名>.md`（列：时间|工单|项目|施工模型|effort|施工token(万)|审查token(万)|Lead轮数|结果|问题标记|备注）（格式见 `~/.dsh/foreman-insights/schema.md`）：时间、工单、项目、施工模型、effort、施工/审查 token（dsh 面板值）、Lead 轮数、结果、问题标记（ok/重做/审查抓漏/live事故/文档误导/工具缺陷）。这张台账是产品迭代的原料——真实使用数据，不是自嗨样本。
|
|
147
|
+
|
|
148
|
+
**累计每 10 张单或每周（先到为准）**：读 usage/ 全量，写一份 `~/.dsh/foreman-insights/analysis/<日期>.md`（数据概览→问题按频次→需求候选按价值→与上期对比），需求候选直接立为下一版工单。
|
|
149
|
+
|
|
144
150
|
## 八、收尾
|
|
145
151
|
|
|
146
152
|
工单从 `doing/` 挪到 `done/`。用大白话告诉用户：什么现在能用了、他可能会注意到哪些变化、还剩什么风险。
|