Tyr0new

I spent some time with the newly open-sourced Grok Build repo: 1.07M lines of Rust, 85 crates, one squashed commit, no PRs accepted. Out of the box, `cargo test --workspace` doesn't compile. 190+ errors, all one bug class: cross-crate test helpers hidden behind #[cfg(test)], which Bazel's per-target test builds tolerate but Cargo doesn't, because a dependency is never compiled in test mode. The default-bazel feature is declared in ~20 manifests and wired to nothing. Ungating the benign helpers and putting the signing-key test seam behind a dev-dependency-only feature gets the suite running for the first time on the published tree: 24,663 passed, 28 failed, and every one of the 28 is a pre-existing bug the broken build had been hiding (tests reading your real ~/.claude/settings.json, a tool missing from the registry, macOS /var symlink breakage, one Theme::current() race). Questions for the team: - Did anyone try downloading this repo and running it before publishing? - Why not accept pull requests as a public version? - Half of the code is tests, but the tests don't run out of the box. Which is it? tested or not?

团队 AI 编程成熟度模型（L1-L5） 目前大部分团队都在走向 L3，部分团队进入L4，无法适应 L3 工作模式的开发人员正在被淘汰了。 L3 对开发人员的要求： - 有能力构建项目中的 Harness - 有能力判断和评审 Plan - 有 TDD 思维，能通过测试（API/E2E）验收成果 已经很多团队只要资深人员做方案评审，大量淘汰（30%-50%）基础开发人员了。 有幸见证时代。

Embarrassment of riches. But looks like we might hit 9M soon. Should we reset the ChatGPT Work and Codex usage again or give it some space?