You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI: context-aware native audio vs fast GUI/Pages lanes (no extra workflows) - #386
Goal: faster ArSonMix development without weakening realtime audio
Real changes to existing workflows and executable CI policy tests. No new workflow, no VST3 engine/GUI/CSS runtime changes.
Scope-aware triggers
Native Windows on actual engine/**, src/**, CMake, C++ tests, native web/bridge.js and web/monitor.js, integration contract and explicit release/build scripts. NO blanket web/** or standalone GUI HTML trigger on main. Native owner PRs still run full CMake build + complete CTest; critical PCM/RT/VST3/reliability gate is preserved.
Visual GUI (site/**, other web/**, static HTML, CSS) runs Chromium / graph tests and ultimately GitHub Pages after a successful main push; it does not schedule a Windows build.
UI quick checks preserve canonical WIRE graph, MAIN DOM, v49 direct gestures, v53 FX, v54/V55 WIRE/FX/fader, V51 meter and rollback, approved assets and responsive shell. All historical CSS v8–v27 regressions and legacy extended visual tests still run via UI smoke workflow_dispatch or integration/product-* release PR instead of every ordinary PR/main push.
Native PRs: full audio CMake+CTest, but skip expensive ZIP packaging, staging and standalone artifact verification unless explicitly a release integration / M4 FAT PR. Main/manual still builds & verifies artifacts, with no silent release.
Pages publication unchanged: one guarded downstream publisher reacts only to a successful quick Chromium main push, verifies head SHA and ignores obsolete pushes.
No CI fan-out from docs-only; default triggers cancel superseded PR runs.
Executable regression
tests/ci_workflow_efficiency_test.mjs now enforces file → workflow routing for GUI-only, native-only, WebView native bridge, mixed integration, docs, isolated tests, full manual QA and upload gates.
Evidence and safety
Baseline measured prior: UI/Chromium ~8–12min, Windows ~12–13min, each on overlapping change sets. Speedup is target until exact SHA runs confirm it; no claims of tested latency improvement. Full native CTest and 0FX physical crackle #15 release blocker stay mandatory.
Review/test gate: GitHub Actions must validate both updated workflows on this PR. If tests fail, correct policy/config rather than loosening audio quality. This PR must not collide with GUI/ENGINE owners #266/#271/#270.
Exact-head evidence (2026-11-04): UI smoke (Chromium) at 8e85613780cdc6f9b186e880793aae10c21c4206SUCCESS: run #41814207786, ~1.6 min elapsed, compared with several 8–12 min pre-refactor runs. This confirms the intended fast GUI lane. Static path/CI-policy regression matrix verified GUI-only -> UI, engine/C++ -> Windows, native bridge -> both, docs -> neither. Windows Native VST3 Hostrun #41814207883 still compiling at last check; no native PASS claim or merge until actual outcome.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal: faster ArSonMix development without weakening realtime audio
Real changes to existing workflows and executable CI policy tests. No new workflow, no VST3 engine/GUI/CSS runtime changes.
Scope-aware triggers
engine/**,src/**, CMake, C++ tests, nativeweb/bridge.jsandweb/monitor.js, integration contract and explicit release/build scripts. NO blanketweb/**or standalone GUI HTML trigger on main. Native owner PRs still run full CMake build + complete CTest; critical PCM/RT/VST3/reliability gate is preserved.site/**, otherweb/**, static HTML, CSS) runs Chromium / graph tests and ultimately GitHub Pages after a successful main push; it does not schedule a Windows build.integration/product-*release PR instead of every ordinary PR/main push.mainpush, verifies head SHA and ignores obsolete pushes.Executable regression
tests/ci_workflow_efficiency_test.mjsnow enforces file → workflow routing for GUI-only, native-only, WebView native bridge, mixed integration, docs, isolated tests, full manual QA and upload gates.Evidence and safety
Baseline measured prior: UI/Chromium ~8–12min, Windows ~12–13min, each on overlapping change sets. Speedup is target until exact SHA runs confirm it; no claims of tested latency improvement. Full native CTest and 0FX physical crackle #15 release blocker stay mandatory.
Review/test gate: GitHub Actions must validate both updated workflows on this PR. If tests fail, correct policy/config rather than loosening audio quality. This PR must not collide with GUI/ENGINE owners #266/#271/#270.