Recurring stream name mangled to 'buy shares of Qqqm for $ each' — matching key leaks into the display name

[KenTaniguchi-R]

Symptom

A detected recurring bill is displayed as:

buy shares of Qqqm for $ each     $300.00   Biweekly   Sep 7

The name is a mangled Robinhood order description. The source text is of the form buy 4.1371 shares of QQQM for $290.06 each; the numerals have been stripped, leaving a dangling $ and the phrase for $ each. The title-casing has also lowercased the ticker to Qqqm.

Appears on both /bills and the dashboard "Upcoming Bills" widget.

Notes

The number-stripping is presumably meant to normalize varying amounts so repeated orders collapse into one recurring stream — which is the right goal, but the residue should not be rendered. Two things worth separating:

• the matching key (numbers removed, so occurrences group correctly)
• the display name (should stay readable — e.g. Buy QQQM or the raw description of the latest occurrence)

Ticker casing is a second-order issue: the title-caser should not lowercase all-caps tokens.

Low severity, but it is on the dashboard, so it is one of the first things visible in the app.

Found in UI audit 2026-08-29.

[KenTaniguchi-R]

Partly fixed by #123 — leaving this open deliberately, scoped down to what remains.

Fixed

The rendered residue. stripNoise deleted numeric tokens but left the currency symbol and the words framing it stranded:

before:  "buy 4.1371 shares of QQQM for $290.06 each"  ->  "buy shares of Qqqm for $ each"
after:   "buy 4.1371 shares of QQQM for $290.06 each"  ->  "buy shares of Qqqm"

Two rules now run before the generic digit stripping: a per-unit price clause (for $290.06 each) is removed whole, and a currency amount goes as one token including its symbol. A symbol inside a name is untouched — A$AP Records is unchanged, with a test pinning it.

This also addresses the matching-key/display-name split this issue asked for, though from the other direction: the price is what varies between occurrences, so removing the clause is what lets repeated orders collapse into one stream. The old digit-stripping achieved that by accident and left the wreckage on screen.

Still open: the ticker reads Qqqm

Not fixed, and not for lack of trying. caseToken title-cases all-caps tokens of four or more letters, and the suite pins:

cleanTransactionName("ACH Electronic Debit - CITI AUTOPAY PAYMENT ...") === "Citi Autopay Payment"

CITI and QQQM are both four all-caps letters. No length rule separates them — widening the acronym threshold to 4 turns Citi back into CITI and breaks deliberate behaviour.

I considered a vowel heuristic (QQQM has none, CITI does). It would have fixed the reported case and passed CI, but it still mangles TSLA, NVDA, and every vowel-bearing ticker. Inconsistent casing across tickers is worse than uniform casing, and a half-working heuristic is harder to reason about later than a known limitation. So I did not ship it.

Distinguishing a ticker from a word needs a real signal. The household's own investment_holdings.ticker values would do it exactly — but a pure display-name helper reaching into the database is the wrong shape. If this is worth doing, the shape is probably a caller-supplied set of known tickers passed into cleanTransactionName, so the purity is preserved and the knowledge lives with the sync that already has it.

Low severity, as originally filed — it is cosmetic, and now the only cosmetic part left.