docs(frontend): reorder Summary Table strictly by severity-then-ID (addresses PR #31 Reviewer Issue A) by Adiz4415 · Pull Request #36 · Pi-Defi-world/ACBU-DOCUMENTATION

Adiz4415 · 2026-06-20T14:36:36Z

Summary

Reorder the 12-row Summary Table cluster covering the recent canonical-ID
migrations (F-066 through F-077) strictly by severity-then-ID, addressing
Reviewer Issue A from PR #31.

Previously the cluster was in PR-submission order, which interleaved Low rows
with Medium rows and left F-076 (High) sitting between Medium rows. The new
order groups all rows of the same severity together, sorted by ID ascending
within each group:

Order	Severity	IDs (ascending)
1	🟠 High	F-076
2-6	🟡 Medium	F-066, F-067, F-068, F-071, F-074
7-12	🟢 Low	F-069, F-070, F-072, F-073, F-075, F-077

What changed

Single file: PROJECT/issues/FRONTEND_ISSUES.md
Single change: 12 rows of the Summary Table rearranged.

No content change to any row (severity pill, area, title, dash separators
preserved). No rows added or removed. No arithmetic change.

What stayed the same

Severity Counts remain 5 🔴 / 15 🟠 / 28 🟡 / 29 🟢 = 77 (canonical F-001..F-077)
Resolution Tracker Medium cluster (28 items) and Low cluster (29 items) unchanged
Section 7 (new) markers — already zero after PR docs(frontend): batch canonical IDs F-067..F-077 (Section 7 remaining) #31 merged
Top 20 ship-safety order — unchanged (Medium/Low additions don't promote into Critical/High ranking)
All other files untouched

Branching

Branched off fix/frontend-canonical-id-batch-67-77 (= PR #31) so this
PR stacks cleanly on top of the canonical-ID migration chain:

#28 (F-066 migration) → #29 (F-071 migration) → #30 (F-076 migration)
    → #31 (F-067..F-077 batch) → #35 (F-075/F-041 cross-cut)
        → this PR (Summary Table strict severity-then-ID reorder)

Diff scope

PROJECT/issues/FRONTEND_ISSUES.md  | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)

Each row's content is byte-identical except for vertical position, so
the diff is a permutation of the 12 rows.

…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.

Addresses reviewer Issue A from PR Pi-Defi-world#31: in the 12-row Summary Table cluster covering recent canonical-ID migrations (F-066..F-077), Low rows were interleaved with Medium rows and F-076 (High) sat between Medium rows. Reorder all 12 rows strictly by severity, then by ID: High : F-076 (frontend/api, Frontend request() helper has no default timeout) Medium: F-066, F-067, F-068, F-071, F-074 Low : F-069, F-070, F-072, F-073, F-075, F-077 No row content (severity pill, area, title) is changed — only vertical position. Severity Counts unchanged (5 Critical / 15 High / 28 Medium / 29 Low = 77). All 77 rows preserved. Single file touched: PROJECT/issues/FRONTEND_ISSUES.md. Branched off fix/frontend-canonical-id-batch-67-77 (= PR Pi-Defi-world#31) so this PR stacks cleanly: Pi-Defi-world#28 (F-066) -> Pi-Defi-world#29 (F-071) -> Pi-Defi-world#30 (F-076) -> Pi-Defi-world#31 (F-067..F-077 batch) -> Pi-Defi-world#35 (F-075/F-041 cross-cut) -> this PR (Summary Table reorder).

coderabbitai · 2026-06-20T14:36:44Z

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 5 minutes and 14 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: a93176c5-b03c-416d-a77c-37093dcd8c84

📥 Commits

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

📒 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 11 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(index): trim now-superseded forward-pointer parenthetical from PR #33 CHANGELOG entry #37

Open

docs(project): add Order of Merge Ladder meta-entry for PR #35-#37 in PROJECT/README.MD #38

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs(frontend): reorder Summary Table strictly by severity-then-ID (addresses PR #31 Reviewer Issue A)#36

docs(frontend): reorder Summary Table strictly by severity-then-ID (addresses PR #31 Reviewer Issue A)#36
Adiz4415 wants to merge 11 commits into
Pi-Defi-world:mainfrom
Adiz4415:docs/frontend-summary-table-severity-id-reorder

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

What stayed the same

Branching

Diff scope

Uh oh!

coderabbitai Bot commented Jun 20, 2026

Review limit reached

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant