docs(research): mark B.8 (PR #43) + HTTP serve (PR #44) shipped + fix stale anchor#45
Conversation
…llow + competitive-scan - fallow.md row B.8 was ❌ Open; PR #43 shipped it. Updated to ✅ with implementation notes (rule.id taxonomy, location auto-detection, deferred frontmatter overrides). - fallow.md MCP-server bullet said 'HTTP API stays in roadmap backlog'; PR #44 shipped it. Reworded; added a dedicated PR #44 bullet covering the new transport, shared tool/resource handlers, CSRF/DNS-rebinding guard, Zod validation at the HTTP boundary, and 404/500 status semantics. - competitive-scan-2026-04.md '4. What moved to the roadmap': replaced 'HTTP API (codemap serve) — still backlog' with shipped rows for PR #43 + PR #44. - Fixed broken anchor: cross-ref to fallow.md was #status-snapshot-as-of-2026-05-01 but the heading bumped to 2026-05-02 in PR #42.
|
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Review rate limit: 0/1 reviews remaining, refill in 19 minutes and 35 seconds.Comment |
Summary
Stale-snapshot sweep on the two research docs after PR #43 (SARIF) and PR #44 (HTTP serve) merged:
docs/research/fallow.md— row B.8 was ❌ Open, now ✅ shipped via PR feat(query): --format sarif | annotations (B.8 — pipe rows into GitHub Code Scanning + PR annotations) #43; MCP-server "Adjacent shipped" bullet said HTTP API stays in roadmap backlog (PR feat(serve): codemap serve — HTTP API exposing every MCP tool over POST /tool/{name} #44 shipped it); added a dedicated PR feat(serve): codemap serve — HTTP API exposing every MCP tool over POST /tool/{name} #44 bullet covering the new transport + CSRF guard + Zod boundary + status semantics.docs/research/competitive-scan-2026-04.md§ 4 — replaced "HTTP API (codemap serve) — still backlog" with shipped rows for PR feat(query): --format sarif | annotations (B.8 — pipe rows into GitHub Code Scanning + PR annotations) #43 + PR feat(serve): codemap serve — HTTP API exposing every MCP tool over POST /tool/{name} #44; fixed a broken anchor (cross-ref to fallow.md was#status-snapshot-as-of-2026-05-01but the heading bumped to2026-05-02in PR docs: post-PR #41 nits — fallow snapshot refresh + drop shipped golden-queries from roadmap #42).Behavior change
None — docs only.
Follow-up
docs-governanceRule 8 says "when a research scan's adopt items ship, slim the note to a 'What shipped' appendix linking to canonical homes."competitive-scan-2026-04is now mostly closed (only watch + cross-agent left from § 4). Worth a separate slim-pass PR via thedocs-lifecycle-sweepskill — not blocking this status update.Test plan
bun run checkgreen.