docs(backend): consolidate BACKEND_ISSUES.md catalog#23
Conversation
…catalog - Restructure PROJECT/issues/CONTRACTS_ISSUES.md into a single source of truth using canonical severity/area/evidence/impact/fix/acceptance format. - Cover all 60 catalog entries from issues/contracts.md (Critical 6, High 21, Medium 24, Low 9) with stable C-### IDs. - Preserve the legacy 34-item list as Section 7 cross-reference. - Add Summary Table, Severity Counts, Resolution Tracker, Top Remediations (ship-safety order), Cross-Reference Map, and Maintenance notes. - Provide anchor points for future PR references. Closes Pi-Defi-world#12
|
Warning Review limit reached
More reviews will be available in 50 minutes and 27 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy 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. Comment |
Summary
Mirrors the contracts-catalog consolidation (PR #22) onto the backend. Restructures
PROJECT/issues/BACKEND_ISSUES.mdinto the canonical severity/area/evidence/impact/fix/acceptance format used byissues/backend.md, expanding coverage from 56 to 75 catalog entries with stableB-###IDs.What changed
PROJECT/issues/BACKEND_ISSUES.mdfrom a 56-item annotated list into the canonical severity/area/evidence/impact/fix/acceptance format used byissues/backend.md.issues/backend.md(B-001 through B-075). Severity distribution: 2 Critical, 21 High, 38 Medium, 14 Low (verified unique IDs).(moved)/(new)tags. New findings propose follow-up canonical IDs (e.g. legacy CONTRIBUTING_GUIDE.MD #1 bcrypt salt bug mapped to proposed B-076).Why
Following the established pattern from PR #22 (issue #12, contracts catalog), this consolidates backend MVP flaws into a durable reference. This file is the durable long-form version;
issues/backend.mdremains the live triage-ready catalog and is now faithfully mirrored.Verification
issues/backend.md).PROJECT/issues/to companion files resolve:../../issues/backend.md,../CONTRACTS_ISSUES.md,../SMART_CONTRACT_SPEC.md,../../TECHNICAL/...,../../correction.md.(moved)/(new)tags.Related
issues/backend.mdPROJECT/issues/BACKEND_ISSUES.md