fix(drift): home-dotdir paths are runtime state, not drift (0.1.0-alpha.20) - #50
Conversation
Takes ask 2. Declines ask 1 — the measurement is in the report, not the code. `~/.config/qmd-server/registry.json`, `~/.cache/huggingface/hub/` and friends are caches, credentials and per-host config, absent by design on any machine that has not run the thing yet. Same concept isForeignRuntimePath already encodes for container paths, in `~` form, so it joins the same note path rather than getting a mechanism of its own. Measured across the fleet's rule files first: 17 such references, 12 resolve, and all 5 that do not are runtime state or a doc elision containing a literal "...". None is a defect. A resolving path is silent either way, so this has no false-negative cost on the measured population. Bounded to dotdirs deliberately. `~/saffron/agents/meg/charters` is NOT exempt — that was a real defect in lc-classic-starter, and a home path that is not a dotdir is ordinary content. The test asserts both directions. recall goes from 1 path issue to 0, with the reason stated in the report rather than the finding silently disappearing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 10 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (11)
Comment |
1 participant
Ask 2 shipped. Ask 1 declined — your predicted error is the outcome.
Ask 1: requiring a
/is not sufficient, and it's worse than you fearedI reproduced the fixture first: at
13d8fefab~1,ai-rules/is absent,.rulesync/is present, and drift is silent on it. Confirmed.Then I measured the candidate — backticked references ending in
/— across 36 repos:107 new findings to catch 1 known defect. And the flagged set is not prose words — it's worse, because they pass your
/filter cleanly:Those are directory names inside a described layout ("create a
research/folder") and template placeholders with example slugs. They have the slash.ai-rules/has exactly the same shape — one segment plus a trailing slash — so no segment-count rule separates them either; requiring ≥2 segments would miss the target.The distinguishing information is semantic: is this a path from the repo root, or a name in a layout being described? That's the illustrative-examples problem in a new costume, as you predicted.
Ask 2: shipped
Measured independently before building: 17
~/.<dotdir>references, 12 resolve, 5 absent — caches, credentials, per-host config, and one doc elision containing a literal.... None a defect. Slightly different totals from your 19/11/8 (narrower file scope), same conclusion.It joins the note path
isForeignRuntimePathalready uses rather than getting its own mechanism — same concept,~form.Bounded to dotdirs deliberately.
~/saffron/agents/meg/chartersis not exempt — that was a real defect in lc-classic-starter. The test asserts both directions.recall: 1 path issue → 0, with the reason stated in the report rather than the finding silently vanishing.
Verify
lint · format:check · release:pin --check · typecheck · 530 pass / 0 fail · verify:self-audit-proof.
🤖 Generated with Claude Code