Skip to content

docs(chat): document post-send message ID chain - #897

Open
Anonymity-0 wants to merge 3 commits into
DingTalk-Real-AI:mainfrom
Anonymity-0:feat/chat-message-help-id-chain
Open

docs(chat): document post-send message ID chain#897
Anonymity-0 wants to merge 3 commits into
DingTalk-Real-AI:mainfrom
Anonymity-0:feat/chat-message-help-id-chain

Conversation

@Anonymity-0

@Anonymity-0 Anonymity-0 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • What changed?
    • Document that chat message send returns openTaskId.
    • Document that chat message query-send-status returns openMessageId and openConversationId.
    • Add complete send -> query-send-status -> edit/recall examples to CLI help.
    • Align mono and multi Skill routing so newly sent messages no longer require content-based ID lookup.
    • Add a rendered-help regression test for the complete ID chain.
  • Why is this change needed?
    • The runtime chain already works, but it was not discoverable from CLI help. Agents were still directed to search message history by content before editing or recalling a newly sent message.

Risk tier

  • Documentation-only: prose/assets only; no executable, generated, workflow,
    packaging, or interface behavior changed
  • Standard: ordinary implementation change with a stable package graph
  • High-risk: workflow/policy, package graph, generated Schema/registry,
    platform, auth/keychain, installer, packaging, release, transport, recovery,
    or another fail-closed infrastructure change

Verification

Record the smallest targeted evidence that proves the changed behavior. Do not
repeat the entire CI suite locally only to fill this checklist: CI expands the
selected tier from documentation checks, through affected-package tests, to
the complete high-risk suite.

  • Exact in-place CHANGELOG.md-only check (otherwise N/A):
    N/A — this is not a CHANGELOG-only change.
  • Targeted test/check commands and results:
    • go test ./internal/helpers -run '^TestCrossPlatformCoverageChatMessageHelpDocumentsPostSendIDChain$' -count=1 — passed
    • go test ./internal/helpers -count=1 — passed
    • make build — passed
    • make generate-schema — passed
    • ./scripts/policy/check-schema-catalog.sh — passed
    • ./scripts/policy/check-skill-context-budget.sh — passed
    • ./scripts/policy/check-skill-commands.sh — passed
    • go test ./scripts/policy/multi-im-skill-chain -count=1 — passed
  • Behavior evidence (DWS head 2bd6b297b0140c60a5274e083bc8101302deffe0):
    • chat message send --help — post-send openTaskId handoff:

      send help

    • chat message query-send-status --helpopenMessageId and openConversationId:

      query-send-status help

    • chat message edit --help — complete post-send edit chain:

      edit help

    • chat message recall --help — complete post-send recall chain:

      recall help

  • Documentation links/content/rendering checked (documentation-only, otherwise
    N/A): N/A — Standard tier.
  • Full local suite run because the change is high-risk (optional for other
    tiers; record command/result or N/A): N/A — Standard tier.
  • ./scripts/policy/check-generated-drift.sh
    (when generator inputs or generated artifacts may change) — passed
  • ./scripts/policy/check-command-surface.sh --strict (if command surface changed):
    N/A — no command paths or flags changed.
  • ./scripts/release/verify-package-managers.sh
    (after make package, if packaging or installer surfaces changed):
    N/A — no packaging or installer changes.

Notes

  • Help and Skill discoverability only; RPC behavior and the existing send/status/edit/recall runtime chain are unchanged.

The repository automatically requests one eligible peer reviewer, including
after a new head push when another review is needed. Once the latest push has
peer approval and all nine required checks are current and green, auto-merge
completes the PR; authors do not need to coordinate a separate routine merge.

@Anonymity-0
Anonymity-0 marked this pull request as ready for review August 6, 2026 10:11
@github-actions
github-actions Bot requested a review from audanye-sudo August 6, 2026 10:11
@github-actions
github-actions Bot enabled auto-merge August 6, 2026 10:11
@wxianfeng
wxianfeng self-requested a review August 7, 2026 03:42
@wxianfeng

Copy link
Copy Markdown
Collaborator

开源 DWS Codex 自动 CR:不通过,需补充 Agent 测试报告截图

docs(chat): document post-send message ID chain

  • 评审 SHA:a3773c4384d4f4c039d9d352b3a92f3077059110
  • CI 状态:通过(23 通过,3 跳过)
  • 冲突状态:无冲突
  • Agent 测试报告:不通过,缺少“Agent 测试报告”截图(chat)
  • 指令 CI 集成测试:不通过,缺少“指令 CI 集成测试”截图(chat)
  • 自动 CR 结论:不通过,需补充 Agent 测试报告截图
  • 代码评审结论:通过

变更总结

本次变更补充了个人消息发送后通过 openTaskId 查询 openMessageId/openConversationId,并继续编辑或撤回的帮助文案、路由指南与技能参考,同时新增跨平台帮助输出回归测试。Go 代码仅调整帮助文本,未改变命令执行、参数映射或安全门逻辑;新增示例未包含 --yes 等确认绕过参数,测试命名也符合平台覆盖门约定。受静态审查限制,未执行测试或验证远端 MCP 实际响应结构,剩余风险主要是文档所述返回字段仍依赖服务端契约保持一致。

CI 单测结果

结论说明

自动 CR 不通过,原因如下:

  • PR 描述或发起人评论缺少 chat Agent 测试截图
  • PR 描述或发起人评论缺少 chat 指令 CI 集成测试截图

自动 CR 结论为不通过;未提交 GitHub Review,也不会自动合并。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants