Re-packaged all indomptency issues and aligned new Vite build with co…

[Sadeequ]

Change Report

Issue 1: Proxy Upgrade Timelock

I added request_implementation_upgrade in lib.rs. It requires admin authorization, records the proposed implementation and a 24-hour unlock time in storage dedicated to implementation swaps, and emits a request event.

I changed upgrade to require a matching pending proposal and an expired timelock before swapping. After a successful swap, I clear the pending implementation and unlock time. I also updated the deployment comment to describe the schedule-then-execute flow.

Issue 2: Atomic Batch Rollback

I changed execute_batch_with_retry in lib.rs so that abort_on_failure = true panics as soon as an operation exhausts its retries. That aborts the Soroban invocation, reverting earlier successful operations and the nonce instead of returning a partial result and merely skipping later calls.

I updated the related test in test.rs to run a successful state-changing operation before a failing one, then assert that both its state change and the nonce were rolled back. I also removed duplicate test imports that were already present in that file.

Issue 3: Isolated Dashboard Errors

I added a compact fallback mode to GlobalErrorBoundary.tsx and wrapped the active dashboard view in it from App.tsx. A section render failure now displays a local alert instead of replacing the whole application shell.

I added GlobalErrorBoundary.test.tsx to verify that the fallback appears while sibling navigation remains rendered.

Issue 4: Dashboard Code Splitting

I replaced the inline placeholder overview, transaction history, and SEP-24 sections with lazy imports of the existing page components in App.tsx. I wrapped the active view in Suspense with a loading fallback. The production Vite build emitted separate DashboardOverview, TransactionHistory, and SEP24Flow chunks.

Related Issues

• CLOSES [Soroban/Proxy] Enforce Mandated Upgrade Delay Timelock on Implementation Swaps #1167
• CLOSES [Soroban/Batch] Implement Atomic Execution Rollback for Multi-Operation Batches #1171
• CLOSES [Dashboard/Errors] Implement React Error Boundaries for Isolated Widget Failures #1232
• CLOSES [Dashboard/Performance] Optimize Bundle Size using React Code Splitting & Lazy Loading #1235

[drips-wave]

@Sadeequ Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[Ceejaytech25]

Nice implementation, LGTM! 🚀 Great work on this contribution — the approach is clean and well thought out. Thanks for contributing to AnchorPoint!