feat: block CI on the frontend type check

svelte-check is clean, so it gates like the rest. eslint still reports without
failing, now for two findings rather than 87: both are the unsanitized book
description, written up in TODO.md.

AGENTS.md

@@ -103,11 +103,11 @@ API docs are served by the running backend at `http://localhost:8000/schema/` (S
   manually against a live backend).
 - **Migrations are mandatory.** The app runs with `create_all=False`, so a model change without a
   matching Alembic revision will not reach the database.
-- **CI gates formatting, linting and tests.** `.gitea/workflows/ci.yml` runs on every push and pull
-  request: `ruff format --check`, `ruff check`, `pytest`, and `prettier --check` all **block**;
-  `eslint` and `pnpm check` report without failing until their pre-existing counts reach zero. A
-  `v*` tag additionally builds and publishes both container images — see
-  `docs/ci-release-pipeline.md`.
+- **CI gates formatting, linting, types and tests.** `.gitea/workflows/ci.yml` runs on every push
+  and pull request: `ruff format --check`, `ruff check`, `pytest`, `prettier --check` and
+  `pnpm check` all **block**; only `eslint` reports without failing, and only until the two
+  `{@html}` findings in `TODO.md` are fixed. A `v*` tag additionally builds and publishes both
+  container images — see `docs/ci-release-pipeline.md`.
 - **Commit messages** follow `type: summary` — `feat:`, `fix:`, `refactor:`, `chore:`.
 - The three `README.md` files are user-facing. Agent-facing knowledge belongs in the `AGENTS.md`
   files.