Realign docs and engine contracts to the steering-first direction - #16
Conversation
…tion ADR set rewritten around the new direction: ADR-009 (Pi + Claude Code as the only Tier 1 adapters), ADR-010 (user-input phase, spec only), ADR-003 (minimal createEngine()/evaluate() embeddable API), ADR-008 (no policy-as-code, not a security boundary), ADR-002 (three phases, Tier 1 capability table). README rewritten (steering hero, three doors, honest pack status), new LIMITATIONS.md, SECURITY.md pairing answer. Code alignment only: createEngine facade, internals marked @internal, Tier 1 capability constants, user-input types/validation plumbing (engine wiring lands with the feature PR), and the confirm→block fallback per ADR-002 (was confirm→suggest). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FUpa7w5hYzrXyCYkK8K1DC
|
Warning Review limit reached
Next review available in: 28 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 Plus Run ID: 📒 Files selected for processing (24)
✨ Finishing Touches✨ Simplify code
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 |
|
1 participant
Part 1 of 2 (part 2: #15, stacked on this branch). Pure alignment to the new direction — docs, ADRs, and contract-level code changes only; no new features.
ADRs
user-inputphase (design; implementation ships in feat: steering-first surface — change-17 user-input phase, change-18 QoL steering packs, change-7 claude-code adapter #15)redactUserInput, Claude Coderedactfloor ≥ 2.1.121)createEngine(packs, capabilities)→evaluate(ctx), pack loader, public types; everything else@internalPublic docs
--strictstated as roadmap, per ADR-007)Code (contract alignment only)
createEngine()/Enginefacade (ADR-003); plumbing exports marked@internal(typedocexcludeInternalenforces the published surface)confirm → blockfallback per ADR-002 (removes the confirm→suggest path)claudeCodeCapabilities()user-inputtypes/validation plumbing (inert until feat: steering-first surface — change-17 user-input phase, change-18 QoL steering packs, change-7 claude-code adapter #15 wires the engine)200 tests green; lint/format/typecheck pass.
🤖 Generated with Claude Code
https://claude.ai/code/session_01FUpa7w5hYzrXyCYkK8K1DC