docs(desktop): repoint comments at the modules that now own the code

Comments naming gateway-event.ts, chat-messages.ts and hermes.ts as the
place to look, for files those symbols no longer live in.
This commit is contained in:
Brooklyn Nicholson
2026-08-19 03:34:50 -05:00
parent 5a027a0081
commit 7ed3a5cbe2
4 changed files with 8 additions and 8 deletions
@@ -2,7 +2,7 @@
// usage bands. Each trigger emits ONE synthetic `notification.show` /
// `notification.clear` gateway event through the real fan-out
// (`emitLocalGatewayEvent`), so it exercises the actual dispatcher branch in
// `use-message-stream/gateway-event.ts` — toast render, key-replacement
// `use-message-stream/gateway-event/status.ts` — toast render, key-replacement
// escalation, TTL self-dismiss, native OS notification, and billing re-poll.
//
// Installed only under `import.meta.env.DEV` (see contrib/wiring.tsx), so none
@@ -94,7 +94,7 @@ export function rebindSurvivorRowIds(messages: ChatMessage[], survivorRowIds: Su
/**
* Renderer-synthetic message ids (`${timestamp}-${index}-${role}` from
* chat-messages.ts, plus older `user-…` / `assistant-…` shapes). Gateway
* chat-messages/hydration.ts, plus older `user-…` / `assistant-…` shapes). Gateway
* history never carries them — only durable `row_id` / platform message_id.
*/
export function isSyntheticRendererId(messageId: string | undefined): boolean {
+5 -5
View File
@@ -3,11 +3,11 @@ import { atom } from 'nanostores'
// Event-driven "backend data changed" signals — the workspace-events twin for
// gateway-side state. The change watcher in tui_gateway broadcasts
// `pet.changed` / `cron.changed` / `sessions.changed` when its on-disk
// signatures move (see server._broadcast_watched_changes), gateway-event.ts
// routes them here, and the surfaces that used to poll (cron sidebar/page,
// messaging lists, pet sprite, live session statuses) subscribe to these ticks
// and refresh — so they move exactly when the backend acts and stay idle
// otherwise.
// signatures move (see server._broadcast_watched_changes), the gateway-event
// lifecycle handler routes them here, and the surfaces that used to poll (cron
// sidebar/page, messaging lists, pet sprite, live session statuses) subscribe
// to these ticks and refresh — so they move exactly when the backend acts and
// stay idle otherwise.
//
// `$changeEventsAvailable` is the compat gate: gateway.ready advertises
// `change_events: true` on backends that broadcast. Consumers keep their old
+1 -1
View File
@@ -8,7 +8,7 @@ import { $activeGatewayProfile, normalizeProfileKey } from '@/store/profile'
// picking a profile on one page carries to the next instead of resetting per
// page. `null` means "follow the app's active profile" — the default, which
// keeps single-profile users on the exact pre-existing code path (requests
// fall back to the app-wide active profile in hermes.ts `profileScoped`).
// fall back to the app-wide active profile in api/client.ts `profileScoped`).
export const $settingsScopeOverride = atom<null | string>(null)
// The profile the settings pages are currently editing (a concrete key).