release: v0.7.0-beta.4

[2233admin]

Summary

切 v0.7.0-beta.4。自 beta.3 起 main 上共 20 个提交。

改动 5 个文件：CHANGELOG.md、crates/code-intel-cli/Cargo.toml、Cargo.lock、orchestration/toolchain-versions.v1.json，外加 crates/code-intel-cli/tests/fixtures/cli-head-parity.v2.json——该 golden fixture 把 --version --json 的 stdout 逐字节钉死，含两处版本字符串，不跟着版本号走就会红。

这一版的主线

• G1 诚实位（feat(gate): G1 -- computed honesty bit for repin's scan coverage #141）：Complete 必须携带扫描面才构造得出来，NotComputed 是一等状态。验收是反向测试：把 partial 只改 status 伪装成 complete 必须被拒绝，且关掉校验该测试会红。
• 架构收敛（feat(arch): converge CLI into typed controllers and singular run kernel #134）：main.rs 73 行进程壳，单一权威迭代，已提交证据与工作树建议分权。
• eval 基线抗重构（fix(eval): resolve golden spans by content anchor, not pinned line number #137）：golden span 按内容锚解析；锚不到的题标 broken，不再被静默记成「A 臂答不出」。
• 自扫四修（fix(doctor): probe ast-grep so bootstrap stops reporting ok on a machine where edit.ast-grep-plan cannot run #143 fix(doctor): --require-understand 真的检查 Understand Anything，终结 fail-open 空转 #144 fix(run): 发布名撞车给出独立退出码 73 与可解析 stdout，终结「exit 65 + 零字节」 #145 fix(evidence): 墙上时钟不再进 payload 摘要，未变的树不再重发对象 #147）：全部来自用本项目的工具扫本项目，每条都带一个「撤销就红」的测试，且各自经过独立验伪。

一条明确的负结果

#140（symbol-bounded chunks）未合并，作为证据保留。实现前写下的预测与实测完全一致：零覆盖变化，而 chunks 产物 ×3.56。由此得到 #142——Arm A 的字节开销 99.8% 是产物全量扫描，把产物做得更精确只会更贵。

验证

• cargo test --workspace --locked → 2963 passed（52 suites，125s）
• code-intel repin --json → stalePins: []（跳过项均为二进制文件）

已知问题

见 #148（help 静默绿灯、巨石门禁只报数量不报文件名、sentrux dsm 边矩阵结构性为空、149 条 rustc 警告直通发布等）。本次不修。

Refs #139 #142 #148

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[repowise-bot]

🔒 Repowise is not analyzing this repository

The PR bot is free on public repositories. This one is private, which needs a Pro plan.

See plans · Manage this repository

[coderabbitai]

Warning

Review limit reached

@2233admin, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 31 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: aa741e9f-0913-45a6-9fe6-42f3dddfca17

📥 Commits

Reviewing files that changed from the base of the PR and between 303a005 and 0105da1.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• CHANGELOG.md
• crates/code-intel-cli/Cargo.toml
• crates/code-intel-cli/tests/fixtures/cli-head-parity.v2.json
• orchestration/toolchain-versions.v1.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Code Intel change risk

Score	Percentile	Level
56/100	37th (vs last 49 commits)	🟢 low

Top signals

• Diff shape: 5 file(s), +37/-5 (max file share 0.76)
• Test asymmetry: source changed, tests touched
• Bug-magnet: 14 fix commit(s) in touched files (180d)
• Churn: 65 commit(s) touching these files (90d)

_{revspec: origin/main..HEAD · threshold: percentile >= 90 blocks unless labeled risk-accepted · code-intel change risk}