Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

test(docs): 补 doc_claims.rs 守住五通道叙事与中英双语一致（审计 §七 声称已落地，实际不存在）

Open
  • Is something wrong?
#18 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
documentation, testing

Research direction

Start by reading src/bridge/transport/registry.rs and the existing integration tests under tests/ to match the project’s test conventions. Add a pure-std tests/doc_claims.rs covering the registered transport count, obsolete claims in tracked files, and consistency of channel lists across English and Chinese docs; keep the documented ilink only via claim valid. Run the Rust test suite and confirm the new checks pass.

Written by the indexing model from the issue text.

Description

优先级 P2 · 依赖：无

基线 HEAD = e4f8200

Summary

大仓审计的「防漂移机制落地」表声称本仓已落地「文档断言测试」，该文件实际不存在：

  • 审计声称（大仓 docs/DOC_CODE_AUDIT-2026-10-01.md:307）：「im-agentproc/tests/doc_claims.rs（4 用例，纯 std）」
  • 实际 tests/ 下只有：mcp_per_turn_context.rs、wip_issue3_fatal_cli_classification.rs、wip_issue5_cli_session_store.rs、wip_issue8_text_limits.rs、wip_issue10_degraded_cli_session.rs、wip_issue15_session_store_persistence.rs、wip_issue15_stale_resume_fallback.rs、wip_issue15_wecom_serialization.rs；无 doc_claims.rs。

旁证「没有回归门」的代价：README.md:61 长期写 iLink is the only real adapter today, Feishu / Telegram / … land as new Transport implementations.，而 src/bridge/transport/registry.rs 早已注册 5 个 Transport（:96-100 with_builtins() 顺序 ilink → telegram → wecom → feishu → discord，telegra/wecom/feishu/discord 各自的 adapter 见 :18-22 导入），CI 从未报警。

影响

  • 五通道这类对外能力声明没有机器守卫；本仓 README 与 Cargo.toml 的 description 因此落后于代码（对外门面出错）。
  • 本仓有中英双语文档（docs/ 与 docs/zh/），漂移会各自发生：本次修正时发现 3 处只有中文镜像漏改（如 docs/zh/guide/configuration.md:10,40、docs/zh/transport.md:79），英文侧已更新而中文侧仍写「只实现了 ilink」。

建议

补 tests/doc_claims.rs（纯 std、无需网络与外部 CLI），至少覆盖：

  1. registry.rs 注册的 Transport 数量与 README / Cargo.toml description 的声明一致；
  2. 仓库跟踪文件中不出现 only real adapter / iLink/WeChat today 等旧文案（git grep 级别断言或直接读文件断言）；
  3. 中英双语通道清单一致（docs/ 与 docs/zh/ 对应页面的 kind 清单互相一致）。

边界

  • 只加测试，不改文档与代码（文案修正另有 PR：jeffkit/im-agentproc#17）。
  • 注意保留一处不改的表述：docs/guide/configuration.md:11,43 的 via: … (ilink only) 是正确的（registry.rs:242 显示 ilink_factory 是 ctx.via 的唯一消费者），断言不要把它一并禁掉。
  • 同根源另见 jeffkit/hitl-mcp#4 与 jeffkit/argusai#13（跨仓拆开提）。
Dominant language
Rust
Stars
0
Forks
0
Avg merge
11m
Merged PRs (30d)
7

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jeffkit/im-agentproc

All issues in jeffkit/im-agentproc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.