Pinky AAAAA: the growth cure — indexes + first paint + action latency (v1.112.0) #146

Merged
ClaudiuSchuster merged 1 commit from oss-oo/pinky-aaaaa-growth into main 2026-10-25 10:56:53 +00:00
Owner

RV frame + owner global note: 3 indexes (idempotent startup migration), LIMIT pushdown (EXPLAIN-proven), first-paint on the response cache (re-measured 4303ms→264ms), UI-action latency + optimistic dismiss/retry + ghost cards + the V-F1 acceptedMs sourcing fold. Validated SHIP (measurements re-measured independently).

RV frame + owner global note: 3 indexes (idempotent startup migration), LIMIT pushdown (EXPLAIN-proven), first-paint on the response cache (re-measured 4303ms→264ms), UI-action latency + optimistic dismiss/retry + ghost cards + the V-F1 acceptedMs sourcing fold. Validated SHIP (measurements re-measured independently).
Pinky AAAAA: the growth cure — indexes + first paint + action latency (v1.112.0)
Some checks failed
Checks / Functional checks (pull_request) Failing after 56s
2248a69311
RV's verdict frame (binding): the transcript slowness is a GROWTH problem,
not a regression — the session DB's whole history ran with ZERO indexes on
message/part/session. The Owner refined: the pain is GLOBAL, so first paint
weighs at least as much as the excerpts.

A1 — ensure_query_indexes: the startup index migration (message(session_id,
sequence), part(session_id, message_id, sequence), session(time_updated));
prefix-aware (the desktop's newer schema satisfies the first two without
duplicates), idempotent, deferred honestly on read-only/locked DBs.

A2 — the query shapes: the transcript LIMIT pushdown (bounded slice BEFORE
the joins; the part join seeks the exact index prefix) + the first-paint
lean on the response cache (a CONVERGING boot primer + stale-while-
revalidate on unchanged keys, single-flighted; content mutations keep the
synchronous fresh path — G3 unchanged).

A3 — optimistic action acknowledgment (dismiss/retry/turn-retry settle the
card at the click; an honest refusal is the only resurrection), the
ghost-card law (cards die with their entry OR by owner choice), the strip
dismiss optimism, and the V-F1 fold: acceptedMs sourced from the
dispatcher's startedAtUtc (the honest 202 moment), never the file mtime.

Measured on the hermetic rig (quarter station census, BEFORE=v1.108.0 base
driven via ZDO_RIG_REPO/ZDO_RIG_PHASE): transcript cold 15114→24 ms, warm
189→23.5 ms, post-TTL serve 3123→28 ms, first paint 3491→318 ms (min of 3),
dismiss ack 127→5 ms (median of 5). Full table + EXPLAIN QUERY PLAN
transcripts in the round dossier; rig tests/rigs/aaaaa_growth_cdp.py.

Version note: the mission named v1.110.0; the sibling BBBBB took v1.110.0
(PR #145) and v1.111.0 (local tag) mid-round — the version guard forces
v1.112.0.
ClaudiuSchuster force-pushed oss-oo/pinky-aaaaa-growth from 2248a69311
Some checks failed
Checks / Functional checks (pull_request) Failing after 56s
to 42cb4b090a
Some checks failed
Checks / Functional checks (pull_request) Failing after 58s
2026-10-25 10:23:41 +00:00
Compare
ClaudiuSchuster force-pushed oss-oo/pinky-aaaaa-growth from 42cb4b090a
Some checks failed
Checks / Functional checks (pull_request) Failing after 58s
to 59701b2e94
All checks were successful
Checks / Functional checks (pull_request) Successful in 58s
2026-10-25 10:53:49 +00:00
Compare
ClaudiuSchuster deleted branch oss-oo/pinky-aaaaa-growth 2026-10-25 10:56:53 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
OSS-Singularity/zcode-dispatch-observatory!146
No description provided.