QA: dev-build ship-readiness evidence pack (candidate 365a14a)

[rowkav09]

Dev-build evidence pack - candidate #331 (365a14a)

This is a living QA record, not a stable-release approval. Recheck and republish verdicts whenever the rolling dev build moves to a new SHA. PASS means observed evidence at this candidate; FAIL means a known unmet gate; UNVERIFIED means missing evidence. Runner success is not Rowan's real-machine acceptance. Rowan tests before deciding whether to ship; do not publish stable without his explicit go.

Gate	Current verdict	Evidence / next check
Candidate integrity and Windows installer/portable smoke	PASS on Windows runner; real machine UNVERIFIED	Dev build #331 is 365a14a. Validation run succeeded at that SHA. Validator reports digest/SHA256SUMS, provenance and embedded build-info checks; portable launch and silent installer launch/uninstall; first-run WebUI and discovery API probes. It does not prove interactive GUI, live server or Discord behavior.
#141: clean Windows install to media sign-in, playback, DRP and local/hosted card without terminal	UNVERIFIED end to end	Test actual WebUI flow, not the old native wizard in the issue wording. Need candidate-specific real provider, playback, card and Discord output evidence.
Four provider sign-ins and discovery, error handling, user/player choice	UNVERIFIED live	Test Plex, Jellyfin, Navidrome, Emby against candidate; capture redacted repro/evidence per provider.
Local Discord presence, pause/skip, offline/reconnect; no hosted dependence	UNVERIFIED live	Automated #140 tests are not live Discord-client acceptance.
Hosted privacy, upload, exact SVG readback, stale/offline, disconnect, multi-device	PARTIAL automated; UNVERIFIED live	#140 checks technical boxes, but live card readback and observable behavior on this build remain to test.
#253: WebUI Settings, add/remove/discover, save, status, logs	PARTIAL runner smoke; UNVERIFIED full UI	Interactive GUI, no old setup window, server flows and visual checks remain.
#141 keyboard, Narrator, 200% scaling and deuteranopia	FAIL as release gate, unchecked	Automated accessibility tests exist. Real Windows screen-reader/zoom pass not recorded.
#142: docs and tested examples	FAIL as release gate, mostly unchecked	Link/snippet check is done; audit current Windows/WebUI, four providers, Discord, hosted cards, troubleshooting, and version labels.
#287: security baseline	PARTIAL; full gate not passed	CodeQL (JS/TS, Actions, C#) and Dependency Review workflow files exist. Verify their conclusions at this SHA; verify secret scanning and push protection settings and the history scan. An existing workflow is not proof of passing.
#215: macOS/Linux	OUT OF SCOPE	Board says long-term and blocked behind Windows v0.2. This candidate contains Windows assets only; do not imply other-platform support.
Ship decision	HOLD	Windows runner validation alone is insufficient. Main/post-merge checks, remaining gate evidence, Rowan's test and explicit go are required.

Evidence receipt for each result: gate, candidate SHA/build and asset digest; tester/environment; exact steps; expected/actual; timestamp; redacted screenshot/log or workflow run and issue links; runner versus Rowan's machine; retest SHA. Missing evidence stays UNVERIFIED. Bugs belong in reproducible scoped issues linked here. Source: rolling dev release, Windows validation PR.

[rowkav09]

Verdict clarification for candidate 365a14a: the #141 accessibility row's "FAIL as release gate" meant the issue's keyboard/Narrator/200%-zoom/deuteranopia acceptance box remains unchecked. It did not mean we reproduced a product defect. No candidate-specific real Windows accessibility run or failing steps have been supplied yet. Treat behavior as UNVERIFIED / NOT ACCEPTED, then file individual bugs only if testing finds a reproducible failure. Runner/API smoke does not cover this.

[rowkav09]

Candidate rollover - 26 Sep, 12:48 BST

The moving dev release is now #337, 0.2.1-dev+76bfa90 (full commit 76bfa90e8abadee2178b5ec9810d96beed077083). This supersedes the issue body's #331/365a14a verdicts. The successful Windows validation run belongs to the old SHA and must not be presented as #337 validation. The validation workflow page shows no new #337 run yet. Candidate integrity/installer runner gate returns to UNVERIFIED pending a fresh run and asset checks.

Other candidate-specific flows remain UNVERIFIED: live four-provider sign-in and discovery, playback through Discord and local/hosted cards, full WebUI interactions, and keyboard/Narrator/200%/color acceptance. Existing automated checks are narrower. Reproduced issues #576, #578 and #579 are still open with fixes under review; do not carry their eventual PR claims over to this build without a new SHA and retest. Docs #142 and security #287 remain incomplete. CodeQL lists a main run for 76bfa90, but I have not established full candidate-head job conclusions, and Dependency Review PR results plus secret-scanning/push-protection and history-scan evidence remain unverified.

Ship verdict: HOLD. macOS/Linux #215 stays outside the Windows release scope. Runner evidence never substitutes for Rowan testing the working candidate and explicitly choosing to ship.

[rowkav09]

Candidate rollover - 26 Sep, 13:19 BST

The rolling dev release has advanced to #341 / 723ed56db9f8078ccd0cc08b7d7208901ed63950. This supersedes the #337/76bfa90 status above. Main has newer commits than the packaged dev build, so do not attribute newer code or PR fixes to #341. The real-install validation workflow still lists only the old #6 run at 365a14a; downloaded-artifact Windows runner PASS is UNVERIFIED for #341.

A new reproduced security/privacy failure #588 is explicitly against the current dev-tag code: offline Disconnect this PC loses the local revocation key while the hosted card retains the old title and the old token remains authorized. That makes hosted-card disconnect/revocation FAIL for #341, not merely unverified. Its issue documents a fixture-based reproduction, not Rowan's real-machine test. A later fix must be merged, rebuilt in dev and retested before this gate can pass.

The other end-to-end paths (live provider -> playback -> DRP/card, interactive first-launch/WebUI, accessibility) are still UNVERIFIED at this SHA. #142 docs and #287 security baseline remain incomplete. Ship verdict: HOLD. No runner result or checked issue box substitutes for Rowan's acceptance and explicit go.

[rowkav09]

Candidate rollover - 26 Sep, 13:45 BST

Current rolling dev release is #343 / abe2377243f478f6aaf6a06def17cfdf5941c72b. This supersedes the #341/723ed56 status above. The #588 offline-disconnect defect is fixed in this build and retested against this exact dev tag: fixture pushed a track, disconnected offline (kept protected key and pending state), restored service, retried, verified card idle and old token rejected with 401. Hosted disconnect/revoke is PASS for that fixture-level path on #343, but still UNVERIFIED on a real Windows account and live Vercel/network failure. The broader hosted/privacy gate is not thereby complete.

Downloaded-artifact Windows validation is UNVERIFIED at #343: its workflow still shows only the old #6 manual run at 365a14a. Live provider -> playback -> Discord/card, full interactive WebUI, accessibility, docs and full security baseline remain unaccepted/unverified as described above. Ship verdict remains HOLD, pending the candidate-specific checks and Rowan's own test and explicit decision.