VibeScope Standalone — Reawakening Status

Date: 2026-07-29 19:15 BST  |  Thread: vibescope-standalone-mavis (id 14)

What I found

The blocker

The vibescope-module/ symlink target is missing.

The on-disk worktree is a 4-file thin shell:

src/main.tsx       (imports from @vibescope/workspaceDef)
src/styles.css     (3-column grid + mobile menu)
src/stubs/StudioContext.ts
vite.config.ts     (resolves @vibescope → vibescope-module/src)
package.json       (Mantine + React only)

The alias @vibescope points to vibescope-module/src/ — a symlink to the real VibeScope components (LayerPanel, Canvas, Properties, Toolbar, the 5 layer kinds). That symlink target is not on this machine.

Where the source might be

  1. The previous Mavis session built the live bundle from a source tree that wasn't committed anywhere (not in FVS git, not in vibescope-standalone git, not on the VPS)
  2. The FVS source at /workspace/repos/freshvibestudio/studio/modules/vibescope/src/ has the older 8-chip registry (VisualCard, EditorCard, etc.) — does NOT have the toolbar/panel/curtain code that the live bundle has
  3. No VibeScopeLayerToolbar, VibeScopeCanvas, or workspaceDef.tsx exists anywhere on disk

What this means for the parked work

The brief listed 5 features to add:

  1. + image, + svg, + frame layer types (with file picker / SVG path / container)
  2. Fill empty canvas with starter content (3 starter layers on new project)
  3. Multi-select (shift-click + drag all selected)
  4. Snap to grid (8px, default off, toggle in toolbar)
  5. Layer reorder via drag in the layer list

To do any of these, I need the actual source code that the live bundle was built from.

What I propose

Three options, in order of preference:
  1. Best: the operator has the missing vibescope-module/ source somewhere — a backup, an appx upload, a different git remote. Point me at it and I do the parked work in 1 session.
  2. OK: port the components from FVS's cards/ into a fresh vibescope-module/src/ (VisualCard → Canvas, InspectorCard → Properties, TimelineCard → LayerPanel-ish) so the standalone can build from a known-good baseline. 2-3 day task.
  3. Last resort: wait — if the previous Mavis session is reachable, ask them where the source is.

What I shipped this turn