Skip to content

M3-E FAT: exact-SHA Windows hardware kit, 44.1/48k 0FX/VST3 evidence and integrity gates - #406

Merged
masarray merged 8 commits into
mainfrom
fat/m3e-exact-sha-hardware-evidence-20261105
Nov 5, 2026
Merged

masarray merged 8 commits into
mainfrom
fat/m3e-exact-sha-hardware-evidence-20261105

Conversation

@masarray

@masarray masarray commented Nov 4, 2026

Copy link
Copy Markdown
Owner

M3-E — FAT-only substantial milestone (no PCM/GUI fork)

Base: main@6b51caf07dd4ae04047c04717adcb3f53e3f673f. This PR extracts only the independent scripts/collect_hardware_fat_windows.ps1 from parked historical #270; it does NOT merge #270's src/**, engine/**, site/**, CMake or workflows.

Implemented on branch

  • Windows distribution scripts/package_native_windows.ps1 now packages independent offline field collector and Node FAT verifier, tied to immutable BUILD_PROVENANCE.json hashes (sourceCommit, exe SHA256, approved /preview/ GUI SHA256, collector SHA256, verifier SHA256).
  • scripts/verify_native_windows_artifact.ps1 checks current checkout → distribution → ZIP member SHA256 for both FAT tools as well as existing AMD64 GUI EXE and approved resource parity. Wrong EXE, swapped collector, altered ZIP member all fail.
  • Read-only scripts/m3e_fat_evidence_gate.mjs checks two distinct 44.1 kHz and 48 kHz session matrices: OUTPUT_ONLY_TONE, CAPTURE_ONLY, wired DRY_THROUGH_0FX, wired LIVE_THROUGH_1FX, 1800 seconds each for 0FX/1FX, identical endpoint/driver/buffer/physical pins, VST3 identity, full report SHA256, independent human witness. Detects forged elapsed timing, missing hashes, active session and mismatched exact source/exe SHA.
  • Automated offline regression: tests/m3e_fat_evidence_gate.test.mjs imported through existing tests/native_artifact_packaging_contract_test.mjs, already run in the existing Windows Node gate. No new workflow and no unnecessary GUI CI.
  • Operator runbook docs/M3E_FAT_RELEASE_ADMISSION_20261105.md and updated packaged first-sound hardware guide.

Important truth boundaries

Merge criteria

Require exact-head existing Windows native/MSVC CTest + offline FAT test PASS; package/ZIP verifier on packaged Windows job (may only run on main/manual per workflow, so record PENDING until independently executed). If CI proves a bug, fix only this FAT-owned branch; keep draft pending independent review. Do not merge stale #270 raw.

masarray commented Nov 4, 2026

Copy link
Copy Markdown
Owner Author

M3-E INTEGRATOR active execution — protected main + exact owner handoffs (2026-11-05 WIB)

WORKSTREAM: INTEGRATOR. Baseline main@4a40e7132871ace9fb7ec4b8c0af07aa42630a39 now includes merged #407 (CRLF-safe Node policy + precise Product Qualification), #405 coordination and #404 routing safety. The sole owned #402 has been reconciled on top of this protected main by expected-SHA fast-forward merge commit c99f60233a1a. Only 9 INTEGRATOR paths changed: approved native readback/translator/MAIN seam, anti-double-dry, tests, CMake. No GUI/DSP/FAT/workflow edits. Branch is DRAFT pending exact-head Product Qualification (new PR UI job + reusable native Windows build), review, then selective merge. Prior joined Windows+Chromium green at cb7a44eb; earlier failure at a2a025d was cross-platform #405 LF test, fixed by owner #407. DO NOT run parallel duplicate native CI.

ENGINE #266 owner handoff REQUIRED for actual FIRST SOUND: Branch still 59d1ef66d62fb66f030feca5ede8e47b77ca959d, 157 ahead / 115 behind main and not raw-mergeable. Source-only reconcile the ONE LiveAudioEngine/LiveDryRoutingLab ChannelId PCM callback + public setNativeInputMix/setNativeInputMuteSolo and WIRE authority, original CH1–10 + dynamic CH11, native VST3 leases and original CH1/Orbit/AUX/MONITOR/Show parity, then exact-head Windows/CTest. Put only ENGINE-owned paths in your changes, hand src/Main.cpp/CMake/approved bridge changes to #402 through #397. No historical GUI/workflow/parallel callback. Without installed producer #402 MUST keep public supportedOps=[] and arMixConsoleIntent REJECTED (not fake LIVE).

FAT #406 owner handoff: reconcile FAT-only ZIP/collector/evidence kit from 4ca9f242 onto corrected main; verify exact software SHA with Windows real PCM/VST3 and 44.1/48k 0FX/1FX 30min matched device runs. Physical crackle #15 remains STOP-SHIP, report UNKNOWN hardware counters honestly.

Owner / merger must never replace frozen approved https://masarray.github.io/arsonmix/preview/ skin. End goal: one accepted EXE commit, one native callback, ACK→later accepted PCM snapshot, measured evidence.

…epair PowerShell verifier and two-rate field safety

masarray commented Nov 5, 2026

Copy link
Copy Markdown
Owner Author

M3-F FAT consume checkpoint — accepted INTEGRATOR native readback on main

Current accepted main f7d2993e4973cf8944cedac570dc87451beed43f after #402 merged. Its exact PR head 039b8746215349517556616343ad48dd839a8cc8 passed Product Qualification #41928672962 (Windows JUCE/CTest and Chromium). Post-merge main UI 41938242509 SUCCESS; main Windows 41938242006 still RUNNING at checkpoint.

FAT owner #406 remains independent and only you should edit FAT evidence/package source. Its latest head 2f7f3b92e63ac907895e2d40d0e2ad30942a8f8b is still DRAFT and based on main@4a40e713; please selectively reconcile with current main (no blind overwrite) and requalify exact head. Preserve ASIO/WASAPI 44.1/48k 0FX/1FX + 30-min physical witness and exact source/EXE/ZIP hashes; no false audio PASS. Present hardware issue #15 remains STOP-SHIP.

Critical native producer gap: accepted main lacks real ChannelId PCM control and nativeBus status; ENGINE #266 must first selectively bring setNativeInputMix, setNativeInputMuteSolo, real installed publisher and VST3/Show parity. First real sound/GUI ACK+snapshot and beta are NOT yet proven; FAT checks should report PENDING until a single integrated SHA and physical rig are tested. Release ZIP construction alone is not a green physical verdict.

masarray commented Nov 5, 2026

Copy link
Copy Markdown
Owner Author

@codex review

Review FAT-only #406 exact HEAD 835e15557ee916b289fc60eb264ecc2f543d899b on accepted main@f7d2993. Focus on independently auditable Windows PowerShell AST/ZIP/PE+SHA integrity, sourceCommit/tool hashes and portable ZIP provenance, 44.1/48k OUTPUT_ONLY/CAPTURE_ONLY/0FX/1FX 30-min session math, same-endpoint + rates, hard fail for fabricated/failing hardware witness, no misleading LIVE or render XRUN claims. No native PCM/GUI changes; physical #15 must remain PENDING. Please flag concrete code defects, not proposed non-FAT features.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 5, 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-05T00:37:22.408169Z 0942166 Manual request
ℹ️ 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.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 835e15557e

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread scripts/m3e_fat_evidence_gate.mjs Resolved

masarray commented Nov 5, 2026

Copy link
Copy Markdown
Owner Author

FAT #406 — collision-free handoff after concurrent update (2026-11-05 WIB)

Observed your new HEAD 24427debaa84a31f478f22713a2ecd0d54cf3547 arrived after my same-PR main reconciliation 835e15557ee916b289fc60eb264ecc2f543d899b. GitHub correctly canceled the prior in-flight run #41939740203 and started new #41940329375. I will NOT push/force/merge this moving FAT branch while you are editing it.

New 24427de fixes review P2 BOM on scripts/m3e_fat_evidence_gate.mjs + tests, but the other P2 remains in scripts/collect_hardware_fat_windows.ps1 -Action Summary: it trusts elapsedSeconds>=1800 without independently requiring valid startedUtc/endedUtc chronological duration, so edited/forged journals can show EVIDENCE_READY_FOR_HUMAN_REVIEW despite 1-second timestamps. Please fix via PowerShell-side UTC parse + nonnegative monotonic elapsed check (same ~5s tolerance as Node). Add actual Windows PowerShell 5.1 executable functional regression (not AST-only) for fake 1800s elapsed, one-second timestamps; keep current Node gate and SHA pinning. No new workflow.

One small source audit: at -Action Start -Mode LIVE_THROUGH_1FX, current baseline guard rejects only INCONCLUSIVE but accepts baseline CRACKLE; this can waste a 30-minute FX session on an already failed 0FX baseline. Prefer operatorObservation -ne 'CLEAR' with regression. Hardware #15 remains STOP-SHIP.

After these fixes, requalify latest exact SHA Product Qualification; promote/merge FAT tooling only if review resolved and true package ZIP tested (or strictly keep experimental + package gate PENDING). This is NOT authorization to claim First Real Sound; #266 producer remains missing on main.

masarray commented Nov 5, 2026

Copy link
Copy Markdown
Owner Author

M3-G FAT source qualification checkpoint — ready for code review only

Exact candidate: 24427debaa84a31f478f22713a2ecd0d54cf3547 on current main@f7d2993e4973cf8944cedac570dc87451beed43f; 8 FAT-only paths, no engine/**, src/Main.cpp, CMake, integration/**, workflow/GUI changes. Prior #406@2f7f3b92 Product Qualification 41927631811 PASS. Current same-head Windows/CTest 41940329375 was running at checkpoint (ownership/Node + GUI provenance already PASS). No new workflow.

New regression: optional UTF-8 BOM in real Windows PowerShell 5.1 native FAT_RUNS.json and manifest; preserve malformed JSON/source/EXE/SHA256 report fail-closed. Native build/ZIP/GUI and human physical FAT are different gates. For PR builds the workflow intentionally skips expensive packaging; the post-merge main Windows artifact must independently verify actual GUI PE32+, exact /preview/ assets, EXE+tools SHA256, compressed ZIP entries and FactoryFX approved locks before calling SOFTWARE PACKAGE PASS. No physical 44.1/48-kHz 0FX/1FX, dynamic ChannelId audio, VST3 or hardware #15 claim.

Promoting to ready is for FAT-only source review, NOT user UAT/release. If latest software gate or review fails, keep unmerged and fix in this PR.

@masarray
masarray marked this pull request as ready for review November 5, 2026 00:24

masarray commented Nov 5, 2026

Copy link
Copy Markdown
Owner Author

@codex review

Please review exact FAT HEAD 09421664733f602a367084388439d8f3abbc0df1, specifically PowerShell 5.1 module-independent streaming SHA256 field script, real 30min start/end arithmetic in -Action Summary, UTF-8 BOM acceptance without weakening SHA/source provenance, 8-mode 44.1/48k 0FX+1FX integrity and ZIP source/entry attestation. Confirm no release-ready claims, no ENGINE ownership leakage. Prior review findings have targeted code+regressions; latest exact-head Product Qualification is still in progress.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0942166473

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@masarray
masarray merged commit 5f49156 into main Nov 5, 2026
4 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