Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 10 additions & 9 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,10 @@ English · [简体中文](AGENTS_ZH.md)

## Baseline (2026-10-02)

- Published **0.3.0**, latest=next=0.3.0 (2026-10-02 audit). PR #6 release point 85fa7d1c4a7e6f7c274d83df242d10c65e319d24 matches npm gitHead, annotated v0.3.0 and public GitHub Release/tgz. Both channel installs passed all thirteen file comparisons, 28 official-service checks each and real Web acceptance. See docs/release-report-0.3.0.md.
- Published **0.4.0**, latest=next=0.4.0 (2026-10-02 audit). PR #8 release point `3d7ec4aafffbe5be0dfc92e26e49bae287636d28` matches npm gitHead, annotated v0.4.0 and public GitHub Release/tgz. Both channel installs passed all fifteen file comparisons, 28 official-service checks each and the complete real Web workflow. Issue #1 was replied to and closed as completed. See `docs/release-report-0.4.0.md`.
- Previous **0.3.0** release point: PR #6, `85fa7d1c4a7e6f7c274d83df242d10c65e319d24`. Its tag, npm package and read-only release are immutable. At that release audit both channel installs passed thirteen file comparisons, 28 service checks each and real Web acceptance. See `docs/release-report-0.3.0.md`.
- Working repository: `C:/Users/Mashed Potato/Desktop/npm/dsh-git-plugin`. Check the actual checkout; do not edit another worktree inadvertently.
- Previous published package: **0.2.1**. PR #4 preserved history; release point `084a767aa3055d5cb0e06ddf4fb42dda4156458c` matches npm gitHead, annotated v0.2.1, and public GitHub Release. At the last release audit, latest=next=0.2.1. Channel installs and 28 official-service checks per installed entry passed. See `docs/release-report-0.2.1.md`.
- Historical **0.2.1** package: PR #4 preserved history; release point `084a767aa3055d5cb0e06ddf4fb42dda4156458c` matches npm gitHead, annotated v0.2.1, and public GitHub Release. At that release audit, latest=next=0.2.1. Channel installs and 28 official-service checks per installed entry passed. See `docs/release-report-0.2.1.md`.
- Historical 0.2.0 release point: `c83f3322950b0892022d6b3efd1e4f6edbed5be8`, PR #2. Its package contained five files; do not replace it or move its tag. See `docs/release-report-0.2.0.md`.
- Adaptation commit `8181856` introduced strict TypeScript, DSH 0.2.0-rc.2 compatibility and argv/deadline/hook-directory fixes. Timer correction `922408d` removed unref from deadline/grace timers: Linux Node 20/22 could otherwise drain the event loop before timeout. Keep timers referenced and clear them when done.
- Historical verification: 26 original tests; Windows Node 24.19.0 / Git 2.53.0.windows.2; isolated WSL2 Ubuntu 24.04 Node 20.20.2 / 22.23.3 and Git 2.43.0; clean artifact gate and release-point CI passed. See `docs/validation-report-0.2.0.md`.
Expand All @@ -15,8 +16,8 @@ English · [简体中文](AGENTS_ZH.md)

## Current development

- PR #6 merged the first read-only right-sidebar panel for Issue #1 as **0.3.0**, release point 85fa7d1c4a7e6f7c274d83df242d10c65e319d24. GitHub v0.3.0 is public and its installed entry passed 28 service checks plus real Web acceptance. npm registry availability, installed-package acceptance and latest=next=0.3.0 are confirmed. See docs/release-report-0.3.0.md. Published versions remain immutable. The current explicit goal authorizes completing GUI operations in a new release, then closing Issue #1 after real acceptance.
- Source: `src/index.ts`, `src/web-host.ts`, browser-safe `src/panel-types.ts`, `src/client/`. Build Host declarations/JS and generated `lib/client.js`; keep ESM and existing commands/tools.
- PR #8 released the complete Issue #1 GUI workflow as **0.4.0**, following the read-only 0.3.0 release. Both public installation specs passed installed-entry and browser acceptance; latest=next=0.4.0 and Issue closure are confirmed. Published versions and release tags remain immutable; evidence-only follow-up commits do not move the release point.
- Source: `src/index.ts`, `src/web-host.ts`, `src/web-actions.ts`, browser-safe `src/panel-types.ts`, `src/client/`. Build Host declarations/JS and generated `lib/client.js`; keep ESM and existing commands/tools.
- English primary documents and `_ZH.md` counterparts: README, CONTRIBUTING, AGENTS; also paired Web usage documents. Synchronize facts, commands and validation boundaries. README stays a short product page; engineering details belong in CONTRIBUTING/docs and maintenance constraints here. Do not add a skill just for a documentation edit.
- Web evidence: `docs/web-panel-validation.md`. Old release CI does not certify a new development SHA.

Expand Down Expand Up @@ -52,22 +53,22 @@ English · [简体中文](AGENTS_ZH.md)

- The 0.3.0 dual channels, bundle registration and read-only panel are released. Market PR #6296 closed unmerged and the 2026-10-02 public catalog has zero exact repository matches; investigate separately before claiming search/install availability.
- P2 / Issue #1 is released: read-only status, diff and history; reuse the sidebar carrier, not turn-based workspace-change summaries. That summary excludes pre-existing edits and is not an index/worktree Git source.
- P3 / current authorized work: stage/unstage, staged-only commit, branches, stash and backup restore are implemented; finish installed acceptance and publish 0.4.0 before closing the issue. Native approval.request requires an open model turn; explicit operator GUI confirmation is separate, never a fabricated turn or a model-tool grant. See docs/superpowers/specs/2026-10-02-git-actions-design.md.
- Stage prompts: `docs/dsh-tasks/README.md`; 03–05 are complete, 06 has mount-prefix/slow Web cancellation remaining, 07 design is implemented by the current Git actions contract. Adapt them to actual completed evidence rather than repeating historical instructions. Plan/history documents remain clearly dated.
- P3 / Issue #1 is complete in 0.4.0: stage/unstage, staged-only commit, local branches, stash and backup restore passed both public installed workflows. Native approval.request requires an open model turn; explicit operator GUI confirmation is separate, never a fabricated turn or a model-tool grant. See docs/superpowers/specs/2026-10-02-git-actions-design.md. Future remote operations require a new scoped design.
- Stage prompts: `docs/dsh-tasks/README.md`; 01–05 and 07 are complete. Only 06 mount-prefix/slow Web cancellation evidence remains optional follow-up. Do not repeat historical implementation, release or Issue-closure instructions. Plan/history documents remain clearly dated.
- A successful publish exit/HTTP 202 is acceptance, not installability. Allow official scanning and registry propagation; check actual availability/gitHead/tarball and installed behavior before latest promotion. A successful dist-tag write also requires a confirming tag read; do not repeat publish to address delays.
- Finalize release date before publish. Version/lock/CHANGELOG/source/types/lib and tag/Release/npm gitHead/artifacts identify one release point. Publish each version once to next, verify, then promote with dist-tag. Changed published content needs a new version.
- AGENTS/docs/team state are engineering resources, not npm runtime files. Pack only closed runtime outputs, bilingual READMEs, license, patch and referenced assets; verify actual file list. Published 0.2.0/0.2.1 contents are immutable.

## Community collaboration

- CONTRIBUTING and bilingual issue/PR templates describe triage, scope, ownership, evidence, review and release. Labels and branch protection are separate settings; do not claim templates enabled them.
- Use `Refs #1` for the read-only first phase; do not close the whole issue merely because a draft/partial UI exists.
- Issue #1 was closed after complete public-install acceptance of 0.4.0. Link new defects or feature requests to it for context; do not repeat the release response or reopen it merely to track unrelated follow-up.
- Root screenshots.json references the capability illustration and actual released read-only panel screenshots in docs/images. The banner is an illustration; panel images use isolated fixture repositories. Catalog readiness and catalog inclusion are different states.
- Old manual inserts must migrate to id/config overrides when enabling the bundle. DSH 0.2.0-rc.2 does not automatically add a bundle layer when upgrading an old ordinary dependency.
- Preserve the isolated WSL runtimes `~/dsh-node-runtimes/node-v20.20.2-linux-x64` and `node-v22.23.3-linux-x64` unless removal is specifically requested. System Node 18 was not used for the prior matrix.

## 0.4.0 candidate
## 0.4.0 verification and maintenance

- Source commits: 8b9efc1 actions, 293ff98 content previews, 9871360 native Host/Origin seam, da406ac retained controls on refresh. Windows build/check and 55 tests passed before the last UI-only fix; its client test and type check passed. a44650c fixes reviewed rename/stash scope and passed full Windows build/check/57 tests. Run final candidate checks/CI and installed Web before release.
- Release-point Windows/Linux × Node20/22 CI passed all four jobs, as did clean builds/artifact/type/syntax gates and all57 tests. Both public specs passed the full actual browser workflow and28 real-service checks each. Preserve regression coverage for reviewed rename paths, stash index-only previews and native Host/Origin forwarding.
- New Web minimum Git 2.32 is required for stash show --include-untracked; only actual tested versions may be claimed verified. Connection HTTP bridge uses dsh.internal URL; validate mandatory Origin against its trusted Host authority.
- Use a unique development tarball path per SHA; pnpm can cache a repeated filename. Compare installed lib hashes, restart the isolated profile, and never hand-edit installed outputs.
21 changes: 11 additions & 10 deletions AGENTS_ZH.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,9 @@

## 当前基线(2026-10-02)

- 当前 **0.3.0 已完成双渠道发布**,latest=next=0.3.0(2026-10-02 核对)。PR #6 发布点 85fa7d1c4a7e6f7c274d83df242d10c65e319d24 与 npm gitHead、annotated v0.3.0、公开 Release/tgz 一致;两个实际安装 spec 均通过十三文件对比、各 28 项官方服务和真实 Web 验收,详见 docs/release-report-0.3.0.md。
- 上一已发布包版本 0.2.1;PR #4 已保留历史合并,发布点为 084a767aa3055d5cb0e06ddf4fb42dda4156458c。npm latest=next=0.2.1、annotated tag 与公开 GitHub Release 均已核对该发布点,双渠道独立实装和各 28 项服务栈通过。市场 PR #6296 已于 2026-10-01 关闭且未合并、无说明评论,不宣称已收录,详见 docs/release-report-0.2.1.md。
- 当前 **0.4.0 已完成双渠道发布**,latest=next=0.4.0(2026-10-02 核对)。PR #8 发布点 `3d7ec4aafffbe5be0dfc92e26e49bae287636d28` 与 npm gitHead、annotated v0.4.0、公开 Release/tgz 一致;两渠道正式安装均通过十五文件对比、各 28 项官方服务及完整 Web 操作。Issue #1 已回复并按完成关闭,详见 `docs/release-report-0.4.0.md`。
- 上一版本 **0.3.0**:PR #6 发布点 `85fa7d1c4a7e6f7c274d83df242d10c65e319d24`;其 tag、npm 包及只读发布不可覆盖。当时双渠道十三文件、各 28 项服务与真实 Web 验收通过,见 `docs/release-report-0.3.0.md`。
- 历史 0.2.1;PR #4 已保留历史合并,发布点为 084a767aa3055d5cb0e06ddf4fb42dda4156458c。当时 npm latest=next=0.2.1、annotated tag 与公开 GitHub Release 均已核对该发布点,双渠道独立实装和各 28 项服务栈通过。市场 PR #6296 已于 2026-10-01 关闭且未合并、无说明评论,不宣称已收录,详见 docs/release-report-0.2.1.md。

- 主工作目录:`C:/Users/Mashed Potato/Desktop/npm/dsh-git-plugin`;先确认所在 checkout,避免把改动写到另一 worktree。
- 适配已提交:`8181856`,包含严格 TypeScript 迁移、DSH 0.2.0-rc.2 适配、Git 参数安全/超时/钩子目录修复、测试与文档。
Expand All @@ -17,10 +18,10 @@

## 当前开发任务

- PR #6 已保留历史合并 Issue #1 首版只读面板为 0.3.0,发布点 85fa7d1c4a7e6f7c274d83df242d10c65e319d24;GitHub v0.3.0 已公开,固定 tag 实装的 28 项服务及真实 Web 通过。npm 注册表可见、正式实装及 latest=next=0.3.0 已确认;实际状态见 docs/release-report-0.3.0.md;旧版本不可覆盖;当前明确目标已授权补完整 GUI 操作,正式实装验收后关闭 Issue #1。
- PR #8 在 0.3.0 只读首期基础上,以 **0.4.0** 发布 Issue #1 的完整 GUI 操作。两种公开安装 spec 的真实入口及浏览器验收、latest=next=0.4.0 与 Issue 关闭均已确认。已发布包和 tag 不可覆盖;后续证据提交不移动发布点。
- README / CONTRIBUTING / AGENTS 采用英文主文档和 `_ZH.md` 中文对应页;面板使用文档同样配对,修改时同步事实、命令和验收边界。
- 新 Web 证据见 `docs/web-panel-validation.md`;不能将旧发布点的 CI 当作本分支 CI。
- 当前源码为 src/index.ts、src/web-host.ts、src/panel-types.ts 和 src/client/;客户端通过小型构建生成官方 loader 包装,复用宿主 React,不手改 lib/client.js、不捆绑第二份 React。
- 当前源码为 src/index.ts、src/web-host.ts、src/web-actions.ts、src/panel-types.ts 和 src/client/;客户端通过小型构建生成官方 loader 包装,复用宿主 React,不手改 lib/client.js、不捆绑第二份 React。
- Web 从运行中/持久化 Session 获取 cwd;拒绝请求提供任意 cwd/root/argv,限制相对路径、literal pathspec、external diff/textconv。DSH 0.2.0-rc.2 是单一已准入 operator,并无按租户分隔的 Session ACL,不能宣称租户隔离。
- 禁用时清理 UI、样式、tab、slot、路由和进行中的请求;切换会话后旧响应不能覆盖新视图。真实 Web 验收脚本 scripts/verify-web-panel.mjs 按需运行,不进入 npm test/CI。

Expand Down Expand Up @@ -48,8 +49,8 @@
## 后续顺序与发布

- P1:`0.2.1` 双渠道发布、bundle 自动启用、README 展示与市场收录申请已完成;市场 PR #6296 已关闭未合并、无说明评论;目录没有本仓库精确匹配,不宣称已收录。GUI 另开阶段。
- P2:[Issue #1](https://github.com/MashedPotato817/dsh-git-plugin/issues/1) 的 Web 只读 Git 面板:状态、diff、历史首期已实现;继续补验及用户验收。
- P3:再考虑 stage/commit/branch/stash 等写操作,核对 DSH 权限与审批及恢复方式。
- P2:状态、diff、历史只读面板已在 0.3.0 发布。
- P3 / [Issue #1](https://github.com/MashedPotato817/dsh-git-plugin/issues/1):暂存/取消暂存、仅暂存提交、本地分支、stash 与备份还原已在 0.4.0 双渠道验收发布,Issue 已完成关闭。GUI 人工确认与需要 open turn 的模型审批分开;未来远端操作先另定范围与设计。
- 版本文件、CHANGELOG、源码、编译配置、测试和 `lib/` 一起纳入发布提交;确保 tag、Release、npm gitHead 与包内产物对应同一提交。
- 同一版本只 `npm publish --tag next` 一次;验证通过后用 `npm dist-tag add dsh-git-plugin@<版本> latest` 推广。需要修改已发布内容时提升版本。
- `AGENTS.md`、`docs/`、`.agent-teams/` 不进入 npm files;已发布 0.2.1 实际为 7 文件;当前开发包增加 Web 产物及 README_ZH,按实际 pack 文件表核验。原 0.2.0 发布包仍为 5 文件,不可覆盖;缓存与独立测试目录保持忽略。
Expand All @@ -66,7 +67,7 @@

## 后续任务入口(2026-10-01 核查)

- 任务分包见 [docs/dsh-tasks/README.md](docs/dsh-tasks/README.md):03–05 已完成并发布;06 仅余挂载前缀/真实慢 Web 请求取消,07 的审批与恢复设计已由当前 Git 操作契约实现;逐包推进。
- 任务分包见 [docs/dsh-tasks/README.md](docs/dsh-tasks/README.md):01–05 与 07 已完成;06 仅余挂载前缀/真实慢 Web 请求取消的可选补验。不要重复历史实现、发布或 Issue 关闭任务。
- 原候选 feba7b8,定时器修复 922408d,发布点 c83f332;PR/main 当前 SHA CI 均通过,协作文档与模板已进入默认分支。包 02 的 npm、GitHub、latest 推广与双渠道安装均完成;随后 03–05 的只读 Web 已实现为 0.3.0,继续 06/07 的剩余项目。
- Linux Node 20/22 已用**隔离运行时**(WSL2 Ubuntu 24.04,`~/dsh-node-runtimes/node-v20.20.2-linux-x64`、`node-v22.23.3-linux-x64`)完成修复后 build/check/test 复验;修复候选 922408d 的 npm ci/build/产物门/check/语法/test/pack 全部通过。系统 Node 18.19.1 未用于验证。证据见 `docs/validation-report-0.2.0.md`。未推送 SHA 的干净检出从本地主仓库克隆。

Expand All @@ -86,10 +87,10 @@

## 当前完整目标

按 docs/superpowers/specs/2026-10-02-git-actions-design.md 实施暂存/取消暂存、仅暂存提交、分支、stash 和备份还原。人工 GUI 写确认独立于需要 open turn 的模型审批;同源 JSON、一次性确认、状态复核,不伪造模型回合。完整实装/CI/双渠道发布后回复并关闭 Issue #1,不把只读首期当作完整交付。
docs/superpowers/specs/2026-10-02-git-actions-design.md 的完整操作已通过正式实装/CI/双渠道发布,Issue #1 已关闭。维护同源 JSON、一次性确认与状态复核;人工 GUI 写确认独立于需要 open turn 的模型审批,不伪造模型回合。

## 0.4.0 候选
## 0.4.0 验证与维护

- 源码提交:8b9efc1 操作,293ff98 内容预览,9871360 原生 Host/Origin,da406ac 刷新保留操作区。最后界面小修前 Windows build/check 和 55 项测试通过;小修后的客户端与类型检查通过。a44650c 修复审查指出的 rename/stash 范围,完整 Windows build/check/57 项通过;发布前须复跑最终候选/CI/正式安装 Web。
- 发布点 Windows/Linux × Node20/22 四组合 CI 通过,干净构建/产物/类型/语法及完整 57 项测试通过;两种正式安装均通过完整真实 Web 操作与各 28 项宿主检查。维护审查修复的 rename 路径、stash 仅暂存预览及原生 Host/Origin 转发回归覆盖。
- 新 Web 能力要求 Git 2.32(stash show --include-untracked),仅实际测试版本声明已验证。原生 bridge 的 URL 为 dsh.internal,强制 Origin 绑定已受信 Host authority。
- 每个开发 SHA 使用不同 tarball 文件路径,避免 pnpm 同名缓存;比较实际安装 lib 哈希并重启独立 profile,不手改安装产物。
2 changes: 2 additions & 0 deletions docs/dsh-tasks/07-gui-write-design.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Package 07: GUI write approval design / GUI 写审批设计

> Completed2026-10-02: design and implementation released as0.4.0; both public installs passed complete Web acceptance and Issue #1 is closed. Native operator GUI confirmation is separate from turn-bound model approval. The instructions below are historical, not a request to repeat implementation or publication. / 已完成设计、实现及 0.4.0 双渠道验收发布,Issue #1 已关闭;GUI 人工确认独立于模型回合审批。下文保留历史提示词,不重复执行。See [release evidence](../release-report-0.4.0.md) and [accepted design](../superpowers/specs/2026-10-02-git-actions-design.md).

Read AGENTS, Issue #1, the implemented read-only Host/client and the exact upstream approval contracts. 阅读维护指引、Issue #1、已实现只读面板与上游审批契约。

Owner / 执行:DSH. Scope / 范围:reviewable design and optional isolated proof, not production write buttons. 可审设计与隔离验证,不直接加入生产写按钮。
Expand Down
Loading
Loading