# VibeChat Build Test — magazine-test-001 (2026-08-19 18:58 CEST)

**Test**: Asked VibeChat (PM2 panel) to "Build a small basic landing page app named 'magazine-test-001' with magazine style (large hero, 3-column grid, footer)."

**Result**: Build SUCCEEDED in agent. App preview overlay OPENED. But the app URL returns 503 and the app is NOT in the registry. Bug in the preview event dispatch + deploy step.

## What actually happened (timeline)

| Time | Event |
|---|---|
| 0s | User sends prompt |
| 5s | Agent calls `read_files_for_context` (200 OK) — read 1 file (annotation template) |
| 26s | `build_freshvibe_app` tool returns ✓ in 0ms — too fast to have actually built anything |
| 26s | System message: "🎉 App 'magazine-test-001' built — preview in main canvas" |
| 26s | `fv:vc-preview` event dispatched with `{appName: "magazine-test-001", source: "build_freshvibe_app"}` |
| 26s | App browser refreshes, sees the new app, opens iframe at `https://magazine-test-001.freshvibeapps.com/` |
| 26s | Iframe loads, shows "remote connection failure, transport failure reason: ..." (nginx 503) |

## The 5 findings (in order of severity)

### 🔴 Finding 1: `build_freshvibe_app` returns instantly (0ms) with a fake success

**What the chat shows**:
```
[tool] 🔧 build_freshvibe_app → ✓ (0ms)
[tool] Build started for magazine-test-001 with 2 file(s). The chat loop will generate
       each file via focused LLM calls and write them through the v8-enforcing bridge.
       You don't need to do anything else — execution is automatic.
```

**What's actually true**:
- Tool returns immediately with `success: true` in 0ms
- No actual LLM file generation happens
- No `write_file` calls to `/var/www/freshvibeapps/clients/magazine-test-001/...`
- No annotation.json written
- The "execution is automatic" text is a **lie from the agent** — the bridge has no auto-execute path

**Root cause** (look at `src/agent/tools.ts` for `build_freshvibe_app`):
The tool just returns a success message in its output. The Day 10dd implementation says "the chat loop takes over after this call" but the chat loop doesn't actually call `executePlan` for `build_freshvibe_app` — it only does that for the `plan` tool. The build call is a **noop that lies about success**.

### 🔴 Finding 2: The agent dispatches `fv:vc-preview` for a non-existent app

The vibechat-panel.js dispatches `fv:vc-preview` immediately on tool success:
```js
window.dispatchEvent(new CustomEvent('fv:vc-preview', { detail: { appName, source: 'build_freshvibe_app' } }));
```

This opens the iframe overlay and tries to load `https://<appName>.freshvibeapps.com/`. Since no app was actually built/deployed, the URL returns 503 from nginx (no vhost for that domain), and the iframe shows a connection failure.

The user sees "App built — preview in main canvas" which is misleading.

### 🟡 Finding 3: The app browser does NOT show the new app in the list

```json
"app_buttons": ["oscar-cms4-cssfix-20260813-061643"]
```

Only the pre-existing app shows up. The new "magazine-test-001" was NEVER added to `/api/agent/freshvibe-apps` because:
1. The bridge never wrote the annotation.json (Finding 1)
2. `/api/agent/freshvibe-apps` only lists apps with annotation.json in `app-fragments/cms-data/`

The overlay still opens via the dispatched event (Finding 2), but the app button list is wrong.

### 🟡 Finding 4: The iframe sandbox has `sandbox="allow-same-origin allow-scripts allow-forms allow-popups"` but the response is 503

The nginx site for `magazine-test-001.freshvibeapps.com` doesn't exist. Looking at the actual response:
```
HTTP/2 503
content-length: 240
content-type: text/plain
server: istio-envoy
```

This is the catch-all default vhost (istio-envoy is the sidecar). So the iframe gets a 503 + plaintext body, and the browser tries to display the plaintext which becomes the "remote connection failure" error.

### 🟢 Finding 5: The agent loop is healthy + the chrome wiring is correct

What works:
- Tool call → tool result dispatching
- Reading files for context (read_files_for_context, 200 OK)
- The chat rendering of tool_call, tool_result, plan, system events
- The `fv:vc-preview` event dispatch in the panel
- The app browser refresh on event
- The iframe overlay opening

What doesn't work:
- `build_freshvibe_app` actually building anything
- Files being written to the bridge workspace
- Annotation being saved
- Deploy to nginx

## Bridge API calls (full log)

```
200 GET  /api/agent/freshvibe-apps        # initial app list load (from mountAppBrowser)
200 POST /api/agent/read_files_for_context  # agent reading the FvW v8 template
200 GET  /api/agent/freshvibe-apps        # refresh after fv:vc-preview
```

**No `write_file` calls. No `build_freshvibe_app` POST. No deploy.**

## Page errors (only 1)

```
@mantine/core: MantineProvider was not found in component tree, make sure you have it in your app
```

This is the React tree error from `?legacy=1` mode — irrelevant for `?legacy=0` PM2 path. Has been in console for days, not blocking anything.

## What's the actual fix?

The `build_freshvibe_app` tool needs to be reimplemented to actually call the bridge `/api/agent/build_freshvibe_app` endpoint and trigger the v8-enforcing pipeline. Currently it just returns a string. The Day 10dd port didn't wire the bridge side — it just stubbed the success message.

There are 2 options:
1. **Quick fix**: Replace the `build_freshvibe_app` tool with a real POST to the bridge. The bridge has 82 endpoints (per exec-tracker). One of them is `/api/agent/build_freshvibe_app` — I can check.
2. **Proper fix**: Re-port Day 10ee's full build pipeline (the 18 endpoints + 3 new endpoints per the 8/18 work). The build loop generates each file via focused LLM calls. This is 4-6 hours of work.

## What you saw

The screenshot shows:
- VibeChat panel (left) with: prompt → read files → build_freshvibe_app ✓ → "App built — preview in main canvas"
- App browser at top right (hidden by panel) — only shows oscar-cms4-cssfix-20260813-061643, not magazine-test-001
- Preview iframe (right) — loading `https://magazine-test-001.freshvibeapps.com/` → 503 → "remote connection failure" error

## What I should NOT do

Don't make the user think the build worked when it didn't. The "✓" and "App built" messages are misleading. Either:
- (a) Fix `build_freshvibe_app` to actually build (4-6 hours), OR
- (b) Replace the success message with "I'm calling build_freshvibe_app, but this tool isn't fully wired — let me try the individual file writes instead" (5 minutes)

I think (b) is the right next step while I investigate the bridge endpoint for (a).

## Bulletins

b1440 (already posted): PM2 VibeChat shipped with full agent
b1441 (posting now): audit reveals build_freshvibe_app is a noop that lies