# DSH mobile acceptance - preview.10

Updated 2026-10-06 (UTC). New installers are DSH-only. This record separates actual runtime operations, controlled tests and outstanding checks. It does not certify every feature, version or physical device.

## Preview.10 actual npm operation

Four published npm versions were run locally in separate D-drive environments: 0.1.0-rc.8, 0.1.1-rc.2, 0.1.7-rc.2 and 0.2.0-rc.2. Actual pointer/keyboard operations covered different subsets; see the [current compatibility table](DSH-COMPATIBILITY.md). Successful modern replies, question answers and approval allow/reject results came from the real DSH/model processes. The old versions' model and tool selections were confirmed through independent readback; their missing valid API-key errors remain credential failures.

The measured mobile layouts were 390-by-844 with no horizontal overflow. Earlier operations in tabs that retained a desktop-sized viewport are not relabelled as mobile-sized acceptance. Desktop-browser viewport emulation does not operate a physical iPhone or Android keyboard/network. Actual Save links in the current in-app browser did not produce a confirmed completed download; historical downloads and controlled download fixtures remain separate evidence.

The new durable replay, WebSocket, screenshot-schema, private-HTTPS admission, capability panel and legacy refresh regressions use owned isolated fixtures. They do not establish real Tailscale enrollment, a production replay attack, physical-phone recovery or all-feature compatibility. Publication requires fresh whole-suite CI and compiled installer/payload/privacy gates for the final source.

## Historical preview.9 desktop: actual public browser operation

The host runtime was desktop **DSH 0.1.7-rc.2**. The updated installed interface was operated through its authenticated, encrypted public quick-tunnel route in Chromium at 390-by-844 and 320-pixel-wide viewports. Tests used disposable computer projects and conversations. These are actual runtime and internet-route operations, not a mocked model; they are not physical iPhone, Android or 5G acceptance.

The following results were observed in the installed candidate. After the language and runtime corrections were installed, their affected operations were repeated through the public route. Final CI, installer, source/payload and privacy gates remain separate.

| Operation | Observed result |
| --- | --- |
| Project and conversation navigation | Loaded the current desktop's projects and conversations. Created two disposable projects and three conversations. |
| Send and assistant reply | Harmless prompts reached the selected conversations and returned their requested replies. Acknowledgement alone was not the success criterion. |
| Model and reasoning strength | Selected the account provider's Pro model and Low reasoning strength; current-runtime readback confirmed the settings. |
| Permission and tools | Readback confirmed workspace read-only permission and the minimal tool configuration. |
| Plan mode | Turned Plan on and confirmed the current setting. This does not certify every goal or planning workflow. |
| Workspace Files | Listed and previewed the exact 59-byte test file. |
| Save file | The actual Save link was operated, but the in-app browser did not confirm a completed download. This public-route result remains unconfirmed. |
| Upload and model image reading | Uploaded a 1,570-byte PNG. The actual DSH image-reading tool and assistant correctly described its bridge artwork. |
| Temporary preview of a fresh upload | Explicit Load displayed the freshly uploaded 192-pixel PNG from the current page's bounded local cache. This is not persistent history retrieval. |
| Historical official image reference | After correcting the shared-runtime guard, explicit Load decoded a complete 192-by-192 PNG from an official tool-image reference. A separate installed encrypted endpoint check matched its bytes and digest to DSH's authorized response. This does not make old generic file uploads remotely readable. |
| Computer screen | The encrypted response returned a complete 1,280-by-720 image. |
| Composer and layout | Enter inserted a newline. Operated visible controls met the 44-pixel target and the 320-pixel layout had no horizontal overflow. |
| Stored language after reload | After the mount fix, the actual update action and subsequent reload preserved English across static and dynamic controls. Controlled English/Spanish reload and remount checks also passed. |

## Isolated browser and protocol checks

The current real Chromium action fixture passed **192 checks**, retaining command/session fencing, permission readback, uncertain queue/goal edits, image Retry, keyed rows, streaming coalescing and byte-exact completed downloads. It also exercises actual original File uploads, temporary-preview eviction and cancellation, lazy official image-ID reads, and persisted English/Spanish reload and remount against the default Chinese HTML. The language regression reproduced the original failure before the fix and checks 12 static controls per locale. The existing full UI, adapter and language suites passed at author freeze. These use controlled upstream data and do not certify the corresponding public or physical-phone operation.

An earlier candidate completed **89 isolated CI entries**. That result predates the latest language and runtime corrections and is not final acceptance of their source tree. Shared security fixtures retain proof/auth/key-loss negatives; remote raw/classic HTTP and unknown WebSocket routes are refused before dispatch. Final CI, compiled installer, payload identity and privacy results must refer to the final frozen candidate.

Separate measurements were also recorded:

| Check | Scope and result |
| --- | --- |
| Public asset compression | An actual HTTP check passed 49 assertions across 11 resources: 528,084 uncompressed bytes became 132,814 compressed bytes, about 75% less. This is an asset-transfer result, not a mobile startup or cellular benchmark. |
| PWA resources | 20 HTTP/manifest checks passed. Physical home-screen installation was not operated. |
| Gateway health | 12 samples on an earlier installed candidate were 1.48 ms minimum, 2.14 ms median and 13.70 ms maximum. They do not establish final release latency or every phone operation's response time. |

## Compatibility and parity

The [compatibility matrix](DSH-COMPATIBILITY.md) records four actual historical npm web-version experiments, their prepared dependency graph, the successful flows and the credential/device limits. They have not all been repeated against this candidate. Old desktop wrappers and arbitrary plugin combinations are not certified by those tests.

This phone interface exposes capabilities supplied by the connected runtime. Complete desktop-plugin parity is not claimed. Tool activity and reasoning depend on exposed runtime data. Generic pathless uploads have a temporary preview only when this page retained the verified original File; a reload or cache eviction removes it. Official image-reference retrieval is a separate, session-authorized operation, accepted for one actual historical tool-image preview. Arbitrary text-file upload remains unsupported on the legacy protocol. An unsupported control must be unavailable or explain its limit; its appearance is not a passed action.

## Remaining acceptance

- Confirm public-route download completion separately from the controlled byte-exact browser download.
- Operate microphone/voice, live model-triggered choices and approvals, and remaining goal, queue, cancellation and failure/recovery workflows. Their controlled fixtures are not current-desktop live acceptance.
- Run fresh whole-suite CI and compiled installer acceptance on the final frozen tree; verify fresh install, upgrade, uninstall, retained user data, payload identity and private-data exclusion. Earlier successful candidates do not cover later edits.
- Keep physical iPhone Safari, Android, home-screen installation, cellular networks, old npm model/approval gaps and other desktop wrappers unverified until their own operations are observed. Full desktop parity and all-version compatibility remain unclaimed.