Skip to content

CI: context-aware native audio vs fast GUI/Pages lanes (no extra workflows) - #386

Merged
masarray merged 4 commits into
mainfrom
ci/smart-context-aware-fast-development-20261104
Nov 4, 2026
Merged

masarray merged 4 commits into
mainfrom
ci/smart-context-aware-fast-development-20261104

Conversation

@masarray

@masarray masarray commented Nov 4, 2026

Copy link
Copy Markdown
Owner

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.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-04T10:28:25.541413Z 8e85613 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

masarray commented Nov 4, 2026

Copy link
Copy Markdown
Owner Author

Exact-head evidence (2026-11-04): UI smoke (Chromium) at 8e85613780cdc6f9b186e880793aae10c21c4206 SUCCESS: 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 Host run #41814207883 still compiling at last check; no native PASS claim or merge until actual outcome.

@masarray
masarray merged commit 064e449 into main Nov 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant