Skip to content

docs(backend): consolidate BACKEND_ISSUES.md catalog#23

Open
Adiz4415 wants to merge 2 commits into
Pi-Defi-world:mainfrom
Adiz4415:fix/backend-issues-catalog-issue-13
Open

docs(backend): consolidate BACKEND_ISSUES.md catalog#23
Adiz4415 wants to merge 2 commits into
Pi-Defi-world:mainfrom
Adiz4415:fix/backend-issues-catalog-issue-13

Conversation

@Adiz4415

Copy link
Copy Markdown
Contributor

Summary

Mirrors the contracts-catalog consolidation (PR #22) onto the backend. Restructures PROJECT/issues/BACKEND_ISSUES.md into the canonical severity/area/evidence/impact/fix/acceptance format used by issues/backend.md, expanding coverage from 56 to 75 catalog entries with stable B-### IDs.

What changed

  • Restructured PROJECT/issues/BACKEND_ISSUES.md from a 56-item annotated list into the canonical severity/area/evidence/impact/fix/acceptance format used by issues/backend.md.
  • Coverage expanded from 56 to 75 catalog entries, fully aligned with issues/backend.md (B-001 through B-075). Severity distribution: 2 Critical, 21 High, 38 Medium, 14 Low (verified unique IDs).
  • Legacy 56-item list preserved as Section 7 cross-reference with (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).
  • Added structural sections mirroring PR docs(contracts): consolidate CONTRACTS_ISSUES.md to close #12 #22 pattern: Summary Table, Severity Counts, Resolution Tracker (Section 8), Top Remediations (ship-safety order), Cross-Reference Map, Maintenance guidelines.
  • Acceptance criteria included for every entry so each issue can be unambiguously verified when fixed.

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.md remains the live triage-ready catalog and is now faithfully mirrored.

Verification

  • IDs B-001 through B-075 all present and unique (75 verified).
  • Severity counts tally: 2 + 21 + 38 + 14 = 75 (matches issues/backend.md).
  • Cross-reference paths from PROJECT/issues/ to companion files resolve: ../../issues/backend.md, ../CONTRACTS_ISSUES.md, ../SMART_CONTRACT_SPEC.md, ../../TECHNICAL/..., ../../correction.md.
  • Legacy list preserved as Section 7 with explicit (moved) / (new) tags.

Related

Adiz4415 added 2 commits June 20, 2026 12:25
…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
@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Adiz4415, we couldn't start this review because you've reached your PR review rate limit.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f7864fa8-82ea-4a62-8a2f-3e6d581fb483

📥 Commits

Reviewing files that changed from the base of the PR and between ea8aa4b and 6583ac6.

📒 Files selected for processing (2)
  • PROJECT/issues/BACKEND_ISSUES.md
  • PROJECT/issues/CONTRACTS_ISSUES.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant