Verifiable reset notifications + Codex banked-resets 0-state#43
Closed
tsouth89 wants to merge 2 commits into
Closed
Verifiable reset notifications + Codex banked-resets 0-state#43tsouth89 wants to merge 2 commits into
tsouth89 wants to merge 2 commits into
Conversation
Codex is the only provider with banked rate-limit resets, and the indicator was hidden whenever the count was zero: the backend collapsed a zero count to None and every surface only rendered the chip when the value was non-null. A user with no banked resets saw nothing and had no way to know the feature was being tracked. - codex/api.rs: record Some(available_count) including 0 on a successful fetch. None now means only "not fetched / unknown", never "zero". - capacityPresentation: resetCreditsAvailable returns 0 as a real value; new codexResetCredits() keeps the indicator Codex-only. - PlanStatusCard, ProviderDetailView, TaskbarFlyout: always show the chip for Codex, with a muted --empty variant when the count is 0.
Unexpected-reset toasts are already wired and default-on, but there was no way to confirm the Windows toast pipeline (AUMID registration + PowerShell + WinRT) actually delivers on a given machine, and debug builds suppress toasts entirely. - notifications.rs: extract the shared toast-script builder and add send_test_notification(), which runs the real pipeline synchronously (.output()) and returns Ok/Err. It deliberately bypasses the startup baseline gate and rate limits: it is user-initiated and must prove delivery end-to-end. - Expose it as a Tauri command (registered + allowlisted) and a sendTestNotification() bridge wrapper. - Settings > Notifications: a "Send test" button with sending/sent/failed states, disabled when notifications are off. - New NotificationTest* locale keys across locale.rs, keys.ts, and all 6 .ftl files (English).
Contributor
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ceiling | f17c392 | Commit Preview URL Branch Preview URL |
Jul 17 2026, 11:54 PM |
📝 WalkthroughWalkthroughAdds a settings control for sending test notifications through Tauri and native notification APIs. It also preserves explicit zero Codex reset credits and renders them as muted indicators across capacity-related views. ChangesNotification testing and reset-credit presentation
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant GeneralTab
participant TauriBridge
participant NotificationCommand
participant notifications
GeneralTab->>TauriBridge: sendTestNotification()
TauriBridge->>NotificationCommand: invoke send_test_notification
NotificationCommand->>notifications: send_test_notification()
notifications-->>NotificationCommand: Result<(), String>
NotificationCommand-->>TauriBridge: command result
TauriBridge-->>GeneralTab: success or failure
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
Comment |
This was referenced Jul 18, 2026
Owner
Author
|
@coderabbitai review |
✅ Action performedReview finished.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
rust/src/locale/ja-JP.ftl (1)
1-1: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winNew
NotificationTest*locale entries are untranslated across all four non-English locale files. The shared root cause is that all six new notification-test strings were added in English instead of being translated to each locale's language.
rust/src/locale/ja-JP.ftl#L369-374: TranslateNotificationTest,NotificationTestHelper,NotificationTestButton,NotificationTestSending,NotificationTestSent, andNotificationTestFailedto Japanese.rust/src/locale/ko-KR.ftl#L369-374: Translate the same six keys to Korean.rust/src/locale/zh-CN.ftl#L369-374: Translate the same six keys to Simplified Chinese.rust/src/locale/zh-TW.ftl#L369-374: Translate the same six keys to Traditional Chinese.🤖 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 `@rust/src/locale/ja-JP.ftl` at line 1, Translate the six NotificationTest locale entries—NotificationTest, NotificationTestHelper, NotificationTestButton, NotificationTestSending, NotificationTestSent, and NotificationTestFailed—in each non-English locale file: Japanese, Korean, Simplified Chinese, and Traditional Chinese. Preserve the existing keys and provide natural translations matching each locale’s language.
🧹 Nitpick comments (1)
apps/desktop-tauri/src/surfaces/settings/tabs/GeneralTab.test.tsx (1)
118-152: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winConsider adding a test for the "failed" notification state.
The success and disabled paths are covered, but the failure path (
sendTestNotificationrejects → button showsNotificationTestFailed) is untested.✨ Suggested test
it("shows failure message when notification send fails", async () => { sendTestNotificationMock.mockRejectedValueOnce(new Error("fail")); render( <GeneralTab mode="notifications" settings={settings} set={vi.fn()} saving={false} />, ); fireEvent.click(screen.getByRole("button", { name: "NotificationTestButton" })); await waitFor(() => expect( screen.getByRole("button", { name: "NotificationTestFailed" }), ).toBeInTheDocument(), ); });🤖 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 `@apps/desktop-tauri/src/surfaces/settings/tabs/GeneralTab.test.tsx` around lines 118 - 152, Add a failure-path test alongside the existing notification tests, using sendTestNotificationMock to reject once, rendering GeneralTab with notifications enabled, clicking the NotificationTestButton, and awaiting the NotificationTestFailed button state.
🤖 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 `@rust/src/locale/es-MX.ftl`:
- Around line 369-374: Translate the six notification-test localization
values—NotificationTest, NotificationTestHelper, NotificationTestButton,
NotificationTestSending, NotificationTestSent, and NotificationTestFailed—into
natural Spanish suitable for the Windows settings UI, preserving their existing
Fluent keys and meaning.
In `@rust/src/locale/ja-JP.ftl`:
- Around line 369-374: Translate all six NotificationTest* entries in the
Japanese locale, including the title, helper text, button label, sending and
sent statuses, and failure message. Keep the existing Fluent keys unchanged and
provide natural Japanese user-facing text.
In `@rust/src/locale/ko-KR.ftl`:
- Around line 369-374: Translate all six NotificationTest* entries in the Korean
locale, including the title, helper text, button label, sending and sent
statuses, and failure message, while preserving each existing Fluent key and
placeholder-free message structure.
In `@rust/src/locale/zh-CN.ftl`:
- Around line 369-374: Translate all six NotificationTest,
NotificationTestHelper, NotificationTestButton, NotificationTestSending,
NotificationTestSent, and NotificationTestFailed values into Simplified Chinese
while preserving their existing Fluent keys and notification meanings.
In `@rust/src/locale/zh-TW.ftl`:
- Around line 369-374: Translate all six NotificationTest*,
NotificationTestHelper, NotificationTestButton, NotificationTestSending,
NotificationTestSent, and NotificationTestFailed values into natural Traditional
Chinese while preserving their keys and Fluent syntax.
In `@rust/src/notifications.rs`:
- Around line 763-768: Update ensure_aumid_registered_once to return a Result
and cache completion only after successful AUMID registration, allowing later
calls to retry after failure. Propagate the registration error through
send_test_notification so the test stops before invoking PowerShell, while
preserving clear, user-facing diagnostics with friendly error messages.
- Around line 788-798: Bound both the PowerShell and notify-send notifier
processes with a finite deadline instead of awaiting Command::output()
indefinitely. Update the notifier execution around Command::new("powershell")
and its notify-send counterpart to monitor the child, terminate it when the
deadline expires, and return a clear user-friendly timeout error while
preserving existing launch-error handling.
---
Outside diff comments:
In `@rust/src/locale/ja-JP.ftl`:
- Line 1: Translate the six NotificationTest locale entries—NotificationTest,
NotificationTestHelper, NotificationTestButton, NotificationTestSending,
NotificationTestSent, and NotificationTestFailed—in each non-English locale
file: Japanese, Korean, Simplified Chinese, and Traditional Chinese. Preserve
the existing keys and provide natural translations matching each locale’s
language.
---
Nitpick comments:
In `@apps/desktop-tauri/src/surfaces/settings/tabs/GeneralTab.test.tsx`:
- Around line 118-152: Add a failure-path test alongside the existing
notification tests, using sendTestNotificationMock to reject once, rendering
GeneralTab with notifications enabled, clicking the NotificationTestButton, and
awaiting the NotificationTestFailed button state.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 4d398440-6832-46f8-a604-688d3c352e5a
📒 Files selected for processing (22)
apps/desktop-tauri/src-tauri/permissions/commands.tomlapps/desktop-tauri/src-tauri/src/commands/system.rsapps/desktop-tauri/src-tauri/src/main.rsapps/desktop-tauri/src/components/PlanStatusCard.tsxapps/desktop-tauri/src/i18n/keys.tsapps/desktop-tauri/src/lib/capacityPresentation.test.tsapps/desktop-tauri/src/lib/capacityPresentation.tsapps/desktop-tauri/src/lib/tauri.tsapps/desktop-tauri/src/styles.cssapps/desktop-tauri/src/surfaces/ProviderDetailView.tsxapps/desktop-tauri/src/surfaces/TaskbarFlyout.tsxapps/desktop-tauri/src/surfaces/settings/tabs/GeneralTab.test.tsxapps/desktop-tauri/src/surfaces/settings/tabs/GeneralTab.tsxrust/src/locale.rsrust/src/locale/en-US.ftlrust/src/locale/es-MX.ftlrust/src/locale/ja-JP.ftlrust/src/locale/ko-KR.ftlrust/src/locale/zh-CN.ftlrust/src/locale/zh-TW.ftlrust/src/notifications.rsrust/src/providers/codex/api.rs
Comment on lines
+369
to
+374
| NotificationTest = Test notifications | ||
| NotificationTestHelper = Send a sample alert to confirm Windows delivers Ceiling notifications | ||
| NotificationTestButton = Send test | ||
| NotificationTestSending = Sending… | ||
| NotificationTestSent = Sent | ||
| NotificationTestFailed = Couldn't send. Check Windows notification settings. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Translate the notification-test flow into Spanish.
These new values are English, so the Spanish settings UI becomes partially untranslated.
Proposed translations
-NotificationTest = Test notifications
-NotificationTestHelper = Send a sample alert to confirm Windows delivers Ceiling notifications
-NotificationTestButton = Send test
-NotificationTestSending = Sending…
-NotificationTestSent = Sent
-NotificationTestFailed = Couldn't send. Check Windows notification settings.
+NotificationTest = Probar notificaciones
+NotificationTestHelper = Envía una alerta de muestra para confirmar que Windows entrega las notificaciones de Ceiling
+NotificationTestButton = Enviar prueba
+NotificationTestSending = Enviando…
+NotificationTestSent = Enviada
+NotificationTestFailed = No se pudo enviar. Revisa la configuración de notificaciones de Windows.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| NotificationTest = Test notifications | |
| NotificationTestHelper = Send a sample alert to confirm Windows delivers Ceiling notifications | |
| NotificationTestButton = Send test | |
| NotificationTestSending = Sending… | |
| NotificationTestSent = Sent | |
| NotificationTestFailed = Couldn't send. Check Windows notification settings. | |
| NotificationTest = Probar notificaciones | |
| NotificationTestHelper = Envía una alerta de muestra para confirmar que Windows entrega las notificaciones de Ceiling | |
| NotificationTestButton = Enviar prueba | |
| NotificationTestSending = Enviando… | |
| NotificationTestSent = Enviada | |
| NotificationTestFailed = No se pudo enviar. Revisa la configuración de notificaciones de Windows. |
🤖 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 `@rust/src/locale/es-MX.ftl` around lines 369 - 374, Translate the six
notification-test localization values—NotificationTest, NotificationTestHelper,
NotificationTestButton, NotificationTestSending, NotificationTestSent, and
NotificationTestFailed—into natural Spanish suitable for the Windows settings
UI, preserving their existing Fluent keys and meaning.
Comment on lines
+369
to
+374
| NotificationTest = Test notifications | ||
| NotificationTestHelper = Send a sample alert to confirm Windows delivers Ceiling notifications | ||
| NotificationTestButton = Send test | ||
| NotificationTestSending = Sending… | ||
| NotificationTestSent = Sent | ||
| NotificationTestFailed = Couldn't send. Check Windows notification settings. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
New NotificationTest* entries are untranslated in this Japanese locale file.
All six new notification test strings (lines 369–374) are in English. User-facing labels like "Send test" and "Sending…" should be translated to Japanese for a proper localized experience.
🤖 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 `@rust/src/locale/ja-JP.ftl` around lines 369 - 374, Translate all six
NotificationTest* entries in the Japanese locale, including the title, helper
text, button label, sending and sent statuses, and failure message. Keep the
existing Fluent keys unchanged and provide natural Japanese user-facing text.
Comment on lines
+369
to
+374
| NotificationTest = Test notifications | ||
| NotificationTestHelper = Send a sample alert to confirm Windows delivers Ceiling notifications | ||
| NotificationTestButton = Send test | ||
| NotificationTestSending = Sending… | ||
| NotificationTestSent = Sent | ||
| NotificationTestFailed = Couldn't send. Check Windows notification settings. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
New NotificationTest* entries are untranslated in this Korean locale file.
All six new notification test strings (lines 369–374) are in English. User-facing labels like "Send test" and "Sending…" should be translated to Korean for a proper localized experience.
🤖 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 `@rust/src/locale/ko-KR.ftl` around lines 369 - 374, Translate all six
NotificationTest* entries in the Korean locale, including the title, helper
text, button label, sending and sent statuses, and failure message, while
preserving each existing Fluent key and placeholder-free message structure.
Comment on lines
+369
to
+374
| NotificationTest = Test notifications | ||
| NotificationTestHelper = Send a sample alert to confirm Windows delivers Ceiling notifications | ||
| NotificationTestButton = Send test | ||
| NotificationTestSending = Sending… | ||
| NotificationTestSent = Sent | ||
| NotificationTestFailed = Couldn't send. Check Windows notification settings. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
New NotificationTest* entries are untranslated in this Simplified Chinese locale file.
All six new notification test strings (lines 369–374) are in English. User-facing labels like "Send test" and "Sending…" should be translated to Simplified Chinese for a proper localized experience.
🤖 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 `@rust/src/locale/zh-CN.ftl` around lines 369 - 374, Translate all six
NotificationTest, NotificationTestHelper, NotificationTestButton,
NotificationTestSending, NotificationTestSent, and NotificationTestFailed values
into Simplified Chinese while preserving their existing Fluent keys and
notification meanings.
Comment on lines
+369
to
+374
| NotificationTest = Test notifications | ||
| NotificationTestHelper = Send a sample alert to confirm Windows delivers Ceiling notifications | ||
| NotificationTestButton = Send test | ||
| NotificationTestSending = Sending… | ||
| NotificationTestSent = Sent | ||
| NotificationTestFailed = Couldn't send. Check Windows notification settings. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
New NotificationTest* entries are untranslated in this Traditional Chinese locale file.
All six new notification test strings (lines 369–374) are in English. User-facing labels like "Send test" and "Sending…" should be translated to Traditional Chinese for a proper localized experience.
🤖 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 `@rust/src/locale/zh-TW.ftl` around lines 369 - 374, Translate all six
NotificationTest*, NotificationTestHelper, NotificationTestButton,
NotificationTestSending, NotificationTestSent, and NotificationTestFailed values
into natural Traditional Chinese while preserving their keys and Fluent syntax.
Comment on lines
+763
to
+768
| /// Register the AUMID at most once per process before showing a toast. | ||
| #[cfg(target_os = "windows")] | ||
| fn ensure_aumid_registered_once() { | ||
| use std::sync::Once; | ||
| static AUMID_INIT: Once = Once::new(); | ||
| AUMID_INIT.call_once(ensure_aumid_registered); |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
Propagate AUMID registration failures and allow retries.
Once::call_once is permanently completed even when ensure_aumid_registered only logs a registry error. The test then continues through PowerShell, and subsequent button clicks cannot retry registration.
Return a Result and cache only successful registration; propagate failures from send_test_notification.
As per coding guidelines, preserve clear error handling and user-facing diagnostics using friendly messages where applicable.
🤖 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 `@rust/src/notifications.rs` around lines 763 - 768, Update
ensure_aumid_registered_once to return a Result and cache completion only after
successful AUMID registration, allowing later calls to retry after failure.
Propagate the registration error through send_test_notification so the test
stops before invoking PowerShell, while preserving clear, user-facing
diagnostics with friendly error messages.
Source: Coding guidelines
Comment on lines
+788
to
+798
| let output = Command::new("powershell") | ||
| .args([ | ||
| "-NoProfile", | ||
| "-ExecutionPolicy", | ||
| "Bypass", | ||
| "-Command", | ||
| &toast_powershell_script(title, body), | ||
| ]) | ||
| .creation_flags(0x08000000) // CREATE_NO_WINDOW | ||
| .output() | ||
| .map_err(|e| format!("Could not launch the Windows notifier: {e}"))?; |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟠 Major | 🏗️ Heavy lift
Bound synchronous notifier execution with a timeout.
Both powershell and notify-send can remain running indefinitely. Because the Tauri request awaits Command::output(), Settings remains stuck in its sending state with no recovery.
Apply a deadline, terminate the child on expiry, and return a friendly timeout error.
Also applies to: 823-825
🤖 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 `@rust/src/notifications.rs` around lines 788 - 798, Bound both the PowerShell
and notify-send notifier processes with a finite deadline instead of awaiting
Command::output() indefinitely. Update the notifier execution around
Command::new("powershell") and its notify-send counterpart to monitor the child,
terminate it when the deadline expires, and return a clear user-friendly timeout
error while preserving existing launch-error handling.
tsouth89
added a commit
that referenced
this pull request
Jul 18, 2026
…es (#46) Collapses three reviewed passes onto current `main` (1.0.0-rc.1) as one clean merge, per the plan. Supersedes #43, #44, #45 (each fully reviewed by adversarial subagents + CodeRabbit; all findings addressed). Only conflict was the English-only `.ftl` removals, resolved by accepting the deletion. ## What's included - **Codex banked resets (#43):** explicit "0 avail" chip (Codex-only, all 3 surfaces); backend records `Some(0)` instead of hiding it. **Send test notification** button that runs the real Windows toast pipeline and reports success/failure. - **Explicit enforcement states — SOU-122 (#44):** `EnforcementState { Tracked, NotEnforced, Unavailable }` exposed to every surface without fabricating a %. A process-local, per-scope `EnforcementTracker` flags a core subscription window `unavailable` when it drops out of a successful response — sticky until it returns, core-windows-only (bonus pools never false-flag), scoped by provider|source|email|org, ignores errors. - **Exact & Calm floatbar modes — SOU-178 (#45):** `float_bar_information_mode` (Exact default, safe migration). Calm leads with a trustworthy pace state + next reset; exact % on keyboard/click expand. Pace claimed only when live and actually supported. ## Verification (against this main) - Rust `codexbar` lib **621**, desktop crate **372** — 0 failures - Frontend **246** (48 files); `tsc` clean; locale-drift OK (English-only) ## Review fixes folded in Sticky/core-only tracker (one-shot bug), org-scoped observations, compact-density calm layout, calm aria-label matching visible state. --------- Co-authored-by: tsouth89 <tsouth89@users.noreply.github.com>
Owner
Author
|
Superseded by #46, which collapsed all three reviewed passes onto current main (1.0.0-rc.1) and merged. All findings from this PR's reviews were addressed there. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First pass of a multi-pass reliability/UX effort on Ceiling. Two focused, independently-reviewable changes.
1. Show Codex banked resets, including an explicit "0" state
Codex is the only provider with banked rate-limit resets, but the indicator was invisible whenever the count was zero (backend collapsed 0 to
None; surfaces only rendered when non-null). A user with no banked resets couldn't tell the feature was being tracked.codex/api.rs: recordSome(available_count)including 0 on a successful fetch.Nonenow means only "not fetched / unknown".capacityPresentation:resetCreditsAvailablereturns 0 as a real value; newcodexResetCredits()keeps it Codex-only.--emptyvariant at 0.2. "Send test notification" button to verify toast delivery
Unexpected-reset toasts are already wired and default-on, but there was no way to confirm the Windows toast pipeline (AUMID + PowerShell + WinRT) actually delivers on a given machine.
notifications.rs: extracted the shared toast-script builder; addedsend_test_notification()that runs the real pipeline synchronously and returns Ok/Err. It intentionally bypasses the startup gate and rate limits — it's user-initiated and must prove delivery end-to-end.sendTestNotification()bridge, and a Settings button with sending/sent/failed states.NotificationTest*locale keys acrosslocale.rs,keys.ts, and all 6.ftlfiles.Verification
codexbarlib: 630 passed (incl. new zero-count test)tscclean; locale-drift OKcargo checkcleanNext pass
SOU-122 — explicit enforcement states (tracked / not-enforced / unavailable) without fabricating a %. Kept separate for reviewability.
Summary by CodeRabbit
New Features
Bug Fixes
Tests