docs(frontend): batch canonical IDs F-067..F-077 (Section 7 remaining)

[Adiz4415]

Summary

Single batched follow-up PR that migrates the remaining 9 (new) distinct findings from Section 7 of PROJECT/issues/FRONTEND_ISSUES.md (legacy #55, #56, #68, #69, #72, #73, #74, #75, #77) into canonical IDs F-067..F-077 in the live issues/frontend.md triage-ready catalog. Complements the three highest-impact follow-ups from PRs #28 (F-066 Skeleton primitive), #29 (F-071 Toast delay), and #30 (F-076 fetch timeout) by completing the migration of every (new) marker in Section 7.

What changed

9 new canonical entries appended to issues/frontend.md (in ID order)

ID	Legacy	Title	Severity	Area
F-067	#55	Contact inputs have no maxLength	🟡 Medium	frontend/forms
F-068	#56	Profile inputs have no maxLength or format validation	🟡 Medium	frontend/forms
F-069	#68	Icons recreated each render	🟢 Low	frontend/perf
F-070	#69	Menu items use router.push instead of Link	🟢 Low	frontend/nav
F-072	#72	Mobile detection treats "unknown" as desktop	🟢 Low	frontend/compat
F-073	#73	Post-KYC upload navigation uses uncleaned setTimeout	🟢 Low	frontend/hygiene
F-074	#74	Silent username normalization on signup	🟡 Medium	frontend/auth
F-075	#75	Auto-fill heuristic requires length ≥ 56	🟢 Low	frontend/ux
F-077	#77	/p2p route is client-side redirect only	🟢 Low	frontend/nav

PROJECT/issues/FRONTEND_ISSUES.md updates

• Section 1 Summary Table \u2014 9 new rows appended after F-076; totals updated from 68 \u2192 77 items.
• Section 2 Severity Counts \u2014 Medium bucket +3 (F-067, F-068, F-074) at 25 \u2192 28; Low bucket +6 (F-069, F-070, F-072, F-073, F-075, F-077) at 23 \u2192 29.
• Section 4 High \u2014 unchanged (no new High items in this batch).
• Section 5 Medium \u2014 3 detailed entries appended (F-067, F-068, F-074).
• Section 6 Low \u2014 6 detailed entries appended (F-069, F-070, F-072, F-073, F-075, F-077).
• Section 8 Resolution Tracker \u2014 Medium cluster (25 \u2192 28 items); Low cluster (23 \u2192 29 items); both rows reconciled with Severity Counts.
• Section 7 Legacy \u2014 all 9 legacy markers (#55, #56, #68, #69, #72, #73, #74, #75, #77) retargeted from (new \u2014 propose F-XXX) \u2192 (new \u2192 adopted as F-XXX in companion canonical-ID batch PR; see Section 5/6 and Section 8 for canonical rows), preserving the legacy ordinal anchor for traceability.
• Final distribution: 5 \ud83d\udd34 Critical / 15 \ud83d\udfe0 High / 28 \ud83d\udfe1 Medium / 29 \ud83d\udfe2 Low = 77 total. Arithmetic verified: 5 + 15 + 28 + 29 = 77.
• ID range text updated F-001 through F-077.

Severity rationale

• F-067/F-068/F-074 → Medium \u2014 Form-input maxLength/validation gaps cause silent truncations / backend rejections mid-flow; silent username normalization has data-integrity and phishing-typo implications.
• F-069/F-070/F-072/F-073/F-075/F-077 → Low \u2014 Performance polish, nav-pattern alignment with Next.js <Link>, fail-open mobile-default trade-off, setTimeout cleanup, heuristic refinement, placeholder route gating. Acceptable trade-offs and minor polish.

Build context

This PR is branched off fix/frontend-canonical-id-f076 (PR #30), which itself is cumulative on fix/frontend-canonical-id-f071 (PR #29) and fix/frontend-canonical-id-f066 (PR #28). When those earlier PRs land in main, this branch can fast-forward or rebase. Sequential stacking ensures each layer merges cleanly without overlap.

Verification

• code-reviewer-minimax-m3 confirmed all 9 IDs are present in issues/frontend.md and all 6 editing sites in FRONTEND_ISSUES.md (Summary Table row, Severity Counts Medium/Low, Resolution Tracker Medium/Low cluster, Section 5 entries, Section 6 entries, Section 7 markers, Totals line, IDs range).
• Final arithmetic 5 + 15 + 28 + 29 = 77 verified.
• No duplicates; F-001..F-065 set preserved; PRs docs(frontend): promote canonical ID F-066 (Shared Skeleton primitive) #28/docs(frontend): promote canonical ID F-071 (Toast removal delay ~17min) #29/docs(frontend): promote canonical ID F-076 (Frontend request() no timeout) #30's earlier additions (F-066/F-071/F-076) intact.
• Severity Counts, Resolution Tracker, and Summary Table counts all reconciled.

Follow-up

This PR is the natural terminus of the (new) migration series. With PRs #28, #29, #30, and now this PR #31 all merged, no further canonical-ID promotions remain in Section 7. Subsequent work:

• Each canonical F-067..F-077 can be triaged as actual tickets in the engineering tracker, with evidence pointers from the canonical catalog.
• Maintenance section 11 of FRONTEND_ISSUES.md now reads naturally with all (new) markers cleared \u2014 future audits adding new distinct findings will create the next batch of (new) markers and the cycle continues.
• Future docs-only reconciliation: align F-008 cluster to optionally drop F-011 reference in Severity Counts Low bucket if it's intentionally excluded from the Low cluster Resolution Tracker row (pre-existing minor inconsistency noted by reviewer).

[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 23 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: 1278eb02-0ac8-40e0-bdda-527fa83fc97b

📥 Commits

Reviewing files that changed from the base of the PR and between a9a1a45 and 6b31daa.

📒 Files selected for processing (6)

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