Trial 6 cover cards
Test one shortcut and 3–4 shortcuts, narrow-phone wrapping, explicit cover lookup, refresh and bridge restart persistence.
DASH DEVRevision 30
LINKUI 10 · Trial 6
DASH PUBLICRevision 27 docs
DEMO SOURCEd1a5abd
UPDATEDOct 5, 2026
NEBULAH / EVIDENCE
Testing & compatibility.
See what is implemented, host-tested, browser-verified or console-confirmed—and what still needs hardware acceptance.
Evidence labels
| Label | What it means |
|---|---|
| Requested / planned | A goal or backlog item. Do not present it as working. |
| Implemented | The relevant code/artifact exists in the identified version. |
| Host-tested | Named automated checks passed; this is not console/browser acceptance. |
| Browser-verified | The behavior was actually observed in a real browser environment. |
| Console-confirmed | The user or connected test environment confirmed the behavior on hardware. |
Current compatibility snapshot
| Area | Evidence | Status |
|---|---|---|
| Dash reference console | Trinity / RGH3 / kernel 17559 historical reference; Revision 28 Aurora and COD4 targeted launch success recorded. | Scoped console evidence |
| Dash Revision 30 | Host/source checks and Windows preflight reported for the exact source tree. | Console run pending |
| Link core flows | Maintainer confirmed telemetry, storage browsing, application launch and capacity. | Console-confirmed |
| Link HDD round trip | 404,910-byte upload/download with matching SHA-256 1eb7064…d29900c. | Console-confirmed |
| Link Trial 6 | 127 Python + 36 JavaScript host checks reported, plus syntax checks. | Host-tested |
| Trial 6 cover cards | Real browser layout, persistent artwork and Windows/console trial still required. | Pending |
| Phone + broader devices | Core responsive design exists; phone transfer/browser behavior remains part of acceptance. | Pending |
High-value tester missions
Transfer matrix
Disposable 0-byte, 1-byte, 64 KiB, 64 KiB + 1 and larger files on available HDD/USB roots; compare SHA-256 after download.
Revision 30 console run
Use the exact build package, preserve all reports and test recovery/storage-review behavior without enabling persistent writes.
Report a result
Include build/commit, Windows/Python/PowerShell architecture, browser/device, safe console/plugin context, exact steps, expected vs actual result, and a sanitized diagnostic. Never post CPU keys, pairing tokens, keyvaults or proprietary SDK/game files.