Replies: 3 comments
|
Follow-up on the adoption track: two more upstream-ready specs are now published at https://github.com/zoahdev/dsh-docs/tree/main/docs/specs ? (1) Community Plugin Registry Contract v2 (shared registry.json schema so any marketplace/CLI/agent tool can consume the same catalog; reference implementation ships with a validator), and (2) first-class |
|
Support this direction. Maintainer of https://github.com/boyin111-1/dsh-doctor here (17 offline checks, zero deps, single file, runs before dsh boots - listed alongside dsh-plugin-doctor in the proposal). Three alignment points worth echoing from our side:
Also happy to align check names/schema with dsh-plugin-doctor and moonquake2004/dsh-doctor so the three tools converge instead of forking. |
|
The adoption track now has a formal RFC for maintainer feedback: #1846 ? Community plugin registry contract v2 + first-class |
Uh oh!
There was an error while loading. Please reload this page.
Proposal: adopt dsh-plugin-doctor as official
dsh plugin checkanddsh doctor对应 #1629(
dsh plugin check)与 #1719(dsh doctor)两个社区请求:实现已存在并经过验证,本提案给出可直接采纳的规格。为什么现在采纳
建议命令
规格(与社区实现对齐)
{ "ok": bool, "checks": [{ "name": string, "status": "PASS|WARN|FAIL", "detail": string }] }实现证据
preflight全链路 +--profile(宿主遮蔽,被 moonquake2004 独立验证)+--env --port采纳路径建议
dsh plugin check(结构预检,无争议、无执行风险);dsh doctor作为第二期(环境诊断);如果官方愿意,我可以直接把 checks 抽成纯函数库并提交(PR 通道开放后)。
All reactions