Can I vibecode Nuclino?

Build a personal replacement for Nuclino in an empty repository.
Use Tauri 2, React, TypeScript, SQLite, and Markdown files as the source of truth; do not offer alternative stacks.
The core loop is: maintain a fast linked team knowledge base with collections and simple boards, search notes instantly, surface backlinks, and export a normal Markdown folder.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Store one Markdown file per note and a small SQLite index that can be rebuilt at any time.
Support wiki links, tags, backlinks, daily notes, pinned notes, and full-text search.
Add a fast command palette and keyboard-first create, rename, move, and link actions.
Render Markdown with task lists, code blocks, tables, and local image attachments.
Detect external file changes and show a safe conflict-resolution view.
Provide full-folder export, import, and an index-rebuild command.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out proprietary sync servers.
Deliberately leave out real-time multiplayer documents.
Deliberately leave out a plugin marketplace and hosted public sites.
Finish by running the tests and listing the exact commands used.