Repository navigation
refactor: delete doctor staleness/bloat checks and dead lib.js readers (#458) - #465
Conversation
#458) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X9gZYk7FcYSLAZBBe7JXvZ Co-authored-by: Cursor <cursoragent@cursor.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 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 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 402e16726b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| active, | ||
| ...perTrack.map((run) => run.sprint_shape), | ||
| ...perTrack.map((run) => run.in_flight_trace), | ||
| ...perTrack.map((run) => run.in_flight_staleness), | ||
| checkContextBloat({ repoRoot: root, sprintsDir, threshold: contextLineThreshold }), | ||
| ]; |
There was a problem hiding this comment.
For stale in-flight work or an _context.md over 200 lines, this list now lets the doctor report no corresponding warning, but spec/capabilities.md:100 still explicitly declares in_flight_staleness and context_bloat as retained doctor checks. Either preserve them or obtain explicit approval and amend the durable capability spec so shipped behavior does not contradict the living contract.
AGENTS.md reference: AGENTS.md:L56-L60
Useful? React with 👍 / 👎.
1 participant
Closes #458. Part of #456.
Keep test:
in_flight_staleness(--stale-days) is a threshold overage_daysthatsprint-state.jsalready emits,context_bloatiswc -l; nothing consumed either.lib.jsdropsparseMarkerMonthand the triage config readers orphaned by #433. The three guard checks (active_sprint,sprint_shape,in_flight_trace) and their JSON shapes are unchanged.backlog-doctor.js490 → 389,lib.js308 → 239. Implemented by Grok 4.6 (cursor-agent); reviewed by GPT-6 Astra (codex, read-only) before merge.Verified:
node --testgreen, smoke green, doc-drift OK.🤖 Generated with Claude Code
https://claude.ai/code/session_01X9gZYk7FcYSLAZBBe7JXvZ