Can I vibecode Zenkit?

Build a highly usable, production-ready personal replacement for the core loop of Zenkit in an empty repository.
Use exactly this tech stack without deviation: Next.js 15 (App Router), TypeScript (strict mode), and SQLite for local data persistence. Do not suggest or offer alternative technologies.

Your primary objective is to build a single-user, flexible work management workspace. The system must support creating projects, tracking tasks with customizable statuses, applying advanced filters, scheduling recurring items, and providing a robust JSON export.

Data and Security:
- Make the default mode strictly single-user and private, running locally.
- Store all user-generated data locally using SQLite to ensure privacy and data sovereignty.
- Provide a straightforward, robust JSON import and export mechanism so data is never trapped in the application.
- Keep all secrets in `.env`, ship a `.env.example`, and enforce that no credentials or sensitive data are ever committed.
- Validate all untrusted input thoroughly and never log private file contents or task details.

Core Features:
- Implement a comprehensive data model covering projects, tasks, custom statuses, recurrence rules, and filters.
- Provide polished views for managing tasks (e.g., list view, board view) that update seamlessly.
- Use realistic, clearly labelled sample data during the initial load that demonstrates the app's capabilities but is easy for the user to delete or ignore.
- Implement the smallest but most polished interface possible that completes the core loop: create project -> add tasks -> update status -> filter -> export.
- Include crystal-clear empty states, loading indicators, rigorous input validation, and distinct success/failure notifications.
- Ensure accessible keyboard navigation, clear visual labels, distinct focus states, and sensible color contrast across the UI.

Explicit Exclusions & Constraints:
- Do NOT add analytics, telemetry, advertisements, or third-party user accounts.
- Deliberately exclude paid-product advantages such as enterprise permissions, multi-user collaboration, a large integration catalog, and native mobile capture/notifications.
- Do NOT fake integrations, network effects, proprietary algorithms, compliance certifications, or security claims.
- The application should run without requiring external services. If any external API is optionally used, the application must degrade gracefully without it and explain the degraded mode.

Testing & Documentation:
- Write focused unit tests covering the SQLite data model interactions, recurrence logic, and filtering algorithms.
- Add at least one comprehensive end-to-end smoke test that proves the core loop (creating a task, updating it, and filtering) works correctly.
- Create an exhaustive README containing setup instructions, permission requirements, architectural overview, data location details, backup steps, and known limitations.
- Provide helper scripts in `package.json` for installation, development, testing, building, and running a production-style local instance.

Finalize your work by executing the test suite and building the project before finishing. If errors occur, fix them in code rather than merely describing what went wrong.