Diamond polish round K: twelve owner refinements + superseded-steer count fix #35
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/observatory-diamond-polish-nkyk20260925"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Owner morning-coffee round K — twelve subtle-but-visible refinements plus the two round-J validation findings.
The twelve items
⏳ ZCode chat residency cycle: …now lives in the header's right cluster beneath the mute button/update stamp (it describes ZCode, not the observatory).… · 12s agobeside the update time, ticking every second off the poll clock.!importantkeeps the hovered row's glow above the transient family wash.Turns+Tokens in/outrun-on), fixed columns enlarged so the action column is tight (air ~20px at 1132px table).hide harness noise(drawer meta line + modal footer), one shared switch persisted inlocalStorage(zdo-follow), both checkboxes mirror each other.Send to sessionas upright stacked letters in two slim columns, stretching the prompt's full height (prompt min-height 112px — the reclaimed dead air); Enter still sends.family.parentTitleadded to the API).Round-J validation findings
_STEERSkeeps only the newest steer per session, so a superseded (replaced-record) dispatcher still running was invisible toqueueDepth.inFlight/rowsteerQueue.inFlight("2 in flight" read as "1 queued"). Every spawn is now tracked (_STEER_SPAWNS, pruned on read) and both counters count all live dispatchers of the session.Evidence
/tmp/pinky-polish3-evidence/(max-width + 390px passes per item), results inresults-roundk.json.queueDepth.inFlight = 2, rows parity2; after killing the dispatchers →0.py_compile+--helpboot check green (forge CI lane).