docs(index): add CHANGELOG entry for PR #31 (F-067..F-077 batch) + totals 77/212 by Adiz4415 · Pull Request #34 · Pi-Defi-world/ACBU-DOCUMENTATION

Adiz4415 · 2026-06-20T14:23:54Z

Summary

Refresh of issues/MASTER_INDEX.md that closes the documentation loop on the canonical-ID follow-up series once PR #31 (the F-067..F-077 batch) merges. Updates the master index to reflect the post-#31 catalog state (frontend 68 \u2192 77 items, total 203 \u2192 212 items, distribution 5/15/25/23=68 \u2192 5/15/28/29=77, F-001..F-076 \u2192 F-001..F-077) and adds a second CHANGELOG entry documenting the batch migration that landed in PR #31.

Follows PR #33 (docs/master-index-changelog-pr28-30), which itself followed the four canonical-ID follow-ups PRs #28 #29 #30 #31. Total four-PR canonical-ID migration series: PRs #28 (F-066 Skeleton primitive, Medium), #29 (F-071 Toast removal delay, Medium), #30 (F-076 Frontend request() no default timeout, High), #31 (F-067..F-077 batch: 3 Medium + 6 Low).

What changed

`issues/MASTER_INDEX.md`

Intro line: Frontend (acbu-frontend): 68 \u2192 77 items; Total: 203 \u2192 212 items.
Catalog sources & deduping live line: [frontend.md](./frontend.md) \u2014 68 items (F-001..F-076) \u2192 77 items (F-001..F-077).
Catalog sources & deduping durable-long-form line (PROJECT/issues/FRONTEND_ISSUES.md):
- Expanded to all 77 canonical entries (F-001..F-077).
- Severity distribution 5 \ud83d\udd34 Critical / 15 \ud83d\udfe0 High / 28 \ud83d\udfe1 Medium / 29 \ud83d\udfe2 Low = 77.
- Citations: kept PR #25 (initial consolidation) + PR #28 (F-066 Skeleton, Medium) + PR #29 (F-071 Toast delay, Medium) + PR #30 (F-076 request() timeout, High) and now added PR #31 (F-067..F-077 batch: 3 Medium + 6 Low).
Top 20 (ship-safety order) intentionally unchanged \u2014 the F-067..F-077 batch added 3 Medium + 6 Low entries; none would rank above the existing Critical / High entries already on the ship-safety list. Re-sorting for marginal gain was not worth the churn.
CHANGELOG \u2014 single new entry at TOP titled 2026-06 \u2014 F-067..F-077 batch canonical-ID migration ([PR #31](https://github.com/Pi-Defi-world/ACBU-DOCUMENTATION/pull/31)) with three sub-bullets:
- 3 promoted to \ud83d\udfe1 Medium (data-validation / privacy): F-067 (Contact inputs no maxLength, frontend/forms), F-068 (Profile inputs no maxLength/format validation, frontend/forms), F-074 (Silent username normalization on signup, frontend/auth).
- 6 promoted to \ud83d\udfe2 Low (perf / nav-pattern / hygiene): F-069 (Icons recreated each render, frontend/perf), F-070 (Menu items use router.push instead of Link, frontend/nav), F-072 (Mobile detection treats "unknown" as desktop, frontend/compat), F-073 (Post-KYC upload uncleaned setTimeout, frontend/hygiene), F-075 (Auto-fill heuristic requires length \u2265 56, frontend/ux), F-077 (/p2p client-side redirect only, frontend/nav).
- Severity distribution bumped 5 / 15 / 25 / 23 = 68 (post-docs(frontend): promote canonical ID F-066 (Shared Skeleton primitive) #28..docs(frontend): promote canonical ID F-076 (Frontend request() no timeout) #30) \u2192 5 / 15 / 28 / 29 = 77 \u2014 completing the (new) Section 7 backlog for PROJECT/issues/FRONTEND_ISSUES.md.
- Top 20 ship-safety list intentionally unchanged (Medium/Low additions don't promote into the Critical/High ranking).
- All 12 Section 7 (new) markers are now adopted into canonical IDs F-066..F-077 \u2014 the _proposed_ backlog is now zero. Future audit findings will create fresh (new) rows for the next canonical-ID promotion cycle.

The previous CHANGELOG entries (PR #31 entry is now top; PR #28..#30 entry from PR #33 at position 2; PR #25 / PR #24 / PR #23 / PR #22 unchanged below) are preserved as historical anchors without modification.

Verification

Arithmetic: 5 + 15 + 28 + 29 = 77 verified; 77 + 75 (Backend) + 60 (Contracts) = 212 verified.
Top 20 still has exactly 20 numbered items, all with …#resolution-tracker-fix-status pointer (untouched in this PR).
CHANGELOG in strict reverse-chronological order: PR docs(frontend): batch canonical IDs F-067..F-077 (Section 7 remaining) #31 entry at top, PR docs(frontend): promote canonical ID F-066 (Shared Skeleton primitive) #28..docs(frontend): promote canonical ID F-076 (Frontend request() no timeout) #30 entry at position 2 (from PR docs(index): add CHANGELOG entry for PRs #28..#30 + Top 20 reorder for F-076 #33), PR docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25 / docs(index): add CHANGELOG + per-item Top-20 tracker pointers #24 / docs(backend): consolidate BACKEND_ISSUES.md catalog #23 / docs(contracts): consolidate CONTRACTS_ISSUES.md to close #12 #22 entries below.
Only real PR numbers cited (docs(contracts): consolidate CONTRACTS_ISSUES.md to close #12 #22, docs(backend): consolidate BACKEND_ISSUES.md catalog #23, docs(index): add CHANGELOG + per-item Top-20 tracker pointers #24, docs(frontend): consolidate FRONTEND_ISSUES.md catalog #25, 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, docs(frontend): batch canonical IDs F-067..F-077 (Section 7 remaining) #31) \u2014 no fabricated IDs.
No broken markdown links; canonical anchors use #resolution-tracker-fix-status slug.

Scope

This PR covers only the post-docs(frontend): batch canonical IDs F-067..F-077 (Section 7 remaining) #31 follow-up refresh of MASTER_INDEX.md. It does NOT itself add canonical IDs (that was completed by PR docs(frontend): batch canonical IDs F-067..F-077 (Section 7 remaining) #31) or alter the catalog files.
It does NOT change the Top 20 ship-safety list (Medium/Low additions in docs(frontend): batch canonical IDs F-067..F-077 (Section 7 remaining) #31 don't promote into ship-safety order, and arbitrary re-sort would reduce clarity for marginal gain). If a future maintainer wants F-067..F-077 cluster introduced into the Top 20, that would be a separate top-20 reorder PR.
Two known non-blocking follow-ups preserved from prior PR reviews: (a) FRONTEND_ISSUES.md Summary Table row-order issue (Lows interleaving with Mediums) \u2014 reviewer's Issue A on PR docs(frontend): batch canonical IDs F-067..F-077 (Section 7 remaining) #31 \u2014 (b) F-075 / F-041 cross-cut note \u2014 reviewer's Issue B on PR docs(frontend): batch canonical IDs F-067..F-077 (Section 7 remaining) #31. Both are documentation-only batchable items; neither is a blocker for this PR.

Follow-up after #31 + this PR

The four-PR canonical-ID migration series and its two master-index refresh PRs (#33 and this one) now constitute a complete documentation trail. With PR #31 + this PR merged, no further canonical-ID promotions are pending \u2014 the next audit cycle will produce fresh (new) rows in Section 7.

…catalog - Restructure PROJECT/issues/CONTRACTS_ISSUES.md into a single source of truth using canonical severity/area/evidence/impact/fix/acceptance format. - Cover all 60 catalog entries from issues/contracts.md (Critical 6, High 21, Medium 24, Low 9) with stable C-### IDs. - Preserve the legacy 34-item list as Section 7 cross-reference. - Add Summary Table, Severity Counts, Resolution Tracker, Top Remediations (ship-safety order), Cross-Reference Map, and Maintenance notes. - Provide anchor points for future PR references. Closes Pi-Defi-world#12

- Catalog sources & deduping section renames the prior Deduping section and explicitly elevates PROJECT/issues/CONTRACTS_ISSUES.md (PR Pi-Defi-world#22) and PROJECT/issues/BACKEND_ISSUES.md (PR Pi-Defi-world#23) to durable long-form references; FRONTEND_ISSUES.md remains legacy pending follow-up PR. - Top 20 list gains per-item deep links to the Resolution Tracker (Section 8) of each consolidated catalog and uniformly bolds IDs. - New CHANGELOG section appended in strict reverse-chronological order (this PR refresh first, then PR Pi-Defi-world#23 backend, then PR Pi-Defi-world#22 contracts, then future frontend consolidation).

…d 11 per-item tracker pointers - Catalog sources & deduping elevates PROJECT/issues/FRONTEND_ISSUES.md to durable long-form reference (was legacy/\u2018pending follow-up\u2019), cited to PR Pi-Defi-world#25. - Top 20 list gains per-item tracker pointers for the 11 user-listed frontend items: F-001/F-002/F-005 (Critical, wallet+auth) and F-014/F-015/F-019/F-020/F-022/F-025/F-051/F-063 (top-High ship-safety), mirroring the contracts/backend pointer pattern. - CHANGELOG now in reverse-chronological order with Frontend PR Pi-Defi-world#25 at top; Master Index Refresh entry cites PR Pi-Defi-world#25 directly; legacy\n \u2018_(Future) Frontend_\u2019 placeholder retired. - F-004 (item 20) remains Critical in Top 20 without a per-item pointer\n by design \u2014 not in user\u2019s explicit 11-set; CHANGELOG documents this so\n it is addressable in a follow-up PR.

…E.MD - New nested 'Catalog consolidations' block under Project Management subsection listing PROJECT/issues/CONTRACTS_ISSUES.md (PR Pi-Defi-world#22), PROJECT/issues/BACKEND_ISSUES.md (PR Pi-Defi-world#23), and PROJECT/issues/FRONTEND_ISSUES.md (PR Pi-Defi-world#25) as durable long-form references with canonical-entry counts and severity distributions. - Corrected the adjacent pre-existing 'Known issues' line link paths from bare filenames to the working 'issues/...' form so the whole block is discoverable. - Bumped footer 'Last Updated:' from 2026-01-26 to 2026-06-20 to match the June catalog-consolidation PR envelope.

- Add F-066 \u2014 "Inconsistent loading / empty state skeletons across pages" (Medium, frontend/components) to issues/frontend.md and the Summary Table / Severity Counts / Resolution Tracker / Severity 5 block of PROJECT/issues/FRONTEND_ISSUES.md. - Migrate legacy Section 7 item #49 ("Empty and loading states inconsistent \u2014 missing Skeleton primitive") from "new \u2014 propose F-066" to "new \u2192 adopted as F-066", preserving the legacy #49 anchor for traceability. - Severity distribution bumped from 5/14/23/23=65 \u2192 5/14/24/23=66. Summary Table totals line, Severity Counts row, and Resolution Tracker Medium cluster row all reconciled to (24 Medium). - Cross-references: F-066 evidence path covers per-page loading.tsx / empty.tsx under app/(app)/**.

- Add F-071 \u2014 "Toast removal delay is ~17 minutes" (Medium, frontend/ux) to issues/frontend.md and the Summary Table / Severity Counts / Resolution Tracker / Severity 5 block of PROJECT/issues/FRONTEND_ISSUES.md. - Migrate legacy Section 7 item #71 ("Toast removal delay is ~17 minutes; TOAST_REMOVE_DELAY = 1000000") from "new \u2014 propose F-071" to "new \u2192 adopted as F-071", preserving the legacy #71 anchor for traceability. - Severity distribution bumped from 5/14/24/23=66 \u2192 5/14/25/23=67. Summary Table totals line, Severity Counts row, and Resolution Tracker Medium cluster row all reconciled to (25 Medium). - Cross-references: F-071 evidence points at acbu-frontend/lib/toast.ts TOAST_REMOVE_DELAY constant. - Build context: this PR builds on fix/frontend-canonical-id-f066 (PR Pi-Defi-world#28, the F-066 migration) which is now part of the branch base.

…eout) - Add F-076 \u2014 "Frontend request() helper has no default timeout" (High, frontend/api) to issues/frontend.md and the Summary Table / Severity Counts / Resolution Tracker / Severity 4 block of PROJECT/issues/FRONTEND_ISSUES.md. - Migrate legacy Section 7 item #76 ("API fetch has no timeout; Frontend request() uses fetch with no default timeout") from "new \u2014 propose F-076" to "new \u2192 adopted as F-076", preserving the legacy #76 anchor for traceability. - Severity distribution bumped from 5/14/25/23=67 \u2192 5/15/25/23=68. Summary Table totals line, Severity Counts High row, and Resolution Tracker High cluster row all reconciled to (15 High). - Cross-references: F-076 evidence points at acbu-frontend/lib/api/client.ts request() function. - Build context: this PR builds on fix/frontend-canonical-id-f071 (PR Pi-Defi-world#29, the F-071 migration) which is on top of fix/frontend-canonical-id-f066 (PR Pi-Defi-world#28). Both prior PRs are part of the branch base.

- Add F-067..F-077 to issues/frontend.md in the canonical severity/area/evidence/impact/fix/acceptance format. - Mirror into PROJECT/issues/FRONTEND_ISSUES.md Summary Table, Severity Counts (Medium 25\u219228, Low 23\u219229), Resolution Tracker Medium/Low cluster rows, Section 5 Medium (3 detailed entries), Section 6 Low (6 detailed entries), and totals 68\u219277. - Migrate legacy Section 7 markers #55, #56, #68, #69, #72, #73, #74, #75, #77 from "new \u2014 propose F-XXX" to "new \u2192 adopted as F-XXX". - Final distribution: 5 Critical / 15 High / 28 Medium / 29 Low = 77. - Severity rationale: F-067/F-068/F-074 \u2192 Medium (data validation, silent-normalization privacy concern); F-069/F-070/F-072/F-073/F-075/ F-077 \u2192 Low (perf / nav-pattern / hygiene, fail-open where appropriate). - Branch builds on fix/frontend-canonical-id-f066, f071, f076 (PRs Pi-Defi-world#28, Pi-Defi-world#29, Pi-Defi-world#30) \u2014 sequential stack so each layer merges cleanly.

…F-071/F-076 follow-ups - Refresh the FRONTEND_ISSUES.md line under 'Catalog consolidations' to reflect the new distribution 5 Critical / 15 High / 25 Medium / 23 Low = 68 canonical entries (F-001..F-076), up from the post-PR Pi-Defi-world#25 distribution of 65 entries. - Add explicit follow-up PR links (Pi-Defi-world#28 F-066 Skeleton primitive, Pi-Defi-world#29 F-071 Toast-deletion delay, Pi-Defi-world#30 F-076 Frontend request() no default timeout) so contributors can navigate from the README to the canonical-ID-migration PRs without grepping CHANGELOGs. - Per the user's explicit scope: this PR captures PRs Pi-Defi-world#28..Pi-Defi-world#30 only; PR Pi-Defi-world#31 (F-067..F-077 batch) is a separate follow-up if the consolidated totals should advance further.

…rld#30 + Top 20 reorder for F-076 - Append a single '2026-06 \u2014 F-066/F-071/F-076 follow-up canonical-ID migrations (PRs Pi-Defi-world#28\u201330)' CHANGELOG entry at the top of the index, in the same strict reverse-chronological position used by prior entries. The new entry cites [PR Pi-Defi-world#28](F-066), [PR Pi-Defi-world#29](F-071), and [PR Pi-Defi-world#30](F-076) with their respective legacy-to-canonical migrations, severity transitions (frontend 5/14/23/23=65 \u2192 5/15/25/23=68), and explicit pointer to the Top-20 ship-safety reorder for F-076. - Refresh the master index intro line: `Frontend (acbu-frontend)` 65 \u2192 68 items; `Total` 200 \u2192 203. - Refresh Catalog sources & deduping FRONTEND_ISSUES.md bullet to cite PRs Pi-Defi-world#28/Pi-Defi-world#29/Pi-Defi-world#30 alongside the original PR Pi-Defi-world#25, distribution 5 / 15 / 25 / 23, and canonical-ID range F-001..F-076. - Top 20 ship-safety list reordered: F-076 inserted into the High frontend cluster between F-063 and F-020 (the new network-safety item with full per-item tracker pointer); F-004 dropped from the closing slot (previously lacked a per-item pointer). All 20 entries now have an `…#resolution-tracker-fix-status` pointer. - Note: this PR covers PRs Pi-Defi-world#28..Pi-Defi-world#30 only. The 9 remaining `(new)` Section 7 items proposed for F-067..F-077 promotion (#55, #56, #68, #69, #72, #73, #74, #75, #77) are batched separately in PR Pi-Defi-world#31; a subsequent master index CHANGELOG entry can be added when PR Pi-Defi-world#31 merges.

…7 batch) + totals - Bump Frontend (`acbu-frontend`) intro line 68 \u2192 77 items. - Bump Total intro line 203 \u2192 212 items. - Refresh Catalog sources & deduping FRONTEND_ISSUES.md bullet: * canonical range F-001..F-076 \u2192 F-001..F-077 * severity distribution 5/15/25/23=68 \u2192 5/15/28/29=77 * add [PR Pi-Defi-world#31](Pi-Defi-world#31) citation alongside Pi-Defi-world#25, Pi-Defi-world#28, Pi-Defi-world#29, Pi-Defi-world#30 - Refresh Catalog sources frontend.md live line: 68 \u2192 77 items. - Append a single new CHANGELOG entry at the very top documenting the F-067..F-077 batch (PR Pi-Defi-world#31): 3 Medium (F-067/F-068/F-074) + 6 Low (F-069/F-070/F-072/F-073/F-075/F-077), severity transition 68 \u2192 77, explicit note that Top 20 ship-safety list was intentionally unchanged (Medium/Low additions don't improve the Critical/High ranking), and confirmation that all 12 Section 7 `(new)` markers are now closed. - Branch builds on docs/master-index-changelog-pr28-30 (PR Pi-Defi-world#33) so the four-PR canonical-ID follow-up series lands as a clean stack: Pi-Defi-world#28 (F-066) \u2192 Pi-Defi-world#29 (F-071) \u2192 Pi-Defi-world#30 (F-076) \u2192 Pi-Defi-world#31 (F-067..F-077 batch), with this PR Pi-Defi-world#34 (master index refresh) closing the loop.

coderabbitai · 2026-06-20T14:24:02Z

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 17 minutes and 55 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: 0fdf5f09-6bfa-4794-bc48-964191e730c6

📥 Commits

Reviewing files that changed from the base of the PR and between a9a1a45 and 553fc24.

📒 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

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

Adiz4415 added 13 commits June 20, 2026 12:25

docs(backend): consolidate BACKEND_ISSUES.md catalog

6583ac6

docs(frontend): consolidate FRONTEND_ISSUES.md catalog

4835439

This was referenced Jun 20, 2026

docs(frontend): add F-075/F-041 cross-cut parenthetical to canonical row (addresses PR #31 Reviewer Issue B) #35

Open

docs(index): trim now-superseded forward-pointer parenthetical from PR #33 CHANGELOG entry #37

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs(index): add CHANGELOG entry for PR #31 (F-067..F-077 batch) + totals 77/212#34

docs(index): add CHANGELOG entry for PR #31 (F-067..F-077 batch) + totals 77/212#34
Adiz4415 wants to merge 13 commits into
Pi-Defi-world:mainfrom
Adiz4415:docs/master-index-changelog-pr31

Adiz4415 commented Jun 20, 2026

Uh oh!

coderabbitai Bot commented Jun 20, 2026

Review limit reached

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

Adiz4415 commented Jun 20, 2026

Summary

What changed

issues/MASTER_INDEX.md

Verification

Scope

Follow-up after #31 + this PR

Uh oh!

coderabbitai Bot commented Jun 20, 2026

Review limit reached

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

`issues/MASTER_INDEX.md`