1.7 KiB
1.7 KiB
Windows Notification Environment Preparation
Last verified: 2026-06-02
Read this when you need to provide Windows runner, packaging, and signing choices so an agent can finish Windows notification implementation and smoke verification. You do not need to run the test from this document.
Provide
| Needed | What to prepare |
|---|---|
| Windows runner | Local PC, VM, remote machine, or a decision that visible smoke is deferred. |
| Toolchain | Windows version plus Visual Studio/C++ desktop workload/Windows SDK availability. |
| Packaging mode | Unpackaged, MSIX, sparse package, or debug injection only. |
| Notification API | Windows App SDK, WinRT toast, desktop AppUserModelID fallback, or debug injection only. |
| Identity | Package identity or AppUserModelID if visible toast activation is in scope. |
| Signing | Test certificate, organization cert, Store association, or no signing. |
| Evidence path | Choose where sanitized logs/screenshots/run notes should be stored. |
Do Not Put In Tracked Files
- Microsoft account values, package identity if private, signing certificate contents/passwords, Store association files, push credentials, device token, private endpoint, auth token, channel name, user name, or server URL.
Agent Can Then
- add Windows platform registration and host scaffold if selected;
- implement the native notification/action bridge;
- configure the selected notification API and packaging path;
- run routing checks and, if allowed, visible toast smoke;
- record sanitized evidence in the task or private run note.
Current Repo Note
Windows is not registered yet and has no plugin or test-host scaffold. Smoke work first needs platform scaffold plus the environment choices above.