docs(product): 第二仓冷启动实录——tdxcli-rs 全链路 8/5/2 + 摩擦五条 - #110
Conversation
Refs #99 #59 13 steps, 181s total wall-clock against D:/projects/tdxcli-rs (foreign, non-self-hosted repo) — 8 ok as documented/specified, 5 needed adaptation, 2 hard-failed outright (both later fixed by a later step). 5 numbered friction items filed (F1-F5): F2 is a real bug (run execute commits a layout artifact query can never index, silently), F1 and F3 are missing docs (the full-chain commands this task needed are invisible outside --help --all; README's documented output file tree doesn't exist on disk for any run style tested), F4 is a hardcoded CWD assumption on `change risk`, F5 is an unconfirmed but live ambient CODE_INTEL_HOME precondition. Target repo verified byte-identical (git status --porcelain + HEAD) before and after. Pipeline code untouched; frictions are the deliverable.
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
🔒 Repowise is not analyzing this repository The PR bot is free on public repositories. This one is private, which needs a Pro plan. |
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
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. Comment |
Code Intel change risk
Top signals
revspec: |
干什么(#99 最小版:第一次非自举仓全链路)
目标仓
tdxcli-rs(用户真实仓、带活未提交改动)。铁律执行到位:目标仓零写入,前后git status --porcelain+ HEAD 逐字节一致(双重验证)。按"局外人故事"(README/SKILL.md 文档路径)走,不用内部人捷径——文档断在哪,哪里就是发现。数字
docs/runbooks/frictions.md,逐条带原始报错与源码根因)docs/runbooks/second-repo-cold-start.json(机读真源)+ 派生 md 视图头号发现
F2(真 bug):
run execute --authority-root X --final-name Y——CI 自审用的同款调用形状——exit 0 报committed,但artifact query永远索引不到:查询侧要求X/<repo>/<run-id>/两级嵌套,写入侧从不强制也不提示。干净的写入实为死端。已验证 invocation 级 workaround(手工把 repo 名折进 authority 路径)。其余:F1 全链路命令在 README/SKILL.md 里不可见(只活在
--help --all和 CI yml);F3 README"输出在哪里"文件树与实际 content-addressed 布局不符;F4change risk独缺--repo旗标、静默评 CWD 所在仓;F5 多 worktree 机器上 ambient CODE_INTEL_HOME 疑似可绕过 foreign-checkout 守卫(未复现,低置信标注)。五条将逐一开 issue 跟踪。
Refs #99 #59