fix: avoid duplicate gh view bodies

2026-07-10 06:27:46 +02:00
parent 0addf8d3b9
commit 0fc0fb7336
7 changed files with 25 additions and 4 deletions
@@ -16,6 +16,7 @@ GitHub issue/PR 正式读写必须走 `bun scripts/cli.ts gh ...` 或 `trans gh:
 - 规划型、多阶段、架构/API/平台运维类 issue 第一阶段必须 `P0 SPEC 先行`；细则见 [references/issues.md](references/issues.md)。
 - `P0 SPEC 先行` 段不得写入硬编码阈值、采样周期、重试次数、并发数等可调参数；必须写明这些参数由指定 YAML/source-of-truth 控制，issue 只列配置路径、字段族和验收读取方式。
 - `gh` 默认输出是 k8s 风格 text/table/summary/Next/Disclosure；脚本消费或全量排障必须显式用 `--json`、`--full` 或 `--raw`。
+- `gh issue view` / `gh pr view` 显式请求 `--json body,...` 时，完整正文只在 `.data.issue.body` / `.data.pullRequest.body` 出现一次；兼容 `.data.json.body` 不再复制大字段，迁移路径由 `.data.compatibility.bodyPath` / `bodyMigrationHint` 披露。
 - 多行正文使用 quoted heredoc：`--body-stdin <<'EOF'`；issue close/reopen 生命周期评论只用 `--comment-stdin <<'EOF'`。不要把 Markdown 塞进 shell 参数。
 - PR merge 只走 guarded `gh pr merge`；`gh pr create` 的 Next 默认是 `--merge --delete-branch`，只有确认 ancestry 可丢弃时才显式 `--squash`。

@@ -5,6 +5,7 @@ Issue writes use `bun scripts/cli.ts gh ...` or the `trans gh:` virtual filesyst
 - Body and comments default to Chinese.
 - Recent issue comment progress should prefer `bun scripts/cli.ts gh issue comments <number> --repo owner/name [--limit N] [--full|--raw]`; structured output is stable at `.data.comments`.
 - `gh issue view <number> --json comments` remains the legacy compatibility path at `.data.json.comments`; when comments are requested it should disclose the preferred `gh issue comments <number>` migration path instead of silently pushing operators toward `/tmp` dump recovery.
+- `gh issue view <number> --json body,...` emits the full body once at `.data.issue.body`; `.data.json.body` is intentionally omitted, and `.data.compatibility.bodyPath` plus `bodyMigrationHint` disclose the stable machine-readable path.
 - New issues include `目标合并分支`.
 - Multi-stage architecture/API/platform issues begin with `P0 SPEC 先行`.
 - Long body text uses `--body-stdin`.
@@ -3,6 +3,7 @@
 PR work uses guarded UniDesk GitHub commands:

 - `pr review-plan`, `pr diff --file`, and bounded file drill-down before review.
+- `pr view <number> --json body,...` emits the full body once at `.data.pullRequest.body`; `.data.json.body` is intentionally omitted, and `.data.compatibility.bodyPath` plus `bodyMigrationHint` disclose the stable machine-readable path.
 - `pr preflight` is optional read-only diagnosis; `pr merge` runs preflight internally.
 - `pr merge --merge` by default deletes the merged same-repo head branch, cleans a matching clean local `.worktree`, and fast-forwards the local main worktree on the PR base branch.
 - `pr merge --merge --sync-node JD01` additionally runs mapped node source-workspace sync when supported, currently HWLAB `v0.3`.