test(template): diagnose intermittent installed UI input timeouts #23
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: KofTwentyTwo/AppKit#23
Reference in new issue
Block a user
Problem
The fresh CLI-enabled installed-update smoke passed all four CLI versions and archive byte checks, the published seven-case UI suite, and the stable
0.1.0 -> 0.4.0upgrade/restart, then timed out waiting for the greeting in the installed stable UI suite. The application stayed running; five other cases passed and guarded uninstall succeeded. Dev installation was not reached. No signing or publication was involved.Evidence:
artifacts/starter-finish/artifacts/temp-stage-with-cli/artifacts/installed-temp-stage/installed-stable-ui.trx,process-29.log,stable-before.json,stable-after.json. This is separate from the retained byte corruption in #22: all four package byte checks passed in this attempt.Five focused greeting checks and the complete six-case sequence against the exact previously failing 0.4.0 published executable passed. The failure's cause is not established; these later passes do not erase the original failure. Added observed greeting and isolated app logs to timeout diagnostics. A fresh full CLI attempt with those diagnostics is underway.
Acceptance criteria
Related: #11, #20, #22. Substantial AI assistance: Codex (GPT-6). No push, release or settings change was performed.
Additional evidence
A second fresh CLI run passed every byte gate, the seven published UI cases and stable upgrade/restart, then timed out waiting for the crash-test button's log entry (five other installed cases passed). Evidence is in the sibling
installed-temp-stage-diagnostic/directory. Guarded uninstall again completed. This broadens the investigation to input-driven installed tests; no product or environmental cause is established. Physical mouse input now explicitly focuses the target and waits for input processing before clicking, and keyboard fallback waits after focus. A fresh full acceptance run for that candidate is underway; no timeout was increased and no failed check was skipped.Committed locally: starter
2c8816b187b3a9a540f28daea20e0b1b061e8c5bonfix/template-onboarding. Six starter commits now; 21 signed/DCO commits total across AppKit, starter and shared builder. No pushes or new releases.Verified GUI-only evidence: four actual self-contained publishes, 532 preserved files in each portable/full package, loose/portable checks, real stable
0.1.0 -> 0.4.0and dev0.3.0-beta.1 -> 0.3.0-beta.2installs/upgrades, same-channel feeds, restart, target assembly SHA256 and 19 UI tests. Evidence remains inartifacts/starter-finish/artifacts/temp-stage-no-cli/artifacts/installed-temp-stage/.CLI evidence: four single-file versions execute and all package byte checks pass; seven published UI checks and stable upgrade/restart pass. Two installed suites exposed different input timeouts, tracked in #23. Focused greeting tests (five) and the complete six-case sequence against the exact failed published 0.4.0 binary pass, without establishing the original cause. The candidate now focuses physical input and waits before clicking; its published seven UI cases pass. Its latest full attempt stopped on disk exhaustion while extracting portable assets, before any installation. Retained the failed runs; no test was skipped or timeout increased.
The smoke harness now parses source PE headers, copies only four probe files, isolates system-temp build/packer staging and refuses to start below 8 GB free on the artifact volume. Moved completed diagnostic fixtures to the approved cache without deleting them; workspace now has about 9.4 GB free. The candidate's complete CLI installed acceptance still needs a fresh run.
Current source validation: 31 Pester tests, changed-file PowerShell analysis, zero-warning UI-test build, scoped C# format, Markdown lint and commit hooks/signature verification pass. Source and prepared shared-builder worktrees are clean. AppKit head is
146138957506b79459a6d811a1e70a626e006699; shared head is4dfde0976a59f3a2b07b974444e837574310c083.Live AppKit UI updater/public hosting, signing, hosted CI and source/template rollout remain acceptance requirements. Keep this issue open. Substantial AI assistance: Codex (GPT-6).
The fresh CLI smoke from committed starter
2c8816bfinished with a retained failure. All four version packages passed the 532-file portable/full archive byte comparison. The first published-output UI suite passed six tests and failedUnhandledException_IsLoggedAndTheAppSurvives: its physical crash-button click did not produce the expected log entry within the unchanged ten-second timeout; the app remained running.Evidence:
artifacts/starter-finish/artifacts/committed-with-cli/artifacts/installed-committed-focus/published-ui.trx,process-23.log, andbuild-directory.txt. The build directory isC:/Users/james/AppData/Local/Temp/k22-smoke-3a4c3ce1642e4ec5997b9dcafe592921. This run stopped before installed stable/dev tests. Earlier installed upgrade successes and the complete GUI-only smoke remain separate evidence; this attempt does not prove current CLI acceptance.The committed foreground/focus/input-processing candidate did not eliminate the failure. No cause is established, timeout increased, failed check skipped, or extra retries used to turn this run into a pass. The problem now also reproduces against a published loose executable, so it is not confined to installed output. Keep #23, #11 and the readiness acceptance open. No signing or publication was involved.
Observed cause for one retained recurrence: the crash button's clickable point and final mouse position belonged to Windows Terminal, not the test app, even though UIA reported keyboard focus in the app. Expected PID 91788, hit PID 73516; the latter was confirmed as WindowsTerminal without reading its window contents. Evidence:
artifacts/starter-finish/artifacts/committed-with-cli/artifacts/input-diagnostics/published-input-observed.trx. The diagnostic status lookup also exposed an unsupported UIA Name on a blank label; it now uses ValueOrDefault so it cannot replace that timeout.Signed local starter commit
df40b60e6ea0fe75719fbc59c595e3202e768530waits for an enabled, visible clickable point owned by the app before sending one physical click. It records process/point/focus observations and app-only identifiers, with isolated state/logs on failure. Product handlers and timeouts are unchanged; no retry after a failed click was added.Three focused crash checks passed on the exact retained executable. The full seven-case suite reproduced the missed click with diagnostics, then the guarded full suite passed seven cases; its observed hit ID was ThrowButton and the expected app owned the point before and after clicking. Source/same-identity diagnostic builds, targeted formatting, Markdown and hooks pass; signature verified.
This establishes the missed-click cause for that observed recurrence, not every earlier greeting/input failure. Fresh actual CLI/GUI-only projects have now been generated from the committed packed template. The complete CLI installed stable/dev harness is running; its full acceptance and hosted CI remain required. Diagnostic tests applied to the earlier fixture are identified as such and do not substitute for fresh-template acceptance. Prior failing reports are retained.
Fresh committed-template CLI attempt
df40b60completed all four 532-file portable/full byte comparisons, CLI executions, both installed stable/dev upgrades/restarts, channel isolation and exact target assembly checks. Published UI passed 7/7; installed stable passed 6/6; installed dev passed 5/6, failing the theme-save check with app alive. Guarded cleanup completed. Retain the failure; full harness exit was failure, not success.Evidence:
artifacts/starter-finish/artifacts/guarded-with-cli/artifacts/installed-guarded/, includingpublished-ui.trx,installed-stable-ui.trx,installed-dev-ui.trx,stable-after.json,dev-after.json,process-34.logandbuild-directory.txt. AppKit reported installed versions 0.4.0/stable and 0.3.0-beta.2/dev; only each channel's feed was requested.Starter menu/control input was missing the foundation sample's existing foreground step. Signed local commit
7eef2a489cb8a1924cb46f4c08e2593a532d930daligns those paths, applies the observed point-ownership guard to every physical fallback, and captures invocation kind/settings/logs for theme failures. Product code and timeouts remain unchanged.Three focused theme checks and all six feature checks passed on the exact failed dev publish payload. These are clearly identified same-identity diagnostic tests, not a fresh complete installed acceptance run. Evidence: sibling
artifacts/input-diagnostics/theme-foreground-{1,2,3}.trxanddev-feature-foreground.trx. Source and diagnostic zero-warning builds, formatting, hooks and Markdown passed. The earlier crash occlusion trace remains separate evidence; this does not prove every prior failure had the same cause.Keep #23/#11/#20 open for a complete current packed-template CLI/GUI-only run and hosted acceptance. Current R: capacity is below the 8 GB start gate after retaining fixtures; preserve evidence in the approved cache before launching another full run. No signing or publication occurred.
Fresh actual packed-template acceptance from signed starter commit
7eef2a489cb8a1924cb46f4c08e2593a532d930dcompleted successfully. Published UI passed 7/7, installed stable 6/6, installed dev 6/6: 19 checks, zero failures/skips. All four 532-file portable/full payload comparisons passed before runtime acceptance. Stable0.1.0 -> 0.4.0and dev0.3.0-beta.1 -> beta.2downloaded, applied, restarted and passed installed version/target hash/channel isolation checks. Guarded uninstalls completed.Evidence:
artifacts/starter-finish/artifacts/foreground-with-cli/artifacts/installed-foreground/:results.json,published-ui.trx,installed-stable-ui.trx,installed-dev-ui.trx,stable-after.json,dev-after.json, andbuild-directory.txt. This is generated from the committed package, not manually synchronized diagnostic files. Earlier failing runs remain retained.The harness uses real Velopack installed upgrades with an offline GitHub transport. It does not prove live public feeds, the AppKit UI check/apply flow, production signatures, deltas or hosted CI. Current-head GUI-only acceptance is next; no test process remains live. Keep the applicable remaining criteria open. No push, PR, merge, new release, settings change or Azure login retry occurred. Twenty-eight signed local commits remain prepared across AppKit, starter and shared signing.
Both actual packed-template variants from signed starter head
7eef2a489cb8a1924cb46f4c08e2593a532d930dnow complete the installed smoke: CLI 19/19 UI checks and GUI-only 19/19, all four 532-file portable/full comparisons per variant, stable0.1.0 -> 0.4.0and dev0.3.0-beta.1 -> beta.2real downloads/apply/restarts, exact installed version/target hashes and no cross-channel requests/offers. Guarded cleanup completed.Current GUI-only evidence:
C:/Users/james/.cache/AppKit-acceptance/2026-10-10/foreground-no-cli/artifacts/installed-reserved-desktop/{results.json,published-ui.trx,installed-stable-ui.trx,installed-dev-ui.trx,stable-after.json,dev-after.json,build-directory.txt}. Current CLI evidence remains inartifacts/starter-finish/artifacts/foreground-with-cli/artifacts/installed-foreground/.The first current GUI attempt is retained in sibling
installed-foreground/: published UI 6/7, crash-log timeout, app alive. Its trace owned the target before clicking but afterward reported a distant pointer position over a gclo process. The owner then reserved the desktop; the unchanged fixture passed the complete run. This supports desktop input interference for that observed failure, without proving every earlier timeout had the same cause. Completed older guarded-with-cli evidence moved intact toC:/Users/james/.cache/AppKit-retained-fixtures/2026-10-10/guarded-with-cliwith all seven TRX reports; no evidence deleted.Foundation AppKit
bbf7efdfreshly passes locked restore, zero-warning full build, format verification, 161 unit tests/100% core-update coverage, 14 WinUI/WPF UI tests, seven review-validator tests and ESLint. Current exact-commit review and rollout packets are prepared. Two additional signed shared-rollout commits (helper3334d02, builder5887a83) start from published standards v1.0.0; 35 tests and workflow/docs/hooks pass. Thirty signed local preparation commits total; original checkouts are preserved.Remaining criteria stay open: actual hosted gates/review bootstrap, public starter/package/feed rollout, AppKit's live check/apply integration, final Azure identity/role/resource/signature proof, owner badge attestations and age reassessment. Offline GitHub transport is not hosted or signing evidence. No push, PR, merge, new release, live settings change or Azure retry occurred.
Completed fresh public AppKit installed acceptance for both actual packed template variants:
The real shipped AppKit 0.1.0 public
CheckAsyncandDownloadAndApplyAsyncdrive these upgrades. Only offline transport is injected; actual backend/manager/locator/channel selection remains intact. Both results record successful public checks, apply calls, the target full-package URL, exact installed application SHA256, target manifest, a restarted window, and no remaining update offer. Stable/dev requests stay isolated. Both portable and full archives preserve all 532 original non-PDB publish files for each of four versions. Loose-build rejection and portable behavior pass. Both installations and each unique uninstall registry entry are confirmed removed.Retained evidence is in
~/.cache/AppKit-acceptance/2026-10-10/{public-api-false,public-api-final-cli}/artifacts/installed-public-appkit: results.json, three passing TRX files each, channel before/after JSON, installer/process logs and package byte evidence. GUI runtime source is c2b7b8c; CLI uses e93f7ca. Current signed starter head 49df4902d91d8e4c5e8f29cce9b4f6a2ba5c1a74 adds only the updated acceptance guide after those runtime tests. Source and final packed/renamed CLI script suites pass 46/46. Original metadata-free CLI failure and regression evidence remain retained.Desktop reservation has ended. No build/test process remains intentionally active.
Remaining limits: this proves offline public AppKit service integration, not a public GitHub release feed, interactive update-dialog check/apply, hosted starter CI, production Authenticode signing, deltas or non-x64 runtimes. No broad issue closure or complete compliance claim.
The analyzer exception is now matched to the still-open upstream PSScriptAnalyzer #1708. Latest published release is still 1.25.0. Current follow-up script analysis remains unverified; no error suppression, disabled rule or retry gate was introduced. AppKit #25 remains green except the enforced license policy; standards #31/#32 are green, and EX-0009 remains Proposed. Azure retry stays deferred; no merge/publication/settings/Azure change.