5 Commits

Author	SHA1	Message	Date
Nicholai	cf5f775e0f	feat(flash): add Flash (predrawn) items - schema, API, hooks, UI section on artist page; booking form prefill via flashId	2025-10-20 18:45:31 -06:00
Nicholai	a77f62f949	feat: implement CalDAV Nextcloud bidirectional calendar integration ... Adds complete CalDAV integration for syncing appointments between the web app and Nextcloud calendars with real-time availability checking and conflict resolution. Core Features: - Bidirectional sync: Web ↔ Nextcloud calendars - Real-time availability checking with instant user feedback - Conflict detection (Nextcloud is source of truth) - Pending request workflow with 'REQUEST:' prefix for unconfirmed appointments - Hard time blocking - any calendar event blocks booking slots - Graceful degradation when CalDAV unavailable New Dependencies: - tsdav@^2.0.4 - TypeScript CalDAV client - ical.js@^1.5.0 - iCalendar format parser/generator Database Changes: - New table: artist_calendars (stores calendar configuration per artist) - New table: calendar_sync_logs (tracks all sync operations) - Added caldav_uid and caldav_etag columns to appointments table - Migration: sql/migrations/20250109_add_caldav_support.sql New Services: - lib/caldav-client.ts - Core CalDAV operations and iCalendar conversion - lib/calendar-sync.ts - Bidirectional sync logic with error handling New API Endpoints: - GET /api/caldav/availability - Real-time availability checking - POST /api/caldav/sync - Manual sync trigger (admin only) - GET/POST/PUT/DELETE /api/admin/calendars - Calendar configuration CRUD Updated Components: - app/api/appointments/route.ts - Integrated CalDAV sync on CRUD operations - components/booking-form.tsx - Added real-time availability indicator - hooks/use-availability.ts - Custom hook for debounced availability checking Documentation: - docs/CALDAV-SETUP.md - Complete setup guide with troubleshooting - docs/CALDAV-IMPLEMENTATION-SUMMARY.md - Technical implementation overview Pending Tasks (for future PRs): - Admin dashboard UI for calendar management - Background sync worker (Cloudflare Workers cron) - Unit and integration tests Tested with local database migration and linting checks passed.	2025-10-08 20:44:17 -06:00
Nicholai	1378bff909	updated the following components to use the API instead of hardcoded data: ... ### 1. __artists-grid.tsx__ (Main Artist Browsing) - Uses hook from - Fetches from endpoint - Includes loading states, error handling, and filtering - __Impact:__ Primary artist browsing experience now fully API-driven ### 2. __artist-portfolio.tsx__ (Individual Artist Pages) - Uses hook - Fetches from endpoint - Fixed all TypeScript errors (changed image ID from number to string) - Added loading/error states - __Impact:__ Artist detail pages now fully API-driven ### 3. __booking-form.tsx__ (Artist Selection Dropdown) - Uses hook for artist selection - Updated to use API data structure ( array, , etc.) - Added loading state for dropdown - __Impact:__ Booking flow now uses real artist data ## ⚠️ REMAINING (Decorative/Marketing Components) Two complex components still use hardcoded : ### 4. __artists-section.tsx__ (Homepage Hero - 348 lines) - Homepage marketing section with complex parallax scrolling - Uses hardcoded artist data for visual cards - __Non-blocking:__ This is a decorative homepage element ### 5. __artists-page-section.tsx__ (Artists Page Section - 413 lines) - Full-page artists showcase with parallax effects - Uses hardcoded artist data for visual layout - __Non-blocking:__ Alternative to artists-grid.tsx (which IS using API) ##	2025-10-06 04:44:08 -06:00
Nicholai	b20db98051	feat(ci,flags,ops): ship end-to-end CI, feature-flag framework, gated surfaces, and ops docs ... CI (.gitea/workflows/ci.yaml): lint → typecheck → vitest w/ coverage → OpenNext build → preview smoke → bundle-size budgets; Node 20; npm ci; artifacts; safe env; D1 dry-run scaffold. Budgets: add scripts/budgets.mjs; TOTAL_STATIC_MAX_BYTES and MAX_ASSET_BYTES thresholds; report top offenders; fail on breach; README CI section. Flags: add lib/flags.ts with typed booleans and safe defaults (ADMIN_ENABLED, ARTISTS_MODULE_ENABLED, UPLOADS_ADMIN_ENABLED, BOOKING_ENABLED, PUBLIC_APPOINTMENT_REQUESTS_ENABLED, REFERENCE_UPLOADS_PUBLIC_ENABLED, DEPOSITS_ENABLED, PUBLIC_DB_ARTISTS_ENABLED, ADVANCED_NAV_SCROLL_ANIMATIONS_ENABLED, STRICT_CI_GATES_ENABLED, ISR_CACHE_R2_ENABLED); robust parsing; client provider; unit tests. Wiring: gate Admin shell and admin write APIs (503 JSON on uploads and artists writes); disable booking submit and short-circuit booking mutations when off; render static Hero/Artists when advanced animations off; tests for UI and API guards. Ops: expand docs/prd/rollback-strategy.md with “Feature Flags Operations,” Cloudflare Dashboard and wrangler.toml steps, preview simulation, incident playbook, and post-toggle smoke checklist. Release: add docs/releases/2025-09-19-feature-flags-rollout.md with last-good commit, preview/production flag matrices, rollback notes, and smoke results; link from rollback doc. Chore: fix TS issues (gift-cards boolean handling, Lenis options, tailwind darkMode), remove next-on-pages peer conflict, update package.json scripts, configure Gitea act_runner label, open draft PR to trigger CI. Refs: CI-1, FF-1, FF-2, FF-3, OPS-1 Impact: defaults preserve current behavior; no runtime changes unless flags flipped	2025-09-19 21:33:09 -06:00
Nicholai	06abb52024	v05 push to origin	2025-09-16 21:36:20 -06:00