docs(frontend): consolidate FRONTEND_ISSUES.md catalog

[Adiz4415]

Summary

Mirrors the contracts-catalog consolidation (PR #22) and backend-catalog consolidation (PR #23) onto the frontend. Restructures PROJECT/issues/FRONTEND_ISSUES.md into the canonical severity/area/evidence/impact/fix/acceptance format used by issues/frontend.md, expanding coverage from 77 (legacy) to 65 (canonical) catalog entries with stable F-### IDs.

What changed

• Restructured PROJECT/issues/FRONTEND_ISSUES.md from a 77-item annotated list into the canonical severity/area/evidence/impact/fix/acceptance format used by issues/frontend.md.
• Coverage aligned to all 65 canonical entries (F-001 through F-065). Severity distribution: 5 Critical / 14 High / 23 Medium / 23 Low (verified 65 unique IDs).
• Legacy 77-item list preserved as Section 7 cross-reference with (moved) and (new) tags. New findings propose follow-up canonical IDs in the F-066..F-077 range — exactly as the contracts catalog (PR docs(contracts): consolidate CONTRACTS_ISSUES.md to close #12 #22 → B-076+) and backend catalog (PR docs(backend): consolidate BACKEND_ISSUES.md catalog #23 → B-076+) did.
• Added structural sections mirroring PR docs(contracts): consolidate CONTRACTS_ISSUES.md to close #12 #22 / PR docs(backend): consolidate BACKEND_ISSUES.md catalog #23 patterns: Summary Table, Severity Counts, Resolution Tracker (Section 8), Top Remediations (ship-safety order), Cross-Reference Map, Maintenance.
• Acceptance criteria included for every canonical entry so each issue can be unambiguously verified when fixed.

Why

Following the established pattern from PR #22 (issue #12 contracts) and PR #23 (backend), this consolidates frontend MVP flaws into a durable reference. The file is the durable long-form version; issues/frontend.md remains the live triage-ready catalog and is now faithfully mirrored. This is the third and final piece of the three-catalog consolidation (Contracts → Backend → Frontend) plus the master-index refresh (PR #24).

Verification

• IDs F-001 through F-065 all present and unique (65 verified).
• Severity counts tally: 5 + 14 + 23 + 23 = 65 (matches issues/frontend.md).
• Cross-reference paths from PROJECT/issues/ to companion files resolve: ../../issues/frontend.md, ../CONTRACTS_ISSUES.md, ../BACKEND_ISSUES.md, ../../TECHNICAL/..., ../../correction.md.
• Legacy list preserved as Section 7 with explicit (moved) / (new) tags.
• Top Remediations ship-safety list covers all 5 Critical items in item 1 and all 14 High items across items 3–6.

Related

• Mirrors PR docs(contracts): consolidate CONTRACTS_ISSUES.md to close #12 #22 (contracts) and PR docs(backend): consolidate BACKEND_ISSUES.md catalog #23 (backend) patterns
• Mirrors issues/frontend.md
• Preserves legacy content from prior PROJECT/issues/FRONTEND_ISSUES.md
• Completes the three-catalog consolidation: 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) + this PR (docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25 frontend)
• Closes the CHANGELOG forward reference for frontend in issues/MASTER_INDEX.md

[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 32 minutes and 3 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: e10e7efe-9841-4586-851a-cc26ea852d50

📥 Commits

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

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