dsh-local-link 0.2.1 → 1.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,12 +2,58 @@
2
2
 
3
3
  All notable changes to this project are documented here.
4
4
 
5
+ ## 1.1.0 — 2026-09-07
6
+
7
+ `1.1.0` updates Local Link for DeepSeek Harness `0.1.2-rc.1` while preserving the existing trusted-private-LAN product and security boundary. It keeps the stock Harness client, session state, permissions, and live stream instead of introducing a second remote client.
8
+
9
+ ### Changed
10
+
11
+ - Migrated the browser client to the DeepSeek Harness `0.1.2-rc.1` Cordis context, API session controller, UI renderer/session services, session projections, and subagent contracts.
12
+ - Pinned the direct development contracts to the exact RC and moved the plugin's Cordis peer contract to `^4.0.2`.
13
+ - Kept the previous trusted-LAN scope after the RC removed method-specific transport tiers: Local Link now rejects configuration, credential, native Host-action, and agent-preset-authoring RPCs at its own gateway.
14
+
15
+ ### Fixed
16
+
17
+ - Revoking a paired device now immediately closes every open Local Link WebSocket tunnel authenticated by that device, while leaving other paired devices and `trusted-lan` connections untouched.
18
+ - The mobile appearance control now follows the left drawer transition instead of appearing abruptly while the drawer opens or closes.
19
+ - Current session statistics now round fractional token throughput consistently instead of exposing the raw floating-point tail.
20
+
21
+ ### Validated
22
+
23
+ - Passed the full TypeScript, test, build, peer-dependency, and package gates against the exact `0.1.2-rc.1` contracts.
24
+ - Passed all 98 automated tests across 16 test files, the production dependency audit with no known vulnerabilities, and `npm publish --dry-run` for `dsh-local-link@1.1.0`.
25
+ - Booted the installed `0.1.2-rc.1` Web profile with Local Link, completed pairing and native browser authentication through the Ethernet gateway, verified the loopback-only Settings RPC returns `403`, and revoked the test device.
26
+ - Verified the new client services in the live boot manifest, opened the desktop QR panel, and exercised the responsive AppFrame at `390 × 844` without browser console errors.
27
+ - Installed the packed `1.1.0` release into fresh `0.1.1-rc.2`, `0.1.1-rc.1`, and `0.1.0-rc.8` profiles. Every RC passed real-client Local Access, `390 × 844` responsive navigation, private-LAN pairing, authenticated HTTP and `/api/events.mux`, plus revoke with immediate socket closure and a subsequent `401`.
28
+
29
+ ## 1.0.0 — 2026-08-29
30
+
31
+ The first stable Local Link release. It keeps the focused same-LAN access and
32
+ responsive Harness-client scope established by the `0.2.x` previews, with an
33
+ exact compatibility matrix covering the current verified Harness release and
34
+ prerelease targets.
35
+
36
+ ### Fixed
37
+
38
+ - Added the native browser-authentication handoff required by DeepSeek Harness `0.1.2-alpha.1`, while preserving the separate Local Link device credential and the older release-candidate flow.
39
+ - Kept alpha boot-manifest batches aligned when withholding the remote native directory picker, and allowed the alpha's exact `/api/remote.mux` live-stream endpoint without widening the WebSocket allowlist.
40
+ - Made Current session tolerate alpha conversation summaries that omit the legacy `nodes` collection while continuing to resolve the selected model through Harness's native model directory.
41
+
42
+ ### Validated
43
+
44
+ - Verified pairing, current-session opening, live conversation streaming, responsive navigation, Current session, and subagent surfaces in an isolated checkout of DeepSeek Harness `0.1.2-alpha.1`.
45
+ - Reverified Local Access, one-use QR regeneration, and responsive navigation against DeepSeek Harness `0.1.1-rc.2`, `0.1.1-rc.1`, and `0.1.0-rc.8` using the same release source.
46
+
5
47
  ## 0.2.1 — 2026-08-29
6
48
 
7
49
  ### Fixed
8
50
 
9
51
  - Quoted the `trustedHosts` JavaScript expression in the bundled Cordis overlay so a clean npm installation parses and boots with the strict DSH patch-list YAML schema.
10
52
 
53
+ ### Validated
54
+
55
+ - Documented supported and verified Harness versions in a newest-first compatibility matrix.
56
+
11
57
  ## 0.2.0 — 2026-08-29
12
58
 
13
59
  ### Added
package/README.md CHANGED
@@ -1,16 +1,45 @@
1
1
  # dsh-local-link
2
2
 
3
- [![CI](https://github.com/DoNotEatMe/dsh-local-link/actions/workflows/ci.yml/badge.svg)](https://github.com/DoNotEatMe/dsh-local-link/actions/workflows/ci.yml)
3
+ [![CI](https://github.com/donoteatme/dsh-local-link/actions/workflows/ci.yml/badge.svg)](https://github.com/donoteatme/dsh-local-link/actions/workflows/ci.yml)
4
4
  [![npm](https://img.shields.io/npm/v/dsh-local-link.svg)](https://www.npmjs.com/package/dsh-local-link)
5
+ [![Awesome DSH Plugin](https://awesome-dsh-plugin.com/badge.svg)](https://awesome-dsh-plugin.com)
5
6
  [![license](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
6
7
 
7
- Lightweight, self-hosted [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin for paired LAN access and a practical Mobile View of the complete DSH Web interface.
8
+ Use the same [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) Web session from a phone, tablet, or another computer on your trusted private network. `dsh-local-link` adds one-time QR pairing and a responsive Mobile View to the stock DSH client—without a hosted relay, cloud account, native app, replacement chat UI, or second workspace picker.
8
9
 
9
- Open `Local access`, scan one QR code, and continue the desktop's currently selected Harness session from a phone, tablet, or another computer on the same private network. There is no hosted relay, tunnel provider, native application, account, replacement chat UI, or second workspace picker.
10
+ Open `Local access`, scan the QR code, and the paired browser arrives at the desktop's currently selected Harness session with the same live conversation, permissions, workspaces, and plugin surfaces.
10
11
 
11
- Version `0.2.0` also addresses the stock Web client's desktop-first behavior on narrow touch screens. It reorganizes the existing Harness interface into responsive drawers, compact session controls, and touch-friendly actions while keeping the same client, session, plugin slots, permissions, and live agent stream.
12
+ The `1.1.0` line supports DeepSeek Harness `0.1.2-rc.1` and keeps the stock Web client usable on narrow touch screens. It reorganizes the existing Harness interface into responsive drawers, compact session controls, and touch-friendly actions while keeping the same client, session, plugin slots, permissions, and live agent stream.
12
13
 
13
- > **Preview security boundary:** the gateway uses plain HTTP and is intended only for a trusted private network. Do not expose its port to the internet or use it on public Wi-Fi.
14
+ > **Security boundary:** the gateway uses plain HTTP and is intended only for a trusted private network. Do not expose its port to the internet or use it on public Wi-Fi.
15
+
16
+ <p align="center">
17
+ <img src="docs/images/local-access-qr.jpg" width="960" alt="DeepSeek Harness with dsh-local-link open: one-time QR pairing to the current stock Harness session">
18
+ </p>
19
+
20
+ <p align="center"><sub>One Harness session, paired directly across the trusted LAN.</sub></p>
21
+
22
+ ## Focused product scope
23
+
24
+ Local Link is intentionally a small LAN companion for the existing Harness Web client, not a general remote-access platform. Its purpose is to make one path dependable: open the Harness instance already running on a computer from another trusted device on the same private network, then use the same sessions and interface in a browser.
25
+
26
+ Development stays focused on:
27
+
28
+ - reliable same-LAN browser access to the current Harness Host;
29
+ - short-lived invitations and understandable paired-device lifecycle controls;
30
+ - responsive presentation of the stock client without duplicating Harness business logic;
31
+ - compatibility with registered Harness views, slots, permissions, themes, and session state;
32
+ - accessibility, localization, bounded diagnostics, and security hardening inside that boundary.
33
+
34
+ The following are deliberate non-goals:
35
+
36
+ - public-internet exposure, hosted relays, managed tunnels, or cloud accounts;
37
+ - a separate native phone or desktop application;
38
+ - a replacement chat client or fork of the Harness interface;
39
+ - independent workspace, file, or session synchronization outside Harness;
40
+ - a general-purpose remote extension runtime unrelated to opening the current Web UI.
41
+
42
+ This does not mean the plugin is finished or frozen. It means future changes should make the local browser path simpler, safer, more compatible, or easier to diagnose instead of widening the product into a different class of system.
14
43
 
15
44
  ## Install
16
45
 
@@ -25,10 +54,10 @@ dsh web
25
54
 
26
55
  ### Git clone — development checkout
27
56
 
28
- Requirements: Git, Node.js 22.19+ or 24+, Corepack, and a global `dsh` installation running DeepSeek Harness `0.1.1-rc.2`.
57
+ Requirements: Git, Node.js 22.19+ or 24+, Corepack, and a global `dsh` installation running a verified DeepSeek Harness version from the compatibility table below.
29
58
 
30
59
  ```shell
31
- git clone https://github.com/DoNotEatMe/dsh-local-link.git
60
+ git clone https://github.com/donoteatme/dsh-local-link.git
32
61
  cd dsh-local-link
33
62
  corepack pnpm install --frozen-lockfile
34
63
  npm run verify
@@ -38,6 +67,21 @@ dsh web
38
67
 
39
68
  The profile points at the checkout, so rebuild after changing client code and restart `dsh web` after Host-side changes.
40
69
 
70
+ ## Compatibility
71
+
72
+ Compatibility is checked against exact DeepSeek Harness versions—not inferred from a successful installation.
73
+
74
+ | DeepSeek Harness | Local Link status |
75
+ | --- | --- |
76
+ | `0.1.2-rc.1` | **Supported release** |
77
+ | `0.1.1-rc.2` | **Verified** |
78
+ | `0.1.1-rc.1` | **Verified** |
79
+ | `0.1.0-rc.8` | **Verified** |
80
+
81
+ All four rows were checked with the packed `1.1.0` release. The historical RC gate covers a clean Web profile, the real client, Local Access, pairing, authenticated HTTP and WebSocket traffic, revoke, and responsive navigation at `390 × 844`. `0.1.2-rc.1` remains the development baseline and receives the complete current-runtime gate.
82
+
83
+ Versions older than `0.1.0-rc.8` are untested and unsupported. New Harness versions are checked independently. See [Compatibility](docs/COMPATIBILITY.md) for the evidence and remaining real-device boundary.
84
+
41
85
  ## Use
42
86
 
43
87
  ### Open Harness on another device
@@ -45,21 +89,17 @@ The profile points at the checkout, so rebuild after changing client code and re
45
89
  1. Open the session you want on the computer.
46
90
  2. Click `Local access` at the bottom of the Harness sidebar.
47
91
  3. Scan the QR code or copy the one-time link to another device on the same network.
48
- 4. The first browser to use the invitation opens the full Harness UI at the selected session.
92
+ 4. The first browser to use the invitation opens the stock Harness client at the selected session. Host-level administration that Harness reserves for loopback remains unavailable remotely.
49
93
 
50
94
  The invitation is one-use, expires after five minutes by default, and is replaced immediately when `Generate another code` is selected.
51
95
 
52
96
  Phone and tablet browsers automatically receive Mobile View when the viewport is at most 834 CSS pixels wide. The same responsive behavior can be previewed with browser device emulation; no URL parameter, user-agent switch, or second client is involved.
53
97
 
54
- <p align="center">
55
- <img src="docs/images/local-access-qr.jpg" width="960" alt="DeepSeek Harness with the Local access QR panel, one-time link, and Paired devices shortcut">
56
- </p>
57
-
58
98
  ## Mobile View
59
99
 
60
100
  The stock Harness Web interface is difficult to operate on a phone: persistent desktop navigation consumes the viewport, session controls compete with the conversation title, several actions depend on hover or long press, and subagent information is too dense for a narrow screen. Mobile View makes that existing interface usable without introducing a second client or duplicating Harness business logic.
61
101
 
62
- | Stock narrow-screen behavior | Mobile View in `0.2.0` |
102
+ | Stock narrow-screen behavior | Mobile View in `1.1.0` |
63
103
  | --- | --- |
64
104
  | Desktop navigation competes with the conversation | Workspace and session navigation opens as a dismissible left drawer |
65
105
  | Session metadata crowds the header | Context, model, access, preset, activity, and export move into a compact right drawer |
@@ -75,6 +115,7 @@ The implementation changes presentation, not Harness ownership or behavior:
75
115
  - Current session opens from the header with context breakdown, model, workspace access, preset, activity, and session-log download;
76
116
  - child-agent status shows total and active counts, then opens the native nested catalog as a touch-friendly bottom sheet;
77
117
  - the Harness theme service powers a compact sun/moon action;
118
+ - desktop-only Settings and the nested Local access action are omitted from mobile navigation, while the appearance action remains available;
78
119
  - session and active-workspace menus stay immediately available on touch screens;
79
120
  - safe areas, scrollable tabs, bounded media, and virtual-keyboard behavior are adapted for narrow viewports;
80
121
  - plugin-owned modal drawers contain keyboard focus and return it to the invoking control when closed;
@@ -88,16 +129,16 @@ These previews are captured from the running Harness client at a `430 × 932` vi
88
129
 
89
130
  ### Permissions
90
131
 
91
- The remote browser inherits the selected Harness session's **Read only**, **Workspace write**, or **Full access** authority. Mobile View displays that value but does not create or weaken a permission layer. Hiding `Add workspace` is a usability constraint, not an authorization boundary.
132
+ The remote browser inherits the selected Harness session's **Read only**, **Workspace write**, or **Full access** authority. Mobile View displays that value but does not create or weaken a permission layer. This applies to ordinary session operations; Settings, credentials, native Host actions, and agent-preset authoring remain loopback-only. Hiding `Add workspace` is a usability constraint, not an authorization boundary.
92
133
 
93
- The responsive enhancements target viewports from 360 through 834 CSS pixels wide. The release matrix covers `360 × 800`, `390 × 844`, `430 × 932`, and `768 × 1024`, plus portrait/landscape checks on a real phone. See [Mobile View](docs/MOBILE_VIEW.md) for behavior, theme persistence, compatibility surfaces, and the complete acceptance checklist.
134
+ The responsive enhancements target viewports from 360 through 834 CSS pixels wide. The release matrix defines checks at `360 × 800`, `390 × 844`, `430 × 932`, and `768 × 1024`; release acceptance also requires portrait and landscape checks on a real phone. See [Mobile View](docs/MOBILE_VIEW.md) for behavior, theme persistence, compatibility surfaces, and the complete acceptance checklist.
94
135
 
95
136
  ### Manage trusted browsers
96
137
 
97
- Use `Paired devices` in the QR panel or open `Settings → Local access`. Each new browser starts as `My device`; its subtitle is detected automatically, for example `Phone · Chrome`, `Tablet · Safari`, or `Computer · Edge`.
138
+ On the Harness computer, use `Paired devices` in the QR panel or open `Settings → Local access`. Each new browser starts as `My device`; its subtitle is detected automatically, for example `Phone · Chrome`, `Tablet · Safari`, or `Computer · Edge`.
98
139
 
99
140
  - `Rename` changes display metadata only.
100
- - `Revoke` invalidates the browser credential for subsequent HTTP requests and reconnects.
141
+ - `Revoke` invalidates the browser credential and immediately closes its open Local Link WebSocket connections.
101
142
  - A cleared cookie, private window, new browser profile, or revoked device needs a new invitation.
102
143
 
103
144
  Browsers do not reliably distinguish laptops from desktop computers, so both are shown as `Computer`.
@@ -140,7 +181,7 @@ The gateway does not create a second Harness session. During first connection it
140
181
 
141
182
  Authorization uses a 256-bit random cookie credential. Only its SHA-256 hash is stored. The editable name and detected device/browser text never grant access.
142
183
 
143
- The LAN authority is declared through Harness's official connection `trustedHosts` contract. This enables ordinary session API and WebSocket traffic without pretending that the phone is loopback; Settings, credentials, native Host actions, and agent-preset authoring remain loopback-only.
184
+ The LAN authority is declared through Harness's official connection `trustedHosts` contract. This enables authenticated session API and WebSocket traffic without pretending that the phone is loopback. Because Harness `0.1.2-rc.1` authenticates the transport as a whole, Local Link itself rejects the configuration, credential, native Host-action, and agent-preset-authoring RPCs that earlier supported Harness builds kept loopback-only.
144
185
 
145
186
  ## Configuration
146
187
 
@@ -204,6 +245,7 @@ npm run verify
204
245
  Project documentation:
205
246
 
206
247
  - [Architecture and compatibility boundaries](docs/ARCHITECTURE.md)
248
+ - [Verified DeepSeek Harness compatibility](docs/COMPATIBILITY.md)
207
249
  - [Mobile View behavior and release matrix](docs/MOBILE_VIEW.md)
208
250
  - [Local diagnostics and event codes](docs/DIAGNOSTICS.md)
209
251
  - [Security model](docs/SECURITY.md)
@@ -212,24 +254,19 @@ Project documentation:
212
254
 
213
255
  ## Known limitations
214
256
 
215
- - LAN traffic is not encrypted in the current preview gateway.
216
- - Revocation blocks new requests and reconnects but does not yet terminate an already-open WebSocket.
217
- - The shortcut that opens a specific Settings section uses a small semantic compatibility bridge because Harness `0.1.1-rc.2` exposes `openSection` only to onboarding.
257
+ - LAN traffic is not encrypted; the current gateway uses plain HTTP.
258
+ - Revocation blocks new requests and reconnects and terminates every open Local Link WebSocket authenticated by the revoked device.
259
+ - A light/dark choice made from a remote browser is page-scoped in the supported Harness builds; reload returns to the Host preference and resolves `system` against the remote device.
260
+ - Invitations use the highest-ranked private IPv4 interface detected at startup; choosing among multiple LAN interfaces is not exposed yet.
261
+ - The shortcut that opens a specific Settings section uses a small semantic compatibility bridge because Harness does not expose a general settings-navigation service.
218
262
  - Harness's footer-action container needs a compatibility layout rule when the full-width Cordis action is present.
219
- - Compatibility is currently pinned to DeepSeek Harness `0.1.1-rc.2` and must be retested for each supported Harness release.
220
263
  - Mobile View targets viewports from 360 CSS pixels wide, but third-party fixed-width views, virtual keyboards, orientation changes, split-screen browsers, and operating-system text scaling still require real-device acceptance.
221
- - Plugin-owned buttons and text inputs use Harness `Button` and `Input` primitives and their semantic variants. Harness `0.1.1-rc.2` still has no public responsive-shell, spacing, or radius contract, so mobile geometry, responsive compositions, and the few missing primitive icons remain documented design-system compatibility risks.
264
+ - Plugin-owned buttons and text inputs use Harness `Button` and `Input` primitives and their semantic variants. Harness `0.1.2-rc.1` still has no complete public responsive-shell, spacing, or radius contract, so mobile geometry, responsive compositions, and the few missing primitive icons remain documented design-system compatibility risks.
222
265
 
223
266
  ## Development disclosure
224
267
 
225
268
  The initial implementation and documentation were developed collaboratively with OpenAI Codex. Changes remain subject to maintainer review, automated tests, security review, and the same contribution requirements as human-authored changes. No runtime AI service, telemetry, or generated-code dependency is included in the package.
226
269
 
227
- ## Acknowledgements
228
-
229
- The mobile UX research included the MIT-licensed [DSH Mobile](https://github.com/sorsama/deepseek-harness-mobile) project by its contributors. Its mobile navigation, session-details, subagent, and activity-status presentation helped inform the interaction direction used here.
230
-
231
- No DSH Mobile source code or assets are included in this package. Local Link implements its Mobile View independently in TypeScript and React, using the stock Harness client, design primitives, services, and plugin slots instead of shipping a replacement Android client.
232
-
233
270
  ## License
234
271
 
235
272
  [MIT](LICENSE) © 2026 dsh-local-link contributors.
package/SECURITY.md CHANGED
@@ -4,4 +4,4 @@
4
4
 
5
5
  Until a private reporting address is configured, open a GitHub Security Advisory in the repository. Include the affected version, deployment topology, reproduction steps, and expected impact.
6
6
 
7
- The current preview uses unencrypted HTTP on the local network. This is a documented limitation rather than a supported internet-facing deployment. See [docs/SECURITY.md](docs/SECURITY.md) for the complete threat model and safe-use boundary.
7
+ The current release uses unencrypted HTTP on the local network. This is a documented limitation rather than a supported internet-facing deployment. See [docs/SECURITY.md](docs/SECURITY.md) for the complete threat model and safe-use boundary.
@@ -8,7 +8,7 @@ The architecture follows six constraints:
8
8
 
9
9
  1. Keep the stock Harness listener loopback-only.
10
10
  2. Put the network boundary in a dedicated Host-side gateway.
11
- 3. Use Cordis lifecycle and Harness slots for all rendered UI; isolate the one settings-navigation compatibility bridge required by Harness `0.1.1-rc.2`.
11
+ 3. Use Cordis lifecycle and Harness slots for all rendered UI; isolate the settings-navigation compatibility bridge not covered by a public Harness service.
12
12
  4. Make automatic QR pairing and paired-device state explicit and revocable.
13
13
  5. Keep presentation text outside implementation code.
14
14
  6. Keep support diagnostics local, bounded, structured, and free of credentials or user content.
@@ -46,7 +46,9 @@ Configuration accepts only the wildcard `0.0.0.0` or an explicit private/loopbac
46
46
 
47
47
  After authentication, the gateway forwards the browser's original `Host`, `Origin`, referrer, and fetch-site headers to the loopback Harness listener. The Cordis profile patch supplies the gateway's current LAN authorities to the official connection module through its public `trustedHosts` option. Ordinary Harness API and WebSocket traffic can therefore pass the declared origin check without pretending to be loopback.
48
48
 
49
- The connection module separately rechecks privileged configuration, credential, native Host-action, and agent-preset-authoring methods with an empty trust extension. Those operations remain loopback-only. `tests/trust-boundary.test.ts` exercises this split against the real connection package: a trusted gateway authority reaches ordinary dispatch while every privileged method returns `403`.
49
+ Harness `0.1.2-rc.1` requires a native browser-authentication exchange. After Local Link pairing succeeds, the plugin asks the injected Harness connection service for an authenticated URL at the gateway origin, validates that the result stays on that origin, and lets the stock root consume the short-lived token. The gateway forwards Harness authentication cookies but strips its own device cookie before proxying, so the two credentials remain independent. Older supported builds that do not expose this service keep the direct-root redirect.
50
+
51
+ Harness `0.1.2-rc.1` authenticates the connection transport as a whole and no longer applies the older method-specific loopback tier. To preserve Local Link's established scope, the LAN gateway rejects the former privileged configuration, credential, native Host-action, and agent-preset-authoring RPCs before proxying. This applies equally to `pairing` and `trusted-lan`; enabling `trusted-lan` never grants those Host administration operations. `tests/trust-boundary.test.ts` exercises the RC Host/Origin and browser-authentication fence, while `tests/gateway.test.ts` pins the Local Link RPC restriction including the renamed RC Settings methods and encoded-path handling.
50
52
 
51
53
  ### Authentication state
52
54
 
@@ -64,11 +66,13 @@ The loopback administration route exposes list, clear, and a narrow allowlisted
64
66
 
65
67
  `src/client.tsx` registers two normal Harness contributions: a compact desktop `sidebar.footer.action` that shows a QR code and copyable one-time link, and a desktop-only `settings.section` that manages paired devices and the local diagnostic report. It does not replace the root layout. The desktop surfaces use plugin-owned classes and semantic selectors; version-sensitive stock-DOM hooks are isolated in `src/mobile-layout.tsx` and documented below.
66
68
 
67
- The Harness `sidebar.footer.action` contract is a list, but `0.1.1-rc.2` renders that list as a horizontal flex row while the stock Cordis action reserves `width: 100%` with `flex: none`. Without a compatibility rule, Cordis reduces later actions to zero width. Local Link orders its entry first and changes only the footer container that semantically contains `.dsh-local-link-footer` into a vertical stack. The same scoped rule normalizes the list gap and removes the following action's private top margin so Local access, Cordis, and Settings keep one visual rhythm. The selector is anchored on the plugin-owned class and accounts for the slot renderer's `display: contents` wrapper; it never names a generated Harness class.
69
+ The `0.1.2-rc.1` browser graph is a normal Cordis `Context`. Session state comes from `@deepseek-ai/dsh-api-session-controller/client`; React slot hooks are supplied by `@deepseek-ai/dsh-client-ui-session/client`, and slot ownership/rendering comes from `@deepseek-ai/dsh-client-ui-renderer/client`. Agent-preset display reads `SessionSummary.projectionValues.agentPreset`, while subagent types come from `@deepseek-ai/dsh-subagent/client`. The removed `@deepseek-ai/dsh-client-runtime` aggregate is neither injected nor imported.
70
+
71
+ The Harness `sidebar.footer.action` contract is a list, but the supported Web client renders that list as a horizontal flex row while the stock Cordis action reserves `width: 100%` with `flex: none`. Without a compatibility rule, Cordis reduces later actions to zero width. Local Link orders its entry first and changes only the footer container that semantically contains `.dsh-local-link-footer` into a vertical stack. The same scoped rule normalizes the list gap and removes the following action's private top margin so Local access, Cordis, and Settings keep one visual rhythm. The selector is anchored on the plugin-owned class and accounts for the slot renderer's `display: contents` wrapper; it never names a generated Harness class.
68
72
 
69
73
  The connection card is fixed to the viewport and positioned from the rendered Local access action. On desktop it opens just beyond the sidebar edge and remains vertically centered. Its final QR-state height is reserved before the pairing request resolves, so loading the QR cannot move the card after its first visible frame. On narrow or short viewports it is clamped to a 12 px viewport gutter and scrolls internally instead of moving footer actions or covering them.
70
74
 
71
- Harness `0.1.1-rc.2` keeps settings open state and section selection private inside its shell; the public `openSection` callback is only projected to onboarding steps. The popover's `Paired devices` shortcut therefore uses one bounded compatibility bridge: it clicks the semantic settings dialog trigger and then the nav row matching this plugin's own localized section label. The bridge uses no generated class names, mutates no DOM, and can be removed when Harness exposes a general settings-navigation service.
75
+ Harness keeps settings open state and section selection private inside its shell; the public `openSection` callback is not a general navigation service. The popover's `Paired devices` shortcut therefore uses one bounded compatibility bridge: it clicks the semantic settings dialog trigger and then the nav row matching this plugin's own localized section label. The bridge uses no generated class names, mutates no DOM, and can be removed when Harness exposes a general settings-navigation service.
72
76
 
73
77
  The Host plugin exposes the running gateway authorities as a Cordis service. `cordis.patch.yml` merges that service with `webRuntime.trustedHosts` before the stock connection module starts. Trust is therefore declared once on the Host; client code neither mutates `connection.isLoopback` nor carries an authentication marker.
74
78
 
@@ -88,9 +92,9 @@ The stock Settings dialog is intentionally not exposed inside the narrow mobile
88
92
 
89
93
  The compact appearance button is visually placed in the stock sidebar brand row without becoming part of the Harness brand action. A scoped mobile geometry rule changes the stock flexible brand button to a content-sized hit area and leaves the remaining row space to the separate appearance and sidebar-toggle controls. This keeps all three hit areas disjoint while preserving Harness's own buttons, actions, focus behavior, and tap highlight. Harness exposes no sibling slot in this row, so the compatibility rule identifies the stock CSS-module button by its semantic `_brand` class suffix; Harness upgrades must verify that hook.
90
94
 
91
- Theme persistence remains entirely owned by Harness SettingsScope. In Harness `0.1.1-rc.2`, the client Settings binder selects durable `host` storage only for loopback connections and `memory` storage for non-loopback connections. A phone can therefore change the theme for its current page, but reload creates a new remote SettingsScope and returns to the durable host preference—often `system`, which is then resolved using the phone's own color scheme. Local Link does not impersonate a loopback client and does not add a competing cookie or browser-storage preference. Persistent per-device theme selection requires a safe client/device preference scope from Harness.
95
+ Theme persistence remains entirely owned by Harness. A phone can change the theme for its current page, but reload returns to the durable Host preference—often `system`, which is then resolved using the phone's own color scheme. Local Link does not impersonate a loopback client and does not add a competing cookie or browser-storage preference. Persistent per-device theme selection requires a safe client/device preference scope from Harness.
92
96
 
93
- The authenticated gateway manifest omits Harness's host directory-picker client capability. The stock WorkspaceBrowser already treats `sidebar.workspaces.directoryFlow` as optional, so it naturally keeps Search, View options, existing workspaces, and sessions while withholding `Add workspace` from every remote gateway viewport. Loopback desktop boot entries are unchanged; no DOM selector or duplicated workspace browser is involved.
97
+ The authenticated gateway manifest omits Harness's host directory-picker client capability. The stock WorkspaceBrowser already treats `sidebar.workspaces.directoryFlow` as optional, so it naturally keeps Search, View options, existing workspaces, and sessions while withholding `Add workspace` from every remote gateway viewport. In alpha manifests the same entry is removed from the batch activation list without rewriting the server-registered batch URL. Loopback desktop boot entries are unchanged; no DOM selector or duplicated workspace browser is involved.
94
98
 
95
99
  Subagent controls also stay inside the native graph. A mobile-only list entry in `conversation.input.dock` projects the existing `useSessions` catalog into a compact status chip above the composer. The sheet itself is an additive `shell.overlay` entry, while a higher-priority mobile occupant of `conversation.session.header.lineage` removes the desktop dropdown without replacing the session header. Opening and expanding the sheet uses `ctx.sessions.setSubagentCatalogOpen`; selecting a row uses `ctx.sessions.openSubagent`. Closing the sheet or a tree branch releases every corresponding catalog observation. There is no second session store, WebSocket, or data-polling loop. While the sheet is visible, one one-second presentation clock updates displayed activity durations from the already-observed catalog and is cleared when the sheet closes.
96
100
 
@@ -104,11 +108,11 @@ The automatic pairing page runs before the Harness client and locale service loa
104
108
 
105
109
  Local Link uses Harness semantic color, state, border, background, elevation, and typography variables wherever the supported client exports an applicable token. Icons are imported from `@deepseek-ai/dsh-client-ui-primitives` when that package exposes the required glyph, and stock Harness menus, dialogs, conversation actions, Settings surfaces, and session operations that Local Link does not replace remain their native components. Literal colors following a `var(--dsw-*, fallback)` expression are defensive fallbacks and are not selected in the supported Harness build. The context breakdown's purple tools segment intentionally matches the stock Harness `ContextMeter` implementation exactly.
106
110
 
107
- Harness `0.1.1-rc.2` does not expose a public responsive-shell or Drawer component, spacing scale, radius scale, or mobile component recipes. Mobile geometry—safe-area placement, drawer widths, tap-target dimensions, spacing, radii, and transition timing—therefore remains plugin-owned CSS. One plugin-scoped `--dllm-side-drawer-width` value keeps the stock sidebar projection, the right details surface, and Current session visually identical instead of duplicating width literals. A small set of concepts also has no exported Harness primitive: Local access/device, navigation, current-session information, permission variants, and the subagent group glyph. The compact feedback-note affordance is a scoped presentation adapter because the stock feedback action accepts text only and exposes no icon-mode contract.
111
+ Harness `0.1.2-rc.1` does not expose a complete public responsive-shell or Drawer contract, spacing scale, radius scale, or mobile component recipes. Mobile geometry—safe-area placement, drawer widths, tap-target dimensions, spacing, radii, and transition timing—therefore remains plugin-owned CSS. One plugin-scoped `--dllm-side-drawer-width` value keeps the stock sidebar projection, the right details surface, and Current session visually identical instead of duplicating width literals. A small set of concepts also has no exported Harness primitive: Local access/device, navigation, current-session information, permission variants, and the subagent group glyph. The compact feedback-note affordance is a scoped presentation adapter because the stock feedback action accepts text only and exposes no icon-mode contract.
108
112
 
109
113
  All plugin-owned button and text-input controls use the exported Harness `Button` and `Input` primitives. Their semantic variants (`primary`, `outline`, `ghost`, and `toolbar`) remain owned by Harness; Local Link adds only the geometry required by its composed surfaces, such as a full-width sidebar row, a segmented copy action, a scrim, or a tree row. A source-level test rejects new raw `<button>` and `<input>` elements in the plugin UI.
110
114
 
111
- Component-level alignment remains bounded by the contracts Harness actually exports. The responsive shell, side drawer, bottom sheet, QR composition, context card, and diagnostics disclosure have no equivalent public responsive component contract in `0.1.1-rc.2`, so their structure remains semantic HTML plus scoped CSS. They use Harness tokens and primitive controls internally and should migrate if Harness later publishes compatible responsive components.
115
+ Component-level alignment remains bounded by the contracts Harness actually exports. The responsive shell, side drawer, bottom sheet, QR composition, context card, and diagnostics disclosure have no equivalent complete public responsive component contract in `0.1.2-rc.1`, so their structure remains semantic HTML plus scoped CSS. They use Harness tokens and primitive controls internally and should migrate if Harness later publishes compatible responsive components.
112
116
 
113
117
  These are compatibility surfaces, not an independent theme. Every Harness upgrade must compare them against the current token vocabulary, primitive icon catalog, slot contracts, and stock mobile behavior. They should be deleted in favor of upstream tokens or components as soon as equivalent public contracts exist.
114
118
 
@@ -140,10 +144,10 @@ This boundary keeps connection setup in one place and persistent access manageme
140
144
  2. The Host builds a LAN URL containing the token and current session in the fragment, then renders the same URL as a QR data URL. Neither value reaches the initial HTTP request.
141
145
  3. The phone opens a minimal automatic connection page. The secret remains in the URL fragment and is not sent in the initial HTTP request.
142
146
  4. The page immediately POSTs the token with a coarse device category and browser name; there is no confirmation form and no fingerprinting.
143
- 5. The gateway consumes the token, stores a credential hash, and sets the browser cookie.
147
+ 5. The gateway consumes the token, stores a credential hash, and sets the Local Link browser cookie.
144
148
  6. The desktop's loopback-only status check observes the consumed token and closes the QR panel.
145
149
  7. Before booting Harness, the page writes the selected session into Harness's own `dsh.sessions.current` persisted-selection cell for the LAN browser origin.
146
- 8. The browser redirects to the complete stock Harness root. Harness loads the shared server-side session list and opens the transferred current conversation, whose ordinary WebSocket stream shows live agent activity.
150
+ 8. The browser continues through the native Harness browser-authentication handoff when the installed version requires it, then redirects to the complete stock Harness root. Harness loads the shared server-side session list and opens the transferred current conversation, whose ordinary WebSocket stream shows live agent activity.
147
151
 
148
152
  ### Normal request
149
153
 
@@ -151,11 +155,12 @@ This boundary keeps connection setup in one place and persistent access manageme
151
155
  2. Reject a `Host` that is not one of the machine's current private IP literals and configured port.
152
156
  3. Reject the gateway administration prefix.
153
157
  4. Validate the paired-device cookie unless `trusted-lan` was explicitly configured.
154
- 5. Proxy to the loopback Harness listener.
158
+ 5. Reject the established loopback-only RPC set, including the RC Settings method names.
159
+ 6. Proxy all remaining traffic to the loopback Harness listener.
155
160
 
156
161
  ### WebSocket upgrade
157
162
 
158
- The same network, Host, and credential checks run before the upgrade is passed to the upstream server. Revocation affects new connections; a future milestone will actively close already-open sockets for a revoked device.
163
+ The same network, Host, and credential checks run before an exact supported stream path is passed to the upstream server. The compatibility allowlist contains `/api/events.mux`, `/api/events.host`, and the current `/api/remote.mux`; query-bearing and arbitrary WebSocket paths remain rejected. In `pairing` mode, the gateway retains an in-memory association between each upgraded tunnel and the paired-device ID that authorized it. Revocation destroys both sides of every tunnel for that ID after removing the credential, without disconnecting other devices. `trusted-lan` tunnels have no paired-device identity and remain outside this lifecycle.
159
164
 
160
165
  ## Dependency policy
161
166
 
@@ -164,21 +169,23 @@ Runtime dependencies are intentionally limited:
164
169
  - `@deepseek-ai/schemastery`: Cordis-compatible configuration schema.
165
170
  - `qrcode`: QR rendering for the desktop sidebar panel.
166
171
 
167
- HTTP forwarding and the two Harness event WebSocket tunnels use Node's built-in `node:http` and `node:net` modules. No general-purpose proxy package is shipped.
172
+ HTTP forwarding and the supported Harness event WebSocket tunnels use Node's built-in `node:http` and `node:net` modules. No general-purpose proxy package is shipped.
168
173
 
169
174
  No service discovery, certificate generator, tunnel client, native application, analytics SDK, remote log collector, or extension runtime is included.
170
175
 
171
176
  ## Compatibility strategy
172
177
 
173
- The plugin targets DeepSeek Harness `0.1.1-rc.2`. Most integration uses declared package contracts, but several adapters are intentionally version-sensitive:
178
+ The plugin develops against the exact DeepSeek Harness `0.1.2-rc.1` contracts. Most integration uses declared package contracts, but several adapters are intentionally version-sensitive:
174
179
 
175
180
  | Adapter | Why it exists | Failure behavior | Removal condition |
176
181
  | --- | --- | --- | --- |
177
- | Connection `trustedHosts` profile patch | Authenticated non-loopback pages need an explicitly declared LAN authority for ordinary API and WebSocket traffic. | An undeclared authority is rejected; privileged RPCs remain loopback-only independently. | Harness exposes a first-class authenticated-gateway registration contract. |
182
+ | Connection `trustedHosts` profile patch | Authenticated non-loopback pages need an explicitly declared LAN authority for ordinary API and WebSocket traffic. | An undeclared authority is rejected before browser authentication. | Harness exposes a first-class authenticated-gateway registration contract. |
183
+ | Browser-authentication handoff | `0.1.2-rc.1` requires a native one-time browser token in addition to Local Link device pairing. | An absent or invalid handoff fails closed and records `BROWSER_AUTH_HANDOFF_FAILED`; older builds without the service keep their direct-root path. | Harness publishes a stable authenticated-gateway handoff contract across releases. |
184
+ | Loopback-only RPC filter | The RC connection transport authenticates all methods uniformly, while Local Link must preserve its narrower pre-RC remote scope. | Configuration, credential, native Host-action, and agent-preset-authoring methods return `403` from the LAN gateway in both access modes. | Harness exposes a server-side authenticated-gateway capability policy with an equivalent restriction. |
178
185
  | Remote boot capability filter | The native directory picker targets the Host filesystem and is misleading from a remote browser. | If the known picker entries change, `Add workspace` can reappear; server authorization remains unchanged. | Harness exposes a remote-client capability policy. |
179
186
  | Settings navigation bridge | The shell keeps `openSection` private outside onboarding. | The shortcut does nothing; ordinary `Settings → Local access` remains available. | Harness exposes general settings navigation. |
180
187
  | Footer stack rule | Cordis reserves a full-width cell inside a horizontal list container. | Without it, Local access has zero width while Cordis is mounted. | Harness stacks full-width footer actions or gives entries an explicit layout contract. |
181
- | Remote theme persistence | Harness `0.1.1-rc.2` gives non-loopback clients a memory-backed SettingsScope. | An explicit mobile light/dark choice resets on reload to the host preference, commonly `system`. | Harness exposes a safe per-client or per-device preference scope. |
188
+ | Remote theme persistence | Remote clients have no durable per-device theme preference. | An explicit mobile light/dark choice resets on reload to the host preference, commonly `system`. | Harness exposes a safe per-client or per-device preference scope. |
182
189
  | Responsive AppFrame adapter | Harness exposes its root, layout controller, semantic tokens, and button/input primitives, but no public responsive-shell recipe, spacing/radius scale, several required glyphs, or icon mode for the feedback note action. | Token, component, or stock DOM/action changes can degrade mobile presentation while business operations remain intact. | Harness publishes responsive contracts and glyphs for the remaining plugin-owned surfaces. |
183
190
  | Mobile stock-DOM touch adapters | Harness has no touch-visible contract for session/workspace overflow actions, a separately slotted brand-row action, or compact feedback-note mode. | A CSS-module or stock DOM change can hide an action or enlarge its hit area while the underlying Harness operation remains available. | Harness exposes mobile action visibility and brand-row/feedback extension contracts. |
184
191
 
@@ -187,7 +194,7 @@ The manifest transformation and scoped adapter invariants have source-level test
187
194
  ## Known pressure points
188
195
 
189
196
  - **Plain HTTP:** avoids certificate onboarding but offers no confidentiality from other machines able to capture LAN traffic.
190
- - **Socket revocation:** the credential is checked before an upgrade; an already-upgraded socket survives until it disconnects or Harness restarts.
197
+ - **RPC compatibility list:** the gateway pins the administration methods that must stay loopback-only. New Harness configuration or native Host RPCs require an explicit review before the RC support claim moves forward.
191
198
  - **Browser metadata:** category and browser are coarse display hints supplied during pairing, not trusted identity. Laptop versus desktop is intentionally reported as `Computer`.
192
199
  - **Interface selection:** the first private IPv4 address is used in invitations. Multi-interface selection is not exposed yet.
193
200
  - **Harness upgrades:** directory-picker boot IDs, AppFrame DOM semantics, or connection contracts may change even when TypeScript package contracts still compile.
@@ -0,0 +1,51 @@
1
+ # DeepSeek Harness compatibility
2
+
3
+ Local Link touches version-sensitive Harness Host, slot, theme, layout, session,
4
+ and Settings contracts. Each supported version is therefore checked directly.
5
+
6
+ ## Compatibility matrix
7
+
8
+ Last checked on 2026-09-07 with Node.js 22 and Windows using the packed
9
+ `dsh-local-link@1.1.0` release source for every row. Versions are newest first.
10
+
11
+ | DeepSeek Harness | Status | Local Link source | Last checked |
12
+ | --- | --- | --- | --- |
13
+ | `0.1.2-rc.1` | **Supported release** | `1.1.0` | 2026-09-07 |
14
+ | `0.1.1-rc.2` | **Verified** | `1.1.0` | 2026-09-07 |
15
+ | `0.1.1-rc.1` | **Verified** | `1.1.0` | 2026-09-07 |
16
+ | `0.1.0-rc.8` | **Verified** | `1.1.0` | 2026-09-07 |
17
+
18
+ Versions older than `0.1.0-rc.8` are untested and unsupported.
19
+
20
+ ### Status meanings
21
+
22
+ - **Supported release** is the current development target and receives the
23
+ complete repository and installed-runtime gate.
24
+ - **Verified** means the current packed Local Link release passed the historical
25
+ RC gate on that exact version.
26
+ - **Untested** means no compatibility claim is made.
27
+
28
+ Every newer Harness version still requires an independent check; support for
29
+ `0.1.2-rc.1` does not imply support for a moving `next` tag or later alpha.
30
+
31
+ ## Verification policy
32
+
33
+ The historical RC gate starts from a fresh isolated installation. The packed
34
+ release must compose into the Web profile, boot in the real client, render Local
35
+ Access, preserve the private-LAN and loopback-admin boundaries, complete one-use
36
+ pairing, proxy authenticated HTTP and a supported WebSocket, close that socket
37
+ on revoke, reject the revoked device, and activate the responsive shell at
38
+ `390 × 844`. Automated tests cover Current session, subagent, locale, slot, and
39
+ composition contracts.
40
+
41
+ All four rows passed with `1.1.0`. The `0.1.2-rc.1` baseline additionally covered
42
+ native browser authentication, the loopback-only Settings RPC, a live Current
43
+ session, and the Current session and subagent browser surfaces.
44
+
45
+ Historical RC runs used empty profiles, so they did not create provider-backed
46
+ conversations. Physical-phone portrait and landscape acceptance also remains a
47
+ separate release check.
48
+
49
+ A successful package installation alone is not compatibility proof. Harness
50
+ may change authentication, DOM semantics, client slots, exported primitives,
51
+ theme storage, or responsive geometry while the plugin still appears to boot.
@@ -82,7 +82,8 @@ The copied report wraps the retained events with a schema version and export tim
82
82
  | `REQUEST_REJECTED` | Source-address or `Host` validation rejected the LAN request. | Confirm both devices use the same private network and the QR URL contains the computer's current private address. |
83
83
  | `AUTH_REQUIRED` | An unpaired browser opened a protected gateway page. | Pair that browser with a fresh QR/link; direct `:3088` access is intentionally rejected. |
84
84
  | `HTTP_UPSTREAM_ERROR` | The gateway could not reach Harness on `127.0.0.1:3080`. | Confirm `dsh web` is running and `upstreamOrigin` matches its port. |
85
- | `INDEX_REWRITE_ERROR` | The returned Harness index did not match the supported boot contract. | Confirm the installed Harness version is supported; currently `0.1.1-rc.2`. |
85
+ | `BROWSER_AUTH_HANDOFF_FAILED` | Harness returned an invalid browser-authentication handoff target. | Confirm the installed Harness version is supported and restart `dsh web`. |
86
+ | `INDEX_REWRITE_ERROR` | The returned Harness index did not match the supported boot contract. | Confirm the installed Harness version appears in the compatibility matrix and restart `dsh web`. |
86
87
  | `WS_REJECTED` | A WebSocket upgrade failed trust, authorization, or path validation. | Re-pair the browser and verify no proxy rewrites the URL. |
87
88
  | `WS_UPSTREAM_ERROR` | The gateway could not open the loopback Harness event socket. | Confirm the desktop Harness process is still running and reload the paired browser. |
88
89
  | `CLIPBOARD_COPY_FAILED` | The browser refused or failed to copy the one-time link. | Grant clipboard permission or select and copy the displayed link manually. |
@@ -15,7 +15,7 @@ Presentation remains independent of authorization: changing the viewport never g
15
15
  - **Dynamic views:** Chat, Trajectory, composer extensions, overlays, and third-party conversation tabs continue to resolve from Harness plugin slots.
16
16
  - **Current session:** a right drawer shows context usage and its System prompt / Tools / Messages breakdown, model, workspace access, agent preset, activity statistics, and session-log download.
17
17
  - **Subagents:** a compact status chip exposes total and active counts with the native activity state, then opens the nested subagent catalog as a touch-friendly bottom sheet.
18
- - **Appearance:** a sun/moon action uses the Harness theme service. In Harness `0.1.1-rc.2`, remote theme storage is page-memory-backed, so reload returns to the host preference and resolves `system` against the phone or tablet.
18
+ - **Appearance:** a sun/moon action uses the Harness theme service. Remote theme selection remains page-scoped, so reload returns to the host preference and resolves `system` against the phone or tablet.
19
19
  - **Touch behavior:** native session and active-workspace overflow actions remain visible without a long press, and switching sessions does not automatically focus the composer or open the software keyboard.
20
20
  - **Keyboard accessibility:** plugin-owned modal drawers receive and contain focus, close with Escape, and restore focus to their invoking control.
21
21
  - **Responsive AppFrame:** safe-area insets, full-viewport scrims, scrollable tab groups, media bounds, and matching left/right drawers enhance the shipped Harness layout only while the media query matches.
@@ -51,13 +51,13 @@ Landscape phones, split-screen browsers, virtual keyboards, third-party fixed-wi
51
51
 
52
52
  Mobile View keeps the official Harness root and AppFrame mounted. It contributes controls through overlay, conversation, theme, session, locale, button, and input contracts wherever Harness exposes them. The stock desktop presentation is unchanged when the media query does not match.
53
53
 
54
- Harness `0.1.1-rc.2` does not expose a public responsive shell, drawer recipe, spacing/radius scale, or every required glyph. The plugin therefore owns mobile geometry and a small number of scoped presentation adapters for stock brand, workspace, session-action, and feedback elements. Those hooks are documented in [Architecture and compatibility boundaries](ARCHITECTURE.md) and must be retested for each supported Harness version.
54
+ Harness `0.1.2-rc.1` does not expose a complete public responsive shell, drawer recipe, spacing/radius scale, or every required glyph. The plugin therefore owns mobile geometry and a small number of scoped presentation adapters for stock brand, workspace, session-action, and feedback elements. Those hooks are documented in [Architecture and compatibility boundaries](ARCHITECTURE.md) and must be retested for each supported Harness version.
55
55
 
56
56
  ## Security
57
57
 
58
58
  Mobile View uses the same one-use invitation, paired-browser credential, private-network validation, HTTP/WebSocket gateway, and revocation behavior as desktop-shaped remote access. It adds no relay, account, analytics, fingerprinting, polling loop, or duplicate conversation store.
59
59
 
60
- LAN traffic remains plain HTTP in this preview, and an already-open WebSocket is not immediately terminated by revoke. See the full [security model](SECURITY.md) before enabling the gateway.
60
+ LAN traffic remains plain HTTP in this release. Revoking a paired device blocks its next request or reconnect and immediately terminates its open Local Link WebSocket tunnels. See the full [security model](SECURITY.md) before enabling the gateway.
61
61
 
62
62
  ## Release acceptance checklist
63
63
 
@@ -70,4 +70,4 @@ LAN traffic remains plain HTTP in this preview, and an already-open WebSocket is
70
70
  - Confirm `Add workspace` is absent on every authenticated remote gateway page and remains available on the loopback desktop.
71
71
  - Check a third-party conversation tab and Cordis panel if installed.
72
72
  - Test the four viewport sizes above plus one real phone in portrait and landscape.
73
- - Revoke the device and verify subsequent requests and reconnects are rejected.
73
+ - Revoke the device and verify its live stream disconnects immediately while subsequent requests and reconnects are rejected.
package/docs/SECURITY.md CHANGED
@@ -24,10 +24,11 @@ Mobile View does not reduce that authority. It inherits the selected Harness ses
24
24
  - `HttpOnly` and `SameSite=Strict` device cookie.
25
25
  - Device expiry and explicit revocation.
26
26
  - Authentication before HTTP proxying and WebSocket upgrade.
27
+ - Separation of the Local Link device credential from Harness browser-authentication cookies during proxying and the native browser-token exchange.
27
28
  - Gateway-side block for desktop administration paths.
28
29
  - Structural loopback source, Host, and Origin validation for every desktop administration request; lookalike DNS names fail closed.
29
30
  - Gateway authorities declared through the stock connection `trustedHosts` contract without claiming loopback identity.
30
- - Independent loopback enforcement for Settings, credentials, native Host actions, and agent-preset authoring.
31
+ - Gateway enforcement that keeps Settings, credentials, native Host actions, and agent-preset authoring outside both Local Link access modes even though the RC connection transport authenticates methods uniformly.
31
32
  - Bounded local diagnostics with an explicit context allowlist and no credentials, addresses, identifiers, names, paths, or user content.
32
33
  - No external relay, telemetry, analytics, or remote log collector.
33
34
 
@@ -37,19 +38,19 @@ Diagnostics are enabled by default because a local networking plugin otherwise b
37
38
 
38
39
  The report is designed to be safe to review and attach to a public bug report, but users should still inspect copied JSON before sharing it. Disabling `diagnosticsEnabled` prevents new events from being retained.
39
40
 
40
- ## Known limitations of the preview
41
+ ## Known limitations
41
42
 
42
43
  ### Plain HTTP
43
44
 
44
- The initial release does not encrypt LAN traffic. Pairing credentials and Harness traffic can be observed by an attacker who can capture traffic on the local network. Use only on a trusted home network while HTTPS support is under development.
45
+ The current release does not encrypt LAN traffic. Pairing credentials and Harness traffic can be observed by an attacker who can capture traffic on the local network. Use only on a trusted private network while HTTPS support is under development.
45
46
 
46
- ### Existing WebSockets
47
+ ### WebSocket revocation
47
48
 
48
- Revoking a device blocks subsequent requests and reconnects, but an already-upgraded WebSocket is not actively terminated yet. Restart the Harness Web process to close every active connection immediately.
49
+ Revoking a paired device blocks subsequent requests and reconnects and immediately destroys both sides of every open Local Link WebSocket tunnel authenticated by that device. Tunnels belonging to other paired devices remain connected. Connections opened in the explicit `trusted-lan` mode are not associated with paired-device records and therefore are not affected by paired-device revocation.
49
50
 
50
51
  ### Version-sensitive Harness integration
51
52
 
52
- Authenticated LAN trust, remote boot capability filtering, direct Settings navigation, coexistence with the stock Cordis footer action, and responsive AppFrame presentation currently need small compatibility adapters for Harness `0.1.1-rc.2`. They do not grant privileged loopback methods, but a Harness upgrade can break presentation or fail closed. Before declaring another Harness version supported, rerun the trust-boundary suite and manually retest pairing, live conversation streaming, Settings navigation, rename, revoke, Cordis coexistence, mobile workspace/session actions, Current session, subagents, theme switching, and third-party conversation tabs.
53
+ Authenticated LAN trust, browser-authentication handoff, the loopback-only RPC list, remote boot capability filtering, direct Settings navigation, coexistence with the stock Cordis footer action, and responsive AppFrame presentation need small version-sensitive adapters. They do not grant privileged Host administration methods, but a Harness upgrade can add or rename a method, break presentation, or fail closed. Before declaring another Harness version supported, audit the current Remote namespaces, rerun the trust-boundary suite, and manually retest pairing, live conversation streaming, Settings navigation, rename, revoke, Cordis coexistence, mobile workspace/session actions, Current session, subagents, theme switching, and third-party conversation tabs.
53
54
 
54
55
  ### Firewall automation
55
56