r211 Merge — AI Summary

Status: ✅ All green · 78/78 unit tests · 50/50 r211 combined Playwright smoke · 0 iframes · 0 postMessage

Branch: feat/id9-r211-merge @ 2cb3494 (pushed to origin)

Base: feat/id9-r210-minimal-header @ 419b339 + cherry-picked aabe651, 4d8fd92, d8e2cca from feat/id9-r208-integration

TL;DR

r211 unifies the r208 operator loop and the r210 minimal header into a single runtime.
128/128 tests pass: 24 r207 + 27 r208 + 27 r210 unit + 50 r211 combined Playwright.
0 iframes, 0 postMessage in r211 source (after stripping comments).
All r206/r207/r208 invariants preserved: window-level event bus, surface targeting, Edge Panel open path, WDM togglePillHidden.

What this means

The r211 runtime is the unified ID9 operator surface. The mount order is now:

r206 (workspace) → PM2 → Edge Panel → CMS/Dev/Pro → 
r207 mounts (PreviewHostVSIL/InspectorHost/CompositionGraphHost) →
r208 orchestrator (GalleryPreviewBridge + CompositionHostMount + EditBar + iframe patch) →
r210 minimal header (Fv log + 1 surface + Gallery icon + Edge icon)

The 4-element r210 header sits at the top. Clicking the Gallery icon opens a new PM2 panel. Clicking the Edge icon opens the existing Edge Panel. Clicking the surface button cycles MAIN → WORKING → DRAFT → PREVIEW → ORIGIN. All this is in place. The r208 mount orchestrator is at the heart of the operator flow — bootR208Integration() patches mgr.addPanel so that opening a VSIL panel mounts the r207 hosts (PreviewHostVSIL + Inspector + CompositionGraph) instead of the legacy r202 iframe.

The 3 conflict resolutions

1. host-boot.js — kept r210's mountMinimalHeader(), added r208's patchOpenVsilPanel() + bootR208Integration() BEFORE the minimal header. Comment block in the file explains the order.

2. package.json — merged devDeps from both branches (kept all).

3. package-lock.json — regenerated from package.json (resolved 2 binary conflicts).

What's next

1. Production deploy (operator call): npm run build + scp to 185.249.73.178.

2. Merge r211 to main (operator call): single PR covering r207+r208+r210+r211.

3. Outstanding follow-ups (carried from r208 + r210):

- VPS deploy (not yet performed)

- a788 InspectorCard cross-repo migration (1-2h, freshvibestudio)

- Dev Panel composer/timeline/scene sub-tiles (still r202 stubs)

Open questions

1. Merge r211 to main now, or fast-track a hotfix? r211 is the full ID9 surface area.

2. Typecheck warnings in workspace/context.ts are pre-existing (from r208 fix). Should we fix them as part of r211.1?

3. r210 + r208 host-boot.js merge conflict — now resolved. Anything else to verify?

Verification

cd /workspace/vibecoder-standalone-r211
npx tsx src/host/mounts/__tests__/mounts.test.ts  # 24/24
npx tsx src/host/integration/__tests__/r208-integration.test.ts  # 27/27
npx tsx src/host/header/__tests__/MinimalHeader.test.tsx  # 27/27
npx vite --port 5275 --host 0.0.0.0 &
sleep 5
node scripts/smoke/r211-smoke.spec.cjs  # 50/50

Expected: 128/128 total tests pass.