Can I vibecode Roam Research?

Build a comprehensive personal replacement for the core loop of Roam Research, a "networked thought" knowledge management tool.
Use exactly this stack: Tauri 2 + React + TypeScript + SQLite.

Your primary objective is to build a local-first networked notes application that treats knowledge as an interconnected web via a graph-based data model, avoiding rigid folder hierarchies.

### Core Features & Specifications
1. **Bi-directional Linking**: Implement the core engine where wrapping words in double square brackets, e.g., `[[Topic]]`, automatically creates a page and a persistent link between the current note and the target topic. Show "Linked References" at the bottom of each page to display all blocks referencing the current page.
2. **Daily Notes**: The default view upon opening the app must be a "Daily Note" (e.g., "August 3, 2026"). This encourages a journaling style for capturing thoughts, tasks, and meeting notes, automatically indexed by date.
3. **Block-Level Referencing & Outliner**: The editor must be an outliner where the smallest unit is a "block" (a bullet point). Users must be able to nest blocks (indent/outdent) and reference individual blocks across different pages without duplicating text.
4. **The Right Sidebar**: Implement a collapsible right sidebar that allows users to open multiple pages or search results simultaneously by shift-clicking links. This is essential for cross-referencing information and drafting content while keeping source materials visible.
5. **Graph Overview**: Provide a visual representation (nodes and edges) of how notes and pages are interconnected, helping users identify clusters of ideas or "orphaned" notes. Use a library like react-force-graph or d3.
6. **Filtering and Querying**: Allow users to filter their database by tags or combinations of tags (e.g., `#project` and `#urgent`), making it powerful for task management.

### UI Layout & Interactions
- **Main Layout**: A left navigation sidebar containing links to "Daily Notes", "Graph Overview", and "All Pages". A main editor area in the center, and a resizable, collapsible Right Sidebar for secondary panels.
- **Aesthetics**: Ensure a premium, modern design with a sleek dark mode, smooth micro-animations for interactions, and a clean typography system (e.g., Inter or Roboto). Use accessible keyboard navigation, hover states, and clear focus states.
- **Interactions**: 
  - Typing `[[` should open a floating autocomplete popover showing existing pages.
  - Pressing `Tab` / `Shift+Tab` should indent/outdent blocks.
  - Hovering over a block should show a drag handle for reordering.

### Step-by-step Instructions
1. Initialize the project with the specified stack. Start from an empty folder and create the complete working project.
2. Setup the local SQLite database schema for blocks, pages, and links. Store user data locally.
3. Build the outliner editor component capable of handling block-level indenting and typing detection for `[[` triggers.
4. Implement the Daily Notes view and the page routing.
5. Add the bidirectional linking logic and the Linked References section at the bottom of pages.
6. Build the Right Sidebar and ensure shift-clicking a link opens it there.
7. Integrate the Graph Overview visualization.
8. Polish the UI with premium aesthetics, handling empty, loading, and error states. Validate untrusted input.
9. Add Markdown import and export functionality so the user is not trapped in the app.
10. Write focused unit tests for the data model and the most important workflow. Run the tests and build before finishing, then fix errors.