4 Commits

Include renames

Author	SHA1	Message	Date
NixReaperandClaude Sonnet 5	0ab31a314c	Add movie/series ratings and watchlist ... Builds on the accounts foundation: PUT/DELETE a rating (0.5-10.0) or a watchlist entry on any movie or series, all scoped to the bearer token's own user, plus GET /account/ratings|watchlist/{movies,series} to list them back. Both are polymorphic entity_type/entity_id tables, same shape as watch_provider_offerings and trending_entries, so movie and series share one repository/router each rather than duplicating per type. Co-Authored-By: Claude Sonnet 5 <[email protected]>	2026-09-06 10:47:41 -05:00
NixReaperandClaude Sonnet 5	7bee596a0e	Add user accounts: registration, login, and JWT auth ... The first authenticated-user concept in Aurora Core -- everything else in this codebase is public, read-only catalog data. Foundation for ratings and a watchlist (not yet built): POST /auth/register, POST /auth/login, GET /auth/me. Security specifics worth knowing: - Passwords hashed with argon2 (via argon2-cffi), never stored plain or logged. - Login returns an identical 401 for a nonexistent email and a wrong password on a real one, including matching response timing (burn_time_like_a_password_check) -- otherwise either the status code or the timing alone lets a client enumerate registered emails. - AURORA_SECRET_KEY now actually signs JWTs (previously defined but unused anywhere) -- .env.example's existing token_urlsafe(48) guidance already produces a long enough key, just flagged its new stakes. - Email matched case-insensitively via explicit normalization in the service layer, not relied on from Pydantic's EmailStr (which does not lowercase the local part). 12 new integration tests (register/login/me over real HTTP via the `client` fixture) plus 10 unit tests for the hashing/JWT logic itself, following the same-day lesson that only unit tests actually execute locally without Postgres -- the auth core is tested for real here rather than only through integration tests that might not run before a deploy. Co-Authored-By: Claude Sonnet 5 <[email protected]>	2026-09-06 06:15:39 -05:00
NixReaperandClaude Sonnet 5	fde5e76bd7	Fix crash: watch_provider was never registered as an Aurora ID entity type ... app/services/common.py:build_watch_providers_out calls aurora_id("watch_provider", ...) for every provider entry -- this raised ValueError on any movie/series detail response (or the dedicated /watch-providers route) containing watch-provider data, since the entity type was never added to ENTITY_PREFIXES. Never caught locally because every test exercising this path is an integration test that skips without a reachable Postgres. Not yet deployed (redeploy has been on hold pending the bulk import), so this never hit production traffic, but confirms it's worth actually running the test suite against real Postgres before the next deploy rather than trusting lint/mypy + locally-skipped tests alone. Co-Authored-By: Claude Sonnet 5 <[email protected]>	2026-09-06 06:08:08 -05:00
NixReaperandClaude Sonnet 5	c20df1c503	Initial Aurora Core 0.1 implementation ... Production-grade media metadata backend per docs/aurora-core-spec.md: Aurora-owned UUIDv7 identity system, normalized movie/TV/people/credits schema, provider abstraction with a TMDb adapter, an idempotent async ingestion pipeline (normalize -> match -> upsert -> provenance), a Postgres FTS/trigram search layer, a stateless FastAPI v1 API with Redis caching/rate-limiting, arq workers, dev/prod Docker Compose topologies, unit + integration + load tests, CI, and architecture/ database/API/ERD documentation. Co-Authored-By: Claude Sonnet 5 <[email protected]>	2026-09-04 17:34:03 -05:00