Skip to content

M6: current FX ownership guide and safe Harmony/O1 integration rules - #570

Merged
masarray merged 1 commit into
mainfrom
docs/m6-cross-lane-fx-ownership-guide-20261111
Nov 11, 2026
Merged

masarray merged 1 commit into
mainfrom
docs/m6-cross-lane-fx-ownership-guide-20261111

Conversation

@masarray

Copy link
Copy Markdown
Owner

#527 — Maintainable onboarding, architecture truth and concurrent PR interoperability

Refresh the contributor entrypoint and feature-extension playbook from live main@b5b03669c616ac55a5d935023e0402ec7a99f7be. Existing docs were frozen at the first M6 workpack and still omitted the actually merged #565, #567, #564, #568.

Changes

  • CONTRIBUTING.md: explicit shared NativeFxControlRequest ownership and pure JS contract / browser adapter split; cross-thread guidance for active Harmonice #529, physical output #563, candidate M4: typed FX host envelope hardening compatible with Harmonice presets and O1/O2 #569. Require final combined HEAD CI, not a new sign-off committee.
  • docs/architecture/FEATURE_EXTENSION_PLAYBOOK.md: production FX extension recipe now references exact native typed envelopes, logical-only epoch 0 and hpres- distinct from realtime harm- commands; no new host or DSP stage.
  • docs/architecture/README.md: accurate M0–M6 merged-versus-partial status; O1/O2 candidate not merged into main, physical ASIO FAT unproven; source map includes shared host request.

All three changed paths are disjoint from active #529/#563/#521/#512 code work. Docs only: no C++, JavaScript runtime, GUI, DSP, ASIO, workflow or product behavior changes. By smart CI policy, inspect links and diff only; NO Windows or Chromium dispatch.

@chatgpt-codex-connector

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

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

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

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-11T06:09:17.548332Z 9077247 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.

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