Skip to content

[OSS] Smart Auto Updater — published release, recovery and real Windows FAT #625

Open

Description

@masarray

Milestone B verified triage — 2026-11-17: P1 / updater / qualification / field-fat. Classification ≠ completion of product feature or physical FAT.

Scope / release boundary: Published updater already exists; verify current Windows release rather than rewrite it.

Exit criteria:

  • Prove upgrade, rollback, repair and interruption behavior on exact public alpha.26 installer with SHA256/provenance and old version fixture.
  • Verify user's Studio/.smix and VST3 settings preserved, no forced app closure during live monitoring, offline/restart recovery.

Canonical issue ledger. Preserve historical evidence below; no speculative merging or rewriting approved audio.


Audit baseline

Repository masarray/arsonmix, main 0e3115f (2026-11-13). Smart Auto Updater M3 PR #501 and safe installer PR #443 are merged. This issue tracks remaining production qualification and user-facing recovery; it is NOT an engine-rewrite request or an assertion that the alpha updater is fundamentally broken.

Confirmed safeguards (preserve)

  • Independent below-normal PowerShell supervisor, separate from audio callback; GitHub published release identity, strict SemVer, SHA256+size+checksums+provenance; staged candidate AND old rollback installer.
  • No in-use mixer close by auto-update, Inno fail-closed active-process/exclusive-file checks; only normal exit applies; one bounded retry, 20min network cooldown, state reconciliation, Start Menu Repair ArSonMix.
  • GUI_READY + EXE SHA/length post-install gate, studio/.smix/plugin state retained. Authentic historical alpha.4→alpha.5→alpha.4 Inno FAT https://github.com/masarray/arsonmix/actions/runs/42721612866 passed at an older exact SHA. This is not desktop WebView2/ASIO verification of current main.

Open-source update policy (owner decision 2026-11-13)

No paid/commercial code-signing certificate, DRM, licensing, anti-crack enforcement, mandatory version lock, or vendor-controlled service is required to ship ArSonMix. Treat official GitHub Releases under masarray/arsonmix as the project distribution authority. The SHA-256 release digests, explicit SHA256SUMS.txt, INSTALLER_PROVENANCE.json, exact source commit, byte-level pre-execution checks and verified offline rollback are the actual project baseline. HTTPS/TLS plus unique release identity remain mandatory. Optional free publisher signing can be considered separately, never a shipping blocker or claimed defense against local MOD binaries. Do not claim tamper-proof publisher identity from GitHub-hosted checksums alone.

P1: Honest post-update health — partially resolved in M4

M4 now has a silent GUI_READY_NO_AUDIO WebView2/native probe, explicitly does not start audio devices or session writes, and avoids surprise audible relaunch. Continue test of GUI failure and rollback on disposable Windows runner. This probe qualifies app/UI startup, not ASIO listening; driver unavailable should not invalidate a healthy executable.

M4 resolved: No-surprise UX

Merged PR #628: compact one-OK nonmodal GUI notice, exact candidate/previous commit consent, X dismisses; safe installation after normal Quit; startup probe silent/no ASIO; no auto-launching audible mixer. Keep this UX stable and do not invent a technical updater dashboard.

P1: Recovery when main EXE cannot run

Repair ArSonMix is manually invoked and needs installed provenance plus GitHub access. Offline/missing provenance/PowerShell blocked/partial install can require manual intervention. Define an optional open-source offline recovery package distributed through the official GitHub Releases, or a verified last-known-good local installer cache, with bounded retry and a safe fallback that never removes Studio/.smix/user VST or kills an active mix. Commercial signing is not required.

M5 resolved / remaining P1: Legacy and transient resilience

Merged PR #641: bounded 1000-release history instead of first 100; re-validate candidate+rollback SHA-256 immediately before execution and rollback again before use. Continue focused cases: rate limit, no network, partial download, disk space, AV file locking, interrupted install, bounded overall transaction time/cleanup.

Required real Windows acceptance

  1. Verified staged update on natural exit; preserve settings/.smix/custom VST, no installer while mixer active.
  2. Current native Windows GUI and original audio settings restored, with distinct WebView2/session/audio health evidence (not mere ready marker).
  3. Corrupt/revoked/candidate-change or checksum-mismatch rejected before execution; old image retained. Digital signer identity is optional, not a release gate.
  4. Missing EXE, damaged state/provenance, offline and partial Inno result — deterministic safe recovery or clear recovery path, no infinite loop.
  5. Fresh official GitHub version upgrade + rollback on exact source SHA; GUI probe and owner ASIO hearing are separate evidence—not a blocker to shipping an alpha preview build.
  6. Intentional Quit never accidentally re-arms the live mixer. Unsupported/portable builds never auto-install.

Delivery discipline

Isolated updater hardening PR; no DSP/WIRE/GUI mixer redesign. Run low-cost deterministic policy tests, then one opt-in genuine Windows FAT and desktop validation. Alpha installer can ship after exact-source Windows build, real Inno smoke, SHA-256 provenance and safe failure tests pass. Physical ASIO owner test still needed for audio release qualification, but commercial signing is not required. Never advertise impossible 'fool-proof MOD prevention'.

M4 + M5 integrated checkpoint

Alpha.18 candidate (2026-11-13)

  • Owner-sourced official release branch releases/alpha/v0.5.0-alpha.18 at 98ef30d1305eb1efe3b9104297747c97fdc8167c; contains merged M4/M5 main plus its release notes only.
  • Authenticated owner command accepted in issue Release controller: owner-only exact-SHA comments, tri-OS roadmap, landing-only downloads #450; SMART_RELEASE_DISPATCHED confirmed (controller run 43377638043). Exact-SHA Windows build and publisher run 43377654851 is running. No release is public until that workflow succeeds and the real GitHub release/installer assets exist.
  • Owner instruction: ArSonMix is a community open-source project, and commercial digital signing is neither required nor a shipping gate. Do not reintroduce DRM, license checks or mandatory anti-crack claims.

Activity

  1. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    Implementation checkpoint 2026-11-13: M4 PR #628 exact SHA 72b2167797678ef814dd7217e11e1438ba382d40 contains real JUCE/PowerShell/test changes. User sees one OK for a fully staged published candidate (tag+source SHA+previous SHA); auto-install remains deferred to natural close; no auto-force kill. The post-install probe now skips audio device opening, session restore and shutdown saving; it emits GUI_READY_NO_AUDIO, exits and does not secretly restart audible mixing. Windows Inno smoke and quick contract passed at this SHA; selective exact-head Windows native CI requested via owner comment. NOT production mandatory/anti-tamper: official publisher signing, hard min-version attestation and physical ASIO compatibility still need separate gates.

  2. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    Updater M4 integration handoff — 2026-11-13

    PR #628 #628

    Current reconciled SHA: b4e7554ead5ec0400450e0d649226a969065c33a; includes main@383cf1927498d9c3f557110d71825363077b5be6 and preserves all concurrent preview/WIRE changes. PR diff is only 3 scoped files: src/Main.cpp, installer/ArSonMixAutoUpdate.ps1, tests/windows_installer_contract_test.mjs.

    New behavior: stage candidate + rollback with existing M3 verified release rules; 10s low-cost message-thread polling; compact nonmodal native dark update notice, OK-only consent (X = dismiss), exact tag/candidateSHA/previousSHA approval; silent install only after natural host exit. No new background service, no audio callback work, no forced close.

    Post-install ARSONMIX_UPDATE_PROBE uses GUI_READY_NO_AUDIO: no audio-engine device startup/ASIO output/FX catalog scan/session write, and an automatic JUCE exit after marker. A finished update does not secretly reopen the audible mixer.

    Evidence on reconciled SHA: PR fast contracts PASS; Inno graceful smoke PASS (run 43361017626). Full exact-head Windows native/MSVC CTest dispatched once via standard owner /arsonmix-ci native and is https://github.com/masarray/arsonmix/actions/runs/43361099478; not a PASS until terminal success. Prior native dispatched SHA was superseded to avoid running obsolete binary qualification.

    Important separation: M4 is merge candidate after exact-head native PASS, not certificate for production mandatory anti-tamper update. Authentic publisher signing/pinned signer, genuine two-release upgrade/rollback with desktop GUI and ASIO hearing, absent provenance/offline launcher recovery and minimum-version policy remain unresolved and MUST NOT be claimed complete or silently activated.

  3. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    M4 source milestone merged — 2026-11-13

    PR #628 merged into main as squash commit 7232c1ebe9e490ed20bcb02cb8cbffcd02e847ed (expected exact head c9c9f1582c6db9bb483082c30582e7993de48747). Exact-head Windows Inno silent upgrade smoke + updater contracts PASS (run 43365256324); fast contracts PASS (run 43365256272); selective Windows MSVC compile/realtime CTest PASS (run 43365384875). Pre-merge compare showed only src/Main.cpp, installer/ArSonMixAutoUpdate.ps1, and tests/windows_installer_contract_test.mjs modified; main was ancestor (0 behind). M4 provides nonmodal explicit OK consent bound to staged release identity and GUI-only health probe without audio engine startup. Source milestone only; no public release. Production remains gated on independent publisher signing/verification, genuine Windows release upgrade/rollback, visual GUI and physical ASIO/session verification. No anti-crack guarantee.

  4. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    M4 + M5 updater source milestones merged — 2026-11-13

    • M4 Updater M4: one-click OK consent for background-staged safe Windows upgrade #628 merged into main at 7232c1ebe9e490ed20bcb02cb8cbffcd02e847ed. Confirmed exact-head native Windows MSVC / realtime CTest PASS (run 43365384875), Windows Inno smoke PASS, fast contract PASS. Safe nonmodal one-OK consent is bound to the exact proposed version + source commit + previous source, and on-exit update does not close or rearm a live ASIO mixer. GUI-only post-install probe intentionally does not certify real audio/ASIO.

    • M5 Updater M5: legacy release paging and last-mile install/rollback SHA verification #641 merged with explicit expected head b634a914b7d0d5e7792381a0162cb03d721bdf0f, squash commit a6b8a3f4c98f7c8552442ffb1ae68f990034f2e0. Fast native contracts PASS (run 43376009458), Windows PowerShell/Inno smoke PASS (run 43376009170). M5 supports bounded traversal of GitHub's release history beyond the first 100 entries (up to 1000, fail closed) and re-hashes BOTH staged candidate and offline rollback executables immediately before Inno execution, plus another rollback hash check before rollback. Includes offline PowerShell tamper fixtures and Node regression contracts. Only installer/updater and test code changed; no DSP/PCM/ASIO callback modifications.

    Delivery classification: M4/M5 integrated source milestone is DONE, but not yet included in public release (latest verified published was v0.5.0-alpha.17). This issue remains OPEN for production hardening: independent pinned publisher Authenticode or signed manifest + key rotation/revocation, actual contemporary two-authentic-release Windows desktop/rollback qualification, session and physical ASIO owner listening, and offline recovery if provenance/PowerShell is unavailable. GitHub release SHA256 and JSON provenance alone are not proof of the independent software publisher or resistance to locally modified/cracked binaries. Do not claim mandatory anti-crack enforcement until that security boundary exists.

    No unnecessary Windows native rebuild was triggered for M5 because it changed no native C++; Windows Inno and policy tests were the actual safety gates.

  5. changed the title [-][P0] Audit Smart Auto Updater: signing, honest health, offline recovery, no-surprise UX[/-] [+][OSS] Smart Auto Updater — published release, recovery and real Windows FAT[/+] on Nov 13, 2026
  6. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    OSS updater release milestone shipped — v0.5.0-alpha.18 (2026-11-13)

    Official GitHub prerelease published: https://github.com/masarray/arsonmix/releases/tag/v0.5.0-alpha.18

    • Immutable release source 98ef30d1305eb1efe3b9104297747c97fdc8167c on releases/alpha/v0.5.0-alpha.18. Candidate differs from merged M4+M5 main@a6b8a3f4c98f7c8552442ffb1ae68f990034f2e0 by release notes only; source lineage checked against main at owner dispatch.
    • Owner-authenticated controller PASS 43377638043, including SMART_RELEASE_DISPATCHED.
    • Exact-SHA Windows release build, native executable/portable integrity, Inno install/upgrade/uninstall qualification, provenance and SHA256 assets, release publication, and official Pages refresh dispatch all SUCCESS: 43377654851.
    • GitHub Pages deployment build + deploy SUCCESS: 43378093159.
    • Seven official release assets uploaded: ArSonMix-v0.5.0-alpha.18-Windows-x64-Setup.exe, ArSonMix-v0.5.0-alpha.18-Windows-x64-Setup.zip, Portable.zip, BUILD_PROVENANCE.json, INSTALLER_PROVENANCE.json, FACTORYFX_STAGE_REPORT.json and SHA256SUMS.txt.
    • This release contains merged M4 nonmodal OK on-next-update consent + safe GUI-only check, and M5 bounded older release discovery / repeated candidate+rollback byte verification.

    Project policy (explicit owner instruction): no commercial signing needed. Official masarray/arsonmix Releases, GitHub-supplied SHA-256 and the included checksum/provenance crosschecks are enough for an OSS alpha preview. No paid certificate, DRM, proprietary licensing or anti-crack gate added.

    What is not claimed: a physical ASIO listening session was not conducted by GitHub Actions; no claim that unsigned binaries are cryptographically tied to a privately held publisher key; no guarantee against a locally modified executable. Existing old versions obey their embedded prior updater until this build is installed. Physical owner hearing and unusual offline/AV-blocked repairs can be follow-on work, not artificial commercial signing blockers.

  7. masarray commented on Nov 17, 2026

    @masarray
    OwnerAuthor

    2026-11-18 alpha.26 → alpha.27 legacy-user Smart Auto Updater source/release audit

    Conclusion: installed official Windows per-user alpha.26 has code required for startup check and background stage, not immediate silent install at launch. At app startup src/Main.cpp constructs native ConsoleWindow then launchSmartUpdater(false) (approx. lines 8689–8691); launchSmartUpdater(true) is called on normal application shutdown only after session persistence and when Inno is not closing and Windows is not shutting down (approx. 8701–8720). launchSmartUpdater requires exact installed ArSonMix.exe, adjacent ArSonMixAutoUpdate.ps1, adjacent BUILD_PROVENANCE.json, Windows PowerShell, and absence of portable_mode.txt. installer/ArSonMix.iss includes the script, provenance, and EXE in its installed files. Source blob SHA for Main.cpp, updater.ps1 and installer.iss is IDENTICAL in actual public alpha.26 and alpha.27 source commits; no updater rewrite was introduced by alpha.27.

    Published release metadata: alpha.26 source 8ec5b8a3e07837c85fb6e06c952cff1621fecc51; alpha.27 source a93759d6843e30f75a4a28adf9a09c0c1c375fa3. Both are non-draft public prereleases with exactly one uploaded Setup EXE plus required INSTALLER_PROVENANCE.json and SHA256SUMS.txt assets with SHA-256 digests. Updater's SemVer, SHA and asset gates are therefore metadata-eligible for alpha.26 → alpha.27.

    Detailed UX and safety boundaries: source startup updater fetches release metadata only when 20-min attempt cooldown / 6-hour successful-check throttle allows, then downloads and SHA-verifies the target EXE and current-version rollback EXE into %LOCALAPPDATA%\\ArSonMix\\Updates\\stage, marks phase=staged and exits. Native GUI polls staged state every ~10 s and offers small NONMODAL OK notice. User acknowledgement is required for an upgrade: only normal Quit may spawn the post-exit installer. The installer refuses an active session and neither updater nor auto Inno sends WM_CLOSE. No installation while the mixer is open, no auto silent upgrade without OK, and no automatic audible launch after Quit. The standalone silent GUI_READY_NO_AUDIO probe is not an ASIO playback certification. Portable builds, missing updater bootstrap, unknown source provenance, GitHub/network failures and unchanged version do not auto-upgrade; older binaries without updater need one manual setup bootstrap.

    Verified vs UNVERIFIED: source/installer contract tests include static launch/consent/gating and PowerShell -PolicySelfTest. Release #44185766988 built/verified the genuine alpha.27 per-user Inno installer (build, install, upgrade/uninstall, provenance and checksums). The genuine-two-release FAT scripts/test_two_genuine_inno_releases_windows.ps1 still targets historical alpha.4 → alpha.5 → rollback alpha.4, not a real alpha.26→alpha.27 updater-driven startup/dowload/OK/normal-exit transaction. Thus actual end-to-end legacy-user auto-update success remains UNPROVEN; do not equate a passing installation smoke with a verified desktop updater transaction.

    Specific remaining P1 acceptance (no DSP/PCM changes):

    1. Disposable Windows image: install authentic alpha.26 with real GitHub manifest and preserve sentinel user .smix, Studio and user VST directories. Launch normally ONLINE and capture last-result.txt transition STAGED v0.5.0-alpha.27 WAITING_FOR_NORMAL_EXIT; require exact eligible candidate/rollback SHA and version. Allow for successful-check six-hour throttle; avoid artificially bypassing cooldown for production.
    2. Verify user sees nonmodal OK acknowledgement, X-dismiss does not approve; while singer/ASIO mixer remains open there is no EXE replacement nor forced close. Click OK then intentional Quit only; verify silent installer, actual installed exact commit and EXE digest, preserved sessions and no automatic audible device arm/reopen. Open app again and verify alpha.27.
    3. Offline/revocation/tampered/partial stage, antivirus/file lock, failed GUI-only probe and rollback behavior should fail closed, never delete user files.
    4. Record logs %LOCALAPPDATA%\\ArSonMix\\Updates\\last-result.txt, stage/state and installer provenance; redact personal audio/VST paths before sharing.
    5. Leave issue open as P1 until a real fresh-release end-to-end Windows updater FAT is recorded. Do not publish misleading claim that all historical versions update on app open. No commercial signing is required by the current OSS project policy.

    This is an audit record of released code and GitHub asset metadata, not a statement that a user's PC was remotely tested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions