ThemeModeOverride.withFilledAppDefaults — backing the "Set default theme"
button in Chat info > Chat theme — set the wallpaper to the SCHOOL
preset but passed null for presetWallpaperTheme when filling colors. The
five-source priority chain therefore fell through to LightColorPalette /
DarkColorPalette / SimplexColorPalette / BlackColorPalette: the base
palette colors that predate this PR's preset recalibration.
Result: a chat reset via "Set default theme" showed the SCHOOL pattern
on top of pre-recalibration bubble colors that no longer match it. Pass
preset.colors[base] so the priority chain picks up SCHOOL's tuned colors
for the chosen mode, matching what the wallpaper expects.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Two clarity fixes from the audit.
- ChatWallpaper: the private color helper was named gen — too short to
carry its purpose. Rename to colorForElement, the term it actually
computes (a single oklch Color from preset + mode + element params).
- Appearance.FormulaDevTools: both the generateScheme dispatch and the
slider rendering branched via `when { isLight -> ; isBlack -> ; else
-> dark }` and `if (isLight) { } else { ; if (!isBlack) ... }`. Two
parallel dispatches over the same proposition, expressed as boolean
pairs. DefaultTheme already carries that proposition with a name;
switch to `when (baseTheme)` so each branch states which theme it is
and lists its sliders / scheme call. Black's three-slider set becomes
its own branch instead of negative gates inside the dark branch.
The isLight/isBlack locals stay for the small conditionals inside the
defaults map computation (where the ternaries read fine inline).
Pure refactor — no behavior change.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Three duplicated patterns surfaced by the audit, each consolidated into
a single named helper.
1. ThemeOverrides.toColors and toAppColors had the same five-source
priority chain (per-chat → per-user → own → preset → base) inlined
for nine non-bubble fields. Move it into resolveColor so each call
site states the data, not the resolution rule. (Bubble fields keep
their wallpaper-aware logic — different rule, separate concern.)
2. The chat's effective theme — chatInfo.uiThemes.preferredMode resolved
through ThemeManager.currentColors — was computed inline in ChatView
(for SimpleXThemeOverride) and again in App.ActiveChatThemeProvider
(for the chatlist column / Android modal stack). Pull both into a
shared rememberActiveChatTheme. Both call sites also adopt the wider
remember key (whole theme, not just base) that the toolbar fix
already needed; behavior is unchanged when the chat has no override.
3. The toolbar code-output copy in Appearance reimplemented oklch
conversion inline (Color → Oklab → atan2 → degrees) instead of
calling the existing Color.toOklch() extension. Replace with the
extension, which also adds a small near-zero-chroma guard the inline
version was missing.
Pure refactor — no user-visible behavior change.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Three documentation/marker additions surfaced by an engineer-v1 audit:
- ChatWallpaper.kt: the per-mode/per-element constants used by the theme
color formula were a wall of magic numbers. Add a header explaining
what each parameter controls and where the values came from
(empirically tuned via the dev UI in Appearance.kt).
- Appearance.kt: surround the module-level FormulaDevTools state
(formulaSavedParams, patternScaleDragging) with a prominent banner
marking it dev-only. The dev UI is shipped in the current build but
must be removed before reaching end users; the search-tag makes that
trivial later.
- Color.kt: solveCubic had no docstring; the 1e-10f thresholds looked
like magic. Document Cardano's method, the maxChromaForMatrix caller
context, and the numerical-stability rationale for the thresholds.
Pure comment additions; no behavior change.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The toolbar background was always computed from the global CurrentColors
state flow, so a chat with a custom theme override (its own wallpaper or
color scheme) showed a toolbar tinted to the global Appearance scheme
rather than the chat's. On desktop two-pane the chatlist toolbar sat
next to the chat toolbar in different colors; on Android the chat info
and chat-customize modals kept the global tint above and below the
chat-themed content.
Expose the current theme as a new LocalActiveTheme composition local,
provided by SimpleXTheme (global scope) and SimpleXThemeOverride (chat
scope). panelBackgroundColor reads everything — both the wallpaper-hue
tint and the elevation fallback — from this local, so it tints to
whatever scope it renders in. A small ActiveChatThemeProvider helper
propagates the active chat's effective theme to UI surfaces that sit
outside the chat's SimpleXThemeOverride: the chatlist column on desktop,
and the fullscreen modal stack on Android.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Prevents CRLF from sneaking into .kt files when they get opened in
Android Studio on Windows during the dev loop. Without this, the file
on disk picks up CRLF after a save, the next edit commits it, and the
PR diff inflates with line-ending noise.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Four Kotlin files in this PR ended up with CRLF after a Windows-side
merge, which made the diff against master show thousands of unchanged
lines as modified. Convert them back to LF so reviewers see only the
real semantic changes.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* light wallpapers: v4 color formula
all 6 light wallpapers recalculated with the new formula: received
messages are white (read more often, max readability), sent messages
muted in the hue — same pattern as Telegram. tint/chroma tuned per
wallpaper on device.
the formula lives outside the app (node script), only the resulting
oklch constants are in kotlin. LIGHT is served from _background/_tint/
_colors; DARK/SIMPLEX/BLACK keep the generator.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* wallpapers: tune dark theme + refine light pattern intensity
Calibrated full dark theme palette for all 6 preset wallpapers using the
shared chroma formula (bg-anchored, two-cluster muted/color, per-hue P3
saturation). Each wallpaper now has its own dark bg, tint, and bubble
colors instead of a shared neutral gray. Hearts hue shifted from 15° to
5° (slightly cooler), school from 239° to 249° (slightly warmer); hearts,
school and travel had per-wallpaper saturation reduced for visual
balance. wallpaperBackgrounds() now accepts a dark color override.
Light pattern tint also refined for flowers/hearts/kids/school/travel
using a coverage+sharpness regression on the pattern textures, so dense
patterns like hearts read calmer and sparse ones like flowers read
clearer. Light bubbles and backgrounds unchanged from the v4 formula.
Cats remains the calibration anchor for both themes.
* wallpapers: tune black theme (#6912)
* wallpapers: tune black theme
Replaced the legacy hex-derived BLACK palette with calibrated values for
all 6 preset wallpapers. Pure black bg (#000000) replaces the near-black
gray (#070707) — with the chroma formula's "muted side at zero" rule the
BLACK theme now reads as truly hyper-contrast. Each wallpaper's tint and
bubble colors are tuned to its own hue (cats 70°, flowers 130°, hearts 5°,
kids 192°, school 249°, travel 315°) with chroma pulled to per-hue P3
boundary, capped to keep pattern visibility consistent across textures.
* fix color space
* wallpapers: recalibrate all presets + hue-tinted panels
Recalculated bg/tint/bubble colors for all 6 wallpapers across LIGHT/DARK/BLACK
using unified oklch formula. Added subtle hue tint to panel backgrounds (status bar,
top app bar, nav bar) so they pick up the wallpaper's color. Hearts and school use
different hues in dark themes, so added PresetWallpaper.hue(theme) to handle that.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* wallpapers: formula dev tools, normalized patterns, desktop fixes
- Formula dev UI (developer tools only): sliders for all color parameters
per theme (LIGHT/DARK/BLACK), live preview, copyable Kotlin code output
- oklch color formula ported to Kotlin (generateSchemeLight/Dark/Black)
- sRGB gamut boundary for Desktop (maxChromaSRGB), P3 for Android
- Normalized pattern PNGs (consistent element size across wallpapers)
- Desktop pattern scale 0.55 + draft/final rendering (fast during drag,
SCALE_SMOOTH on release)
- Hue-tinted toolbar via ThemeColor.TOOLBAR + AppColors.toolbar
- Received tint slider for light themes
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* wallpapers: fix toolbar color picker + received tint default
Toolbar color: direct replacement instead of alpha-mixing, picker
opens with actual visible toolbar color (panelBackgroundColor),
copy-code hint shows file and line number.
Received tint: default derived from hardcoded colors (fallback 0.005).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* wallpapers: extend pattern depth slider range to 10
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* wallpapers: add BG Lightness slider for light themes
Offset ±0.05 to formula background L, independent of other slots.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* wallpapers: denser hearts pattern + recalibrated LIGHT colors
Tuned LIGHT theme colors for all 6 presets via the formula sliders.
Hearts pattern PNG replaced with a denser variant (all four density
variants regenerated).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* wallpapers: revert iOS hearts variants to old format
The denser hearts PNG is shipped only as the multiplatform @4x file
(used by Android and Desktop). iOS still uses the old pattern renderer
which expects the old non-normalized layout, so the @1x/@2x/@3x
variants are reverted to their previous state to avoid visual breakage
on iOS.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Evgeny Poberezkin <evgeny@poberezkin.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: Evgeny Poberezkin <evgeny@poberezkin.com>
* Revert "core: forward compatible support for owners/admins/moderations deleting channel and public group messages without limitations (#6962)"
This reverts commit 08108ebabb.
* core, ui: allow indefinite deletion from history for public channel/group owners/moderators
* style
Co-authored-by: Evgeny <evgeny@poberezkin.com>
* refactor
* show error on deletion
* better alerts
* test
* plan
* simplify test
* bot api docs
* refactor
* test that removed from history is not delivered to the new subscribers
* fix, refactor
* fix
* rename
* rename predicate in UI
* rename
* do not forward channel deletions from history
* remove redundant check
---------
Co-authored-by: Evgeny @ SimpleX Chat <259188159+evgeny-simplex@users.noreply.github.com>
* plans: design and implementation plan for desktop tray icon
Adds a system tray icon to the SimpleX desktop app with first-close
dialog and an Appearance toggle. Covered: minimize-to-tray on Linux,
Windows, and macOS via ComposeNativeTray; tri-state CloseBehavior
preference; unread-dot icon swap; show/quit menu.
The design plan covers the user-facing behavior, library choice
rationale (AWT/Compose Tray is broken on stock GNOME per JDK-8322750;
ComposeNativeTray uses platform-native APIs and is maintained), and
out-of-scope items. The implementation plan splits the work into 8
incremental commits, each leaving the build green.
* desktop: add CloseBehavior preference
* plans: switch tray to built-in Compose Tray with GNOME probe
* desktop: branch close handler on CloseBehavior preference
* desktop: first-close dialog for tray choice
* desktop: tray icon assets and menu strings
* desktop: system tray icon with show/quit menu
* desktop: unread indicator on tray icon
* desktop: Appearance toggle for minimize-to-tray
* desktop: tray feature fixes from audit
- Scope closedByError per application iteration; set before dispatchEvent.
- Short-circuit Ask to Quit when tray is unavailable.
- Sum users.unreadCount (pre-aggregated) instead of iterating chats.
- Replace dialog's captured lambdas with a top-level flag and
ApplicationScope extension; wrap in SimpleXTheme.
- Probe SystemTray with real add/remove off the EDT.
- Drop duplicate ic_simplex_tray.svg; nudge unread dot to cy=34 to
stop the r=6 circle clipping at the viewBox bottom.
- Use mkSafeEnumPreference, PreferenceToggle, SectionTextFooter.
* plans: sync desktop tray plans with implementation
* desktop: render close-behavior popup via AlertManager
Replaces the bespoke DialogWindow with AlertManager.shared.showAlertDialogButtonsColumn —
same in-app surface as e.g. the link-previews opt-in alert. Drops isAskingCloseBehavior,
the CloseBehaviorDialog Composable, the resetAskCloseBehavior helper, and the per-iteration
reset call: the alert's lifecycle is now bounded by AlertManager's single slot, so a crash
mid-dialog gets cleanly overwritten by the crash report.
* desktop: reset closeBehavior with 'Reset all hints'
Generalises AppPreferences.hintPreferences to a heterogeneous List<HintPref>
so non-Boolean prefs can participate. Adds closeBehavior to the list, so
'Reset all hints' brings the first-close dialog back.
* desktop: skip muted profiles in tray unread sum
Active profile still counts so the user can see their own unread; non-active
muted profiles contribute zero.
* desktop: dark-theme tray icons
Adds ic_simplex_tray_light and ic_simplex_tray_dot_light — copies of the
existing tray SVGs with the navy back-X swapped to white. Picks the variant
via isInDarkTheme() so the icon stays visible against dark tray backgrounds.
Detect the substring /team anywhere in Grok's AI reply (per-message and the
initial post-join reply) and run the same escalation as a customer /team:
invite the team members and switch the conversation to TEAM-PENDING. The reply
itself is still posted to the chat.
* android, desktop: constrain image height in layout
Clamp the image preview Box's aspect ratio so it never goes
below 1/2.33 (matching the height cap already enforced by
PriorityLayout). Prevents tall image previews from overflowing
into the caption area below.
Analogous to iOS #6732.
* plans: justify image text overlap fix
Chat errors emitted via the Haskell `eToView` path (e.g. agent errors
on stale connections after a peer deletes a chat) were caught by the
broad `except Exception` arm in the bot receive loop, producing an
ERROR log with a full traceback for routine soft errors. Match the
desktop client policy (SimpleXAPI.kt:3332-3340): catch ChatAPIError
separately, escalate CRITICAL agent errors to ERROR, log the rest at
DEBUG.
* docs: simplex-chat-python design and implementation plan
* bots: Python wire types codegen
* simplex-chat-python: package scaffold
* simplex-chat-python: native libsimplex loader
* simplex-chat-python: async FFI wrappers
* simplex-chat-python: ChatApi with 49 api methods
* simplex-chat-python: Bot class with decorators and dispatch
* simplex-chat-python: install CLI, example bot, README
* simplex-chat-python: audit fixes
* bots: regenerate API docs and types
Catches up the markdown, TypeScript and Python codegen outputs with two
upstream schema changes:
- APIConnectPlan.connectionLink became optional (from sh/python-lib audit
fixes); cmdString and EBNF syntax now reflect optional parameter.
- APIAddGroupRelays command and CRGroupRelaysAdded/CRGroupRelaysAddFailed
responses added in #6917 (relay management). The TS and markdown outputs
were regenerated when #6917 landed but the Python types module only got
the new entries with this regeneration.
* core: refresh SQLite query plans after relay_inactive_at migration
The M20260507_relay_inactive_at migration (#6917 / #6952) shifted the
query plans that 'Save query plans' verifies. Regenerated via the test
that owns those snapshots; no behavioral change.
* bots: keep APIConnectPlan connectionLink as required parameter
The prior audit-fixes commit changed the syntax expression to `Optional ...`
because the Haskell field is `connectionLink :: Maybe AConnectionLink`.
That misrepresents the API contract: the `Maybe` is purely an internal
signal for link-parsing failure (the handler returns `CEInvalidConnReq`
on `Nothing`), not API-level optionality. Callers MUST always pass a
connection link.
Revert the syntax expression to `Param "connectionLink"` and add a
comment so the intent is preserved next time someone audits.
Regenerates COMMANDS.md, commands.ts and _commands.py to match.
* desktop: pick a free port for the call server if 50395 is in use
startServer() bound a hard-coded port (50395); when it was already in use,
NanoWSD threw "BindException: Address already in use: bind" and the call
failed. It now falls back to an OS-assigned free port, and WebRTCController
opens the browser at the actually-bound port (server.listeningPort) -- still
50395 in the normal case, so browser camera/mic permission stays put.
* plans: justify call server port-bind fix
* core: keep whitelisted query parameters when removing link tracking
In safe mode, "remove link tracking" stripped any query parameter whose
name started with a known tracking prefix in qsSafeBlacklist, ignoring
qsWhitelist. So "list" (e.g. YouTube playlist links) was dropped because
"li" (LinkedIn) is a prefix of it, and github's "ref" was dropped too.
Make the safe-mode filter consult the whitelist, like the other branches.
* docs: plan for keeping whitelisted query parameters when removing link tracking
Design doc for the safe-mode sanitizeUri change (PR #6965): why "?list=" was
stripped from YouTube links, the root cause (safe mode ignoring qsWhitelist),
the fix, what it does/doesn't change, and alternatives considered.
ciBotCommand's regex was unanchored, so a customer message like
"follow/read blog posts?" parsed as a /read command and the Grok
handler silently dropped the message. Anchor the regex with ^ so a
command requires `/` at the start of the (trimmed) message.
In the support bot, filter customer command parsing by the registered
keyword set: any unknown `/word` from a customer (e.g. /help) is now
routed as plain text instead of being silently dropped by Grok. This
also makes /grok when Grok is disabled behave consistently as text,
removing the previous ad-hoc workaround.
* plan: delete channel messages
* core: allow deletion of own messages in public groups in channels to moderators-owners
---------
Co-authored-by: Evgeny @ SimpleX Chat <259188159+evgeny-simplex@users.noreply.github.com>
* support bot: take Grok initial context as messages array
Generalizes GrokApiClient to take a list of seed messages instead of a
single system prompt. Behavior is unchanged.
* support bot: accept YAML transcript in --context-file
Plain text → single system message (existing behavior).
`.yaml`/`.yml` → parsed as harness transcript; only system and
assistant turns are included.
* desktop: keep text selection on the originally selected message when a new message arrives or is sent
Selection stored positional indices into the merged-items list. When a new
message was appended, the reversed list shifted every index by one — but the
stored start/end indices did not — so the highlight slid onto neighboring
messages.
Anchor the selection to ChatItem IDs instead of list positions. Offsets are
already content-relative (character cursors in rendered text), so they stay
valid across list mutations. Positional indices are derived on read via
derivedStateOf, which keeps per-item reads O(1) amortized. If either
anchored item is removed from the list, a SideEffect synchronously clears
the selection so the copy button does not flash at a stale location.
* desktop: minimize selection fix — anchor ids in SelectionRange
Replaces the previous derivedStateOf-based approach with a surgical
diff: SelectionRange carries startItemId/endItemId alongside the
existing positional indices, and a SideEffect calls resyncIndices()
to translate ids back to current positions when the items list mutates.
All existing call sites of range.startIndex / range.endIndex remain
unchanged. Net diff vs master is +19/-2.
* plans: justify desktop text selection id-anchored fix
* android, desktop: open correct image in fullscreen viewer
Fullscreen image viewer occasionally opened a different image than
the one clicked. Root cause: when the LaunchedEffect probe at
ImageFullScreenView.kt:48-55 calls getMedia(initialIndex - 1) to check
whether a previous media item exists, getMedia returns null for both
"no item" and "item found but failed to load" (e.g. undecodable bytes,
missing file, crypto error). The probe treated null as "no previous
item" and called scrollToStart(), which rewrote initialChatId to the
chat's oldest media item - making the viewer display that oldest item
instead of the clicked one.
Fix: scrollToStart() no longer rewrites initialChatId. The pager is
still repositioned to page 0; getMedia(0) resolves against the
already-set initialChatId (the clicked item) and renders it correctly.
* android, desktop: regression test for fullscreen viewer anchor preservation
Drives the public providerForGallery interface: moves the anchor away from
cItemId via currentPageChanged, calls scrollToStart, then reads the anchor
back through onDismiss's scrollTo callback. The pre-fix code rewrote
initialChatId to the chat's oldest showable, which would surface as
scrollTo(2); the fix preserves the anchor and produces scrollTo(1).
* plan: design doc for fullscreen viewer wrong-image fix
Documents the pager state model, the root cause of the wrong-image bug,
why the one-line deletion in scrollToStart fixes it for both call sites,
and why the wider getMedia null-overload refactor is deliberately out of
scope for this fix.
* desktop: fix copying selected text in reports
Text selection in report items rendered a red reason prefix (e.g. "Spam: ")
before the user's comment but dropped the prefix when copying, because
selection offsets are in rendered-text space while copy extraction was
operating on ci.text / ci.formattedText directly.
Introduce itemPrefixText(ci) as the single source of truth for the rendered
prefix, and drive both selection copy and snap-to-segment from a unified
itemDisplaySegments list that prepends the prefix as a leading segment.
This also fixes mention/link snapping on the selection boundary inside
report comments.
* desktop: scope report-selection fix to report items
Inline a prefix preamble + offset shift in selectedItemCopiedText and
snapOffset instead of routing every item through itemDisplaySegments.
Non-report items now run the original pre-PR loop unchanged; reports
emit the selected slice of the rendered prefix and shift body offsets
by prefix.length.
* desktop: simplify report selection arithmetic
Selection offsets are in display-text space, which already includes the
leading itemPrefixText for reports. Treat the prefix as the leading
display segment and seed displayOffset with prefix.length, instead of
shifting body offsets by prefix.length in the inner loop and gating
snapOffset on offset <= prefix.length.
The inner loop body of selectedItemCopiedText becomes identical to
pre-PR for non-reports (prefix is "" so displayOffset starts at 0),
and snapOffset reduces to a one-line seed change. Same fix, smaller
diff, fewer intermediate variables.
* desktop: drop helper, inline report-prefix in selection only
Revert itemPrefixText helper extraction (TextItemView.kt and
FramedItemView.kt back to pre-PR). Inline the report-prefix expression
at its two use sites in TextSelection.kt directly.
PR diff is now confined to TextSelection.kt: +13/-6.
* desktop: extract itemPrefixText, drop dead defensive code
Re-introduce itemPrefixText(ci) helper in TextItemView.kt and migrate all
four sites that compute the report prefix (FramedItemView,
ChatPreviewView, TextSelection x2). The prefix expression now has one
definition and one place to change.
Also drop the unreachable sel.first.coerceAtLeast(0) on the prefix-slice
append — selectedRange guarantees sel.first >= 0.
* plans: justify desktop fix for copying selected text in reports
Add 2026-05-08-fix-select-in-reports.md covering the problem, the offset
flow, the minimal structural change (seed displayOffset with prefix.length),
the itemPrefixText single-source-of-truth migration across the four
prefix sites, the verified edge-case table, and the rollback path.
* desktop: fix RTL text rendering under the send button (#4137)
The chat composer's text field reserved 50dp on the wrong horizontal side
when an RTL message was typed under an LTR system locale: BiDi auto-detection
right-aligned the text onto the BottomEnd edge where the send button sits,
hiding the first characters as they were typed.
The padding was originally written inside the CompositionLocalProvider(
LocalLayoutDirection provides Rtl) scope (#4675), where start resolved to
the right edge for RTL paragraphs. The "edge to edge design" refactor
(#5051) lifted the modifier out of that scope onto the outer BasicTextField,
so start began resolving against the global LTR direction and the
reservation drifted to the left.
Always reserve on the global end - the same side Alignment.BottomEnd in
SendMsgView resolves to - so the reservation tracks the send button
regardless of locale or typed-text direction. Behavior is byte-identical
for LTR text and for any RTL-locale combination; only the buggy
"RTL text + LTR system locale" pair changes.
* desktop: minimise diff of RTL fix to 2 lines (#4137)
The previous commit (bfc111cc6) renamed/removed several helper locals
and rewrote the comment block alongside the behaviour change. The
behaviour-changing part is just two lines: making startPadding always
0.dp and endPadding equal to startEndPadding.
Restore the surrounding code (startEndPadding name, startPadding decl,
PaddingValues argument, .padding modifier, and the original two-line
comment) to its master form so the PR's only effect on master is the
two-line fix.
Behaviour: cases 1, 3, 4 of the locale x text matrix are byte-identical
to master. Only case 2 (LTR locale + RTL text) flips the reservation
from the wrong side to the correct side.
* plans: desktop RTL composer fix (#4137)
* plans: align with surgical 2-line fix in PR (#4137)
* bots: document APIGetChats command and CRApiChats response
* bots: regenerate API docs and TypeScript types
* simplex-chat-nodejs: add apiGetChats
* support bot: avoid OOM on large databases
apiListGroups / apiListContacts return every record in one response and
overflow V8's string allocation on large DBs. Replace list-then-find-by-id
patterns with apiGetChat(type, id, 0) lookups, and the one genuine scan
(refreshAllCards) with paginated apiGetChats, count=1000.
* support bot: update test assertions to match current message text
* bots: simplify PaginationByTime, expose only PTLast
* simplex-chat-nodejs: bump types and nodejs versions
another-simple-pixel