4 Commits

Include renames

Author	SHA1	Message	Date
Lucas WintherandClaude Opus 5	f32eb93289	docs: record that CI, the registry and the deploy moved to Gitea ... The pipeline change made a set of sentences false, and they are the only record of why things are the way they are, so they move with it: the CI section and deploy target in README, the cron and BASE_PATH notes in ARCHITECTURE, the documented User-Agent in INGESTION, and the contact URL in SOURCES. Two comments in source were false in the same way and are fixed here rather than left for the next reader. `serve.ts` said compression was "the whole difference between the Docker image and the deployed site" — the image *is* the deployed site now, so that negotiation is the only compression any reader gets. `robots.ts` justified product-token matching with "our contact URL contains the string StereotypicalCat", which it no longer does; the hazard is the arbitrary substring, not that one, so the comment now says so and the regression test keeps the URL that actually caused it. What is deliberately NOT rewritten: game8.co's refusal stays in the past tense with the Gitea result marked unverified, in AGENTS.md, README, SOURCES and FEEDBACK alike. A new runner address is the variable that failure turns on, so it may well be served — but "may well be" is not evidence, and the four places that would have to change are named together so they change together once a cycle has actually run. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-09-16 04:32:51 +02:00
Lucas WintherandClaude Opus 5	3e30ab07aa	perf: compress text responses from the static server ... GitHub Pages gzips for us, so the deployed site never had this problem. The Docker image serves through serve.ts, which did not — so a self-hoster shipped the bundle at 344 KB where the site sends 100 KB, and the feed at 90 KB where the site sends 10 KB. Roughly three times the bytes, and on anything slower than a laptop on wifi three times the download. Negotiated on `accept-encoding` and applied only to the text types this app serves; a PNG is left alone rather than spending CPU to grow it. `Vary` goes out on both answers, because a shared cache that does not know the response depends on the request header will hand gzipped bytes to a client that never asked. The compressed bytes are cached in memory and keyed by mtime — these files change only on deploy, so re-gzipping 344 KB per request is waste, and keying on mtime rather than holding forever keeps `bun run dev` serving what was just rebuilt. A failure to compress falls through to the raw file: this is an optimisation and never a reason to fail a request. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-08-20 06:55:34 +02:00
Lucas WintherandClaude Opus 5	f2cf9ba0cb	fix: make the server tests hermetic ... They read from public/, which does not exist on a clean checkout — CI runs bun test before any build, so the four of them failed there while passing locally against stale build output. serve.ts now takes PUBLIC_DIR, and the tests serve a temporary tree they create themselves. They exercise serve.ts rather than the build, which is what they were always meant to do. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-08-15 01:26:01 +02:00
Lucas WintherandClaude Opus 5	517066dc65	feat: add Docker image, static server and GitLab CI ... The server is a placeholder for the one in docs/ARCHITECTURE.md — it serves public/ and a health endpoint, nothing more. Reads are confined to public/ by resolving the path and checking it stays inside the root; string-matching ".." is not enough, since encodings and URL normalisation both change what the string looks like and only the resolved path says which file would open. The image runs typecheck and tests during build, ships no source or toolchain, and runs unprivileged. CI's feed job fails if the event count collapses. A source that quietly stops yielding events is what a parser-only pipeline is most prone to, and nothing else would surface it. Everything is offline, so a red pipeline always means the code changed rather than a wiki being down. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-08-15 01:20:42 +02:00