📝 Track self-hosted coverage hosting plan in backlog

Record the decision to host CI coverage from a tiny dir-listing server in
the Gitea docker setup (shared volume keyed by repo/tag) instead of the
GitHub upload-artifact zip. This unblocks dropping the coverage artifact
from the Gitea CI port. Adds the lipanski docker-image author to cspell.

backlog.tasks

@@ -48,6 +48,11 @@ Documentation:
 ☐ Create backlog tasks for implementation
 
 Maintenance:
+☐ Serve CI coverage over a tiny self-hosted webserver (replace the zip artifact) @low
+    ☐ Add a minimal dir-listing webserver to the gitea docker setup (e.g. caddy `file_server browse` reusing the existing reverse proxy, or any single-binary static server, lipanski/docker-static-website)
+    ☐ CI writes each run's `coverage/` into a shared volume keyed by project + tag (e.g. `/coverage/tiny-pattern-ts/<tag>/`)
+    ☐ Browse to `…/coverage/<repo>/<tag>/index.html` in the browser; drop the `actions/upload-artifact` coverage step in favour of the shared-dir layout
+    → design: no deploy step in CI; the webserver just exposes the shared directory (decided over Gitea Pages / Codecov — neither confirmed available/ wanted)
 ✔ Set up lefthook pre-commit hook @done (9/8/2026, 10:52:56 AM)
 ✔ Configure tsconfig strictest + node26 profiles @done (9/8/2026, 10:08:37 AM)
 ✔ Add check:tsc as first tier in `npm run check` @done (9/8/2026, 10:08:37 AM)