Document the Windows Connector public test track - #59
Conversation
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| The unsigned EXE and ZIP artifacts produced by ordinary CI are deliberately marked **NOT FOR | ||
| RELEASE**. The public Windows distribution is the reserved | ||
| [Microsoft Store listing](https://apps.microsoft.com/detail/9N52Z3FVMFH8), whose accepted MSIX is | ||
| signed and delivered by Microsoft. DevinX will offer it as a supported download only after the | ||
| Store package passes certification and the clean Windows 11 x64 physical matrix in | ||
| [spec 037](specs/037-windows-connector.md), including | ||
| RELEASE**. The Store-signed Windows 11 x64 package is publicly installable from the | ||
| [Microsoft Store listing](https://apps.microsoft.com/detail/9N52Z3FVMFH8) for controlled testing. | ||
| It is still a **public test track**, not a completed support claim, until the clean physical matrix | ||
| in [spec 037](specs/037-windows-connector.md) passes with the exact Store package. That matrix covers | ||
| official Devin ACP discovery, Tailscale routing, pairing, read/send/create grants, | ||
| AskUserQuestion, sleep/reconnect, update, and uninstall. This prevents an unfinished or unsigned | ||
| package from being presented as trustworthy. | ||
| AskUserQuestion, sleep/reconnect, update, and uninstall. Testers should follow the | ||
| [Windows Connector physical test checklist](docs/windows-connector-test-checklist.md) and must | ||
| never sideload the unsigned CI artifacts. |
There was a problem hiding this comment.
🔍 Unchanged capability-boundaries text may now contradict the new public-test-track messaging
This PR reframes the Windows Connector as a Store-signed package that is now publicly installable for controlled testing (README.md:152-153). However, the "Honest capability boundaries" section at README.md:229-232 (outside the diff) still states "Windows 11 x64 is an active release implementation whose public download activates only after its signature and physical compatibility gates pass." Now that the Store package is described as publicly installable, this older wording reads as contradictory. Consider updating it to distinguish the public test track from a fully supported download for consistency with the rest of the PR.
Was this helpful? React with 👍 or 👎 to provide feedback.
1 participant
What changed
Why
The Microsoft Store package is now live and signed, while the required physical Windows acceptance matrix has not yet been completed. The prior wording contradicted that live state and did not give a tester a safe, reproducible checklist.
Validation
npm run ci— 86 suites / 665 tests, lint, typecheck, build, and dependency gate passed--noUnusedLocals --noUnusedParameters