feat(studio): harness transport — daemon + controller client modules - #970
Closed
jtenniswood wants to merge 1 commit into
Closed
feat(studio): harness transport — daemon + controller client modules#970jtenniswood wants to merge 1 commit into
jtenniswood wants to merge 1 commit into
Conversation
src/lib/harness lands whole and final: client.ts (the transport monolith — daemon plane, controller plane, and the RFC-9457 HarnessApiError machinery every satellite assumes), wire.ts, watch.ts (the ADR 0250 SSE grammar with cursor-resumed reconnects), and the learning / learned-skills / dream / storage / debug satellites, each with its colocated vitest suite (server-info.ts waits for its only consumer, the About card, later in the series). One deliberate addition over the original branch: client-surface.test.ts, an export-pin smoke test enumerating the transport surface. Controller-plane functions whose UI consumers land later in the series exist here without a caller; the pin makes that surface knip-visible through a test entry — a permanent, honest guard against export drift instead of a temporary ignore. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jtenniswood
added
enhancement
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
2 participants
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.
Stack 5/21 — Studio: harness transport
src/lib/harness/whole and final — the browser-side client modules over the proxy routes from PR 3, decoding through the protocol seam from PR 4. Transport only; no UI change.client.ts— the transport monolith (daemon plane + controller plane + the RFC-9457 typed-error machinery,HarnessApiError): landed once at its final state rather than regrown across ten PRs. Controller-plane functions whose routes land in PRs 9/11 exist here without a UI caller yet — guarded honestly (below).wire.ts,watch.ts(the ADR 0250 SSE grammar + cursor-resumed reconnect budget), and the satellites:learning,learned-skills,dream,storage,debug— each with its colocated vitest suite (server-info.tswaits for its only consumer in PR 11).client-surface.test.ts, an export-pin smoke test enumeratingclient.ts's 53 public exports. It makes the not-yet-consumed transport surface knip-visible through a test entry — a permanent, honest guard against surface drift instead of a temporary knip ignore. (Called out as a deviation in the series' closing parity sweep.)Part of the stacked landing of #618.
🤖 Generated with Claude Code