Commit Graph
3811 Commits
Author SHA1 Message Date
Evie Gauthier f3aa949d46 Fix formatting in room abbreviations changeset 2026-03-24 23:33:32 -04:00
Evie Gauthier 8966d459ca chore: prettier 2026-03-24 23:33:31 -04:00
Evie Gauthier 97aaac9a49 fix(abbreviations): restore ancestor duplicate check; clear stale validity on input change 2026-03-24 23:33:30 -04:00
Evie Gauthier 4207f82aa6 fix: allow overriding inherited space abbreviations at room level 2026-03-24 23:33:29 -04:00
Evie Gauthier 0767c18a17 fix: correct Chip size prop and add changeset heading 2026-03-24 23:33:28 -04:00
Evie Gauthier 3bf51a2eb2 feat: multi-level space abbreviation inheritance + flat settings list
- useMergedAbbreviations: drop space param; use getAllParents+roomToParentsAtom
  to traverse the full ancestor chain and subscribe to state events at every
  level (not just direct parent) via useStateEventCallback on the mx client
- Room.tsx: drop parentSpace/useSpaceOptionally — hook handles it internally
- RoomAbbreviations settings: replace two-section layout with a single flat
  list; room entries shown without badge, inherited entries show a
  'Space - <SpaceName>' chip badge; supports arbitrary nesting depth
  (mirrors the useImagePackRooms multi-level pattern)
2026-03-24 23:33:27 -04:00
Evie Gauthier 920a992740 fix: abbr dotted underline + space settings label fixes
- Add textDecoration: 'underline dotted' and cursor: 'help' to <abbr>
  elements in AbbreviationTerm so users can see the hover indicator
- RoomAbbreviations: add isSpace prop; when true, show 'Space Abbreviations'
  / 'space-level' labels and hide the inherited-from-space section
- SpaceSettings: pass isSpace to RoomAbbreviations
2026-03-24 23:33:26 -04:00
Evie Gauthier f31d4edf95 feat: inherit space abbreviations in rooms, add abbreviations to space settings 2026-03-24 23:33:25 -04:00
Evie Gauthier 6dd62575b0 fix: case-insensitive matching, remove double tooltip, mobile tap-to-pin
- Revert to case-insensitive matching (gi flag, lowercase map keys) and
  update tests and duplicate-entry check accordingly
- Remove title attribute from <abbr> — was causing native browser tooltip
  to overlap with our custom TooltipProvider tooltip
- Extract AbbreviationTerm component; adds click/tap handler that pins
  the definition as a PopOut positioned above the term
  - Desktop: hover still shows tooltip via TooltipProvider
  - Mobile: tap pins the tooltip open; tap anywhere else dismisses it
    (one-shot document click listener, stopped by e.stopPropagation so
    the opening click does not immediately close it)
2026-03-24 23:33:24 -04:00
Evie Gauthier 4c1dccf648 fix: case-sensitive abbreviation matching with word boundaries
- buildAbbreviationsMap now stores exact-case keys (no .toLowerCase())
- splitByAbbreviations regex uses 'g' flag instead of 'gi' — user-defined
  casing is matched exactly (FOSS won't match 'foss' in text)
- Word boundaries (\b) still prevent matching inside longer words
- RoomAbbreviations settings page duplicate check updated to exact match
- Add 19 unit tests covering edge cases: empty map, no-match, start/mid/end
  splits, case sensitivity, word boundaries, longest-match priority
2026-03-24 23:33:23 -04:00
Evie Gauthier 4460047365 feat: add room abbreviations with hover tooltips (#403)
- Add StateEvent.RoomAbbreviations ('moe.sable.room.abbreviations')
- Include abbreviations event in sliding sync required state
- Add AbbreviationsPage to RoomSettingsPage enum
- New RoomAbbreviations settings page (add/remove term+definition pairs)
- Wire page into RoomSettings.tsx menu
- New useRoomAbbreviations hook + RoomAbbreviationsContext
- Provide context in Room.tsx
- RenderBody.tsx: highlight defined terms in plain-text messages with
  TooltipProvider+abbr tooltip; HTML messages unaffected
2026-03-24 23:33:22 -04:00
7w1 28d8e942ac fix jumbo emojis for messages sent with a per-message-profile (#530)
### Description

added a regex to the rendering of messages to detect jumbo emojis. the
regex used is:

```
^(<img[^>]*data-mx-emoticon[^>]*\/>){1,20}$
```

Fixes https://github.com/SableClient/Sable/issues/458

#### Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).

no AI was used in the creation of this PR
2026-03-25 03:12:30 +00:00
7w1 ec2dcfbe3e fix: prevent 401 errors on authenticated media after service worker restart (#516)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

The service worker (SW) loses its in-memory session on restart (e.g.
after the browser kills the SW background process). Any authenticated
media request arriving before the SW re-reads session data from cache
was returning a 401.

Two fixes:
1. **Eager pre-load on `activate`**: the SW now reads session data from
the cache during the `activate` event, so it is available immediately
when the first `fetch` event fires.
2. **Graceful fallback in fetch handler**: if session data is still
missing or stale at request time, the request is passed through to the
network without injecting a bad `Authorization` header (previously an
empty/invalid token was injected, causing the 401).

Fixes #

#### Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [X] Fully AI generated (explain what all the generated code does in
moderate detail).

<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->

Attempts to resolve issues with the service worker not properly storing
and/or refreshing media auth tokens on load. The changes mainly serve to
ensure that a session is persisted during restarts (and then drop the
persisted session once a live one is available). Also helps with
refreshing tokens (`sw.ts` ln 651-661)
2026-03-25 02:56:58 +00:00
7w1 697d2bd32a Fix encrypted pmp message rendering issues (#526)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->

Should fix the last of the bugs with per-message profile rendering in
encrypted rooms.

Ensures that pmp's are always updated on decryption and gets the
timeline to refresh whenever pmps are unencrypted to make sure they get
grouped together properly.

Vibes are telling me this isn't the best way to do this for some reason,
but it does seem to be working and I can't think of any other method
that doesn't involve creating a billion more event listeners in other
files.

#### Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
2026-03-24 21:57:33 -05:00
Rye 7338be259a fix(Message rederer): jumbo emojis for messages sent with a Per-Message-Profile
added a RegEx to match emoticons, if a message contains 1 to 20 emoticons
2026-03-25 03:34:17 +01:00
7w1 9f22f3c08b trigger the timeline to regroup messages on pmp decryption so latest message is grouped 2026-03-24 19:09:30 -05:00
7w1 2b197aa901 ensure pmp is always updated on event decryption 2026-03-24 18:55:16 -05:00
Rose 3aee3054a5 Fix sending messages with attachments and stickers while using PMP (#525)
### Description

fixes falling back to your non-pmp sender info when sending a sticker or
a attachment

Fixes https://github.com/SableClient/Sable/issues/513

#### Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
No ai was used for this PR
2026-03-24 22:07:47 +00:00
Rose d219615d26 Feat: add quickreply keybindings (#524)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

This adds the keybinds `ctrl+up`/`ctrl+down` to be used to cycle what
message you are replying to. This is inspired by [the vencord plugin
QuickReply](https://vencord.dev/plugins/QuickReply)

#### Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x]  I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->

I couldn't get `pnpm dev ` to run so I used an llm to help me figure
that out so I could test my changes, but no code in this pr has been
touched by an llm
2026-03-24 21:47:57 +00:00
Cassie 944470640c Docs: document quickreply feature 2026-03-24 15:24:36 -06:00
Cassie 8ad6b8b19b Feat: add quickreply keybindings 2026-03-24 15:24:36 -06:00
Rye f6f5e19b75 fix(Per-Message-Profile): sending messages with attachment/stickers with a pmp 2026-03-24 21:33:04 +01:00
Rose 931792acd0 Move language pronoun filter setting to Appearance (#521)
### Description

moved language pronoun filter setting to Appearance (not really much
more to say)

Fixes #520

#### Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

only a ui change, neither a fix nor a new feature

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->

no ai was used in the creation of this PR
2026-03-24 18:17:14 +00:00
Rose f8d30069c2 Merge branch 'dev' into refactor/move-language-filter-settings-out-of-experimental 2026-03-24 19:14:27 +01:00
Rye b41c86b49e style(language pronoun filter): move setting from Experimental to Appearance 2026-03-24 19:11:06 +01:00
7w1 4644e2b2a5 fix: update sliding sync known issues link to SableClient/Sable#39 (#519)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

The "Known issues" link in the Experimental Settings page for Sliding
Sync pointed to the old repository (`7w1/sable#146`). This updates it to
the correct issue in the current repository.

#### Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [x] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).

<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->

AI was used to locate the old link in the codebase. The change itself is
a one-line URL update in `General.tsx` — no logic is involved.
2026-03-24 18:03:59 +00:00
Evie Gauthier 9d9e995364 chore: add changeset for sliding sync link fix 2026-03-24 14:02:05 -04:00
Evie Gauthier 4517d712e1 fix: update sliding sync known issues link to SableClient/Sable#39 2026-03-24 13:36:44 -04:00
Rose 73cc123140 Feat: added location sharing command (#509)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description
Following the spec there needs to be a way to send (as there is a "way"
to display already) location messages.

This PR adds 2 commands one could use for that purpose (in preparation
of maybe adding a location sharing button in the future)

/location [Latitude] [Longitude] [Altitude?] ← for sending any arbitrary
location with its coords
/sharemylocation ← for sharing one's current location using the gps
tracker inside all phones nowadays :3

#### Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
I had to set up a proper self host to test this little thing because my
laptop doesnt have a tracker :3 so i had to use my phone
2026-03-24 16:27:10 +00:00
7w1 a418b928aa chore: prepare release 1.12.3 (#508)
> [!IMPORTANT]
> Merging this PR will create a new release.

## Fixes

* Fixed text autocomplete issues
([#487](https://github.com/SableClient/Sable/pull/487) by @nushea)
* Fix crash when url contains malformed/dangling uri components.
([#512](https://github.com/SableClient/Sable/pull/512) by @7w1)
2026-03-24 15:01:14 +00:00
github-actions[bot] 24bb1d5c6b chore: prepare release 1.12.3 2026-03-24 15:00:46 +00:00
7w1 fec777aed4 Decode urls safely to avoid crashes (#512)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->

Fixes #510 

#### Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
2026-03-24 10:00:23 -05:00
7w1 6ac65cc1f8 stupid linter 2026-03-24 09:58:09 -05:00
7w1 418fe2cc1a unduplicate code 2026-03-24 09:56:13 -05:00
7w1 80c207fc0d linter 2026-03-24 09:51:08 -05:00
7w1 7a6c74eeee decode urls safely! 2026-03-24 09:45:14 -05:00
Shea Duma 43501f84ad hopefully im not spamming 2026-03-24 16:22:53 +02:00
Shea Duma 9275e5fdf7 act made the word more general 2026-03-24 16:21:08 +02:00
Shea Duma 982f93de04 reformulated the sentences 2026-03-24 16:20:04 +02:00
Evie Gauthier c4c99a5e02 chore: add changeset for SW media auth 401 fix 2026-03-24 10:14:27 -04:00
Evie Gauthier a221164304 fix: pre-load session from cache on activate to prevent SW restart 401s
On SW restart the in-memory sessions Map is empty. Previously the fetch
handler fell through to requestSessionWithTimeout (3 s race window), so
all simultaneous thumbnail loads during that window 401'd.

Changes:
- Populate preloadedSession from Cache Storage in the activate handler
  so media fetches get immediate auth before the first live setSession
  arrives from the page.
- Include preloadedSession in the byBaseUrl fast path so the synchronous
  branch handles the burst of thumbnail requests without waiting at all.
- Clear preloadedSession as soon as any real setSession arrives so stale
  tokens cannot linger.
- Handle empty clientId (uncontrolled-context fetches) by falling through
  to byBaseUrl / preloadedSession / loadPersistedSession instead of doing
  a bare return that bypassed respondWith and caused an unauthenticated
  request.
2026-03-24 10:14:26 -04:00
Evie Gauthier d93f4174b2 fix: prevent 401 media errors from stale/missing SW session
Three changes to src/sw.ts:

1. Fix early-return bug in fetch handler: when sessions.get(clientId)
   returns a session but validMediaRequest(url, session.baseUrl) fails
   (e.g. multi-account users on different homeservers, or URL format
   mismatch), the old code returned without calling event.respondWith(),
   causing the browser to make an unauthenticated request → 401.
   Now we only short-circuit if BOTH conditions are met.

2. Proactively broadcast requestSession to all window clients in the
   activate event. After a SW restart the sessions Map is empty; the
   old code relied on the first intercepted media fetch to trigger
   requestSessionWithTimeout. Now the SW pre-populates the Map right
   after claiming clients, eliminating the 3-second race window.

3. Add loadPersistedSession() as a final fallback in the fetch handler.
   If requestSessionWithTimeout returns nothing (
Three changes to src/sw.ts:

1. Fix early-return bug in fetch handler: when sessions.get(clientId)
   returns a session buo a
1. Fix early-return bug i
2026-03-24 10:14:26 -04:00
Shea Duma 75b5abb78f fake-squashed Add location 2026-03-24 11:54:56 +02:00
7w1 8f46cff25e Fix the autocomplete "dropdown" menus (#487)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description
This PR seeks to fix the issues around the autocomplete for emoji, room,
command, and people.

The issues fixed by this PR are: the autocomplete menu not scrolling,
not rollovering (ie when you were at the top you couldnt go back to the
bottom or vice versa), and when editing a message and trying to select
an emoji the arrow buttons not working.

#### Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
Written with all the natural stupidity possible in one so-called human
2026-03-24 06:16:06 +00:00
Shea Duma ad9997756a fixed message edit overtaking the autocomplete for enter 2026-03-24 07:46:00 +02:00
Shea Duma 61151ae909 Merge remote-tracking branch 'upstream/dev' into emoji-scrolling
Updated to the latest version
2026-03-24 07:29:58 +02:00
7w1 8fe5d7e72f chore: prepare release 1.12.2 (#507)
> [!IMPORTANT]
> Merging this PR will create a new release.

## Fixes

* Fix standard embed links not rendering.
([#506](https://github.com/SableClient/Sable/pull/506) by @7w1)
* Added maximum height to state events
([#491](https://github.com/SableClient/Sable/pull/491) by @nushea)
2026-03-24 05:28:33 +00:00
github-actions[bot] 40d919c803 chore: prepare release 1.12.2 2026-03-24 05:27:49 +00:00
7w1 f5d9e4a9c7 Fix: Add max height to state events (#491)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description
This PR wants to cap the height of an event to prevent one single event
taking the entire screensize.

(before the PR)
<img width="1331" height="867" alt="image"
src="https://github.com/user-attachments/assets/b299cacd-85ff-4496-ac28-174c9f511faa"
/>

(after the PR)
<img width="1321" height="769" alt="image"
src="https://github.com/user-attachments/assets/abbdcab2-b375-4572-909c-d59ff6e294b5"
/>

Fixes #

#### Type of change
prevents

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
2026-03-24 05:25:24 +00:00
7w1 04b5ac6f62 Fix standard embeds not rendering (#506)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->

Fixes #

#### Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
2026-03-24 00:26:06 -05:00