docs(index): add CHANGELOG + per-item Top-20 tracker pointers

[Adiz4415]

Summary

Updates issues/MASTER_INDEX.md with three changes: a new Catalog sources & deduping section (elevating PROJECT/issues/CONTRACTS_ISSUES.md and PROJECT/issues/BACKEND_ISSUES.md to durable long-form references via PR #22 and #23), per-item tracker-pointers in the Top 20 list to the Resolution Tracker (Section 8) of each consolidated catalog, and a new CHANGELOG section in strict reverse-chronological order (newest first).

What changed

Catalog sources & deduping (renamed from "Deduping against older docs")

• Live triage-ready catalogs in this folder (canonical working backlog): backend.md (B-001..B-075), frontend.md (F-001..F-065), contracts.md (C-001..C-060).
• Durable long-form references in PROJECT/issues/ (consolidated mirrors, see CHANGELOG):
  • ../PROJECT/issues/CONTRACTS_ISSUES.md — consolidated into canonical format in PR #22; now single source of truth for smart-contract issues.
  • ../PROJECT/issues/BACKEND_ISSUES.md — consolidated analogously in PR #23.
  • ../PROJECT/issues/FRONTEND_ISSUES.md — still legacy; pattern pending a follow-up PR.
• Truly historical (read-only): repo-root ISSUES.md / acbu-smart-contract/ISSUES.md.

Top 20 (ship-safety order) — per-item tracker pointers

Every contract/backend Top-20 line now carries a per-row deep link to the corresponding Resolution Tracker (Section 8) of PROJECT/issues/CONTRACTS_ISSUES.md or PROJECT/issues/BACKEND_ISSUES.md. Items 1–4 (C-001/C-005/C-006/C-002), 15 (C-004) and 16 (C-003) link to the contracts tracker; items 10–14 (B-005/B-006/B-003/B-001/B-002), 17 (B-010), 18 (B-009), and 20 (B-022) link to the backend tracker. Items 5–9 (F-001..F-005) and 19 (F-015) are deferred until the frontend catalog consolidation lands (forward reference noted in CHANGELOG). All Top-20 IDs are now bolded uniformly with **ID**.

CHANGELOG (reverse-chronological)

1. 2026-06 (PR TBD) — MASTER_INDEX.md refresh (this PR)
2. 2026-06 — Backend catalog consolidation (PR #23)
3. 2026-06 — Contracts catalog consolidation (PR #22)
4. _(Future) Frontend catalog consolidation

Why

Issue trackers are the long-term memory of MVP flaws. After PR #22 (CONTRACTS) and PR #23 (BACKEND) consolidated each catalog into its durable, version-of-record form with per-item Resolution Trackers, the Top 20 list needs to anchor to those trackers so a reviewer can move from the ship-safety triage ordering straight to the canonical open/fixed status of any item. PR #22 is the primary motivator (the user explicitly cited it); PR #23 notes the same pattern now provided for backend.

Verification

• All 20 Top-20 items present and uniformly bolded (**C-001**, **F-005**, **B-022**, **F-020**, etc.).
• All anchor references use #resolution-tracker-fix-status (GitHub auto-strips section number prefixes; #8-... would dead-end).
• CHANGELOG order verified reverse-chronological via grep.
• Only real PR numbers referenced (docs(contracts): consolidate CONTRACTS_ISSUES.md to close #12 #22, docs(backend): consolidate BACKEND_ISSUES.md catalog #23); no fabricated links.
• Cross-reference paths from issues/ resolve correctly to PROJECT/issues/ siblings.

Related

• Builds on PR #22 and PR #23 — closes the loop between catalogs and the master index.
• PROJECT/issues/FRONTEND_ISSUES.md will need an analogous update once the frontend consolidation PR lands; the CHANGELOG carries a forward entry for that.

[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 37 minutes and 40 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: 98f4b769-d767-450c-af7d-03d4ca7020c4

📥 Commits

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

📒 Files selected for processing (3)

• PROJECT/issues/BACKEND_ISSUES.md
• PROJECT/issues/CONTRACTS_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.}