Skip to content

GUI #271 — Native adaptation of approved PR #278 V8 Mixer Console (draft) - #271

Closed
masarray wants to merge 148 commits into
mainfrom
work/operator-console-v6
Closed

masarray wants to merge 148 commits into
mainfrom
work/operator-console-v6

Conversation

@masarray

@masarray masarray commented Nov 1, 2026 •

Copy link
Copy Markdown
Owner

ACTIVE PRODUCT GUI TARGET: PR #278 V8 IS THE ONLY APPROVED OPERATOR CONSOLE (2026-11-02). This PR #271 owns the real native WebView adaptation, NOT an alternative UI concept. One-screen Audition-style IN/OUT/FX/SEND/PAN/MUTE/SOLO/PFL/FADER/MAIN, old hardware-like graphite finish, original channel icon/color at TOP and BOTTOM, BTN-180 crystal buttons, 150/125/105 adaptive banks/one-width pinned MAIN, modeless native F8 VST3. Never adopt #278 mock audio. Exact integration 2f8eb8f5046368991dcdc1ce100bbc50601a4f97: 10/15 visual source checks match, 5 blocking gaps: TOP_BOTTOM_COLOR_ICON, ONE_GRAPHITE_CHASSIS, BTN180_HEADER, PINNED_MAIN_EQUAL_WIDTH, V8_DENSITY_AWARE_BANK. Implement those in existing web source and run rendered viewport QA + generated standalone parity; ENGINE #266 owns actual ChannelId ops and PCM. All earlier v5.1/v7 visual statements below are historical, superseded by PRD v5.2 §9 + ARD v5.2 §K. Owner actionable audit. No UAT before combined exact-SHA release.


STOP-SHIP / MANDATORY PRD v5.1 + ARD v5.1 / PUZZLE SOCKET V8 — Product PRD · Architecture ARD · Owner delivery packet. GUI must consume SAME C++ fixture; no fabricated native LIVE. One-screen direct IN/OUT/VST3/SEND/MAIN workflow; async ACK→same revision snapshot; generated standalone parity before CI. Coordinate exact operations with ENGINE #266. Promotion BLOCKED pending S0 actual producer→GUI→FAT same-fixture proof, S1 real callback, S2 complete mixer and S3 exact-SHA Windows/Chromium + independent QA or explicitly pending hardware. This draft PR is NOT customer test/release ready.

Active v7 GUI reconciliation — 2026-11-01

HEAD: 41931ac18e7ad7d0ee0056f0b33047d2ee85b0d9 · Chromium PASS #41274372617 (exact head, after restoring FAT ownership of workflow). Last full supplemental v6 + M4 GUI mock suite with extended screenshot jobs also PASS: #41274185598.

v7 G0: v6 ConsoleIntent now sends reconnect-safe session-scoped opaque requestId; exact canonical decimal-string uint64 ChannelId/epoch/revision validation, noncanonical ID rejection. Native feature flags remain fail-closed pending ENGINE production callback. No fabricated dynamic Group/FX_RETURN/Monitor capabilities.

v7 G1: actual M4 source GUI has 594px device drawer (not centered wizard), demand-mounted advanced software/hardware crosspoints, direct accepted MAIN output truth (no fallback to inventory), one-pin physical mono (no L=R stereo), invalid restored stereo marked INVALID, source ACK not mislabeled audible LIVE. Legacy CH10 renamed Input 10 rather than falsely claiming an FX Return. CSS/JS and embedded standalone generator byte parity PASS.

Ownership: all changes in web/**, GUI tests and generated standalone; src/** / engine/core/** untouched. .github/workflows/ui-smoke.yml restored identical to main, FAT #270 owns integrating supplemental UI tests and screenshots on one combined SHA. Changes from #275 selectively reconciled, #274 standalone parity incorporated. Branch is intentionally DRAFT pending combined ENGINE #266 and FAT #270; current PR is behind independently advancing main and must be resolved at controlled integration gate.

NOT G2/G3/G4: no evidence of real universal production callback, CH11 PCM, serial Group, wet FX Return, independent Monitor, Windows packaged same-SHA EXE, physical sound or #15 crackle clearance. Customer UAT is not requested.


HARD PUZZLE-SOCKET BLOCKER — PR #279. Owner GUI: Consumer: import integration/console-v6/fixtures.json in UI tests, remove fake MAIN/BUS-FX IDs, one-screen direct I/O/FX with native ACK; regenerate standalone before CI. A green independent PR is NOT an integrated product. Follow shared contract, pass node scripts/check_console_puzzle.mjs; final integration branch must pass --release before heavy CI. Report exact SHA/real runtime evidence in #192. No user UAT before finished G4.

M-U-GUI operator-first console cutover — actual M4 WebView2 (2026-11-01)

Exact GUI HEAD: e2da3051e4c4556a9069714c80662bcb9195e841. Consolidated Chromium CI PASS #41272171864; 12+ MB screenshot artifact (11.3 MB raw).

Unlike the earlier future v6 adapter, this milestone changes the actual M4 Windows mixer in web/mixer-io.js/css, web/mixer-layout.js/css, and the packaged standalone HTML:

  • CONSOLE is the default real operator view: one vertical strip shows the verified native source/format, 6 existing VST inserts (scrollable not deleted), 4 native AUX sends, clickable physical MAIN output, pan/trim-adjacent controls, MUTE/SOLO, meters and fader simultaneously. FX/ROUTE/SENDS remain optional engineering inspector layers; no JS DSP or second router. Status after route ACK is explicitly PCM UNVERIFIED rather than claiming audible LIVE.
  • MAIN uses resize-only measured viewport docking rather than ineffective right-sticky on the last horizontally overflowing flex child; the main strip's existing FX editor, controls and meters remain owned by app.js/JUCE. Real 10-channel bank scrolling and selected strip remain intact, with no redraw on mouse movement.
  • Audio Setup is a three-step operator path (1 DEVICE / 2 INPUT→CHANNEL / 3 MAIN OUT), with basic hardware pin enable, optional folded crosspoints, single selected channel source, guarded native ACK and one-pin STEREO L=R rejection / FIX AS MONO action. The read-only native physical MAIN output status is visible on MAIN strip.
  • The vendor FX context menu now opens beside its trigger rather than on top of it; this fixed an actual Playwright regression where a second right-click after changing the vendor plugin was blocked.
  • Browser tests cover actual legacy M4 unified native strip/FX/send/route simultaneity, pinned MAIN geometry before and after scrolling, 1-pin VB-Cable case, legacy 11-strip engineering fader alignment, right-click VST/Orbit menu, v6 future accepted-ACK projection and standalone CSS/JS parity. No src/** or engine/core/** changes.

Release gate remains explicit: This is a draft source PR, not an updated Windows EXE. GUI Chromium passing does not certify Windows packaging, physical 0FX PCM, callback latency, device switching or audible sound. Real M4 hardware and v6 publisher have distinct owners; native preflight of same-pin stereo and callback/ChannelId schema still require ENGINE #266 / #192, hardware FAT #15. Main advanced 3 independent commits; reconcile before merge/release.


ACTIVE DELIVERY LOCK (2026-11-01): ONE PRODUCT RELEASE TRAIN v7 · OWNER WORK PACKET. G0 schema/branch reconciliation → G1 full native callback and First Sound → G2 real channel/VST/Group/FX Return/Monitor/Show → G3 same-SHA quality/packaging/internal FAT → G4 ONE finished product for customer UAT. No half-built First Sound customer testing. See epic #192 and v7 comment in this PR.

P0 field screenshot correction — M4 Audio Setup simplified (2026-11-01)

Exact HEAD 2c40467be2f3d43d02ffec912a4c048ebb47cf4c, Chromium PASS #41270151309. This is a substantive improvement to the ACTUAL legacy Windows WebView2 web/mixer-io.js/css, not a cosmetic v6 mock.

  • Simplified operator path: 1 DEVICE → 2 INPUT→CHANNEL → 3 MAIN OUT. Driver and real enabled input/output pin checkboxes are basic setup; optional hardware M/L/R matrix is folded. The primary input screen focuses ONE selected CH (initially CH01) rather than presenting 10 simultaneously editable rows. USE INPUT commits via the existing monitor.js native staging and ACK controller without a second manual APPLY. A manual APPLY is only offered for advanced crosspoint edits.
  • Direct MAIN stereo L and R selectors appear upfront, with native __arMixStageMainOutputs and guarded APPLY MAIN OUT. Optional advanced output/monitor crosspoint remains functional.
  • Critical screenshot repair: one verified capture pin cannot be newly selected as stereo. If an old accepted route reports STEREO L==R on a one-pin device, GUI marks INVALID STEREO and offers explicit FIX AS MONO, which issues exactly one guarded native source transaction; it cannot invent a second physical pin or assert PCM. Processing channel M/ST remains independent.
  • Device/MAIN/FX/native PCM owner unchanged; src/** and engine/core/** untouched. Existing old M4 UX remains usable before v6 callback publisher exists; web/mixer-layout.js v6 stays capability-disabled.
  • Source-owned web/mixer-io.* + exact-regenerated standalone parity. Existing Chromium native bridge/mock smoke and new one-pin VB-Cable Playwright scenario passed, with audio-setup-one-pin-1366.png included in run artifacts.
  • Actual screenshot had NO RAW CAPTURE PCM, MIXER NO PCM although OUTPUT ARMED. This is a separate real audio path fault; Windows player audio must be sent to CABLE Input to feed VB-Cable's CABLE Output recording endpoint, not directly to Realtek. No hardware sound claim or 0ms guarantee. ENGINE/integration owner asked in issue #192 to reject same-pin stereo at native preflight and validate physical pin epoch.
  • Windows executable has not been rebuilt/released from this draft PR. Browser/Playwright PASS is not a shipping binary, nor physical FAT P0 — Crackling with 0 VST3: diagnose WASAPI clock/input/output buffering before engine expansion #15.

Operator-first GUI V6 — native-accepted console (issue #268)

Verified GUI SHA: 6fd57b931acb518c09cc0f9e1dc0b168d5067969. Chromium exact-head PASS: run 41267502684. Keep as DRAFT pending ENGINE #266 callback and final transport mapping.

Implementation

  • Native ChannelId-keyed direct strip: verified IN, mono/stereo, native VST3 insert/editor/bypass, drag reorder as native intent, SEND/tap/Sends-on-Faders, direct OUT, PAN/MUTE/SOLO, native LED telemetry and fader (no remount on realtime snapshots).
  • Pinned MAIN, bank arrows and compact responsive grid with equal fader alignment even when channels have different insert counts; 12 geometry combinations validated (1024/1366/1440/1680 px × 600/768/900 px). Uses existing fader asset and low-compositor-cost CSS.
  • One read-only native accepted projection, no JS DSP/router/audio processing or optimistic graph edits. Source/FX/send/output rejections restore unchanged readback. ACCEPTED ACK alone cannot add channels/FX or claim sound; await a newer full accepted snapshot, including realtime changes at same revision.
  • Schema v6 reconciled with new main integration/ConsoleNativeContractV6.h and docs/CONSOLE_BRIDGE_INTEGRATION_CONTRACT_V6.md: schemaVersion:6, lossless decimal-string device/roster/graph revisions and ChannelIds, baseGraphRevision/baseRosterRevision, acceptedGraph/rejected ACK. Accepts read-only control-plane projection but never replaces working M4 unless productionCallbackLive + callbackOwnsChannelIds are true.
  • Production UI mutations require explicit native graph.capabilities.supportedOps; absent capability or unavailable new topology is disabled, not mocked. Native bridge event names and per-control operation mapping still require ENGINE agreement in P0 dynamic mixer — qualify add/delete/reorder, native FX/routing and Show persistence #192.
  • Existing M4 GUI / vendor CH1 path remains functional until native cutover. Opt-in browser demo: web/index.html?console=v6 (disabled, no sound). No fake CH11/Group/Return.
  • Source-owned web/mixer-layout.js and web/mixer-layout.css; regenerated offline standalone exact parity, extended pre-existing Chromium workflow and updated historical baseline pointer test (to current v6 lock), no engine edits.

Validation

  • Chromium run 41267502684: PASS including existing 86 JS contract tests, CSS/offline byte parity, existing UI/geometry smoke and new tests/operator_console_v6_smoke.py.
  • New Playwright: two independent CH2/CH7 source bindings, native FX editor, reorder, SEND, OUT and rejection rollback, positive ACK waiting for snapshot, 64-bit ChannelId, CH11 only on full accepted snapshot, 12 responsive dimensions and stable fader DOM, offline v6 integration readback does not activate.
  • Workflow screenshots available via run artifact.

Explicit blockers / no false release claim

  • ENGINE #266 must publish actual live JUCE v6 snapshot and finish full-fidelity CH1 vendor/Orbit, CH2–10, AUX/MAIN/MONITOR/Show, then real CH11/Group/wet FX Return. Integration's current snapshot is control-thread only and all production flags correctly false.
  • Review #192 comment 6552635148 for exact transport event names, native enum operation mapping, supportedOps, source/destination ID and FX payload contract.
  • Physical 0FX acoustic/hardware #15 is still open. Browser test/CTest cannot certify real audible PCM or latency.
  • main has advanced two independent integration/docs commits since this GUI branch fork; no overlapping files, but update/reconcile before eventual merge.

Ownership respected: no src/** or engine/core/** edits.

masarray commented Nov 1, 2026

Copy link
Copy Markdown
Owner Author

Orchestrator gate — PR #271 is now tracked as GUI owner

Thanks for opening the dedicated GUI PR. Exact files inspected: web/mixer-layout.js/css, generated standalone, tests/operator_console_v6_smoke.py, and .github/workflows/ui-smoke.yml. This is real UI development and is correctly native-capability-gated; however it is NOT yet wired to native production. Current src/Main.cpp still only accepts routingDryApply and emits arMixRoutingLabAck, not the new arMixConsoleIntent / arMixConsoleAck / arMixConsoleSubscribe protocol.

Pre-merge integration blockers

  1. Match ENGINE [ENGINE SOLE OWNER] One native callback → full-fidelity ChannelId cutover (draft) #266's typed native ChannelId → browser ID wire with opaque string IDs, never JS coercion of 64-bit numeric IDs; fixture ch-07 is a UI test marker, not actual native identity. INTEGRATION v6: native accepted ChannelId readback + intent ACK fence + two-input golden PCM #269 currently projects decimal native ChannelIds as strings, with graph accepted but productionCallbackLive FALSE.
  2. Agree the requestId wire (GUI currently sends gui<id>:<sequence> opaque string), baseRevision, deviceEpoch, and complete graph.capabilities.supportedOps[] before enabling any real operations; v6 current native command handler doesn't implement these events. Relevant discussion: #192.
  3. GUI PR and FAT PR [INTEGRATION/FAT v7 G0] Canonical JUCE WebView ACK/PCM evidence and exact-SHA release gate #270 both edit .github/workflows/ui-smoke.yml. FAT [INTEGRATION/FAT v7 G0] Canonical JUCE WebView ACK/PCM evidence and exact-SHA release gate #270 is final owner of CI YAML composition: preserve BOTH your Playwright gate and their FAT evidence tests in one existing Chromium workflow after merge. Do not accept branch-only CI as combined-sha proof.
  4. Keep demo clearly marked and no popup-only fake +GROUP/FX RETURN: no native capability → disabled. Avoid heavy DOM repaint or per-meter remount.

No premature GUI merge without exact native WebView bridge, combined tree CI and separate hardware FAT #15. Evidence and response at #192.

masarray commented Nov 1, 2026

Copy link
Copy Markdown
Owner Author

CI finding — exact GUI run #41266802408

Chromium failed at Verify CSS ownership build and offline/WebView2 parity before Playwright. Log: Outdated generated GUI artifact: standalone HTML; run python scripts/build_ui_css.py. This is a source-to-embedded asset parity failure, not a verdict on v6 layout or native audio. GUI owner should run the existing generator after final web/mixer-layout.js/css edits and commit exact AR-MIX-Live-FX-Host-Standalone-v0.3.html output. Do NOT hand-edit the huge standalone independently or weaken --check. Then one consolidated Chromium run on the final GUI branch; no extra workflow required. Evidence: run #41266802408.

masarray added a commit that referenced this pull request Nov 1, 2026
…ceptance

Promote Windows-validated control-only ConsoleNativeContractV6 and exact native golden PCM for CH7/CH2, Group, wet FX Return, Monitor and reject rollback. Physical I/O, VST full-fidelity and production callback remain explicitly unimplemented and are owned by ENGINE #266 / GUI #271.

masarray commented Nov 4, 2026

Copy link
Copy Markdown
Owner Author

ENGINE B2 reconciliation interface for GUI owner, source SHA de347b32123ee3523f2bc7d743631b752e1ce305 on PR #379 (Windows exact-head CTest in progress, not merged/qualified yet): installed ChannelId renderer exports accepted stable edgeId/from/to/gainLinear/tap/primaryOutput through dryRoutingLab.nativeBus.edges, scoped to legacyM4.nativeBus control readback; native control operation currently NATIVE_APPLY_WIRE_TRANSACTION (CONNECT/REMOVE/RETARGET/ROUTE_ONLY) in LiveConsoleBridgeV6::processNativeBusIntent, with nativeGraphRevision/nativeRosterRevision ACK and existing device/legacy revision fences. Native mutation routes through the same LiveDryRoutingLab publisher/VST3 lease; no browser graph authority. Wire edit may now be accepted while output ARMED only when physical source/clock identity is unchanged. Do not map scoped namespace to universal graph.capabilities.supportedOps or mark GUI LIVE until ENGINE #266 merged and v8 same-epoch ACK+accepted-snapshot bridge/combined FAT #270 are verified. Preserve visual GUI. This is coordination only; no GUI file modifications by ENGINE.

masarray commented Nov 4, 2026

Copy link
Copy Markdown
Owner Author

Packet C GUI milestone VERIFIED — 2026-11-04. Existing PR #271 latest head 01e6eea3db5918fbf98369fb4f26e113051b7f64: native v8 WIRE consumer fail-closed on installed supportedOps, exact decimal ChannelId/EdgeId/revision, canonical graph projection and scoped MAIN unplug/replug/ROUTE_ONLY intents through arMixConsoleIntent → ACK → accepted snapshot. Incremental safety fixes: de063388a rejects structural ACK that fails to advance graph revision; 9acae7b37 removes orphaned pending locks for malformed matched ACK while leaving accepted routing unchanged; 01e6eea3d updates both old and new Playwright assertions to prove retry and ignore late reply. Generated standalone parity 3112ff2b; screenshot upload ownership 638a067c. Exact-head Chromium CI SUCCESS: https://github.com/masarray/arsonmix/actions/runs/41810456389 (82 steps, includes native v8 ACK/WIRE consumer and V6 visual geometry tests). Artifact contains actual V6 1366x768 and 1680x900 snapshots. These show the V6 console does not yet render approved physical MAIN wire socket/cable geometry; no visual equivalence to merged Pages GUI #376 is claimed. main UI/Pages Packet A verified at 7ddf79bb3f26bea32bc43fc4995319ec7f04225c. BLOCKERS: Engine #266 currently has different NATIVE_APPLY_WIRE_TRANSACTION on native M5 path and no advertised v8 APPLY_WIRE_TRANSACTION/accepted graph.edges[] + mainChannelId producer; issue #192 has exact ABI discrepancy. #270 same C++ producer fixture, native visual/interaction parity and real Windows PCM/hardware #15 are pending. Keep PR draft; do NOT merge as live product or overwrite approved V52–V56. No CSS/fader/meter/FX redesign in this milestone.

masarray commented Nov 4, 2026

Copy link
Copy Markdown
Owner Author

ENGINE C1 source integration now in draft #384, exact SHA f56056a68d8582c2ee0d3bf58e5f55dea03982c4, Windows CI 41811922398 still in progress, not merged/qualified. When the installed JUCE ChannelId PCM publisher is truly active and advertises native WIRE, arMixConsoleSnapshot.graph now projects the accepted native revision, rosterRevision, channels[], edges[] (decimal string edgeId/from/to, tap, gainLinear, primaryOutput) and scoped supportedOp APPLY_WIRE_TRANSACTION. Standard v8 arMixConsoleIntent (requestId/deviceEpoch/baseGraphRevision/baseRosterRevision/operation:'APPLY_WIRE_TRANSACTION'/targetChannelId/payload.changes[]) maps to the existing same native transaction/FX lease. v8 arMixConsoleAck reflects accepted native graph+roster revisions; next arMixConsoleSnapshot must match before cable COMMITTED. Unfocused source/edge attempts reject before publication. productionCallbackLive remains false until full Show/VST3/FAT parity, so do NOT display product-LIVE based solely on this sub-operation. Preserve GUI approved visuals; no changes made to your web/** files.

masarray commented Nov 4, 2026

Copy link
Copy Markdown
Owner Author

Native GUI adapter handoff (main GUI V59 / PR #385): main@f182e676 contains approved selected-only WIRE + quiet collapse + custom-only OUT. Read docs/workstreams/WIRE_V59_MAIN_NATIVE_ENGINE_RECONCILIATION_20261104.md from PR #385. Please adapt web/mixer-layout.js (native WebView, NOT Pages site/preview-v2) to consume native accepted v8 graph.edges[] with stable decimal string edgeId, selected-only IN/OUT, MAIN fragments only for uniquely selected expanded channel and OUT lit only for non-MAIN sends. Confirmed handshake blocker: validSnapshot currently rejects nonempty graph/support ops when productionCallbackLive=false, while supported('APPLY_WIRE_TRANSACTION') requires LIVE; ENGINE C1 #384 intentionally keeps LIVE false although it exposes installed native WIRE readback. Also C1 rows format/parallelSends and edges without enabled/signalKind do not yet satisfy the validator. Do not weaken unrelated M4 safety or fake LIVE. Agree a bounded installed-native-readback / NOT PRODUCT LIVE stage with #266/#384 and test real native producer ACK + subsequent exact-epoch/revision snapshot under #270 joined FAT.

masarray commented Nov 4, 2026

Copy link
Copy Markdown
Owner Author

Native GUI owner action. The existing web/mixer-layout.js adaptation of retired web/index.html is not visual parity. Stop growing that alternative shell. Rebase the native renderer on the generated /preview/ screen (including the approved PNG button variant), preserve current Pages V59 behavior, and bind it to actual engine acknowledgments without mock audio.

OWNER CORRECTION — EXACT USER-APPROVED GUI, NO RECREATION (2026-11-04)

The user explicitly confirms that https://masarray.github.io/arsonmix/preview/ is the ONLY approved Windows mixer GUI/UX target. ENGINE must be stitched into that GUI; never redesign/reimagine another native console.

Verified source provenance (main at GUI V59, PR #383):

  • site/preview/index.html is only the wrapper; its iframe actually loads ../preview-buttons/index.html.
  • scripts/build_pages.py creates dist-pages/preview-buttons/index.html at publish time, taking all current HTML/WIRE/fader/meter/FX layout and assets from site/preview-v2/** but substituting the user-approved site/preview-buttons/assets/mixer-control-keys.css, mixer-control-keys.js, and PNG artwork. This generated page, NOT site/preview/mixer.html or the plain site/preview-v2/index.html alone, is the effective /preview/ screen.
  • web/index.html is retired legacy UI and web/console-native.html/.css/.js is a divergent native-created screen. Neither is approved as a replacement visual source.
  • PR INTEGRATION (DRAFT): approved M3 Console in native JUCE, real snapshot/intent path — universal still blocked #356 already attempted a Pages→JUCE source port, but it is stale (M3/V48) and not merged. Reuse only applicable native wiring/resource patterns after reconciling with current /preview/ V59; do not merge its old graphics or old engine wholesale.

Binding implementation contract: preserve the exact generated /preview/ renderer, asset material, geometry, selected-only WIRE, folded quiet MAIN, original fader/LED/FX/button behaviors, replacing simulated state with a thin native accepted-snapshot/intent/ACK adapter. Stable ChannelId/EdgeId (decimal uint64 strings), graph revisions and real VST3/PCM come exclusively from the sole JUCE engine. The existing preview's JS demo model is never DSP authority. Maintain one native callback; no parallel GUI, router or generic replacement layout. Do not substitute a fresh 'native console' just because it is easy to wire.

Acceptance before Windows GUI promotion: automatic source/asset provenance assertion against a freshly generated /preview-buttons/ bundle, rendered screenshot and interaction parity at 1366×768 + standard/compact/expanded views, actual EXE embedding proof, controls→real native ACK+same-revision snapshot tests, and real PCM/VST3 FAT separately. Fail closed on a different GUI. No UAT or feature-complete claim until native joined evidence.

This corrects conflicting older PR #271/#266 assumptions; avoid another GUI design study or duplicate CI workflow. Focus directly on reusing the approved GUI and binding ENGINE.

masarray commented Nov 4, 2026

Copy link
Copy Markdown
Owner Author

CLOSED AS SUPERSEDED — binding owner GUI correction (2026-11-04). Retiring the alternative web/mixer-layout.js native GUI. Owner now requires EXACT latest https://masarray.github.io/arsonmix/preview-v2/ with thin native adapter, not reconstructed M4/V6 UI. Native adapter/ACK ideas may be reused selectively through #389; this PR must not be merged as product GUI. Canonical docs: main AGENTS.md + docs/workstreams/HANDOFF_APPROVED_PREVIEW_V2_NATIVE_20261104.md.

This pull request was closed.
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