fix: reload status on undelegation

[GabrielePicco]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
binary-prediction-demo	Ready	Preview, Comment	Jul 22, 2026 10:41am
counter-session-keys	Ready	Preview, Comment	Jul 22, 2026 10:41am
er-rolldice	Ready	Preview, Comment	Jul 22, 2026 10:41am
magicblock-counter-example	Ready	Preview, Comment	Jul 22, 2026 10:41am
magicblock-engine-examples	Ready	Preview, Comment	Jul 22, 2026 10:41am
magicblock-rewards-dashboard	Ready	Preview, Comment	Jul 22, 2026 10:41am
rps-example	Ready	Preview, Comment	Jul 22, 2026 10:41am
spl-tokens	Ready	Preview, Comment	Jul 22, 2026 10:41am

[coderabbitai]

Warning

Review limit reached

@GabrielePicco, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 10 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 236ca78e-c844-4dc7-b125-23bbdcf70516

📥 Commits

Reviewing files that changed from the base of the PR and between 5463533 and 3dda60e.

⛔ Files ignored due to path filters (1)

• roll-dice/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• roll-dice/anchor/app/app/delegated/page.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/delegated-status-check

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3dda60e893

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove the stale root npm lockfile

This new lockfile lives at roll-dice/package-lock.json, but there is no matching roll-dice/package.json; the actual roll-dice manifests use Yarn under roll-dice/anchor and roll-dice/anchor/app. In environments that scan lockfiles for dependency state, this phantom npm project now records Next 15.1.0 and the lock itself marks that version as deprecated for a security vulnerability, so the repo can report a vulnerable dependency that the example does not actually use. Please drop the misplaced lockfile or regenerate it beside the package.json it belongs to.

Useful? React with 👍 / 👎.