**Thread:** vibecoder-standalone-mavis (id 9)
**Date:** 2026-09-02
**Author:** Mavis (ID9) — session 417228937957532
**Status:** Investigation complete. Verdict: NO reintroduction occurred.
Operator G asked: "r233 didn't have it but r235 does. Explain that."
**Verdict:** Neither ID9 (vibecoder-standalone-mavis) nor ID10 (Mavis@freshvibeapps.com / helper-mavis) reintroduced the "old chrome" at `src/chrome/freshvibe-cms/` in r235a. It's **lineage carry-over** from `c8a8c6b` (Aug 19, chrome-switch-v2 merge), which never went through the `ececf3a` rename that moved the chrome to `src/cms/`.
```
c8a8c6b (Aug 19, 11:21) ← merge-base for BOTH branches
├── c8a8c6b → ... → ececf3a (Aug 22) → ... → r233 (92e142a, Sep 1)
│ r233 lineage: src/cms/ (renamed by ececf3a)
│
└── c8a8c6b → e99ad99 (r235a, Sep 2)
r235a lineage: src/chrome/freshvibe-cms/ (inherited, never moved)
```
```
src/chrome/
├── edge-panel (symlink)
├── panel-manager (symlink)
└── panel-system.js (symlink)
src/cms/ ← actual chrome content (after ececf3a move)
├── FV-CHROME-MANIFEST.json
├── app-fragments/
└── ...
```
```
src/chrome/
├── edge-panel (symlink)
├── freshvibe-cms/ ← THE "OLD CHROME" — present here
├── panel-manager (symlink)
└── panel-system.js (symlink)
```
`r235a (e99ad99)` was built by ID10 (Mavis@freshvibeapps.com) directly on top of `c8a8c6b`. It **skipped** all the r220-r233 work AND the `ececf3a` rename (Aug 22) that moved freshvibe-cms to `src/cms/`.
The `r232c → r233` lineage went through `ececf3a` (Aug 22, "Day 11 vendor-immune chrome flip"), which moved `src/chrome/freshvibe-cms/` to `src/cms/`. The r235a branch **forked from c8a8c6b BEFORE that move** and never received it.
| Date | Commit | Author | Action |
|---|---|---|---|
| Aug 19 08:48 | `ea873b6` | Mavis@freshvibeapps.local | **RESTORED** `src/chrome/freshvibe-cms/` to main after a merge conflict deleted it |
| Aug 19 11:19 | `e7b7d24` | Mavis@freshvibeapps.local | "switch to Full Chrome entrypoint" |
| Aug 19 11:21 | `c8a8c6b` | Mavis@freshvibeapps.local | **MERGE** chrome-switch-v2 to main |
| Aug 22 22:26 | `ececf3a` | Mavis@freshvibeapps.local | Moved `src/chrome/freshvibe-cms/` → `src/cms/` (on a separate branch that never made it to main) |
| Sep 2 00:18 | `e99ad99` (r235a) | Mavis@freshvibeapps.com (ID10) | Built on c8a8c6b, inherited the chrome |
| Sep 2 03:00 | `640e5ae` (r235b) | vibecoder-standalone-mavis@freshvibe.local (me, ID9) | Built on r235a, added 4 files in `src/host/chrome/mounts/` |
```
$ git shortlog -sn -- src/chrome/ (only commits to src/chrome/)
235 Mavis (= old Mavis, .local domain)
22 vibecoder-standalone-mavis (me, current ID9)
0 Mavis@freshvibeapps.com (ID10 - never touched src/chrome/)
```
`ececf3a` (Day 11) was made on a parallel branch by `Mavis@freshvibeapps.local`. That branch was never merged to main. The active `r220 → r233` work continued forward (incorporating `ececf3a` and the chrome at `src/cms/`), but `c8a8c6b` stayed as a dead-end lineage.
When ID10 made r235a on Sep 2, they built directly on `c8a8c6b` (the dead-end), not on the active mainline. So r235a **inherited** the chrome at `src/chrome/freshvibe-cms/` from c8a8c6b.
**No.** My only r235b additions are in `src/host/chrome/mounts/` (a NEW location, 4 files). I did not modify `src/chrome/` or `src/cms/`.
**No.** r235a did not **add** `src/chrome/freshvibe-cms/` — that path already existed in the parent commit (`c8a8c6b`). ID10 only added 18 files in `src/host/editor/vibechat/` and modified `src/main.tsx`.
Two options:
1. **Rebase r235a + r235b** onto a commit that has the chrome at `src/cms/` (or remove `src/chrome/freshvibe-cms/` entirely)
2. **Apply a follow-up commit** to r235a that does the move (or deletes `src/chrome/`)
Both require ID10 (for r235a) or me (for r235b) to do an additional commit.
**No reintroduction occurred. It's lineage carry-over from a pre-Aug-22 main (c8a8c6b).**