docs(flare-git-core): ratify unified config.toml design decisions (item #331) - #553
docs(flare-git-core): ratify unified config.toml design decisions (item #331)#553getappz wants to merge 1 commit into
Conversation
#331) Records what PR #336 already shipped (git_shim policy slice: additive union over project-local + user-home config.toml layers, fail-open to baseline on malformed TOML), plus a subsystem survey, precedence order, fail-safe rationale, the next migration target (protected-branch names), and a per-machine-only decision for epic #130 sync. Agentflare-Agent: claude-code Agentflare-Branch: task/331-epic-unified-agentflare-config-toml-make Agentflare-Item: 331
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 19 seconds Limit details: You’ve used all 1 included review currently available under your plan. You completed 60 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour. 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: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Comment |
|
Closing per updated policy: design/research/planning output defaults to local artifacts, not the repo. Content re-published as agentflare artifact instead: http://127.0.0.1:64009/mxdi5_O-UIzhmPuhKK2X2 (see item #513 for the pipeline-level fix). |
1 participant
Summary
Design-spec deliverable for item #331 (EPIC: Unified ~/.agentflare/config.toml). Produced by an automated dispatch (cursor agent, sdd_loop) surveying hardcoded/env-var-only policy across the codebase and ratifying the unified config.toml schema/precedence decisions.
See
crates/flare-git-core/UNIFIED_CONFIG_TOML_DESIGN.mdfor the full design doc.Note
This PR was opened manually after the automated
item_donepush/PR step failed silently (branch had a real diverged commit but no PR resulted — a distinct bug from #511/#550, filed separately). The design work itself is genuine and complete.