ux(settings): toast-undo for Reset on override rows (closes #113)

[cristim]

Summary

• After a confirmed Delete on an override row, snapshot all fields (term, payment, coverage, enabled, ramp_schedule, include/exclude arrays) before the API call.
• On success, show a 5-second info toast: "Override for aws/rds deleted." with an Undo button.
• Clicking Undo re-PUTs the snapshot via saveAccountServiceOverride, reloads the panel, and refreshes recommendations -- restoring the row exactly as it was.
• No changes to toast.ts -- actions[] already existed.

Test plan

• settings-accounts.test.ts: "Delete shows info toast with Undo action and clears row (click-Undo path)" -- verifies toast shape, 5s TTL, and saveAccountServiceOverride called with original values on Undo.
• settings-accounts.test.ts: "let-it-expire path: override is permanently gone after toast timeout" -- verifies saveAccountServiceOverride is NOT called when Undo is not clicked.
• npx tsc --noEmit clean.
• Full jest suite: 2144 pass, 0 fail.

[cristim]

@coderabbitai review

[coderabbitai]

Warning

Review limit reached

@cristim, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 62 minutes and 34 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

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

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 16ece946-c380-42ca-b001-492dc7babbfa

📥 Commits

Reviewing files that changed from the base of the PR and between 4956d66 and efe3a61.

📒 Files selected for processing (2)

• frontend/src/__tests__/settings-accounts.test.ts
• frontend/src/settings.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/113-wave11

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[cristim]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[cristim]

pr-iterate: CR appears to be blocked by org-level usage limits (most recent CR comment includes "Your organization has run out of usage credits"; subsequent @coderabbitai full review ping at 2026-05-30T10:22Z produced only a "Review triggered" ack with no substantive review after ~4.5 days). This PR is otherwise merge-ready (mergeStateStatus=CLEAN, all CI checks green). Re-invoke /pr-iterate 834 after the org's CR billing is topped up to get a substantive CR pass. To clear the wave-level marker after billing is fixed: rm ~/.claude/agent-comms/cr-rate-limit-deadline.txt.

[coderabbitai]

@cristim: Acknowledged — triggering a full review now. Apologies for the earlier disruption caused by the usage limit issue.

---

🧠 Learnings used

Learnt from: cristim
Repo: LeanerCloud/CUDly PR: 0
File: :0-0
Timestamp: 2026-05-05T15:44:54.463Z
Learning: In the LeanerCloud/CUDly repository, when a CodeRabbit review flags something as "outside-diff" that was already implemented in an earlier commit of the same PR, it is likely a stale-snapshot artifact where the review diff was generated against a pre-fix view. The inline comment convention `(CR pass on PR #<number> Finding N)` is used by the maintainer (cristim) to mark lines that were changed in direct response to a prior CodeRabbit review pass.

✅ Action performed

Full review finished.