¿Puedo vibecodear ServiceNow?

Build a local, single-user request queue called "Deskless". This is a personal consolation build for ServiceNow, not an ITSM platform. Be honest about scope.

Stack, no substitutions:
- Next.js 15 App Router, TypeScript, Tailwind.
- SQLite via better-sqlite3, file at ./data/deskless.db, schema created on boot if missing.
- Server Actions for all mutations. No API routes unless needed.
- No auth, no accounts, no telemetry, no cloud. It runs at localhost:3000 for one person.

Data model:
- assets: id, name, kind (laptop, service, subscription, account), owner_note, created_at.
- tickets: id, key (auto like REQ-0001), title, body, type (incident, request, change), priority (low, med, high), state (new, in_progress, waiting, done, cancelled), asset_id nullable, due_date nullable, created_at, updated_at.
- events: id, ticket_id, at, kind (created, state_change, comment, field_change), from_value, to_value, note. Append only, never edited or deleted.

Features in scope:
- Ticket list with filters by state, type, priority, and a text search over title and body.
- New ticket form where the fields shown change by type: change tickets additionally ask for rollback_plan and planned_window, stored as JSON in an extra_fields column.
- Ticket detail page: state transition buttons, comment box, linked asset, and the full audit log rendered as a timeline.
- Assets page: create, list, and see all tickets touching an asset.
- A "Weekly" view: tickets closed in the last 7 days and anything still open past its due date.
- Export everything to a single JSON file via a button, and a CSV export of tickets.

Explicitly out of scope, do not build: SLAs, approval chains, discovery agents, email ingestion, multi-user roles, SSO, a workflow designer.

Deliver: a README with setup in three commands, a seed script that inserts 12 sample tickets and 5 assets, and one Vitest file covering that state changes always write an events row.