docs(index): link Master Index to PR #25 + per-item frontend trackers

[Adiz4415]

Summary

Follow-up to PR #24 (MASTER_INDEX refresh). This PR is the second-stage refresh linking the formerly-placeholder frontend catalog to the actually-merged PR #25 and adding per-item Top-20 tracker pointers for the 11 frontend items the user explicitly listed (mirror of the contracts/backend pointer pattern from PR #22 and PR #23).

What changed

• ## Catalog sources & deduping — PROJECT/issues/FRONTEND_ISSUES.md is now listed alongside CONTRACTS_ISSUES.md and BACKEND_ISSUES.md under durable long-form references (no longer legacy), with PR docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25 cited.
• ## Top 20 (ship-safety order) — per-item tracker pointers added for the 11 user-listed frontend items, each linking to [tracker](../PROJECT/issues/FRONTEND_ISSUES.md#resolution-tracker-fix-status):
  • 3 Critical (wallet/auth): F-001, F-002, F-005
  • 8 top-High (ship-safety): F-014, F-015, F-019, F-020, F-022, F-025, F-051, F-063
  • All anchors use the GitHub-correct #resolution-tracker-fix-status slug (no #8- prefix).
• ## CHANGELOG — strict reverse-chronological order maintained. New top entry: 2026-06 — Frontend catalog consolidation (PR docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25). The Master Index Refresh entry from PR docs(index): add CHANGELOG + per-item Top-20 tracker pointers #24 is preserved but updated to cite PR docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25 directly instead of referencing a placeholder. The legacy "(Future) Frontend" bullet is removed (now realized as PR docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25).
• Intro paragraph under Top 20 updated to cite the three Resolution Trackers (PR docs(contracts): consolidate CONTRACTS_ISSUES.md to close #12 #22 contracts, PR docs(backend): consolidate BACKEND_ISSUES.md catalog #23 backend, PR docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25 frontend).

Honesty note

Item 20 (F-004 — wallet secret base64 obfuscation) remains Critical in Top 20 but without a per-item tracker pointer. The user's explicit 11-pointer list did not include F-004; the CHANGELOG entry explicitly documents this so reviewers can see the rationale. Adding/dropping F-004 can be addressed in a separate follow-up PR if desired.

Verification

• Top 20 still has exactly 20 numbered items.
• All 11 user-listed frontend IDs each carry one …/FRONTEND_ISSUES.md#resolution-tracker-fix-status link.
• CHANGELOG order is reverse-chronological with PR docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25 at top.
• No #8-resolution-tracker-fix-status anchors anywhere (only #resolution-tracker-fix-status).
• All PR references are real and merged: docs(contracts): consolidate CONTRACTS_ISSUES.md to close #12 #22 (contracts), docs(backend): consolidate BACKEND_ISSUES.md catalog #23 (backend), docs(index): add CHANGELOG + per-item Top-20 tracker pointers #24 (master index), docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25 (frontend).

Follow-ups

• Add tracker pointer for F-004 (item 20) OR drop F-004 from Top 20 to fully mirror the contracts/backend pattern.
• Begin removing legacy duplicated content from the repo-root ISSUES.md files now that all three catalogs are consolidated.

[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 21 minutes and 30 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: 0819467e-74d6-436b-bbe4-04be352c7cf3

📥 Commits

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

📒 Files selected for processing (4)

• 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.}