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

[Adiz4415]

Summary

Trim the trailing "(see PR #31)." forward-pointer from a sub-bullet inside the
PR #33 CHANGELOG entry in issues/MASTER_INDEX.md. PR #31 has now closed the
backlog referenced in that line, so the forward-looking pointer is no longer
forward.

Diff scope

One file. One change. One line.

issues/MASTER_INDEX.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Line 67 (PR #33 CHANGELOG sub-bullet)

-- Outstanding (new) items in Section 7 at this snapshot: 9 (legacy #55, #56,
-   #68, #69, #72, #73, #74, #75, #77) proposed for canonical F-067–F-070 /
-   F-072–F-075 / F-077 promotion in a single batched follow-up (see PR #31).
+-  Outstanding (new) items in Section 7 at this snapshot: 9 (legacy #55, #56,
+   #68, #69, #72, #73, #74, #75, #77) proposed for canonical F-067–F-070 /
+   F-072–F-075 / F-077 promotion in a single batched follow-up.

Removed: the trailing " (see PR #31)." — a future-pointer that has now resolved.

What stayed the same

• "Outstanding (new) items" framing preserved as historical record
• All 9 legacy IDs (#55, #56, #68, #69, #72, #73, #74, #75, #77) preserved
• The proposed F-067..F-077 canonical mapping preserved
• All other CHANGELOG entries untouched (5 entries remain in strict reverse-chronological order)
• All counts unchanged (Frontend 68 items, Total 203 etc.)
• No other files touched

Branching

Branched off docs/master-index-changelog-pr28-30 (= PR #33 branch) so the
trim lands cleanly on top of the line it amends, without co-mingling with
PR #34 / PR #35 / PR #36.

Summary by CodeRabbit

• Documentation
  • Restructured known issues documentation across backend, smart contracts, and frontend with improved organization and canonical issue tracking.
  • Added comprehensive issue catalogs with standardized severity levels, resolution tracking, and prioritized remediation guidance.
  • Documented 12 new frontend issues and updated overall issue catalog totals for better visibility into outstanding items.

[coderabbitai]

📝 Walkthrough

Walkthrough

Three PROJECT/issues/ catalog files (BACKEND_ISSUES.md, CONTRACTS_ISSUES.md, FRONTEND_ISSUES.md) are rewritten from simple severity-grouped lists into structured canonical triage catalogs covering 75, 60, and 77 items respectively. Twelve new frontend issues (F-066–F-077) are added to issues/frontend.md. The master index is updated with revised counts and resolution-tracker links, and PROJECT/README.MD is updated accordingly.

Changes

Issue Catalog Consolidation

Layer / File(s)	Summary
New frontend backlog issues F-066–F-077 issues/frontend.md	Adds 12 new entries covering loading/empty state inconsistency, excessive toast delay, missing request() timeout, input validation gaps, icon re-creation on render, router.push vs <Link>, mobile detection misclassification, KYC setTimeout leak, silent username normalization, auto-fill minimum length, and /p2p client-side redirect.
Backend catalog restructure (B-001–B-075) PROJECT/issues/BACKEND_ISSUES.md	Rewrites the file into a 75-item canonical catalog: adds provenance header, summary table, severity counts, per-item triage entries (evidence/impact/fix direction/acceptance check) across Critical/High/Medium/Low sections, a legacy 56-item cross-reference with (moved)/(new) tags, resolution tracker, cross-reference map, top remediations runbook, and maintenance instructions.
Contracts catalog restructure (C-001–C-060) PROJECT/issues/CONTRACTS_ISSUES.md	Rewrites the file into a 60-item canonical catalog with usage instructions, full summary table, per-item triage entries across all severity sections, a legacy 34-item cross-reference, resolution tracker table, cross-reference map, top remediations checklist, maintenance instructions, and related documents list.
Frontend catalog restructure (F-001–F-077) PROJECT/issues/FRONTEND_ISSUES.md	Rewrites the file into a 77-item canonical catalog incorporating the new F-066–F-077 entries; adds usage instructions, summary table, per-item triage entries, a legacy 77-item cross-reference preserving prior ordering with (moved)/(new) tags, resolution tracker, cross-reference map, top remediations runbook, and maintenance instructions dated June 2026.
Master index and README update issues/MASTER_INDEX.md, PROJECT/README.MD	Updates frontend item count to 68 (total 203), replaces the deduping section with a catalog-sources description, rewrites the Top 20 list with #resolution-tracker-fix-status anchor links, adds a reverse-chronological CHANGELOG section, and updates PROJECT/README.MD Known Issues with nested catalog-consolidation bullets and a June 20, 2026 date.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

🐰 Hop, hop — the catalog's neat,
Each B, C, and F gets a triage seat!
Severity counted, legacy mapped,
Ship-blockers flagged, no issue unwrapped.
The master index now links to the tracker,
No bunny leaves bugs in the dark any blacker! 🌟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the specific change: removing a forward-pointer parenthetical from a CHANGELOG entry in the master index file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

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

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (2)

PROJECT/issues/BACKEND_ISSUES.md (1)

1-108: ⚖️ Poor tradeoff

Summary Table ordering inconsistency with stated rule.

Like the frontend catalog, the backend Summary Table (lines 18–95) lists items in strict ID order (B-001..B-075) rather than grouping by severity first, then ID — contradicting the stated rule on lines 7–8: "Items are ordered by severity (Critical → Low), then by ID."

For consistency with the stated rule, the table should be re-sorted: Critical (B-005–B-006), then High, then Medium, then Low — with IDs ascending within each band. Alternatively, clarify that the Summary Table uses ID order while the detailed sections use severity order.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@PROJECT/issues/BACKEND_ISSUES.md` around lines 1 - 108, The Summary Table
lists items in strict ID order (B-001 through B-075) but the documented rule
states items should be ordered by severity first (Critical, then High, then
Medium, then Low) and then by ID within each severity band. Re-sort the Summary
Table so that Critical items appear first (B-005, B-006), followed by High items
(B-001 through B-004, B-007 through B-011, etc.), then Medium items, then Low
items, with IDs ascending within each severity group to align the Summary Table
with the stated ordering rule documented in the "How to use" section.

PROJECT/issues/FRONTEND_ISSUES.md (1)

14-98: ⚖️ Poor tradeoff

Summary Table violates stated ordering rule.

Line 8 says items are "ordered by severity (Critical → Low), then by ID for stable cross-referencing," but the Summary Table (lines 18–97) interleaves new issues (F-066, F-071, F-076, F-067–F-077) within the severity bands rather than grouping them at the end by ID sequence.

For example, within the Medium band, you have F-007, F-009, ..., F-064, then F-066, F-067, F-068, then F-071, then F-074. This breaks the "then by ID" rule.

Recommend re-sorting the Summary Table so that within each severity, IDs ascend monotonically: Critical (F-001–F-005), High (F-006, F-010, ..., F-076), Medium (F-007, F-009, ..., F-074), Low (F-008, F-011, ..., F-077).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@PROJECT/issues/FRONTEND_ISSUES.md` around lines 14 - 98, The Summary Table
violates the stated ordering rule by interleaving issue IDs within severity
bands rather than maintaining monotonic ascending ID order within each severity
group. Re-sort all rows in the Summary Table to group by severity (Critical,
High, Medium, Low) and then arrange IDs in ascending numerical order within each
severity band. For example, ensure all Critical issues (F-001 through F-005)
appear consecutively, then all High issues in ID order (F-006, F-010, F-014,
F-015, F-018, F-019, F-020, F-021, F-022, F-023, F-025, F-027, F-051, F-063,
F-076), then all Medium issues in ID order, then all Low issues in ID order.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@issues/MASTER_INDEX.md`:
- Line 6: The MASTER_INDEX.md file contains multiple outdated references to the
frontend item count. Update the file to reflect the correct count of 77 frontend
items with range F-001..F-077 instead of 68 items with range F-001..F-076.
Specifically, find and update all instances: the "68 items" reference at the
frontend line count, update the total item count from 203 to 211, correct the
range notation from F-001..F-076 to F-001..F-077 wherever it appears in the
frontend section headers and inventory, and update the severity breakdown from
"5 / 15 / 25 / 23 = 68" to "5 / 15 / 28 / 29 = 77" to match the canonical
catalog in FRONTEND_ISSUES.md.

In `@PROJECT/issues/FRONTEND_ISSUES.md`:
- Around line 102-110: The total count in the Severity Counts table is
incorrect. The sum of all severity categories (Critical: 5 + High: 15 + Medium:
28 + Low: 29) equals 77, but the Total row shows 65. Update the Total field in
the Severity Counts table to reflect the correct sum of 77.

In `@PROJECT/README.MD`:
- Around line 53-57: The Frontend entry count in the Catalog consolidations
section of the README.md contains a mismatch between the total canonical entries
count and the severity distribution. Update the Frontend issues line (starting
with [`issues/FRONTEND_ISSUES.md`]) to correct the count from 68 canonical
entries (F-001..F-076) to 77 canonical entries (F-001..F-077) and update the
severity distribution from 5 🔴 Critical / 15 🟠 High / 25 🟡 Medium / 23 🟢 Low
to 5 🔴 Critical / 15 🟠 High / 28 🟡 Medium / 29 🟢 Low to ensure the counts
match across all severity levels.

---

Nitpick comments:
In `@PROJECT/issues/BACKEND_ISSUES.md`:
- Around line 1-108: The Summary Table lists items in strict ID order (B-001
through B-075) but the documented rule states items should be ordered by
severity first (Critical, then High, then Medium, then Low) and then by ID
within each severity band. Re-sort the Summary Table so that Critical items
appear first (B-005, B-006), followed by High items (B-001 through B-004, B-007
through B-011, etc.), then Medium items, then Low items, with IDs ascending
within each severity group to align the Summary Table with the stated ordering
rule documented in the "How to use" section.

In `@PROJECT/issues/FRONTEND_ISSUES.md`:
- Around line 14-98: The Summary Table violates the stated ordering rule by
interleaving issue IDs within severity bands rather than maintaining monotonic
ascending ID order within each severity group. Re-sort all rows in the Summary
Table to group by severity (Critical, High, Medium, Low) and then arrange IDs in
ascending numerical order within each severity band. For example, ensure all
Critical issues (F-001 through F-005) appear consecutively, then all High issues
in ID order (F-006, F-010, F-014, F-015, F-018, F-019, F-020, F-021, F-022,
F-023, F-025, F-027, F-051, F-063, F-076), then all Medium issues in ID order,
then all Low issues in ID order.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3d9f1ddb-e32c-4b8a-8ebb-8c8b74fe3ab1

📥 Commits

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

📒 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

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify frontend catalog actual item counts by inspecting both files

echo "=== Checking /issues/frontend.md ==="
if [ -f "issues/frontend.md" ]; then
  # Count lines matching canonical ID patterns (F-XXX)
  rg -E '^\*\*F-[0-9]{3}\*\*' issues/frontend.md | wc -l
else
  echo "File not found: issues/frontend.md"
fi

echo ""
echo "=== Checking PROJECT/issues/FRONTEND_ISSUES.md ==="
if [ -f "PROJECT/issues/FRONTEND_ISSUES.md" ]; then
  # Count lines matching canonical ID patterns and extract range claims
  rg -E '^\| F-[0-9]{3}' PROJECT/issues/FRONTEND_ISSUES.md | wc -l
  echo ""
  echo "Range claims in FRONTEND_ISSUES.md:"
  rg -n 'F-001.*F-0[0-9]{2}' PROJECT/issues/FRONTEND_ISSUES.md -m 1
  rg -n 'total.*catalog' PROJECT/issues/FRONTEND_ISSUES.md -i
else
  echo "File not found: PROJECT/issues/FRONTEND_ISSUES.md"
fi

Repository: Pi-Defi-world/ACBU-DOCUMENTATION

Length of output: 657

---

🏁 Script executed:

# Check MASTER_INDEX.md content at the referenced lines
echo "=== Lines 1-30 of MASTER_INDEX.md ==="
head -30 issues/MASTER_INDEX.md | cat -n

echo ""
echo "=== Lines 60-73 of MASTER_INDEX.md (CHANGELOG section) ==="
sed -n '60,73p' issues/MASTER_INDEX.md | cat -n

Repository: Pi-Defi-world/ACBU-DOCUMENTATION

Length of output: 8864

---

Frontend item count in MASTER_INDEX.md is out of sync with the canonical catalog.

MASTER_INDEX.md claims 68 frontend items (range F-001..F-076), but PROJECT/issues/FRONTEND_ISSUES.md explicitly documents 77 total items (F-001..F-077) with severity breakdown 5 Critical / 15 High / 28 Medium / 29 Low (totaling 77, not 68). This requires updates at:

• Line 6: "68 items" → 77
• Line 9: "Total: 203" → 211 (75 + 60 + 77)
• Line 21: "68 items (F-001..F-076)" → 77 items (F-001..F-077)
• Line 26: "68 canonical entries (F-001..F-076)" → 77 items (F-001..F-077)
• Line 65: "5 / 15 / 25 / 23 = 68" → 5 / 15 / 28 / 29 = 77

The range F-001..F-076 is mathematically inconsistent with 68 items (that range contains only 76 items); the correct range for 77 items is F-001..F-077. Per the CHANGELOG, nine outstanding items in Section 7 have been promoted to canonical status but the master index header and catalog inventory remain at the prior state.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@issues/MASTER_INDEX.md` at line 6, The MASTER_INDEX.md file contains multiple
outdated references to the frontend item count. Update the file to reflect the
correct count of 77 frontend items with range F-001..F-077 instead of 68 items
with range F-001..F-076. Specifically, find and update all instances: the "68
items" reference at the frontend line count, update the total item count from
203 to 211, correct the range notation from F-001..F-076 to F-001..F-077
wherever it appears in the frontend section headers and inventory, and update
the severity breakdown from "5 / 15 / 25 / 23 = 68" to "5 / 15 / 28 / 29 = 77"
to match the canonical catalog in FRONTEND_ISSUES.md.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Math error in Severity Counts table.

Line 110 lists the total as **65**, but the header (line 98) and the breakdown (5 + 15 + 28 + 29) both sum to 77. This is likely a copy-paste error from an older version with fewer items.

🔢 Proposed fix

 | **Total** | **65** |
+| **Total** | **77** |

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@PROJECT/issues/FRONTEND_ISSUES.md` around lines 102 - 110, The total count in
the Severity Counts table is incorrect. The sum of all severity categories
(Critical: 5 + High: 15 + Medium: 28 + Low: 29) equals 77, but the Total row
shows 65. Update the Total field in the Severity Counts table to reflect the
correct sum of 77.

[coderabbitai]

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Frontend entry in "Catalog consolidations" carries the same count mismatch as MASTER_INDEX.

Line 57 lists: 68 canonical entries (F-001..F-076); 5 🔴 Critical / 15 🟠 High / 25 🟡 Medium / 23 🟢 Low

This mirrors the discrepancy noted in MASTER_INDEX.md. Once the source count is resolved (should be 77 items, F-001..F-077, with severities 5/15/28/29), this line must be updated to match.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@PROJECT/README.MD` around lines 53 - 57, The Frontend entry count in the
Catalog consolidations section of the README.md contains a mismatch between the
total canonical entries count and the severity distribution. Update the Frontend
issues line (starting with [`issues/FRONTEND_ISSUES.md`]) to correct the count
from 68 canonical entries (F-001..F-076) to 77 canonical entries (F-001..F-077)
and update the severity distribution from 5 🔴 Critical / 15 🟠 High / 25 🟡
Medium / 23 🟢 Low to 5 🔴 Critical / 15 🟠 High / 28 🟡 Medium / 29 🟢 Low to
ensure the counts match across all severity levels.