docs: fork-changes entries for the CLI wave - #410
Conversation
|
Warning Review limit reached
Next review available in: 46 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
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 |
Summary
Backfills
docs/fork-changes.yamlwith the three CLI-wave lane entries (merge hashes836d1a1,2848e96,ff9ee22— the #402 backfill pattern), regeneratesFORK_CHANGELOG.md, the README fork-change-queue table, andllms-full.txt.Wave scope: ten first-class CLI verbs across three lanes (#354–#363, part of #191), 231 new tests, daemon-first routing with
--jsoneverywhere and--confirmgating on destructive verbs. #360 deliberately shipped without--session/list(no session concept in the underlying tool — #408 + palace-daemon#240 track it); #364 stays deferred on palace-daemon#222.scripts/check-docs.sh: docs clean, 7/7.🤖 Generated with Claude Code