(session-state): feed remote sessions through the remote-ssh adapter - #267
Merged
Merged
Conversation
Step 3 of #246. remote-activity-ui.js keeps one createSessionState('remote-ssh') per remote session id, fed by the watch channel (transcriptTouched + busy, decay without arming response-ready), the descriptor (status, liveness) and the attach state; it hands the snapshot to the projection file instead of touching classes. Local and remote rows now share one projection path.
This was referenced Sep 11, 2026
Merged
Merged
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 3 of #246, after #266.
What
public/remote-activity-ui.jsbecomes theremote-sshadapter: one persistentcreateSessionState('remote-ssh')per remote session id, pruned with the decay timers. Ports fed: watch channel →transcriptTouched+busy:true; the 20 s decay →busy:falsewitharmReady:false(a remote row never gets.response-ready); descriptor →descriptorStatus(status, at)andliveness:'alive'when the host's ALIVE-filtered list carries the session (session.remoteDescriptorSeen, one line inmain.js annotateRemoteAttachable; absence staysunknown, neverdead); attach/detach →attached, driven from the per-row PTY signal inapp.js updateRunningIndicators.public/session-activity-dom.jsgainsapplyStateClasses(sessionId, snapshot); the adapter never writes classes (lint from (session-state): pure domain module, single DOM writer, enforced by lint #266 still holds).session-activity.jsare still fed in parallel for two readers not migrated yet (sidebar initial paint, grid-card dot) — same inputs, so the projections cannot disagree; listed in the context note's migration status.session-state.md(adapter section, ports table, status "steps 1-3 done"),session-cache.mdpointer.Proof
test/remote-session-adapter.test.js: event → busy, decay → idle without response-ready, descriptor → liveness/status, attach/detach, seed within the decay window, no-op withoutremoteAlias.armReady:trueturns red the new no-response-ready test and the pre-existingremote-activity-ui.test.jscase; reverted.task check: 1182 + 119 pass, 0 fail, pre-existing skips.