vibe-researchlisted

# Vibe Research Vibe Research treats the AI agent as a "talented but untrustworthy remote research team." The human researcher sets direction and reviews results through a compressed documentation interface. The soul of the system is **bi-directional sync**: code, `paper.md`, and `doc/` are always mirrors of each other. ## Migrating an Existing Project ### Full migration (no existing VR structure) 1. **Understand the project** — if the user hasn't explained the experiment flow, goal, and result locations, ask before touching any files. 2. **Run the init script** (idempotent — safe on existing directories). 3. **Move source code → `src/`**, existing results → `results/`. 4. **Update all path references** in code to match the new layout. 5. **Smoke test** — run with minimal config; no data corruption; delete temp files; estimate runtime first (max 10 min). 6. **Populate `doc/`** from code reading (see [Document Maintenance](#document-maintenance) below). 7. **Populate `paper.md` and `README.md`** based on current state. ### Partial migration (some VR structure already exists) When a project has **some** VR structure but is incomplete or drifted out of sync: 1. **Audit every component** — classify each as conforming / stale / non-conforming / missing. Present the audit table to the user. 2. **Generate a plan grouped by risk** (safe → moderate → caution). Get user approval. 3. **Execute incrementally** — create missing structure first, then move files, then refresh stale d