2026.08.20.1
ReviewQueueRail unselected count chip renders hardcoded #eef3f6 fallback — –color-surface-muted is declared nowhere (KAN-1051)
The item counts next to each queue name in the Review Center sidebar were displaying with a background color that did not match the rest of the app, making the unselected counts look visually out of place. This mismatched styling appeared on every queue row that was not currently selected. The counts now render as clean text that matches the design used throughout the Review Center. Selected queue counts stand out with the app’s accent color, while unselected counts use a neutral tone that fits naturally with the sidebar.
RepeatPayeeFooterCard subline is false for payees with no saved category (suggestedCategoryId NULL) (KAN-1138)
When reviewing imported transactions, the repeat-payee summary card claimed that all listed payees already had a usual category saved, even when some of those payees had no saved category at all. The misleading message appeared alongside every payee name regardless of whether the app actually knew which category to use. The card now shows the saved-category claim only for payees that genuinely have one on file. Payees without a saved category still appear in the list but no longer carry the incorrect statement that new imports will be categorized automatically. The categorize action continues to work correctly for payees that do have a saved category.
Logout never revokes the refresh token — add POST /auth/logout with Cognito token revocation (KAN-463)
When you signed out of Tovari, the app was only signing you out on the screen — behind the scenes, the long-lived key that keeps you signed in on that device stayed usable for up to thirty days, so if it was ever stolen, signing out did not protect your account. That is fixed now. When you sign out — on the web or in the mobile app — Tovari immediately cancels that key with our servers, so it can no longer be used to get into your account. Signing out is still instant and reliable: even if your connection is slow or offline, you are never stuck on the screen. One thing to know: signing out on one device does not sign you out everywhere — any other device where you are signed in stays signed in until you sign out there too.
Opening-plug re-arm silently rewrites RECONCILED plug rows and moves their date — applyOpeningPlug’s ON CONFLICT guard omits status (KAN-1752)
We fixed a problem that could quietly undo part of a balance you had already confirmed. Previously, after you reconciled a connected bank account — confirming that its balance matched your statement — a later automatic refresh from your bank could silently change the account’s starting-balance entry, altering both its amount and the date it appeared on. That meant running balances inside a period you had already confirmed could shift without any warning. Now, once you reconcile an account, its starting-balance entry is locked in place: automatic refreshes will never change or remove it. Your confirmed balances stay exactly as you verified them.
Review Center keeps showing transactions categorized from outside it (payee apply-to-all, Plaid sync) (KAN-1754)
When you gave a payee a category and chose to apply it to all of that payee’s transactions, those transactions kept showing up in the Review Center as though they still needed a category, and the count next to Review Center kept including them. The only way to clear them was to reload the app. They now disappear from the list the moment you apply the category, and the count updates with them. The same refresh problem affected transactions arriving from a linked bank account, from entering a scheduled bill, and from a file import — all of these now update the Review Center right away too. Anything the app deliberately leaves for you to handle yourself, such as a transfer between your own accounts or a transaction whose category you set by hand, still stays in the list as before.
Uncategorized queue row renders the payee’s SUGGESTED category as if the transaction were already filed (KAN-1755)
We’ve polished the Review Center. Each queue now shows a clear “Queues” label and, when you pick a queue, a running total of what’s waiting there. When everything is caught up, the queue list now looks calm and clear instead of showing a leftover highlight, and the cluttered number badge next to each queue name is gone in favor of a simple count. Account icons on transfer matches now always show the right account type. For uncategorized transactions, we no longer quietly pre-fill a suggested category — instead you’ll see it offered as a clear “Suggested” option you can apply with one click, so what’s shown always matches what’s actually been filed. And the note about payees you’ve already categorized before now only appears for payees that actually have a usual category on file.
Account editor modal: Close Account button and Safe to Spend card are squashed once the modal scrolls (KAN-1756)
When you edited an account, parts of the edit window could come out the wrong size once the window was tall enough to scroll. The Close Account button was squeezed to about half the height of the Cancel and Save Changes buttons below it, and the Include in Safe to Spend card was too short for its own text, so the second line spilled out past the edge of the card. Both now stay the size they are meant to be: Close Account matches the buttons beside it, and the Safe to Spend card grows to fit its text. The window still scrolls exactly as before, and shorter windows that never scrolled are unchanged.
writePostingAdjustment/retirePostingAdjustment lack the reconciled-status fence KAN-1752 added to applyOpeningPlug (KAN-1769)
When you reconciled an account, certain automatic balance adjustments created during bank sync were not protected from being overwritten or removed by later sync updates. This meant that a subsequent bank sync could silently alter or delete a balance-correction entry that fell within a reconciled period, potentially changing your reconciled balance without warning. The app now protects all balance adjustments inside a reconciled period from automated changes, matching the same safeguard already in place for opening-balance entries. If a sync encounters a reconciled adjustment, it leaves it untouched rather than modifying or removing it. Your reconciled balances remain exactly as you attested them.
RepeatPayeeFooterCard headline “more from payees you have filed before” is false for non-qualifying repeat payees (KAN-1781)
When reviewing transactions that needed a category, the app listed repeat payees under a headline claiming they were payees “you have filed before.” In some cases, the listed payees had never actually been categorized — they simply appeared in more than one transaction, making the claim misleading. The headline now adjusts its wording to match reality. When every listed payee has a prior category on file, the original description appears as intended. When some do not, the wording accurately reflects that these are simply payees the app has seen before.
enterBillCore’s pre-lock fast path returns not_outstanding for a same-key replay (missing findReplay re-probe) (KAN-1791)
We fixed a timing issue where entering a scheduled bill payment could show an error message even though the payment had actually gone through. This happened in rare cases when a payment confirmation was submitted more than once in quick succession, such as from a slow connection or an accidental double-tap. Now, if that happens, you’ll see your successful payment confirmed instead of a confusing error, with your account and budget totals updated correctly. No payments were ever duplicated by this issue — it only affected what was shown on screen. This makes entering bill payments more reliable, especially on slower or less stable connections.
Mobile: tapping a favorite account on the dashboard shows “coming soon” instead of navigating to the register (KAN-1797)
Tapping a favorite account on the mobile dashboard previously showed a placeholder screen instead of opening the account. Favorite accounts now navigate directly to their transaction register, the same view you reach from the Accounts tab. This makes the favorites section a genuine shortcut to your most-used accounts rather than a dead end.
Improvements
Section titled “Improvements”KAN-1026 coordination package: inter-panel disc glyph correction, transfer leg amount colour, rail header/summary, footer heading copy (KAN-1049)
The Review Center sidebar now displays a heading and a money summary for the selected queue, making it easy to see the total amount awaiting review at a glance. The approval impact section beneath each review item has been updated with a more natural, conversational heading and refined styling that is easier to read. Together these changes bring the Review Center’s visual presentation in line with its intended design.
Web queue rail rows stay interactive/active at all-clear (board 6a shows muted) (KAN-1192)
When all review queues are clear, the queue list in the Review Center now appears visually muted, matching the all-clear celebration shown beside it. Previously, queue rows kept their active highlight and interactive appearance even when there was nothing left to review, which made it look like items still needed attention. Selecting a highlighted row in that state had no effect. The queue list now clearly communicates that everything has been reviewed, and the active highlight only appears when a queue actually contains items waiting for your attention.
Mobile WhatChangesCard heading still reads third-person, diverging from web’s KAN-1049 sentence-case wording (KAN-1780)
The mobile app’s Review Center previously displayed its “What changes” heading using third-person wording and all-uppercase styling that did not match the web version. The heading now uses first-person phrasing, reading “What changes if I approve” and “What changes if I add it” instead of the former “What changes if you approve” and “What changes if you add.” The text also appears in standard sentence casing rather than all caps, making it easier to read and consistent with the web experience.
Mobile WhatChangesCard surface (background/heading color) diverges from Review Center Board (KAN-1792)
In the Review Center, the “you’ve filed this payee before” message on repeat-payee suggestions now only appears when you actually chose that category yourself in the past, instead of sometimes showing up for categories the app guessed or picked up automatically. On mobile, the “What changes” card on alert details now matches the clean white styling used everywhere else in the Review Center, with clearer text and a consistent look and shadow, replacing its previous tinted, slightly mismatched appearance.
RepeatPayee “filed before” claim is not provable from data (suggestedCategoryId can be auto-stamped) (KAN-1793)
The Review Center’s repeat-payee card could incorrectly claim you had previously categorized a payee when the category was actually assigned automatically by the system. This happened because the app treated any existing category suggestion as proof of a prior user decision, even when the suggestion came from an automated source. The card now checks whether the category was genuinely set by you before displaying that claim. Payees whose categories were assigned automatically no longer show the “filed before” language, so the guidance you see while reviewing transactions accurately reflects your own history.
Decide whether to disarm migration 128’s fleet-wide opening_plug_pending before it is consumed — the arming is live and unfired on prod (KAN-1799)
In some cases, a transaction you had already reconciled on a linked bank account could still be quietly rewritten or removed the next time your account synced. That could make an account you had already checked off as correct show a different balance than the one you confirmed. Reconciled transactions are now protected from being changed by a later sync, so once you’ve reconciled an account, it stays exactly as you left it. We also improved how the starting balance is calculated when a bank connection is first linked, so it lines up more precisely with your account’s actual history. Behind the scenes, we added better monitoring so our team can tell the difference between an account that’s fine because you’ve already reconciled it and one that genuinely needs attention.
Mobile transaction register header layout and search UX fixes (KAN-1822)
The transaction register on mobile now has a cleaner, more consistent header layout. The search icon is always visible in the toolbar so you can find transactions without opening a menu first. When you search, the Upcoming Bills, Transfers to Review, and Pending sections step out of the way so only matching results are shown. A vertical ellipsis menu provides quick access to Select/Match and Edit Account actions, and a dedicated Add button lets you create a new transaction right from the header.