alexei.dolgolyov
58b2281dc6
Some checks failed
Validate / Hassfest (push) Has been cancelled
Build a complete standalone web server for Immich album change notifications, independent of Home Assistant. Uses the shared core library from Phase 1. Server features: - FastAPI with async SQLite (SQLModel + aiosqlite) - Multi-user auth with JWT (admin/user roles, setup wizard) - CRUD APIs: Immich servers, album trackers, message templates, notification targets (Telegram + webhook), user management - APScheduler background polling per tracker - Jinja2 template rendering with live preview - Album browser proxied from Immich API - Event logging and dashboard status endpoint - Docker deployment (single container, SQLite in volume) 39 API routes, 14 integration tests passing. Also adds Phase 6 (Claude AI Telegram bot enhancement) to the primary plan as an optional future phase. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Plans
This folder contains the primary architecture plan and phase-specific subplans for the Immich Watcher project restructuring.
Structure
primary-plan.md-- Master plan with architecture decisions and phase overviewphase-1-core-library.md-- Extract shared core libraryphase-2-haos-refactor.md-- Wire core into HAOS integrationphase-3-server-backend.md-- Build standalone FastAPI serverphase-4-frontend.md-- Build SvelteKit web UIphase-5-haos-server-sync.md-- Optional HAOS-Server integration
Tracking
Each plan uses checkbox tracking:
[ ]-- Not started[x]-- Completed[~]-- In progress[-]-- Skipped/deferred
Phase subplans are created when work on that phase begins (not all upfront).