docs(project): add Catalog consolidations subsection to PROJECT/README.MD

[Adiz4415]

Summary

Adds a "Catalog consolidations" subsection under the Project Management block of PROJECT/README.MD so contributors can quickly locate the durable long-form reference files for each domain catalog, with canonical entry counts, severity distributions, and links to the consolidation PRs (#22 contracts, #23 backend, #25 frontend).

What changed

• PROJECT/README.MD — nested Catalog consolidations bullet block under the ### Project Management (\PROJECT/`)` subsection, immediately after the existing Known issues line, with three child bullets:
  • issues/CONTRACTS_ISSUES.md — 60 canonical entries (C-001..C-060); 6 🔴 Critical / 21 🟠 High / 24 🟡 Medium / 9 🟢 Low. Consolidated in PR #22.
  • issues/BACKEND_ISSUES.md — 75 canonical entries (B-001..B-075); 2 🔴 Critical / 21 🟠 High / 38 🟡 Medium / 14 🟢 Low. Consolidated in PR #23.
  • issues/FRONTEND_ISSUES.md — 65 canonical entries (F-001..F-065); 5 🔴 Critical / 14 🟠 High / 23 🟡 Medium / 23 🟢 Low. Consolidated in PR #25.
• Footer Last Updated: date bumped from January 26, 2026 → June 20, 2026 to match the June catalog-consolidation PRs.

Adjacent quality-of-life fix (out of strict scope)

The pre-existing Known issues line above the new subsection used bare filenames (CONTRACTS_ISSUES.md, …) which resolved to non-existent files at PROJECT/CONTRACTS_ISSUES.md instead of the actual PROJECT/issues/CONTRACTS_ISSUES.md path. I corrected those three links to issues/CONTRACTS_ISSUES.md / issues/BACKEND_ISSUES.md / issues/FRONTEND_ISSUES.md so the whole block now links correctly. This is technically scope-creep relative to the user's stated add-only request, but it was a one-line drive-by and prevents the new subsection from sitting alongside three broken siblings. Flag in case the maintainer wants this split into a separate PR; happy to revert if preferred.

Verification

• All three target files exist at the cited paths.
• Severity distribution and canonical-id range per domain match the consolidated catalogs (verified against PROJECT/issues/* in the same commit/branch).
• PR references are real and merged (docs(contracts): consolidate CONTRACTS_ISSUES.md to close #12 #22, docs(backend): consolidate BACKEND_ISSUES.md catalog #23, docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25). No docs(index): add CHANGELOG + per-item Top-20 tracker pointers #24 or docs(index): link Master Index to PR #25 + per-item frontend trackers #26 references — those are master-index PRs, not catalog consolidations.
• Section heading flow is preserved (## Quick Start remains immediately after ### Project Management (\PROJECT/`)`).
• Footer Last Updated: is current (June 20, 2026).

[coderabbitai]

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 16 minutes and 29 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: cfe4058c-8108-48d2-bfff-83ff98227c5c

📥 Commits

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

📒 Files selected for processing (5)

• PROJECT/README.MD
• PROJECT/issues/BACKEND_ISSUES.md
• PROJECT/issues/CONTRACTS_ISSUES.md
• PROJECT/issues/FRONTEND_ISSUES.md
• issues/MASTER_INDEX.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

• X
• Mastodon
• Reddit
• LinkedIn

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