r236 v2 Deploy Report (legacy VibeChat disabled)

**Date**: 2026-09-02 19:43 BST

**Operator**: G (via Mavis v3)

**Project**: vibecoder-standalone (avidtech6/vibecoder-standalone)

**Sandbox**: vibecoder236.freshvibeapps.com

**Job ID**: djmtkdxj68mn2b

Result

**SUCCESS** — r236 v2 deployed. Legacy VibeChat panel DISABLED.

What was wrong with v1

Operator feedback at 19:39: "no it failed it has the old chrome"

**Root cause**: r233 host-boot.js has a `bootVibeChatPanel()` call that auto-registers the legacy VibeChat panel (id=fvcms-vibechat, with ThreadsPanel/ChatPanel UI from before the unification). This is r233 code, not r235a/r235b.

The r235a + r235b code added the unified VibeChatUnified surface on top, but did NOT remove the legacy panel. So the operator saw BOTH:

• The legacy VibeChat panel (r233 bootVibeChatPanel) - the "old chrome"

• The unified VibeChat surface (r235b mount) - only with ?vc-bottom=new

Fix

Commented out `bootVibeChatPanel()` in `src/host/host-boot.js` (r233 baseline mod).

**Note**: r235a files and r235b files are still applied **exactly as they were** (untouched). The only modification is to the r233 baseline (host-boot.js) to honor the "zero legacy chrome" directive.

Bundle Stats

• **Name**: `main-Dzbc5Bk1.js`

• **Size**: 652979 bytes (640 KB)

• **MD5**: `dac6a35c56440d43209e7ce97d2acf6c`

• **sha256**: `365133b1737658830869ee1f01cc20aa3ae6c4389c0259c0bba5caeadeee5c14`

Live URLs

• **Site**: https://vibecoder236.freshvibeapps.com

• **Bundle**: https://vibecoder236.freshvibeapps.com/assets/main-Dzbc5Bk1.js

• **Unified VibeChat**: https://vibecoder236.freshvibeapps.com/?vc-bottom=new

Bundle Markers (verified)

```

bootVibeChatPanel: 0 matches (DISABLED)

function Qm(): 0 matches (DISABLED, the legacy registration fn)

ThreadsPanel: 0 matches (DISABLED)

data-r235b-r235a-slot: 2 matches (r235b mount intact)

r235a-2026-09-02: 1 match (VibeChat API intact)

r235b-2026-09-02: 1 match (mount intact)

```

What you should see now

At **vibecoder236.freshvibeapps.com** (no flag):

• ✅ FV-CMS chrome: CMS Panel (left), Edge Panel (right), Dev Panel (auto-init)

• ✅ Pro pill (top-right), Edge Panel pill (right edge), VibeChat pill (bottom-right)

• ✅ Main canvas = FreshVibeOrigin with 6 sections

• ❌ NO legacy VibeChat panel (was auto-registered before, now disabled)

At **vibecoder236.freshvibeapps.com/?vc-bottom=new**:

• All of the above + new unified VibeChat surface (docked-bottom)

• The new VibeChat has the r235a-rendered UI (VibeChatHeader, VibeChatAnswerPane, VibeChatInputBar, etc.)

Commit

• `fdf4696 r236-fix: disable r233 bootVibeChatPanel() — legacy VibeChat replaced by r235a`

Identifiers

• Bulletin: `b002115` (v2 deployed)

• Bulletin: `b002113` (sanity check ask)

• Bulletin: `b002098` (v1 deployed)

• Tarball ID (appx): `mKX1fIcY`

• Deploy job: `djmtkdxj68mn2b`

• Commit: `fdf4696` on `feat/id9-r236-clean-baseline`

Next Steps (awaiting operator)

• Operator G to verify r236 v2 visually at vibecoder236.freshvibeapps.com

• Should now show: FV-CMS chrome WITHOUT the legacy VibeChat panel

• Then test `?vc-bottom=new` to see the new unified VibeChat surface mount

• If approved: cherry-pick 036a3d4 + fdf4696 onto main and push