docs: refresh stale CLAUDE.md status banner (informal meta: waiver) - #205
Conversation
The top banner said "Status: draft … greenfield … Nothing has been implemented yet … the first ten thousand lines" — flatly stale: the ingest + query stack is built and tested behind RFC acceptance gates, RFC 0001/0007/0008 are at terminal status. Update it to "pre-release, under active RFC-driven development" (mirroring the README status note), keeping the same-care ethos. Per CLAUDE.md's footer a change needs a meta: RFC + majority approval; this is a factual-staleness fix (not a directive change) requested by the maintainer, so it lands as an informal meta: RFC waiver recorded in the footer changelog (precedent: b50067d, the §6.2 bullet). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughTwo sections of ChangesCLAUDE.md Documentation Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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. Comment |
There was a problem hiding this comment.
Pull request overview
Updates the root CLAUDE.md status banner to reflect the project’s current maturity (pre-release, RFC-driven development) rather than the previously stale “draft / nothing implemented” wording.
Changes:
- Replaces the top-of-file status banner with current ingest/query stack status and a pointer to
docs/benchmarks.md. - Records the banner refresh in the
CLAUDE.mdfooter changelog as an informalmeta:RFC waiver (per described precedent).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
What
Refreshes CLAUDE.md's stale top status banner.
Before → after
docs/benchmarks.md. These directives exist to make sure every line is written with the same care as the first — and the hundred-thousandth."The old banner was flatly false (10 crates implemented; RFC 0001/0007/0008 at terminal status). New wording mirrors the README status note and keeps the "same care" ethos.
Process
Per CLAUDE.md's footer, a change to it needs a
meta:RFC + majority approval. This is a factual-staleness fix, not a directive change, and maintainer-requested — so it lands as an informalmeta:RFC waiver recorded in the footer changelog (precedent:b50067d, the §6.2 "tests are specifications" bullet). Say the word if you'd prefer a formal RFC instead.CLAUDE.md only; not under
docs/, so no mdBook impact.🤖 Generated with Claude Code
Summary by CodeRabbit