Muon Mode Status Review Index
Date: 2026-04-28 Purpose: single entry point for current Muon mode functionality, surface coverage, reference comparison, and third-party review.
Document Set
1. Current Per-Mode Functionality
File:
docs/muon-mode-status/2026-04-27-current-per-mode-functionality.md
Use this first for:
- Track Detail preview mode-by-mode status
- Current replay behavior by mode
- Quick snapshot of what is working vs buggy
Current headline:
default: functional with caveatsfluid: reproducible replay bugtendrils: functional in tested session, watchlistspirit: functional in tested session, watchlist
2. Cross-Surface Matrix
File:
docs/muon-mode-status/2026-04-28-surface-functionality-matrix.md
Use this for:
- Comparing Track Detail, Visualizer Lab, and project/embed surfaces
- Seeing which surfaces are testable, blocked, or N/A
- Understanding where mode controls are or are not exposed
Current headline:
- Track Detail is testable and currently shows
fluidreplay failure - Visualizer Lab is blocked without a loaded song
- Project page does not currently expose this Muon replay test path
3. Reference Comparison for Third-Party Review
File:
docs/muon-mode-status/2026-04-28-reference-comparison-third-party-review.md
Use this for:
- Evaluating how local
fluid,tendrils, andspiritcompare to reference demos - Distinguishing verified local facts from inferred reference traits
- Reviewing confidence levels and known uncertainty
Current headline:
fluidis the closest structural match to its referencetendrilsandspiritare better described as reference-inspired approximations than literal ports
4. Reviewer Checklist
File:
docs/muon-mode-status/2026-04-28-reviewer-checklist.md
Use this for:
- PASS / PARTIAL / FAIL / N/A scoring
- Consistent third-party review rubric
- Capturing final approval / caveat decisions
5. Local Iframe Architecture Plan
File:
docs/muon-mode-status/export/muon-mode-review-package-2026-04-28/docs/plans/2026-04-28_local-iframe-visualizer-architecture-plan.md
Use this for:
- The implementation path for moving non-default styles onto a local Muon-like iframe flow
- Phase-by-phase execution guidance
- Host/iframe touch points, risks, and validation gates
6. Visualizer Iframe Protocol Spec
File:
docs/specs/visualizer-iframe-protocol.md
Use this for:
- The frozen Phase 1 postMessage contract
- Current command and event shapes implemented by the Muon iframe transport
- Reserved provider-neutral extensions for later phases (
capabilities,setParam,setPalette,dispose)
Recommended Reading Order
2026-04-27-current-per-mode-functionality.md2026-04-28-surface-functionality-matrix.md2026-04-28-reference-comparison-third-party-review.md2026-04-28-reviewer-checklist.md2026-04-28-claude-review-notes.md— second-pass review by Claude. Catches matrix factual errors (project page mis-marked N/A; lab mis-marked BLOCKED), open questions on the fluid FBO failure root cause, drift between three duplicatedMUON_IFRAME_REVconstants, missing host-side files in the export bundle, and reconciliation between this status package and the 2026-04-27 D-1/D-3/D-5/D-7/D-8 fixes documented indocs/plans/2026-04-27_Muon_Default_Mode_Reactivity/Fixes.md.2026-04-28-handoff-to-copilot.md— start here if you are the next implementer. Single entry point for the per-renderer iframe migration. Pins what's decided, what's open, files to create / modify / not touch, order of operations, stop conditions, and the success definition.docs/specs/visualizer-iframe-protocol.md— frozen Phase 1 transport contract for Muon and the future per-renderer iframe providers.
Reviewer Short Summary
If a reviewer reads only one page first, start with:
2026-04-28-reference-comparison-third-party-review.md
If a reviewer wants only operational status first, start with:
2026-04-27-current-per-mode-functionality.md
If a reviewer is validating reproducibility across UI surfaces, start with:
2026-04-28-surface-functionality-matrix.md
If the next implementer is starting Phase 2 or Phase 3 work, read after the handoff:
docs/specs/visualizer-iframe-protocol.md
Current Overall Assessment
fluid: closest to reference in structure, but currently weakened by replay/FBO reliability issuestendrils: visually in-family, but likely a simplified embedded variant rather than full reference parityspirit: visually in-family, but should be treated as stylistic approximation unless stronger source-level evidence emerges
Evidence Scope Notice
This folder contains a mix of:
- direct source-code review,
- live browser observation,
- runtime probing,
- inference from public reference pages.
It should be treated as a technical review package, not a claim of source-equivalent implementation.