id(web): cursor presence UX remainder — tooltip modes, pin/unpin, lifecycle logging #1790

Activity

1. dezren39

   added

   app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)

   on Oct 28, 2026
2. developing-today commented on Oct 28, 2026

   

   developing-todayBot

   on Oct 28, 2026 – with developing.today

   Contributor

   More actions

   CODE-730
3. github-actions

   assigned

   dezren39

   on Oct 28, 2026
4. dezren39

   added

   kind/featureNew feature or capability requestNew feature or capability request

   source/queue-workerFiled or worked by the queue/worker pilotFiled or worked by the queue/worker pilot

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   priority/lowNice to have; do when convenientNice to have; do when convenient

   effort/mMedium: expected under 1 day of workMedium: expected under 1 day of work

   meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels added

   on Oct 28, 2026
5. dezren39 commented on Oct 28, 2026

   

   dezren39

   on Oct 28, 2026

   MemberAuthor

   More actions

   Intake review

   • Still live: filed this hour as a split from rollup id: TODO.md backlog rollup — small ideas not yet covered elsewhere #1294 (queue triage task 2544, judged at main HEAD e561ab5); cursor fading/strobing/hover already exist in pkgs/id/web/src/cursors.ts and are out of scope — tooltip modes, pin/unpin, minimize/restore, and lifecycle logging are not implemented. Confirmed live.
   • Related: parent rollup id: TODO.md backlog rollup — small ideas not yet covered elsewhere #1294; sibling id(web): settings — client id shows 0s, name propagation to cursors, theme label layout #1792 (settings/name propagation to cursors) touches the same presence surface.
   • Notes: pure web-UI remainder work with existing test infrastructure at web/src/; the connection-liveness verification item (cursor visibility keyed to websocket liveness, not pointer idleness) is a behaviour check worth doing first since it may already hold.
   • Risks: tooltip mode state interacts with pinned/minimized per-cursor lists — state model first, or the modes will fight each other.
   • Suggested approach: verify the liveness item, then modes + pin/unpin behind the existing cursors module, lifecycle logging last.

   🤖 Agent note · filed

   • Agent: fleet monitor
   • Session / ID: repo-fleet-monitor run 2026-10-28 15:19 CDT
   • Found via: monitor reconciliation
   • Task: Intake enrichment — labels normalized, live status verified
   • Expectation: effort/m; done = labels + this review + meta/enriched applied
6. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   on Nov 3, 2026
7. dezren39 commented on Nov 3, 2026

   

   dezren39

   on Nov 3, 2026

   MemberAuthor

   More actions

   agent-note:v1
   state: triaged (coverage pass)
   Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 30 (priority/low). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
   Found via: coverage pass 2026-11-03
8. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 3, 2026
9. dezren39 commented on Nov 3, 2026

   

   dezren39

   on Nov 3, 2026

   MemberAuthor

   More actions

   Triage — still live at main 9a1fe42

   Verified against fresh origin/main = 9a1fe429c8b4b6ece5fcdf1587dfdf022c63ffe6 (2026-11-03).

   Still live. None of the four remaining-scope items exist at current main:

   • pkgs/id/web/src/cursors.ts still only does opacity fade / strobe / hover restore (FADE_START_MS 30s, FADE_END_MS 60s, HIDE_MS 5m in cursor-utils.ts). No tooltip mode state, no pin/unpin, no minimize/restore lists.
   • git grep -ni "tooltipMode|minimiz|pinned|presenceLog" -- pkgs/id at main has no hits in the presence surface (only unrelated vendor/example matches).
   • Lifecycle logging: one client console.log("[cursors] Removing stale cursor:", clientID) at cursors.ts:296. Nothing for first-inactive / minimum-reached / hover / unhover, and no server-side presence lifecycle logs.
   • No open PR implements any of it (gh pr list --state open for cursor/presence returns only fix(id): canonicalize presence channels before cap (#4404) #4571 presence-channel dedup, unrelated).

   Liveness item — verified, and it currently fails the desired behaviour. Inactivity is pointer/selection idleness, not connection liveness:

   • Client lastUpdate is set only when a CURSOR message (msg 4) arrives (cursors.ts:836-847); opacity and hiding derive from that age (cursors.ts:542-548 + getOpacityForAge).
   • The client sends CURSOR only on selection/cursor change (collab.ts sendCursor). The periodic empty-text "pong refresh" only dispatches an empty transaction to re-render decorations and replies with empty text (collab.ts:643-647) — it does not refresh lastUpdate.
   • Server tracks connection liveness separately (last_activity + ping/pong, collab.rs:991-1100) and rebroadcasts existing cursors with idle_secs only to a newly joined client (collab.rs:944-965).

   => A connected client that does not move for 5 minutes has its cursor hidden from everyone. So this is a real behaviour change, not a documentation check.

   Scope / ordering for the implementing PR (fits effort/m):

   1. State model first — one presence-UI state (tooltipMode: full | minimal | hidden, pinned set, per-mode minimized set) as a pure module with tests in the existing web/src/*.test.ts pattern. Modes, pin and minimize interact, so fix the state model before UI.
   2. Tooltip modes — full / minimal (cursor only, tooltip on hover ≥1s) / hidden (tracked but not shown; pinned exempt).
   3. Tooltip interaction — click-to-enlarge plus the 1s revert chain big → tooltip → minimal; per-cursor minimize/restore for full and minimal; pin/unpin from the big tooltip.
   4. Liveness fix — refresh lastUpdate on a connection-liveness tick (server empty-text ping/pong or a presence heartbeat) so a connected idle client stays visible; keep idle_secs backdating for initial load. Document the liveness basis in the PR.
   5. Lifecycle logging last — client lines for first-inactive / minimum-reached / removed / hover / unhover, plus matching server-side tracing in the collab.rs presence paths.

   Blockers: none technical. Step 4 depends on step 1's state model; step 5 last. Sibling #1792 (settings/name propagation) touches the same presence surface but is separable — this issue does not need to wait on it. Parent rollup #1294 is closed; this issue stands alone. Labels stay kind/feature, app/id, effort/m, priority/low.
10. dezren39

    removed

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    on Nov 3, 2026