4 Commits

Include renames

Author	SHA1	Message	Date
peter	d2e40dcffb	feat(design): design lab + DESIGN.md skeleton (E28 S2a) ... - docs/DESIGN.md: the written source of truth for the UI. Decided chapters (principles, device adaptation, action placement, text stays selectable, interaction rules, copy, anti-patterns, decision log); controls and surfaces are marked Pending until the owner picks from the lab. - /design-lab (dev only): renders each open decision's variants with the app's real CSS, themes and font scale. Batch A = six control decisions. - devOnlyGuard: a production build fails if anything under src/design-lab reaches the bundle (seen red with an unguarded import). - Size contract: tablet portrait + landscape and up, replacing the 1024x768 floor with its never-built "too small" message.	2026-09-24 01:34:12 +02:00
peter	efe106dfda	build: pin one Node major across the dev, CI and build machines ... The server gate ran node:22 while the dev gate ran node:24, and the two disagree about Intl.NumberFormat's compact currency padding and about which realm's Blob a Response hands back — so the frontend job had been red for 73 of its last 90 runs while the local gate was green, and nothing said so. Align everything on 24, with `.nvmrc` as the single source of truth: the CI container, the prod build stage, `engines`, and `@types/node` (which was two majors ahead of the runtime, so tsc was green over APIs the shipped engine does not have). The backend job's node only runs the checkout action, so it tracks the pin as hygiene — node 20 is EOL — but deliberately stays outside the contract. The pin is held by a contract test that reads every one of those places AND the engine running it, so the next drift is a red lane on its first run instead of a CI log nobody reads. Verified on node:24-bookworm (the CI lane: 228 files / 1552 tests, typecheck, lint, format:check, knip all exit 0) and on node:24-alpine (the prod build stage, v24.21.0, SPA built). Each assertion of the new test was mutation-checked red.	2026-09-20 18:06:24 +02:00
peter	361ca7872e	docs: add collaboration section to CLAUDE.md, document ruff format gate ... - CLAUDE.md: new "Collaboration" section (plan-first, options-with-marked- optimal-and-why, mockups for design decisions, challenge unsound requests, visual UAT before done, terse otherwise). - CLAUDE.md: clarify release is user-owned in timing, agent-run in execution. - CLAUDE.md + docs/development.md: document the ruff format --check gate step (already enforced in .gitea/workflows/check.yml, was missing from the docs). - CLAUDE.md: refresh the stale footer to point at the now-existing docs/development.md and backend/app/README.md.	2026-08-23 17:17:02 +02:00
peter	b02a9e37e8	docs: write the backend conventions + a development guide (E3 S3, B-core-20) ... The layering rule ("request-only logic in routes/; scheduler+worker-shared logic in the plex|downloads|sync packages; cross-cutting primitives as flat core modules; extract at the SECOND consumer") was real but unwritten — it lived only in three module docstrings and a one-line README mention. Collect it, plus the transaction-ownership rule (a mid-operation helper stages, the caller commits), the atomic-counter / JobStatus-StrEnum conventions, and the one-home-per-config rule, into backend/app/README.md. Add docs/development.md (run locally + the gate commands + branching), so a new session/contributor has one place to look instead of copying whichever pattern they happen to find first.	2026-08-18 22:02:18 +02:00