Skip to content

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

Open
Adiz4415 wants to merge 14 commits into
Pi-Defi-world:mainfrom
Adiz4415:docs/project-readme-merge-ladder-pr35-37
Open

docs(project): add Order of Merge Ladder meta-entry for PR #35-#37 in PROJECT/README.MD#38
Adiz4415 wants to merge 14 commits into
Pi-Defi-world:mainfrom
Adiz4415:docs/project-readme-merge-ladder-pr35-37

Conversation

@Adiz4415

@Adiz4415 Adiz4415 commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Add an "Order of Merge Ladder" meta-entry to PROJECT/README.MD documenting the
chain freshness order for the three post-#31 canonical-ID follow-up PRs
(#35, #36, #37).

This is a documentation-only entry. No code changes. No count changes.

Diff scope

Single file. Single change. One new sub-bullet appended.

PROJECT/README.MD | 1 +
1 file changed, 1 insertion(+), 0 deletions(-)

What the new sub-bullet explicitly clarifies

Point Reason
PR #35 and PR #36 are siblings Both branch off fix/frontend-canonical-id-batch-67-77 (= PR #31); mergeable in either order
PR #37 has a different parent Branches off docs/master-index-changelog-pr28-30 (= PR #33)
Order is a sequencing convention Driven by chain-tip freshness, not by merge-conflict avoidance
Disjoint-lines enumeration PR #35 edits F-075 Evidence; PR #36 edits Summary Table; PR #37 edits PR #33 CHANGELOG sub-bullet — no edit overlap
All three are documentation-only No tests, no typecheck required

What stayed the same

  • Last Updated footer preserved (June 20, 2026)
  • Existing three catalog sub-bullets (CONTRACTS_ISSUES, BACKEND_ISSUES, FRONTEND_ISSUES) byte-identical
  • No files outside PROJECT/README.MD touched
  • No arithmetic or count changes

Branching

Branched off docs/master-index-changelog-pr33-trim (= PR #37 branch) so this
entry lands at the chain tip once the three PRs are merged.

Adiz4415 added 14 commits June 20, 2026 12:25
@Adiz4415
[Fix Pi-Defi-world#12] Consolidate ACBU smart contracts known-issues …
23d9bb5 
…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
@Adiz4415
docs(backend): consolidate BACKEND_ISSUES.md catalog
6583ac6
@Adiz4415
docs(index): add CHANGELOG + per-item Top-20 tracker pointers
4b6ff1c 
- 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).
@Adiz4415
docs(frontend): consolidate FRONTEND_ISSUES.md catalog
4835439
@Adiz4415
docs(index): link frontend catalog to merged PR Pi-Defi-world#25 + ad…
ea73164 
…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.
@Adiz4415
docs(project): add Catalog consolidations subsection to PROJECT/READM…
be1333b 
…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.
@Adiz4415
docs(frontend): promote canonical ID F-066 (Shared Skeleton primitive)
d49b4b7 
- 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)/**.
@Adiz4415
docs(frontend): promote canonical ID F-071 (Toast removal delay ~17min)
84f3b15 
- 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.
@Adiz4415
docs(frontend): promote canonical ID F-076 (Frontend request() no tim…
e79d39a 
…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.
@Adiz4415
docs(frontend): promote canonical IDs F-067..F-077 (Section 7 remaining)
6b31daa 
- 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.
@Adiz4415
docs(project): update README Catalog consolidations to reflect F-066/…
2fff377 
…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.
@Adiz4415
docs(index): add CHANGELOG entry for PRs Pi-Defi-world#28..Pi-Defi-wo…
788a811 
…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.
@Adiz4415
docs(index): trim now-superseded forward-looking parenthetical from PR …
3296cf7 
…Pi-Defi-world#33 CHANGELOG entry

PR Pi-Defi-world#33's CHANGELOG entry appended a sub-bullet at the end stating the
9 outstanding Section 7 (new) items, with a trailing "(see PR Pi-Defi-world#31)"
forward-pointer to the batched follow-up that would migrate them. PR
Pi-Defi-world#31 has now closed that backlog, so the forward-pointer is no longer
forward — it reads to a future reader as a vague reference rather
than as historical context.

Trim the trailing "(see PR Pi-Defi-world#31)." tail from that sub-bullet only.
The sub-bullet's content is otherwise preserved verbatim: the
"Outstanding (new) items" framing, the legacy ID list (#55, #56,
#68, #69, #72, #73, #74, #75, #77), and the proposed F-067..F-077
canonical mapping all remain as historical audit trail.

Single file: issues/MASTER_INDEX.md. Single change: removal of one
trailing substring " (see PR Pi-Defi-world#31)." from line 67. No arithmetic /
count changes. No other files touched.

Branched off docs/master-index-changelog-pr28-30 (= PR Pi-Defi-world#33 branch)
so the trim lands cleanly on top of the line it amends.
@Adiz4415
docs(project): add Order of Merge Ladder meta-entry for PRs Pi-Defi-w…
7f6172f 
…orld#35-Pi-Defi-world#37

Add a documentation-only sub-bullet under the existing Catalog
consolidations entry in PROJECT/README.MD documenting the chain
freshness order for the post-Pi-Defi-world#31 canonical-ID follow-ups:

  Pi-Defi-world#35 (F-075 / F-041 cross-cut parenthetical)
  Pi-Defi-world#36 (Summary Table severity-then-ID reorder)
  Pi-Defi-world#37 ((see PR Pi-Defi-world#31) forward-pointer trim in PR Pi-Defi-world#33 CHANGELOG)

The sub-bullet explicitly distinguishes the two distinct technical
relationships in this sequence: PR Pi-Defi-world#35 and PR Pi-Defi-world#36 are siblings
(both branched off fix/frontend-canonical-id-batch-67-77 = PR Pi-Defi-world#31,
mergeable in either order), whereas PR Pi-Defi-world#37 branched off
docs/master-index-changelog-pr28-30 and is independent in branch
topology. The order Pi-Defi-world#35 -> Pi-Defi-world#36 -> Pi-Defi-world#37 is documented as a
sequencing convention (chain-tip freshness), explicit not a
merge-conflict requirement. The disjoint-lines enumeration
(F-075 Evidence / Summary Table / PR Pi-Defi-world#33 CHANGELOG sub-bullet)
makes the lack of conflict obvious to future readers.

Single file: PROJECT/README.MD. Single change: one new sub-bullet
appended to the existing Catalog consolidations sub-bullet.
Existing three catalog sub-bullets (CONTRACTS_ISSUES,
BACKEND_ISSUES, FRONTEND_ISSUES) byte-identical. Last Updated
footer preserved.

Branched off docs/master-index-changelog-pr33-trim (= PR Pi-Defi-world#37
branch) so this entry sits at the chain tip.
@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown

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 49 minutes and 8 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: 2ebc9a7c-091c-444e-ba96-649b897c3dfd

📥 Commits

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Adiz4415