@danxbot/ui 7.9.3 → 7.9.6

package/dist/types/index.d.ts

@@ -119,7 +119,7 @@ export { applyCalendarDelta, calendarDragResult, createdEvent, describeTarget, r
 export { EVENT_PALETTE, DEFAULT_PALETTE_KEY, isPaletteKey, paletteFor, } from "./components/calendar/palette";
 export { cellLabel, eventLabel, formatDateRange, longDate, monthTitle, timeOfDay, weekdayName, zoneLabel, } from "./components/calendar/format";
 export { initialFocusDay, isInMonth, nextDayForKey, useGridNavigation, type GridNavigation, type GridNavigationOptions, } from "./components/calendar/use-grid-navigation";
-export { AmbiguousTimeError, addDays, addDuration, addMonths, atMidnight, atTime, comparePlainDate, dayFraction, dayLengthMs, dayOfWeek, daysBetween, daysInMonth, endOfMonth, hoursInDay, instantAtFraction, instantToPlainDate, instantToPlainDateTime, isSameDate, isoDateString, isoDateTimeString, monthGridDays, nextDay, offsetAt, parsePlainDate, plainDateTimeToInstant, startOfDay, startOfMonth, startOfWeek, weekDays, type CalendarDuration, type Disambiguation, type Instant, type PlainDate, type PlainDateTime, type TimeZone, } from "./lib/time";
+export { AmbiguousTimeError, addDays, addDuration, addMonths, atMidnight, atTime, comparePlainDate, dayFraction, dayLengthMs, dayOfWeek, daysBetween, daysInMonth, endOfMonth, hoursInDay, instantAtFraction, instantToPlainDate, instantToPlainDateTime, isSameDate, isoDateString, isoDateTimeString, monthGridDays, nextDay, offsetAt, parsePlainDate, plainDateTimeToInstant, relativeAge, startOfDay, startOfMonth, startOfWeek, weekDays, type CalendarDuration, type Disambiguation, type Instant, type PlainDate, type PlainDateTime, type TimeZone, } from "./lib/time";
 export { allDayBandSegment, dayKey, daySlots, isAllDay, packBand, packLanes, snapFractionToInstant, timeSegments, timedBandSegment, type AllDayEvent, type BandInput, type BandOptions, type BandPlacement, type BandResult, type BandSegment, type CalendarEvent, type CalendarEventId, type CalendarView, type DaySlot, type DragKind, type EventDraft, type EventPalette, type LaneInput, type LaneOptions, type LanePlacement, type PaletteEntry, type TimeSegment, type TimedEvent, type VisibleRange, } from "./lib/calendar";
 export { RBACProvider, useRBAC, AccountMenu, DevToolsPopover, RolePermissionMatrix, ProfilePage, RolesPermissionsPage, type RBACProviderProps, type RBACHookResult, type AccountMenuProps, type DevToolsPopoverProps, type RolePermissionMatrixProps, type Permission, type Role, type User, type Team, type TeamMembership, } from "./components/rbac";
 export { UseCaseCard, RoadmapItemCard, RoadmapSwimlaneBoard, UseCaseLedgerPage, RoadmapPage, PhaseManager, TrackManager, deriveRoadmapItemStatus, isFullyBuilt, isUnbuilt, trackIds, trackProgress, toneForIndex, CATEGORY_TONES, type Domain, type Phase, type Track, type RoadmapItem, type RoadmapItemStatus, type UseCase, type UseCaseStatus, type UseCaseDecision, type UseCaseCardProps, type RoadmapItemCardProps, type RoadmapSwimlaneBoardProps, type UseCaseLedgerPageProps, type RoadmapPageProps, type PhaseManagerProps, type TrackManagerProps, } from "./components/roadmap";

package/dist/types/lib/realtime/registry.d.ts

@@ -82,6 +82,38 @@ export declare class SubscriptionRegistry {
      * never touch realtime at all.
      */
     start(): void;
+    /**
+     * The document became visible again, or the page was restored from the
+     * back/forward cache — either way, a gap of UNKNOWN length just ended.
+     *
+     * `pusher:subscription_succeeded`/`state_change` (what `onConnectionState`
+     * listens for) is the transport TELLING us the socket dropped and came
+     * back. It is not the only way a gap happens: the OS suspending the
+     * machine, or the browser freezing a backgrounded tab under memory
+     * pressure, pauses this process's OWN timers along with everything else —
+     * including whatever ping/pong loop the transport uses to notice its own
+     * connection died. A transport that never got to run its detection code
+     * has nothing to report, so `connectionState()` can read "connected"
+     * throughout a gap the socket did not actually survive, and `tick()`'s own
+     * `isDead()` check — which trusts that string — has nothing to catch.
+     *
+     * Pusher has no event replay. Broadcasting is also gated server-side on a
+     * short-TTL registration (`PusherSubscriptionService`, 300s) that a long
+     * enough gap can outlive on its own. Either way, "did we actually miss
+     * anything" has no answer worth computing — the same reasoning
+     * `onConnectionState`'s reconnect branch already acts on — so becoming
+     * visible again is treated exactly like a reconnect: every entry is
+     * resubscribed (which the SubscriptionRegistry itself dedupes against
+     * one that is still genuinely healthy — a resubscribe is bounded, cheap,
+     * and correctness-preserving even when it turns out to have been
+     * unnecessary), and the epoch bumps on each success, which is what
+     * drives every mounted read (`reads/refetch.ts`'s `onEpoch`) to reissue
+     * the request it already made.
+     */
+    private onResume;
+    private handleVisibilityChange;
+    /** `event.persisted` is a bfcache restore — a full page resume with no `visibilitychange` of its own. */
+    private handlePageShow;
     /**
      * Stop the timers. REVERSIBLE, and it keeps every entry and every channel.
      *

package/dist/types/lib/time/index.d.ts

@@ -1,3 +1,4 @@
 export { AmbiguousTimeError, isoDateString, isoDateTimeString, type CalendarDuration, type Disambiguation, type Instant, type PlainDate, type PlainDateTime, type TimeZone, } from "./types";
 export { addDuration, dayFraction, dayLengthMs, hoursInDay, instantAtFraction, instantToPlainDate, instantToPlainDateTime, nextDay, offsetAt, plainDateTimeToInstant, startOfDay, } from "./zone";
 export { addDays, addMonths, atMidnight, atTime, comparePlainDate, dayOfWeek, daysBetween, daysInMonth, endOfMonth, isSameDate, monthGridDays, parsePlainDate, startOfMonth, startOfWeek, weekDays, } from "./plain";
+export { relativeAge } from "./relativeAge";

package/dist/types/lib/time/relativeAge.d.ts

@@ -0,0 +1,14 @@
+/**
+ * A moment's age in words: "just now", "4m ago", "4h ago", "1d 6h ago",
+ * "2w ago".
+ *
+ * Stays two-unit only in the day range (a message from earlier today reads
+ * as "6h ago", not "0d 6h ago") — days-plus-hours is the one range where a
+ * single unit throws away information a reader of a chat transcript actually
+ * wants ("this morning" vs "yesterday afternoon" are different facts, and
+ * "1d ago" collapses both). Beyond a week it drops to whole weeks, same as
+ * every sibling formatter in this codebase — nobody needs "9d ago" instead
+ * of "1w 2d ago", and nobody needs either instead of a calendar date, but a
+ * chat message's hover row has no room for a calendar date, so weeks it is.
+ */
+export declare function relativeAge(when: string | number | Date): string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danxbot/ui",
-  "version": "7.9.3",
+  "version": "7.9.6",
   "type": "module",
   "description": "Danxbot — a domain-agnostic React design system with motion as a first-class primitive.",
   "license": "MIT",