The first release in maintenance mode, and a security one: the apps take
rustix 1.1.6 (RUSTSEC-2026-0486, reachable through the updater's tar and
xattr code), the About page's data-only report links, and two weeks of
dependency updates; the repository gains Qodana with its first findings
fixed.
Version bumps: web/package.json and its lock, src-tauri/Cargo.toml and the
f2p-tracker entry in Cargo.lock, and tauri.conf.json (Android's versionCode
derives from it).
The first release under the changelog split: [Unreleased] becomes
changelog/v4/4.7.x/4.7.2.md (sub-headings up one level, an intro first,
and the "no release yet" phrases reworded), CHANGELOG.md keeps an empty
[Unreleased] and gains the release's row. The GitHub release's notes are
that file below its title and back link.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
changelog/v<major>/<major>.<minor>.x/<version>.md for each of the 42
releases from v1.0.0 to v4.7.1, and changelog/beta/ for pre-releases
(none has been published; its README says how one would be filed).
CHANGELOG.md becomes the index: what the layout is, [Unreleased] exactly
as it was, and a table per major version (version, date, edition) that
links each file.
Each file is its section, copied byte for byte except that its heading
is the file's H1 (so the sub-headings move up one level, outside code
fences), relative links gain ../../../ so they name the same repository
paths, and the --- separators between sections are gone. Checked by
reversing all three changes on every file and comparing with the
original section: 40 of 40 equal. Two releases had no section: v1.0.0
(its GitHub release notes, which the changelog pointed to as "Initial
stable") and v1.1.3 (its tag message).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
README's link, the export-ignore beside CHANGELOG.md's, the watch-paths
note in DEPLOYMENT.md, and a CLAUDE.md rule for where release notes go
and how a release moves [Unreleased] into its own file.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rustix 1.0.0-1.1.5 marks as initialised the bytes an extended-attribute
call (getxattr, listxattr and their l/f forms) never wrote when given a
zero-length buffer - undefined behaviour from safe code. Fixed in 1.1.6
(2026-10-27). In the Tauri shell it comes in through async-io, polling,
zbus and tempfile, and the affected calls through tauri-plugin-updater ->
tar -> xattr. Dependabot raised no alert; an OSV querybatch over
Cargo.lock found it.
Cargo.lock: rustix's version and checksum only. `cargo update -p rustix
--precise 1.1.6` (cargo 1.99) also re-pointed thirteen unrelated
dependency edges to older windows-sys versions and one from syn 3 to
syn 2, so the entry was edited by hand instead; rustix 1.1.6's minimums
(bitflags 2.9.2, errno 0.3.10, libc 0.2.182, windows-sys >=0.52,<0.62)
are all met by what is locked. `cargo metadata --locked` (every platform)
and `cargo test --lib --locked` pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
README: a Qodana badge and the workflow in the list of scanners.
DEPLOYMENT: what qodana.yml runs, the three secrets, the gate, and what
to remove if the licence ends. CLAUDE.md: the setup and the traps the
first runs found (no interpreter in native Python, the Rust image's
missing linker and libraries, plugins only in Docker, the lucide import
false positive). CHANGELOG [Unreleased]: the Qodana entry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SonarCloud's gate wants 80% coverage on new code, and the PR's changed
lines were at 71.8%: ten of them were never run by a test. Now they are:
- appdetails' failures told apart (no answer, 404, success: false, a
body that is not JSON) and the store page's two network_error paths;
- the leaderboards' stars, for a percentage and for "N/A", "No reviews"
and a missing field (both scripts);
- mark_dead_games.parse_players() on the stored formatted strings;
- backfill_discover.parse_released() on every date shape, the year-only
one included.
pytest: 501 passed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each qodana.yaml now fails its job on any problem (failureConditions,
any: 0), as in free-games-itchio-list, and names what it leaves out and
why:
- Python: DuplicatedCode in the two discovery and two leaderboard
scripts (sharing them is a refactor); broad excepts where a failed
request is "no answer" by design (steam_client, the Access diagnosis);
PyCharm's sorted() typing in edit_game.py; the escaped bracket pair in
normalize.py's `\[hover-add\]`.
- JS/TS: ES6UnusedImports (the Svelte plugin cannot resolve
`@lucide/svelte/icons/*` and calls all 122 icon imports unused; every
tsconfig has noUnusedLocals, enforced by svelte-check and tsc), the
admin's relative imports of the public app, `}` escapes kept for
unicode-mode parsing, fetcher.ts's throw-to-own-catch fallback, and
keyCode 229 for IME composition.
- Rust: CargoUnusedDependency, which cannot see the ::serde_json paths
generate_context!() expands to.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No behaviour changes; each is what the inspection asked, or the type
information it lacked.
Python (scripts/):
- `return (a, b)` -> `return a, b` (12, steam_client, store_items,
backfill_discover).
- `log=print` parameters annotated `Callable[[str], None]`: PyCharm could
not type the overloaded builtin as a default and called every log(...)
"not callable" (10, budget, purge_unhealthy, refresh_anticheat,
refresh_peaks).
- fetch_full()'s docstring names all its parameters.
- Nested helpers no longer shadow the loop variables of the function
around them (purge_unhealthy judge(), update_reviews ask()).
- The leaderboards' bare `except:` catches what a reviews string can
raise (AttributeError, TypeError, ValueError), not SystemExit and
KeyboardInterrupt too.
- edit_game.py: unused `import json` dropped; mark_dead_games `[^\d]` ->
`\D`; the DLC section regex loses a group around the whole pattern
(only ever used with search()).
TypeScript / Svelte (web/):
- Two comma expressions written as statements (pipeline route's run
dedupe, CandidateDialog's Reopen button).
- shouldIgnore() returns its last condition instead of if/return.
- Resource's constructor-only private fields are readonly.
- The admin mock seed says HOUR, not 1 * HOUR.
Rust (web/src-tauri/): `serde` dropped - nothing in the crate or in what
generate_context!() expands uses it (only `::serde_json` paths are
generated). serde_json stays, with a comment: Qodana calls it unused
too, but the generated code needs it and the crate does not compile
without it.
Checked: pytest 467, typecheck, vitest 747, knip, cargo test --lib.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What the first runs showed, and the changes:
- Python: SDKs.json was empty - native mode finds no interpreter by
itself, and without one every `dict[int, str]` and `X | None` was an
"invalid type hint" (11 of the 50 problems). The job now builds .venv
from the hashed requirements and passes QODANA_PYTHON_PATH.
- Rust: "Analysis scope: 0 packages" and a Critical "Cargo project
loading" sanity problem: the image has no C linker and none of
Tauri's libraries, and runs as the runner's user, who can neither
apt-get install nor write the image's CARGO_HOME. Now `-u root`,
CARGO_HOME in the cached Qodana cache dir, and a bootstrap that
installs the build packages.
- JS/TS: installing the Svelte plugin fails in native mode with every
released CLI up to 2026.2.3 ("qodana.build.date system property must
be set"; fixed upstream as QD-16701 on 2026-11-05, unreleased), so
this project runs in the Qodana image, on the node_modules and
generated files the job prepared.
One workflow (qodana.yml) with a job per project, as in
free-games-itchio-list: the token check covers all three, triggers skip
data and Markdown-only commits, no PR comment (annotations, Qodana
Cloud and the report artifact carry the results), --repository-root .
for the subdirectory projects, and each job keeps its own cache keys.
The qodana.yaml files use `exclude` and name their Qodana Cloud project.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Three workflows, one per Qodana Cloud project and token
(QODANA_TOKEN_PYTHON, QODANA_TOKEN_TS_JS, QODANA_TOKEN_RUST), each with
the qodana.yaml of its project directory:
- qodana-python.yml: Qodana for Python over scripts/, native mode on the
runner's Python 3.15 with the hashed requirements installed.
- qodana-js.yml: Qodana for JS over web/, native mode on Node 26 after
`npm ci --ignore-scripts` and `npm run build:admin`, with the Svelte
plugin so .svelte files are read.
- qodana-rust.yml: Qodana for Rust (EAP, Docker only) over web/src-tauri/,
with a stand-in web/dist so generate_context!() expands.
Each runs on pushes to main and pull requests that touch its files, and
by hand. The scan is skipped when its token is not available (forks,
Dependabot), as sonarcloud.yml does; the action is pinned by SHA, the
job's token can read contents and write only checks and PR comments, and
each workflow has its own cache keys so the three do not collide.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dependabot's npm-minor-patch group (#256): @lucide/svelte 1.72.0,
bits-ui 2.21.0, knip 6.45.1, rollup-plugin-visualizer 7.1.3, vite 8.3.8,
wrangler 4.162.0 - all released at least four days ago.
#256 failed Web CI on knip: 6.45 follows tsconfig.json's `extends` and
reports "$app" (from "$app/tsconfig", which `svelte-kit sync` generates
into node_modules/$app) as an unlisted dependency - an error. It cannot
be taken back with ignoreDependencies: knip matches those against a
package name, and getPackageNameFromModuleSpecifier() returns nothing for
a specifier starting with "$", so the item is never compared (and "$app"
would be read as a regex anyway). knip.json now ignores unlisted
dependencies in tsconfig.json only (ignoreIssues). The export backlog and
the three configuration hints are unchanged from main.
Local proof: typecheck, 747 tests, build + verify-dist --web (18,911
pages, precache 177 entries, as live), cf:check, knip, Tauri build +
verify-dist --tauri.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
The project is stable: no new features, code changes only for security
advisories and runtime/dependency updates, and issues and pull requests
are for the data (add, correct, remove a game).
- README: status, build, quality, version, licence and runtime badges, a
"Project status" section, and a data-first Contribute section
- CONTRIBUTING, SECURITY, Contact, the PR template and CLAUDE.md state
the same policy
- Issue forms: add_game and edit_game are new; feature_request, feedback
and off_topic are removed; blank issues are off (config.yml)
- About page: "Report something" links the five remaining forms
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Dependabot #249 (coverage 7.17.2), #250 (action-gh-release 3.0.4,
sonarqube-scan-action 8.4.1) and #251 (twelve npm patch and minor
releases) were merged as they were. Nothing security-relevant, so the
entry waits in [Unreleased] for the next release.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
The apps go from 2.5.0 to 2.5.1, which is the first app build with the
accessibility fixes from #244. The desktop app is also the first build that
can zoom.
Version bumps: web/package.json and its lock, src-tauri/Cargo.toml and the
f2p-tracker entry in Cargo.lock, and tauri.conf.json (Android's versionCode
derives from it).
The CHANGELOG's [Unreleased] section becomes v4.7.1, with an intro, and a
fresh [Unreleased] goes above it. ACCESSIBILITY.md now says what works for
the website and the apps 2.5.1, instead of "the apps get it with their next
release".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SonarCloud's gate counted 6 new lines no test had loaded: the overlay state
and focusOnMount (lib/overlays.svelte.ts), and the palette shortcut's new
early return. overlays.test.ts drives them in Node: overlays.open follows
either overlay, focusOnMount focuses without scrolling, and Ctrl+K is left
alone under an overlay (palette shut, default not prevented) but toggles the
palette otherwise.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
src/lib/a11y.test.ts reads the source, like mobile-layout.test.ts. It
checks:
- the table's roles, counts and row indexes, and that no <a> is a row or
carries a fake link;
- every column has a name, and the cards are a list with positions;
- the panes have a minimum height;
- there is no colour-only kernel badge;
- the overlays are dialogs that focus themselves and make the page inert;
- the palette shortcut stands down, and back-to-top is inert while hidden;
- the zoom setting and its capability are present.
It also computes the theme's contrast with the WCAG formula, so a token
edit that drops below 4.5:1 for text or 3:1 for a control's edge fails.
ACCESSIBILITY.md moves the fixed items from "Known limitations" to "What
works today". The desktop and Android apps 2.5.0 predate them and get them
with their next release. CLAUDE.md lists the rules behind each fix, and
CHANGELOG [Unreleased] describes them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Computed with the WCAG formula, against the page, cards, and each colour's
own /12-/15 tint.
Light theme:
- Links, primary button labels, warnings and some badges measured
3.2-4.3:1. --primary goes 42% -> 34% (with --ring), --warning
38 -> 29, --destructive 47 -> 42, --success 32 -> 27 and --info 40 -> 35.
- --input goes from the --border value to 3.2:1, so text boxes and
drop-downs show an edge. --border stays light; card edges carry no
meaning.
Dark theme:
- --destructive 62 -> 67 brings red badges from 4.05 to 4.6.
- --input goes 19 -> 40% for the same 3:1 edge.
Desktop zoom: tauri.conf.json sets zoomHotkeysEnabled (Tauri's default is
false, which also turned off WebView2's zoom). capabilities/zoom.json, which
is desktop-only like updater.json, grants core:webview:allow-set-webview-zoom.
macOS and Linux zoom through a script Tauri injects that calls it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The terms screen was a plain div, rendered last in the page. Focus stayed
where it was, and Tab walked through the whole hidden page before reaching
its buttons. The human check had role="dialog", but neither moved focus
nor kept it.
Both now:
- report themselves to lib/overlays.svelte.ts;
- are role="dialog" with aria-modal, labelled by an h2 (each used to add a
second h1);
- move focus into themselves on mount (focusOnMount).
The layout makes everything behind them inert: the bare pages' wrapper,
the skip link and the shell. BackToTop moves inside the shell to go inert
with it.
Ctrl/Cmd+K stands down while they are open. It could open the palette
UNDER the gate (z-50 against z-[60]) and trap focus there, out of sight.
Also:
- BackToTop is inert while hidden: it only faded out, so it stayed a Tab
stop. Its JS smooth scroll follows prefers-reduced-motion.
- The command palette's search box gets a focus ring, drawn on its row.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The games table:
- The rows were <a role="row"> with nothing around them, so a screen reader
read them as neither a link nor a table. The grid now has the complete
ARIA table: role="table" with aria-rowcount/aria-colcount, a rowgroup,
and aria-rowindex on every virtualised row. The icon-only columns have
names for screen readers (srLabel), and the non-sortable "Platforms"
header is plain text rather than a disabled button.
- A row is no longer a link wrapped around a fake one. The name is the
row's only Tab stop, and its link stretches over the row, so a click
anywhere still opens the game. The Steam icon is a real link, kept out
of the Tab order (a game's page has the same links). The tooltips sit
above the stretched link, and screen readers get their words.
- The row draws the focus ring, because the cells clip overflow.
The phone cards are a list with aria-setsize/aria-posinset.
Both panes keep a minimum height (min-h-64). Sized to the window alone,
they shrank to nothing at 300-400% zoom.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Kernel-level anti-cheat differed from the rest only by its badge colour,
red against amber, with the product name as the only text. That told a
colour-blind reader and a screen reader nothing.
games/AntiCheatBadge.svelte adds a shield icon and the words
"Kernel-level". They are visible on a game's page, and read only by screen
readers where a long product name already fills the badge (/random here;
the table and the cards in the next commit).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A read-through against the code found about forty claims that had drifted.
README:
- Dynamic game-count and version badges. The count is index.json's total.
The version is the newest v* release by semver, since an app release
published last would otherwise count as "latest".
- SvelteKit 3, every desktop package, and the shard layout without a last
shard number.
- The media host, which commits deploy, and the nine workflows the table
left out.
- The accessibility statement and form in the link lists.
SECURITY.md:
- Fix the broken bullet list.
- Describe the real stack, and pushes with the built-in GITHUB_TOKEN.
- Add to scope: the media host, /api/ingest/*, /api/updates/desktop and the
avatar origin.
AUTHORS.md and username.txt:
- Donations are in FUNDING.yml.
- The Add-games template is gone.
- Test devices come from pc_spec.
The issue forms lose the hash URLs, the GitHub Pages permalink, and the
editing and GPG options.
web/README.md, dev_env (EN + VI), the acknowledgements and the contact page
are updated to match. The last two are not consent documents, so nobody is
asked to accept the terms again.
CHANGELOG [Unreleased] lists all three commits.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The report section gets a fourth form, Accessibility barrier, in a 2x2
grid. Below it are a short note and a link to ACCESSIBILITY.md on GitHub.
The statement is linked rather than rendered under /legal/: it is not a
legal document, and a file rendered there becomes a build input that the
deploy watch paths must list.
The stack list said SvelteKit 2 and a 3,600-row table. The footnote said
everything the page loads comes from this site, which is not true of the
beacon or the human check. The Vietnamese AI note also gets the last
sentence it was missing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ACCESSIBILITY.md sits at the root beside SECURITY.md. GitHub reads it from
.github/, the root or docs/ and shows it as the repository's Accessibility
tab. It covers:
- WCAG 2.2 AA as a target, not a claim.
- What works today and what does not, with a way around each limitation
where there is one.
- The browsers, apps and assistive technology actually used (keyboard,
Narrator, NVDA).
- How to report a barrier without saying anything about yourself.
- Replies on SECURITY.md's terms: first within a week, blockers first, no
fixed deadlines.
- The rules for contributors and coding agents.
.github/ISSUE_TEMPLATE/accessibility.yml files a report under the new
`accessibility` label, with no required final checkbox. The pull request
template is the short checklist, and completes the community profile.
CLAUDE.md says the statement is a claim about the code, and names the two
limitations that look solved but are not.
.gitattributes keeps the new file out of source archives like the other
community files. It also stops leaving out Contact, PRIVACY_POLICY and ToS:
the web build reads every legal document and stops when one is missing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Desktop and Android 2.4.1 -> 2.5.0 (package.json and its lock,
tauri.conf.json, Cargo.toml, the f2p-tracker entry of Cargo.lock); repo
public-facing version 4.6.1 -> 4.7.0. CHANGELOG: the random games page,
Leave site, Decline quitting the Android app, and the 2026-11-03
dependency pass that waited in [Unreleased]. No legal document changed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CLAUDE.md: why /random keeps its picks in memory and only the reader
rolls, the crypto sampling (not Math.random), why the route is top-level,
and the base key a plural needs; how Leave site finds the page before the
site, the watchdog and its three cancel events, the deliberate second click
to close, and why Decline quits through exit(). Both READMEs list the
random page and its modules.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Web: a "Leave site" button on the terms card and on the declined notice.
No page may open the browser's own start page (chrome://newtab,
about:home), so lib/leave-site.ts goes back to the page before the site:
history.go(-(navigation.currentEntry.index + 1)) steps over every entry of
the site's contiguous same-origin run at once. history.go() is silent when
there is nowhere to go, so a 1.5 s watchdog (cancelled by beforeunload,
pagehide and popstate) shows "Nothing to go back to"; when every entry is
the site's that shows at once, and closing the tab is a second, explicit
click, because closing the last tab closes the browser window.
Apps: Decline called getCurrentWindow().close(), which on Android resolves
without closing anything (tao reports a destroyed window only from the
Activity's onDestroy), so Decline did nothing there. It now calls exit()
from @tauri-apps/api/app, which finishes the activity on Android and ends
the process on the desktop; the declined notice appears if the app is
still alive 2 s later. default.json trades core:window:allow-close, which
nothing else used, for core:app:allow-exit. The Leave button is web only.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/random rolls one to five games from the catalogue (five to start with):
any type, online or offline, dead games only when asked, never one marked
unsafe. Roll again avoids the games on screen while enough others remain;
a smaller count keeps the first picks, a larger one adds to them.
- lib/random-pick.ts: crypto.getRandomValues with rejection sampling and a
sparse Fisher-Yates, never Math.random (SonarCloud S2245), plus the pool
rules, read off appidIndex so each game appears once.
- lib/random.svelte.ts: the picks as appids, module-level and memory only,
so Back from a game keeps them and no f2p:* key is needed (a new key
means a privacy-policy edit, which reopens the consent gate). Only the
reader rolls; a revalidation only drops a pick that left the catalogue
or stopped qualifying.
- The page, an entry in the sidebar, drawer and palette (nav.ts) and a
dashboard button. Top-level on purpose: the header search, isActive and
the PWA's globIgnores all treat /games/* specially. The empty state joins
verify-dist's BAKED_EMPTY_STATES; the sitemap ranks the page low.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: Pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Takes Dependabot's npm group (#236) and cargo group (#234) together: the
Tauri shell plugin moves to 2.6.0 on both sides, and the CLI refuses a
JavaScript/Rust pair on different minors. Adds the SvelteKit 3.1.1 and
adapter-static 4.0.1 patches (exact pins kept), @types/node 26.6.6, knip
6.44.1 and @lucide/svelte 1.66.0 - everything at least three days old;
newer releases wait for next week's Dependabot run.
wrangler 4.156.0's miniflare pins undici 7.30.1 itself, so the
"miniflare": {"undici": "^7.30.1"} override goes in the same commit, as
CLAUDE.md required. npm audit: only the known deepmerge low advisory.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: Passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: Passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: Passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: Passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: Passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
- tauri-plugin-updater 2.14.0 -> 2.14.1 moves its Windows zip reader from
zip 4.6.1 to 9.2.0: closes Dependabot #82 (critical), #83, #84 and
RUSTSEC-2026-0367/0368/0369. Targeted cargo update; cargo test --lib ok.
- npm overrides workbox-build -> glob ^14.0.2 and filelist -> minimatch
^11.0.1 (GHSA-3g3m-2fjr-6pw4, GHSA-g3hv-75wg-m249, published 2026-10-30).
The precache lists the same 172 URLs as before.
- deepmerge (#81, low) has no fixed release: build-time only, dismissed.
- CLAUDE.md: when the new overrides and the undici one can go.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved in /admin by admin.
Reason: Passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
appdetails writes "Free To Play"; SKIP_GENRE_TAGS said "Free to Play", and
the exact match let 1,357 of 12,854 games be stored with it as their genre
(the third most common), while the fallback to the first name could pick
it as well.
- fetcher.pick_genre() compares casefolded and never falls back to a price
model or a release state (NOT_GENRES); with nothing else it says
"Uncategorized". ingest uses it.
- Refresh Store Data replaces a stored one from appdetails: 150 games a
day, first after the page repairs, never under an override. It is the one
manual-field value the job writes; no person chose it. A dry run on the
first 150 (2026-10-30): Casual 91, Indie 24, Strategy 11, Simulation 11,
Uncategorized 10, three others; all answered, no override.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/plan/19-all-languages.md: what kept them out, what every workflow
does with them, the re-sweep, and what is left.
- CLAUDE.md: discovery's language rules, ASCII appids, search folds but
storage never does, re-cut descriptions are not news.
- docs/ADMIN.md: the filters as they are now, re-sweeping a whole year,
the Languages line in the candidate dialog.
- README.md, docs/plan/11 (the decision changed), CHANGELOG [Unreleased].
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Without a byte order mark Excel reads a CSV in the system's legacy code
page, Japanese Windows included, and every Japanese, Chinese or Korean
name came out as mojibake. csvForExcel() prepends the mark; JSON is
unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The catalogue now holds games in every language.
- /games filters by language (?lang=, counted like the others); the names
are Steam's English ones as stored, data rather than i18n keys. About
says the catalogue covers every language.
- fold() (NFKC, then hiragana to katakana) on both sides of every search
box - the Fuse index (one getFn per key: the default getter hands back
objects for array fields), the palette, /developers, /publishers and
the anti-cheat list - so half-width, full-width, hiragana and katakana
match. Search only: stored text keeps its spelling.
- The palette takes one kanji, kana or Hangul syllable.
- The header search waits for an input method to finish composing before
it jumps to /games, and jumps with reset: false: the default reset sent
focus to <body>, so the next keystroke went nowhere.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Python's digit class also takes full-width and other scripts' digits.
A queued link in them gave an appid that missed every comparison and
made rotation.slice_of() raise, stopping every refresh. extract_appid
refuses a run of digits with a non-ASCII one in it; normalize_link()
reads NFKC first, so a Japanese keyboard's full-width appid is ASCII.
The blocklist uses ASCII digits and fullmatch, like removal.ts.
- truncate_description() backs off to just after a CJK sentence end as it
does to a space, and trims the CJK comma and full stop before the
ellipsis. Stored descriptions (all within the cap) never change, and
_fuller_cut() lets Refresh Store Data write a re-cut without calling it
news.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The candidate dialog lists the languages discovery recorded, with a
"No English" badge when English is not among them. A row queued before
discovery recorded languages shows "-", which is not the same as an
empty list (a game that declares none). Auto-approve is unchanged: such
a game is decided like any other.
The mock server's payloads carry languages too, and it queues one game
without English so the badge can be seen in dev.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every window swept before needs one more pass for the games without
English, and backfill windows are dispatched several at a time. The
discovery group kept ONE waiting run, so a third cancelled the one
already waiting - the lesson data-write learned in October.
- queue: max in both discovery workflows; pipeline.test.ts now holds
every shared concurrency group to one queue setting.
- Backfill Discovery takes max_pages (through env, default 40): a whole
recent year is about 30 pages of 100.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The store search pinned supportedlang=english, which left out every free
game that does not list English: 1,592 of 18,790 on 2026-10-30, most of
them Chinese, Japanese or Korean only (5118700 among them). Without the
parameter Steam filters on no language at all, with l=english or an
Accept-Language: ja header alike.
- fetch_search_page() sends no supportedlang, and sends l=english so the
row text ("Coming soon", month names) stays English by parameter.
- Candidates carry their languages (appdetails_languages()), a dry run
says which list no English, and every run counts them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Measured on production after v4.5.1 deployed (2026-10-27, SIN): over one
keep-alive connection each budget held exactly - /api/no-such-route
121 x 404 then 429 with Retry-After, no-store and CORS; /api/human-check
19 then 429 - while requests on fresh connections, which Cloudflare
spreads over many servers, were never refused (175 human checks in 70 s
against a budget of 20). A probe Worker in a remote preview confirmed the
binding itself enforces (limit 5: 6 allowed, then refused).
So the layer stops browsers and connection-reusing scripts; a client that
reconnects for every request is the WAF rule's, which counted exactly
(250). The docs, CLAUDE.md, the module comment, wrangler.jsonc and the
unpublished v4.5.1 entry said "per location, approximate"; they now say
what was measured. The section 3b check used xargs (fresh connections) and
would have shown no 429 - it now sends everything over one connection.
No behaviour change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The section 3a check ran 300 separate curls through xargs -P 30. Each one
pays a TLS handshake, so from here it managed about 21 requests a second -
300 x 200 in 14 s - and never crossed 250 in 10 s: the rule looked broken
when it was not. One `curl --parallel` with its URL list on stdin reuses
its connections and does: 250 x 200 then 150 x 429, measured against the
live site-wide rule on 2026-10-27.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Worker-side rate limits behind the edge rule, and the recommended
site-wide WAF rule. Repo-only: nothing in the apps changed, so desktop and
Android stay at 2.3.0 with no new build.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The zone's one Free-plan rate-limiting rule (IP, 10 s, block 10 s) stays
the first layer: it refuses a burst before the Worker is invoked and is the
only limit on the prerendered pages. The Worker now adds a second one with
the `ratelimits` bindings in wrangler.jsonc, 60-second windows and one
budget per surface, keyed by IPv4 address or IPv6 /64:
RL_DATA /api/data/* 240/min
RL_IMG /img/* 600/min
RL_API /api/activity, /api/updates/desktop, … 120/min
RL_HUMAN /api/human-check 20/min
RL_ADMIN /admin, /admin/*, /api/ingest/* 300/min
Checked after the country block and before every route and the Access
check; over a limit the answer is 429 + Retry-After: 60, no-store, with
CORS only where the route itself sends it (data, api). It fails open
(no binding, no CF-Connecting-IP, a throwing limit()) and logs no refusal.
Verified locally under wrangler dev: each budget refused exactly past its
limit, a second /64 address shared the first one's budget, pages were never
counted.
rate-limit.test.ts holds wrangler.jsonc to the code (binding names, period
60 = Retry-After, account-unique namespace ids) and checks that every
run_worker_first prefix draws on a budget. worker-configuration.d.ts gets
the five Env lines (and the IMG_MINT_PER_TICK value it had missed) without
regenerating the runtime types.
docs/SECURITY_SETUP.md section 3 describes both layers and recommends
widening the WAF rule to the whole zone except /_app/immutable/ at 250 per
10 s, counted from the build (a first visit sends 110-130 requests once
the service worker precaches); CLAUDE.md records the rules.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SvelteKit 3 (PR #218) under the site and the apps, plus Tauri 2.12.5 from
Dependabot #214. Desktop and Android 2.2.2 -> 2.3.0 (package.json + lock,
Cargo.toml + the f2p-tracker entry in Cargo.lock, tauri.conf.json);
CHANGELOG section dated, fresh [Unreleased].
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The SvelteKit 3 fallback for a /#/ path that matches no route passed the
hash straight to location.replace(): CodeQL code-scanning alert #25,
client-side XSS, and an open redirect in practice - `#//other.example/x`
resolved to another site once goto rejected it.
The hash is now resolved against the page's origin and ignored when it
names another one, goto gets that URL, and an unmatched path goes to the
404 page at its fixed address (/error/404). Nothing from the hash reaches
location.* any more. Tests cover both off-site forms (`#//host`,
`#/\host`) and the 404 fallback; checked in a browser on `npm run dev`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- legacy-url: a /#/ path renders in place with { replace, reset: false },
and one that matches no route falls back to location.replace (kit 3's
goto rejects it).
- fallback-route: the re-render uses replace / reset: false / refreshAll
(noScroll and keepFocus throw in kit 3's dev build), and leaves routes
that hydrated or cannot fall back alone.
- params.legaldoc: every legal document matches; anything else does not.
- hooks.client: returns nothing for an ordinary error (kit 3 keeps its own
message), and says it is reloading only when the stale-chunk reload ran.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sveltejs/kit 2.70.3 -> 3.1.0, @sveltejs/adapter-static 3.0.10 -> 4.0.0.
Closes GHSA-27mw-82g8-phjj and GHSA-pfhg-q3qv-9q6r (dismissed in v4.4.1
as not applicable), and drops the cookie override kit 2 needed: npm audit
reports nothing.
- Config: svelte.config.js is refused by kit 3. Its options are now
sveltekitConfig(tauri) in build/sveltekit-config.ts, passed by
vite.config.ts as sveltekit(sveltekitConfig(IS_TAURI)), with tests for
both CSP flavours, paths.relative, the sitemap entry and the prerender
404 handler. The unused, now-deprecated "@" alias and typescript.config
hook are gone; tsconfig.json extends $app/tsconfig and owns `include`.
- $lib -> #lib (package.json imports), with .js on module imports.
tsconfig repeats the mapping in `paths`: svelte-check --tsgo only maps
.svelte imports through `paths`, and without it every #lib component
fell back to the *.svelte shim (props unchecked; proven with a planted
error).
- Param matchers: src/params/legaldoc.ts -> src/params.ts (defineParams).
vite build imports that file with Node's own import(), so it imports
#lib/legal.ts and legal.ts imports ./schema.ts by their real names.
- PWA: @vite-pwa/sveltekit never supported kit 3 and wrote the worker when
the SERVER build closed, which kit 3's environment build does first.
build/pwa.ts wires vite-plugin-pwa in a buildApp hook after kit's
prerender and before its adapter, with the same globs and URL mapping.
- goto options renamed (replace, reset: false, refreshAll); the /games
filter write is a shallow goto; a legacy /#/ path that matches no route
falls back to location.replace (kit 3's goto rejects it). Hook types
from @sveltejs/kit/hooks; the client handleError returns nothing to keep
kit's message.
- runed 0.35 (bits-ui) peers kit ^2: overridden to our kit, as for
echarts-wordcloud.
Verified against a kit 2 build of the same commit: same 11,037 files bar
hashed chunks, same non-immutable precache URLs, navigateFallback "/",
identical CSP per page (hashes masked), manifest and sitemap byte-equal,
same visible text.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Desktop and Android 2.2.1 -> 2.2.2 (package.json + lock, Cargo.toml + the
f2p-tracker entry in Cargo.lock, tauri.conf.json), so the apps ship the
patched rustls/webpki stack their updater uses. CHANGELOG section dated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
npm (web/):
- undici 7.30.1 through a "miniflare" override (GHSA-xjj6-f33q-929c,
GHSA-4qv8-2p9j-2685, GHSA-f72v-6w45-q472). miniflare pins undici exactly
and wrangler 4.152.0, the newest, still ships 7.29.1. Local tooling only.
- zod 4.6.7 (GHSA-mrhx-c7xc-m3w5, via knip).
- Minor/patch: @lucide/svelte 1.61.0, @tanstack/svelte-virtual 3.13.48,
bits-ui 2.20.2, vite 8.3.5, wrangler 4.152.0, knip 6.43.0,
@tauri-apps/cli 2.12.4.
cargo (web/src-tauri/Cargo.lock, targeted updates only):
- rustls 0.23.46 (RUSTSEC-2026-0346..0349), rustls-webpki 0.103.16
(RUSTSEC-2026-0382), webpki-root-certs 1.0.11 (RUSTSEC-2026-0383),
tokio 1.54.1 (RUSTSEC-2026-0386), anyhow 1.0.104 (RUSTSEC-2026-0190),
event-listener 5.4.2 (RUSTSEC-2026-0221), plist 1.10.3 -> quick-xml
0.42.0 (RUSTSEC-2026-0194/0195). Dependabot had none of these.
- Left upstream: zip 4 (tauri-plugin-updater 2.14.0 asks for ^4), glib 0.18
(GTK 3), unmaintained proc-macro-error/zbus_names/zvariant.
pip: certifi 2026.10.23, coverage 7.17.0 (tests), with every file's hash.
CI: actions/checkout v4/v5 -> v6 and actions/setup-python v5 -> v6
everywhere (the Node 20 majors warned on every data job), rust-cache 2.9.3
by SHA. dependabot.yml says why those majors are taken by hand.
CLAUDE.md: the undici override and when to drop it; why SvelteKit stays on 2
(GHSA-27mw-82g8-phjj and GHSA-pfhg-q3qv-9q6r need setHeaders or use:enhance,
which the app does not have).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
The first run of the new Update Reviews on main asked appreviews about the
12 games GetItems counted at 0, and all 12 failed: since 2026-10-23
store.steampowered.com/appreviews/<id>?json=1 answers 302 to the store
front, from GitHub's runners as from anywhere else (it worked on 10-17).
The 38 games the ingest added that day were listed with "N/A".
- fetch_full() falls back to the GetItems summary when appreviews gives
none (reviews_from_store_api()), so an ingest gets the value the daily
refresh would write.
- update_reviews: a game never read ("N/A", nothing) with a count of 0
becomes "No reviews" without a question; the first count GetItems has
replaces it. A stored percentage is still never replaced by a 0 without a
second source.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs/plan/18-pipeline-scale.md holds the measurements (9,847 games,
+~280 a day), what each job cost, what GetItems answers, the direction
and what is left. CLAUDE.md gains the rules for reviews, the purge,
budgets and the data-write group; README the new schedules.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- queue: max on every data-write workflow (GitHub, 2026-05-07): up to
100 runs wait, first in, first out. The default kept one, and a run
queueing behind a running job cancelled it.
- ref: main on every checkout. A run's commit is fixed when it is
created, so a run that waited behind another data job wrote shards
from before that job's commit; Auto Update JSON failed four days in
ten on the rebase conflict in data/index.json.
- timeout-minutes everywhere, and JOB_BUDGET_MINUTES at least 20 below
it for the long loops (never for the ingest, which empties its queue).
- pipeline.test.ts fails on a data-write workflow missing any of these.
- The admin's Pipeline and Automation pages, docs/ADMIN.md and the
auto-approve comment no longer say a push evicts a waiting job; the
idle gate stays, so a batch's ingest starts at once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
It sent a HEAD request to every store page every five days, 5.5 hours at
9,847 games, and flagged 404/410. Steam sends a delisted app's page to
the store front, which answers 200: scripts/dead_links.log never existed
and no game ever became "delisted". The purge's GetItems screen sees
delisted games (unlisted) instead.
Removes the workflow, bash/dead_links.sh, scripts/check_dead_links.py
and DEAD_LINKS_LOG, and the workflow from web/shared/pipeline.ts and the
failure notifier's list. check_store_page() stays: it is the health
check's last resort.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Refresh Store Data: the page and appdetails cycles grow past 2,000
pages / 500 appdetails a day (7 -> 14, 30 -> 60) instead of the run,
the slice comes in a daily order, and the store step has a budget. A
game appdetails no longer calls free is listed in a ::warning::, the
case the purge's two-signal rule cannot see; nothing is written.
- Refresh All-Time Peaks: 30 -> 60 days past 400 pages a day, never
shorter, so SteamCharts is still asked at most once a month a game;
the budget stops it with a warning like a refusal does.
- Force Re-fetch: --part K/N, oldest last_updated first, each game
cleared on a copy that replaces it only once appdetails has answered;
no final loop stamping every game. Parts queue one after another.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The purge asked appdetails about every game, 5.3 hours at 9,847, and one
answer was enough to remove one - appdetails has answered success:false
for live games in bursts (2026-09-27).
GetItems now screens the whole catalogue in a few minutes (unknown,
hidden, unlisted, coming soon, not is_free; never type), and
check_game_health() must confirm each flag; "unavailable" is asked again
five minutes later. A failed batch or a network error never reads as
gone, blocklisted games are not asked about, and more than 500 flags or
100 removals stops the run before anything is written. Removals are
logged as before. A notice names earlier removals Steam has since undone.
The dry run on the real catalogue: 8 flagged, 3 removed (the three
unlisted games), 5 kept because appdetails calls them free. Daily now.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Update Reviews asked appreviews about one game at a time, two seconds a
game. At 9,847 games it ran into GitHub's six-hour limit on 2026-10-23
and was stopped with nothing saved; five of its ten runs before that
were cancelled while waiting.
- SteamClient.fetch_items(): GetItems for a whole catalogue, a failed
batch costing only its own ids (the anti-cheat sweep now uses it).
- update_reviews.py reads review_summary() for every game, ~2 minutes,
daily. Steam floors its percentage; reviews_from_summary() floors
appreviews in integers too, so an ingest and the refresh agree. A
count of 0 is never written on GetItems' word (it said 0 for a game
with thousands): a stored percentage or "N/A" is asked on appreviews,
at most 300 a run. last_updated moves on a change, and on a 14-20 day
heartbeat that keeps the site's 30-day "stale" badge quiet without
rewriting every record every run.
- core/budget.py: JOB_BUDGET_MINUTES. Past it process_batch() starts no
further game, so a job saves what it did instead of being killed;
a ::warning:: when a loop used three quarters of its budget.
- rotation.cycle_for() / daily_order(): cycles that grow with the
catalogue as multiples of their base, and an order that changes daily.
- The player-count loops skip the batch pauses meant for store pages
(Top Online ~27 min instead of 48) and take a deadline, like
update_all_full().
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
main's first analysis with coverage failed the "Sonar way" gate at 75.0%
on new code (lines 92/114, conditions 16/30). These tests cover what was
untested in that new code:
- utils.ts: formatNumber, parseIntSafe and parseReleaseDate had no tests.
The year-only branch of parseReleaseDate is unreachable (Date.parse
already reads "2025" as ISO), so only its other side is covered.
- reconcile.ts: an approval the pipeline rejected afterwards becoming
failed (by appid and by link, with no decision recorded), and one removed
only before it, or with no timestamp, staying approved past a
malformed line.
- delete_game.py --list, empty and not; discover_new's search parser on a
page cut off inside an anchor tag.
Against main's new lines and conditions, these lift the estimate to
121/144, about 84%.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The scan job now runs both suites with coverage before scanning:
pytest --cov (pyproject.toml: scripts/ without its tests, relative
paths, coverage.xml) and `npm run test:coverage` (vite.config.ts: v8,
lcov with projectRoot "..", so paths start web/). sonar-project.properties
names both reports and drops sonar.coverage.exclusions.
requirements-test.txt gains pytest-cov 7.1.0 and coverage 7.16.2 with
every file's hash (uv pip compile --universal --generate-hashes
--python-version 3.15; the existing pins are unchanged). web gains
@vitest/coverage-v8 5.0.5, matching vitest; none of its packages has an
install script. Coverage stays off for a plain `npm test`.
The token check is its own job, so the scan steps no longer each repeat
the condition; the workflow grants nothing at the top and the scan job
contents: read. `npm run build:admin` replaces the bare `svelte-kit
sync`: it syncs too, and writes the admin bundle the Worker's tests load.
Locally: 576 vitest tests at 58.35% of lines, 299 pytest tests at 57.7%.
Against main's new-code lines (SonarCloud's isNew), the reports cover
92 of 114 coverable lines, 80.7%: the 80% gate is borderline.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first full CI analysis of main (db804e27) failed the "Sonar way"
quality gate on one condition: coverage on new code 0.0% < 80%, over 109
new lines. The scan uploads no test report, so every executable line
counted as uncovered; automatic analysis never computed coverage, so the
condition was never evaluated before. Every other condition passed, with
0 open issues and 0 hotspots.
sonar.coverage.exclusions=**/* restores that: no lines to cover, no
coverage condition. Measuring coverage means generating reports in the
workflow and removing this line in the same change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first CI scan logged "Failed to parse tsconfig web/tsconfig.json":
it extends .svelte-kit/tsconfig.json, which only `svelte-kit sync`
writes, so web/src was analysed without its compiler options or types.
The job now installs web/ (npm ci --ignore-scripts) and syncs before
scanning; both outputs are gitignored, so neither is analysed itself.
sonar.typescript.tsconfigPaths names all six tsconfigs: auto-detection
found only the two named tsconfig.json, leaving the Worker, shared/ and
the tests on fallback options.
The toolchain plan no longer claims sonar-python knows 3.15: the scan
warns and analyses as 3.14.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A sonarcloud.yml workflow runs SonarSource/sonarqube-scan-action (pinned to
the v8.3.0 commit) on pull requests and main, with full history for blame.
Commits that touch only what the data jobs write are skipped, and a run
without SONAR_TOKEN (forks, Dependabot) passes without scanning.
.sonarcloud.properties becomes sonar-project.properties, now naming the
organization and project key; its scope settings are unchanged. The
toolchain test, Web CI's paths, CLAUDE.md and docs follow the rename.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
CodeQL (js/incomplete-sanitization, high, alert #24) flagged the helper
that turned a version into a RegExp by escaping only its dots. The versions
come from the repository's own files, but no pattern needs building at all:
a pin is now unquoted and compared as a string, and the @types/node major is
read with a literal pattern. The test still fails on a drifted Python, an
unquoted version and a lone .node-version change, each with the file named.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/plan/16-toolchain-2026.md: the assessment - what each release
changes, what was measured here, the decisions, how to move each runtime
next time, and what was left.
- docs/plan/17-typescript-7.1.md: the springboard for dropping TypeScript 6
once 7.1 ships - start conditions and how to check them, the steps, the
planted-error table and the baselines to compare against.
- CLAUDE.md: "TypeScript is two packages, on purpose" and "One version of
each runtime"; the uv compile line says 3.15.
- dev_env (EN/VI), README, AUTHORS, TAURI.md, web/README, THIRD_PARTY,
DEPLOYMENT (Workers Builds' NODE_VERSION=26, the Checks paragraph),
ACKNOWLEDGEMENTs and the About page's stack list ("TypeScript 7 + 6").
- CHANGELOG: the Tooling entry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
eMudhra's `emSign ECC Root CA - G3` had intermediates whose private keys
were compromised. certifi 2026.10.18, the version pinned here, had already
removed every emSign root; 2026.10.19 restores the three that are not
affected (G1, C1, ECC C3) and keeps G3 out. The advisory's range still
covered 2026.10.18, so pip-audit flagged it. The hashes come from
`uv pip compile`, one per file on PyPI (wheel and sdist); every other pin
is unchanged.
Checked on Python 3.15.1: --require-hashes --only-binary :all: installs,
the 299 tests pass, pip-audit finds no known vulnerability.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
web/shared/toolchain.test.ts fails when a pin drifts:
- web/.node-version is one major, which every setup-node step,
engines.node and the @types/node major repeat;
- every setup-python step installs sonar.python.version, which the
--python-version in requirements.txt's header repeats; codeql.yml is the
one named exception (3.14);
- each workflow has as many version keys as setup steps, and every version
is a quoted literal (unquoted, YAML reads 3.10 as 3.1);
- `typescript` is 6, @typescript/native is npm:typescript@~7, and no script
calls a bare tsc.
Web CI also runs on .github/workflows/** and .sonarcloud.properties, so a
pull request that moves only a pin meets the test - and pipeline.test.ts,
which reads the workflows for the data-write group, no longer misses a
workflow-only change either.
Proven by breaking one pin at a time (one workflow's Python, .node-version
alone, a setup-node switched to node-version-file): each failed the test
with the file named.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Node:
- web/.node-version (26) is the pin. The five setup-node steps say '26' as
a literal, not node-version-file: release-android.yml checks out the tag
it rebuilds, and older tags have no such file.
- engines.node >=26 (advisory) and @types/node ^26.6.5; TypeScript 6 still
type-checks clean with the new types.
TypeScript:
- TypeScript 7.0 has no JavaScript API, and svelte-check (which refuses
`typescript` 7) and `svelte-kit sync` (route $types) need one, so
`typescript` stays ^6.0.3 and 7 is the alias
"@typescript/native": "npm:typescript@~7.0.2", the layout svelte-check
documents. ~7.0 because 7.1 breaks svelte-check's experimental mode.
- `check` runs svelte-check --tsgo, on TypeScript 7. `check:admin` stays on
6: --tsgo maps a tsconfig outside the workspace root onto the app's
components (seen: false errors in src/routes instead of the admin's).
- The four `tsc -p` steps and typecheck:worker call
node node_modules/@typescript/native/bin/tsc: both packages declare a
`tsc` bin, so node_modules/.bin/tsc could be either.
- "DOM.Iterable" leaves the admin tsconfigs (an empty lib since 6.0).
- Dependabot ignores the alias (it mishandles npm: aliases) and keeps
ignoring `typescript` majors, now with the reason.
Checked: type errors planted in a route's script, as a wrong prop on
src/lib/ui/Badge.svelte, in a +page.ts and in one file per tsc config were
each reported by TypeScript 7 (the admin's by 6), every step exiting 1;
--listFilesOnly gives the same programs on 6 and 7; the four tsc checks take
0.5 s instead of 6.0 s. From a clean `npm ci --ignore-scripts` on Node
26.12.1: typecheck, the tests, build, verify-dist (web and tauri), cf:check
and knip (report unchanged) pass, with still exactly three packages that
have install scripts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Sixteen setup-python steps move from '3.12' to '3.15'. codeql.yml alone
stays on '3.14': CodeQL's supported-languages page lists Python up to 3.14
and its extractor runs on that interpreter; the pipeline uses no 3.15-only
syntax.
- The updater-json job of release-desktop.yml sets up 3.15 instead of
running the runner image's python3.
- Four text-mode writes name encoding="utf-8": the dead-link log, both
leaderboards and clear_temp(). 3.15 makes UTF-8 the default (PEP 686); on
Windows an older Python writes cp1252, which cannot encode the
leaderboards' emoji, so those scripts crashed there. CI already wrote
UTF-8, so no committed output changes.
- requirements.txt's compile line and sonar.python.version say 3.15.
`uv pip compile --universal` gives the same lock for 3.12 and 3.15, and
every pin installs on 3.15 with --require-hashes --only-binary :all:
(charset-normalizer's cp315 wheels were already hashed).
Checked on Python 3.15.1: the 299 tests pass with EncodingWarning and
DeprecationWarning as errors; edit_game.py --check and delete_game.py
--check pass; a full save_main(load_main()) on a copy of the data leaves all
36 files byte-identical to HEAD, as on 3.14, so no shard and no index.json
changes when the data jobs move.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
- scripts/updater_json.py takes no file path from the command line any more,
only the tag; it reads latest.json, assets.json and the .sig files from
the working directory and rewrites latest.json there
(pythonsecurity:S8707, path traversal from CLI arguments). The job runs it
inside its work directory. New test for main().
- release-desktop.yml asks for nothing at workflow level and gives each of
its two jobs the `contents: write` it needs (githubactions:S8233: with a
second job, a workflow-level write reached both by default).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
.sonarcloud.properties tells SonarCloud what is code, what is test code and
what to skip. Both start at the root and are split by patterns:
- tests: scripts/tests, every *.test.ts, and what only tests and the admin's
dev server use (lib/testing, worker/testing, admin/mock) - analysed with
the test rules, out of duplication and coverage;
- not analysed: the dataset and pipeline-written files (data/, games/,
*.jsonl), the D1 migrations (SQLite, which the PL/SQL analyser parsed as
Oracle), web/src/app.html (SvelteKit's template; its <title> arrives via
%sveltekit.head%), and what the Tauri CLI generated and nobody edits
(Android res/, buildSrc/, the icon set). The manifest, Gradle build files
and MainActivity.kt stay in.
Simulated on the tracked files: 219 code, 84 tests, 16 excluded, none
indexed twice. Takes effect once on main. Also an [Unreleased] CHANGELOG
entry for this and the updater-json job, and the rule in CLAUDE.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tauri-action v1 (Dependabot moved release-desktop.yml from v0 after 2.2.0)
writes each artefact's API URL (api.github.com/repos/<repo>/releases/
assets/<id>) into latest.json, and has no setting to change that. The
desktop updater feed accepts only this release's download URLs and answers
204 to anything else, so desktop-v2.2.1 was offered to no installed app
until its latest.json was fixed by hand.
A new `updater-json` job runs after every platform's build: it downloads
latest.json and the .sig files, rewrites each URL to
github.com/<repo>/releases/download/<tag>/<file> (scripts/updater_json.py,
which refuses a version that is not the tag's, an asset of another release,
any other URL shape, or a signature that is not its file's .sig), and
uploads it back. Run on 2.2.1's original file it produces exactly the
hand-fixed one, and a second run changes nothing. Also renames the v0
input includeUpdaterJson to v1's uploadUpdaterJson (same default).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The previous commit said SonarCloud's automatic analysis covers main only.
That was read from an empty pull-request list at a moment when no PR was
open; this PR got its own "SonarCloud Code Analysis" check (quality gate
passed, no new issues). DEPLOYMENT.md and the CHANGELOG entry now say that
CodeQL and SonarCloud both check pull requests and main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Repo public-facing version 4.3.2 -> 4.3.3; web app + desktop/Android
2.2.0 -> 2.2.1 (package.json and its lock, Cargo.toml and the f2p-tracker
entry of Cargo.lock, tauri.conf.json). The apps also pick up the Contact
page, the reworded anti-cheat paragraphs of the Disclaimer and the Terms
(consent gate shown once) and v4.3.2's anti-cheat grouping.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- CLAUDE.md: the parser worker's origin check and why `e.origin &&` must
stay; CI installs only what is pinned (action SHAs, --ignore-scripts, no
npx, hashed Python requirements and how to add a package); the Android
app's Auto Backup opt-out and why the policy is not the thing to change.
- docs/DEPLOYMENT.md: what web-ci and python-tests run now; CodeQL analyses
pull requests, SonarCloud only main.
- docs/dev_env.md (and docs/i18n/vi): run the pipeline from the repo root
with the hashed installs - `cd scripts` left data/ out of reach.
- docs/THIRD_PARTY.md: requirements-dev.txt goes in a pip call of its own.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The manifest never set android:allowBackup, so it defaulted to true and
Android copied the WebView's storage (consent, settings, the cached
catalogue) into the user's Google account backup, while the Privacy Policy
says none of it leaves the device (SonarCloud xml:S6358). The app now says
allowBackup="false"; the policy stays as it is. No library manifest of the
build (tauri, its plugins, AndroidX) declares the attribute, so the manifest
merge has nothing to reconcile.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Regexes that backtracked quadratically (typescript:S8786) are linear:
chart colour tokens (trimmed, no \s* at the ends), the review percentage
(up to three digits, from the start of a run) and label ([^()]+), the
legal pages' title, the admin router's trailing slashes and the image
route's capsule path (both without a regex), base64url padding
(replaceAll; "=" is only ever trailing) and the admin mock. Checked
against the old forms on random input: the percentage and the colours
agree everywhere, the label and the title only differ on nested
parentheses and blank "#" lines, which no summary or document has.
New utils.test.ts pins the review parsing.
- Bare .sort() on strings (typescript:S2871) becomes .sort(byCodeUnit), a
new shared/sort.ts that states the code-unit order those lists always had.
Not localeCompare: the admin build id hashes this order. The sitemap is
byte-identical.
- Number.parseInt / Number.parseFloat / Number.NaN (typescript:S7773).
- admin.css puts its @imports before @source (css:S8778); the emitted
stylesheet is byte-identical.
- The raw U+FEFF inside removal.ts's split regex is written as an escape.
- normalizeLink, exported and called from nowhere, is removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Linear parsers (python:S8786): the store page's "unsupported" language
rows and its tags, and the discovery sweep's search rows, no longer use
regexes that backtrack quadratically on long input. New tests, written
against the old regexes first, pin what they read, and a differential
fuzz (200,000 random inputs) found no case where old and new disagree.
- Raw invisible and bidi characters in normalize.py and two test files are
written as escapes (text:S6389); every string value is unchanged.
- scrape_store_fields() states when there is no usable page (scraped = None)
instead of deriving it into a separate flag (pythonbugs:S2259).
- cmd_list() in delete_game.py and edit_game.py returns nothing; the
dispatch returns 0 (python:S3516). remove_games.main() keeps its int:
delete_game.py and its tests use the exit code.
- The Steam client mounts its retrying adapter for https only
(python:S5332); nothing is fetched over http.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SonarCloud's GitHub Actions and shell findings, all supply-chain hardening
for jobs that hold a write token (and, in the release workflows, the
signing keys):
- The six third-party actions in release-desktop.yml and release-android.yml
are pinned to the commit their major tag points at today, with the version
in a comment for Dependabot. dtolnay/rust-toolchain is pinned to a master
commit and given `toolchain: stable`: its `stable` branch is regenerated
on top of master, so a commit of it can vanish.
- Every `npm ci` is `npm ci --ignore-scripts`. Only fsevents, workerd and
wrangler's esbuild have install scripts; the last two find their binary in
their optional platform package without them, and fsevents is only file
watching. `npx` is gone from the workflows (`npm run cf:check`,
`npm test -- <file>`).
- requirements.txt pins every runtime package, transitive ones included
(certifi, charset-normalizer, idna), with the sha256 of every file on
PyPI; every install is `--require-hashes --only-binary :all:`. The new
requirements-test.txt holds pytest the same way. python-tests.yml runs the
data jobs' exact install line first, so a Dependabot bump is proven before
a data job meets it.
- `[[ ]]` instead of `[ ]` in the bash wrappers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The catalogue's parser worker is a dedicated module worker: only the page
that created it can post to it, over its implicit port, and those messages
carry origin "". It now refuses any non-empty origin that is not its own,
replying with an error so a pending decode fails instead of hanging. This is
the check CodeQL's js/missing-origin-check looks for; the earlier dismissal
(#3) came back as #20 when the handler moved three lines.
`e.origin &&` is load-bearing (the owner's "" never equals
self.location.origin), and a test without `location` holds it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
After v4.3.1 read every game's anti-cheat from Steam, 68 of the 159 named
ones fell in the charts' "Other" slice. Add the families Steam's
disclosures use most - ACE, Anti-Cheat Toolkit, CrackProof, HoYoKProtect,
NGS (Nexon Game Security), EA Javelin, SARD - to ANTI_CHEAT_PATTERNS and its
web mirror (+ ANTI_CHEAT_ENUM). "Other" drops to 35, all one-off names.
Both sides now match a key or a pattern only as whole words (_has_term /
hasTerm): "ace" is inside "faceit ac", "space" and "interface", and the
web's substring check also filed "vacuum" under VAC. No stored value moves
between existing families (checked over all 56 distinct values).
A stored label is never rewritten: the old raw name and the new key are the
same family. refresh_anticheat.py --dry-run against Steam: 0 games changed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- DISCLAIMER section 5 and ToS item 5: anti-cheat is read from the
anti-cheat disclosure on the Steam store page, which the developer fills
in; an undeclared one shows "-", and a declaration can be wrong. Both are
consent documents: the web gate shows these two diffs once.
- README, CONTRIBUTING, Contact (shown at /legal/contact, not
consent-gated): no more extension; a missing game or a correction goes in
Discussions > Ideas; the manual fork path queues store links only.
- CLAUDE.md: the anti-cheat sweep and its rules, the trio as the one manual
set a writer replaces (an override still wins), OverrideGuard, links-only
queue, clean_notes, the pattern mirror; 15 data writers.
- ADMIN, dev_env (+vi), web/README: the extension is no longer a producer.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
None of the 4,704 games added since September had an anti-cheat. The only
code that read the anti-cheat a developer declares on Steam was the browser
extension (archived; last push 2026-06-25); the pipeline matched appdetails'
categories, which only ever say "Valve Anti-Cheat enabled".
- core/anticheat.py (new, pure): the store page's div.anticheat_section
(its HEADING decides kernel, never the class; a Boot Protection row is a
flag) and GetItems' extra_details.anticheat; labels from
ANTI_CHEAT_PATTERNS, else Steam's name cut at 40 characters; same_family()
("EAC" = "Easy Anti-Cheat", "ACE" = "Anti-Cheat Expert (ACE)"); and
apply_anti_cheat(), the one rule.
- fetch_full() fills, never replaces, from the page it already fetches (or
GetItems for a gated page), else the VAC category, now found in any
position (with a stored "" only the first category was checked).
- refresh_anticheat.py (new): GetItems for every game (~160 requests), a
store page only for a disclosure without a name. Steam wins; an override
wins over Steam and is not fought (OverrideGuard); no disclosure never
clears; a failed batch is unknown. Runs at the end of the daily Refresh
Store Data job with its own commit; only=anticheat runs it alone. That job
now checks out main.
- The queue takes links only: merge_extension_data(), EXTENSION_FIELDS,
ARRAY_FIELDS and the schema.ts mirrors go. translate_notes() becomes
clean_notes(): the extension's leading "Has paid DLC" and "[hover-add]"
are dropped (517 notes, once, never news).
- refetch_all.py keeps "-" instead of resetting it to ""; a retired override
whose was equals its value no longer bumps last_updated on every save.
- "denuvo" joins Denuvo AC on both sides; anti-cheat.test.ts holds the TS
patterns and enum to constants.py.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 500 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 300 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 300 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 300 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: test
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 300 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 300 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 300 a day), enabled by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 300 a day), enabled by admin.
Reason: run by hand from /admin/automation
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 300 a day), enabled by admin.
Reason: run by hand from /admin/automation
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved automatically by the /admin schedule (at most 300 a day), enabled by admin.
Reason: run by hand from /admin/automation
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
The commit step's plain `run:` scalar contained "chore(data): mark dead
games", and a colon followed by a space inside a plain scalar is a
mapping indicator: "mapping values are not allowed here" (line 61). GitHub
answered every push of this branch with a failed run named after the file,
and on main the scheduled job would have stopped running. A block scalar
carries the command as text.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dependabot alert #69: rustls before 0.23.45 accepted TLS 1.3 handshake
messages across encryption-level boundaries. Lockfile only - rustls
0.23.40 -> 0.23.45, rustls-webpki 0.103.13 -> 0.103.15 - and only the
desktop updater's reqwest uses it. cargo test --lib --locked passes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CodeQL (js/stack-trace-exposure) followed a caught exception through
String(err) into the /admin/api/pipeline 502 and auto-approve's "failed"
detail, which /admin/api/automation/run returns. lib/http.ts errorText()
gives an Error's message and only describes anything else that was thrown.
The admin-api test walked worker/ with statSync before readFileSync
(js/file-system-race); it reads the directory entries' types instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Auto-approve for the review queue (off by default, at most 500 a day),
removing games through data/blocklist.jsonl with Restore, and the
Overview, Pipeline and Data quality admin pages. Apps stay at 2.2.0; no D1
migration; the GitHub App's permissions are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CLAUDE.md:
- data/blocklist.jsonl as a data invariant: applied first in save_main(),
logged once, the 500 guard, never named data_*, whole-line writers, the
shared golden fixture, Restore as the only way back.
- The pipeline rules for ingest (blocked links skipped, non-games refused,
ingest-new.yml as the removal job on ref main), auto-approve's gates, and
Remove/Restore's D1 semantics and WRITABLE paths.
- "Publication stays a human decision" now says who decides: a reviewer, or
the capped auto-approve rule a reviewer turned on.
- Admin routes: the Overview at /admin, the queue at /admin/queue, and no
/admin/api route answering 401/403 for anything but Access.
- save_main() has 14 callers, not 11 (here and in core/overrides.py).
docs/ADMIN.md: the App's Contents permission covers temp_info, overrides
and the blocklist (never a shard); why Actions read is not needed; the
discovery token's reach with auto-approve on; sections 11-13 for
auto-approve, removing/restoring and the Overview/Pipeline/Quality pages;
the mock's mock_pipeline switch.
README.md: the admin's description, the new scripts and the ingest
workflow's triggers.
Also: the delete_game.py help example kept its line break, and the mock's
removed rows carry the reason's label as the Worker writes it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The admin grows from five pages to ten. /admin is now the Overview - queue
counts and the backlog by source, auto-approve's day, removed games waiting
for the pipeline, running data jobs, data-quality counts - each card loaded
on its own. The review queue moves to /admin/queue; an old /admin?status=...
link is rewritten there on load (legacyQueuePath), so bookmarks keep working.
- Automation: the switch and limits (validated by the same shared rules the
Worker uses), today's budget, the last run and why it did or did not
approve, the next batch, history, and Run one batch now.
- Remove: search the catalogue or paste up to 100 appids/links, pick a
reason, see that it is public, confirm; the Removed tab lists the blocklist
with what is still waiting for the pipeline, and Restore. Edit links here.
- Quality: every check's count, grouped by who fixes it, and each check's
games with an Edit link.
- Pipeline: the latest runs per data workflow, what is running or waiting
in data-write, and what is queued in Git.
- The queue dialog says a removed game comes back through Restore; Reopen's
refusal says the same. Jobs and Audit filter on the shared JOB_KINDS and
AUDIT_ACTIONS.
- Nav labels show from xl; below that, icons with a title. Links and table
wrappers are positioned, so an sr-only label scrolled out of view no longer
widens the page at 375 px.
- The pipeline endpoint lists each run once: the page keys on run URLs, and
a duplicate key throws in a keyed {#each}.
- The mock dev server serves the new pages: fake Actions runs
(mock_pipeline=busy cookie), auto-approve state, two removed games.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- GET /admin/api/pipeline: the latest runs of every data workflow
(shared/pipeline.ts, keyed by file), what is running or waiting in
data-write, and how many lines wait in scripts/temp_info.jsonl and the
blocklist. A weekly job that fell out of the last 100 runs is asked for by
file. GitHub trouble is a 502 with a JSON body - never 401/403, which the
admin page reads as an expired Access session.
- GET /admin/api/quality: counts of every shared/quality.ts check over the
published catalogue, or one check's games, paged - computed once per
dataset generation by readCatalogue().
- Response types for the new endpoints in shared/admin-api.ts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Off by default. When enabled in /admin (or run once by hand), the 15-minute
cron approves one batch after reconcile - through the same approveRows()
path as a reviewer, so it is still only a request: ingest_new.py checks every
game, and reconcile records the outcome.
Settings (admin_state, validated by shared/automation.ts on both sides):
batch size <= 100, daily limit <= 500 (a ceiling in code, re-applied on
every run), allowed sources ("backfill:*" is a prefix), minimum age, order.
A batch is committed only when every gate says yes, and a gate that cannot
be checked says no:
- the lease (one run at a time; no lease table, no run);
- the UTC day's budget, reserved with bumpCounter before the commit and
returned when it fails (kept when the commit landed);
- scripts/temp_info.jsonl on main is EMPTY - the previous batch has been
ingested - checked again inside the commit (requireEmptyQueue). Not "no
row is approved", which a network-skipped row would hold for 12 hours;
- no data-write workflow is running or waiting: that group keeps ONE pending
run, and the ingest a batch starts would evict a job waiting its turn
(lib/github-runs.ts, the App token, shared/pipeline.ts held to the YAML);
- only pending, free, app_type game, health ok rows, old enough, from an
allowed source, never decided, their game not committed or blocklisted.
The commit says it is automatic and names its limit, never a person; D1
records actor auto-approve (or the person who pressed Run). The last
outcome is kept for the page, and a failure is audited once per cause, not
every tick. The daily prune drops counters older than a month.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/admin/api/remove takes up to 100 published games, a reason and an optional
public note, and commits their lines to data/blocklist.jsonl - one commit,
re-merged with the file as it is on every retry. The push starts the ingest
workflow, whose first step takes them out of data/ (scripts/remove_games.py).
The review queue is made to agree with Git: each game's decision becomes
rejected 'removed:<code>' even over an approved one (unpublishing is a new
fact), and every row for it that is not already rejected is rejected. Its old
committed row therefore no longer makes publishedSql() call it published, so
a restored game whose ingest fails can be approved again instead of sitting
locked forever. Removing an already-removed game commits nothing and re-applies
the D1 side: the repair for a desynced removal.
/admin/api/restore takes one game back, in ONE commit: its blocklist line goes
and its store link is appended to scripts/temp_info.jsonl, so the next ingest
cannot find it still blocked and fetches it fresh. Only a 'removed:' decision
is deleted, and an approved row (source "restore") is left for reconcile to
promote. Reopen refuses a removed game and says to Restore it instead.
Remove and Restore share a D1 lease, so they cannot interleave for one game.
GET catalogue searches published games (or previews a list of appids) and GET
removed lists the blocklist with what is still waiting for the pipeline.
lib/commit-job.ts is the job-then-commit sequence routes/edit.ts had inline,
now shared with removals.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No behaviour change for the existing routes; this is what the removal and
auto-approve features stand on.
- shared/removal.ts: the blocklist line format (key order, compact JSON,
U+2028/U+2029 escaped), reasons, parse/append/remove-one-line helpers.
Held byte-equal to Python by scripts/tests/fixtures/blocklist_golden.jsonl,
and REMOVAL_REASONS to blocklist.py's REASONS.
- shared/quality.ts: the data-quality checks, with safeClass() held equal to
the public app's.
- lib/git-commit.ts: data/blocklist.jsonl joins WRITABLE (shards and
index.json stay out); a blob GitHub returns truncated is never rewritten;
appendLinks() takes {reason, auto, requireEmptyQueue} - an auto batch says
so in its commit, and requireEmptyQueue refuses to commit while the queue
file still holds a batch, checked at the same head the commit uses;
readRepoFiles() reads several files fresh from main.
- lib/records.ts readCatalogue(): the published games as a projection with
their quality issues, each shard checked against index.json's sha256 and
re-read past the edge cache when stale; only verified reads are memoized.
- lib/approve.ts approveRows(): the approve path routes/admin.ts had inline,
so a reviewer and the schedule go through the same job/commit/batch/audit
order. lib/queue-sql.ts holds the SQL both need; lib/hash.ts the sha256.
- shared/admin-api.ts JOB_KINDS / AUDIT_ACTIONS, checked against worker/.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Discovery only proposes appdetails type "game", but the ingest queue is also
fed by the browser extension and, once auto-approve is on, by candidates no
one looked at - a leaked discovery token could post a free DLC, demo or tool
claiming to be a game. ingest_new.py now checks the type Steam itself
returned in the health check it already makes, and logs a refusal as
status_code "not_a_game". A missing type (the store-page fallback) is not
held against the game.
Only in ingest: health_checker is shared with Purge, which would otherwise
start deleting existing records every week.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A game the maintainer removes is now a standing instruction in Git, like an
override, instead of a one-time deletion that the browser extension or the
next ingest could undo.
- core/blocklist.py reads data/blocklist.jsonl (one line per game, written by
/admin and by delete_game.py). save_main() applies it FIRST on every write,
for all 14 callers, without touching the caller's list, and whatever
apply_human_overrides says.
- A dropped game is logged once in scripts/removed_games.jsonl as
status_code "admin_removed", built from the blocklist line alone with
removed_at = blocked_at, so writing it again changes no byte. A later purge
line for the same game keeps winning, as dedup_removed() decides.
- More than 500 drops in one save raises BlocklistError before anything is
written: a damaged file fails the job instead of emptying the catalogue.
- remove_games.py applies the blocklist now and heals a missing log line.
bash/ingest.sh runs it before ingest_new.py, and ingest-new.yml also
triggers on blocklist pushes and checks out the tip of main. One workflow
on purpose: data-write keeps one pending run, so a second workflow and the
ingest would keep evicting each other.
- ingest_new.py skips blocked links before any Steam request, and a link
that is not text ({"link": 730}) no longer crashes the run (and every
three-hourly retry after it).
- Discovery counts blocked appids as known.
- delete_game.py is a non-interactive CLI writing the same bytes as /admin
(golden fixture), with --list and --check; check-overrides.yml runs --check.
- mark-dead-games.yml commits through bash/commit_push.sh, like every other
data job: it rebases and retries, and commits the log with the shards.
- dependabot.yml ignores Svelte-era framework majors and @types/node majors
instead of the React-era names.
With an empty blocklist every path is a no-op.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved in /admin by admin.
Reason: Passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: Passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Pipeline only: nothing under web/ changed, so there is no new web, desktop
or Android build and no app version bump. The catalogue picks the fixes up
from the next data job.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An 'Adult Only' game's store page sends an anonymous client to /agecheck/
and on to a Sign In page that no age cookie opens (measured 2026-10-10).
The scraper read that page as the game's own: no language table, no tags,
no DLC section. 25 games sat with empty tags and languages (about 16 adult
games, plus Warframe, PUBG, Rainbow Six Siege and other M-rated games that
were gated on the US runners), and every one was written has_paid_dlc=false.
- steam_client: classify where a store-page request ENDED (the whole
redirect chain), send age cookies with store-page requests only, ask
appdetails and the page for l=english, add GetItems and GetTagList
(keyless).
- store_items: a pure parser for GetItems items in scrape_store_page()'s
shape (ELanguage tables derived from Steam's own data), plus DLC prices.
- fetcher.scrape_store_fields(): the page first, the JSON API when the page
is gated or redirected, has_paid_dlc from the DLC's prices; None never
overwrites a stored flag.
- refresh_store_data: a game with empty store fields is refreshed every
day, first, capped at 150; --missing-only; values compared as stored.
- scraper: unescape tag and language names ("Point & Click"), name the
"#lang_slovakian" token.
- normalize, run by save_main() before overrides (idempotent, never bumps
last_updated): release_date as "Aug 21, 2012" from any shape Steam
writes; invisible characters and stray whitespace out of names and
blurbs; HTML entities decoded in tags and descriptions; the extension's
"Có DLC trả phí" notes as "Has paid DLC" (overrides translated too, so
they cannot flip-flop).
Dry run on the 25 against Steam: 24 filled, 7 has_paid_dlc corrected
(396420 has no languages on Steam itself). The dataset normalised in
memory: 1,360 dates, 482 notes, 781 entity and 56 text records change, a
second pass changes nothing, and no last_updated moves.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved in /admin by admin.
Reason: passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: passed
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Web app and desktop/Android 2.1.1 -> 2.2.0 (package.json + lock, Cargo.toml
+ the f2p-tracker entry in Cargo.lock, tauri.conf.json, from which the
Android versionCode derives); repo public-facing version 4.1.1 -> 4.2.0.
CHANGELOG's Unreleased section is dated and named, and a fresh empty one
opened above it.
What 2.2.0 brings to the apps: the all-time peak row and column (#167),
the offline catalogue kept as opaque packs (#169), and the dependency
security updates (#168). The Disclaimer's new player-source paragraph
makes the apps show the consent gate once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
IndexedDB held the catalogue as ~5,568 parsed records (~9.5 MB of
structured-clone objects, readable in DevTools) while fetcher.ts threw
away the pack it had just downloaded. Now the cache stores those packs:
seven Uint8Arrays, ~1.4 MB, opaque. Obfuscation and compression like
the wire packs - the key is public - never protection.
- cache.ts: new database `f2p-catalogue`, the SAME two keys the Privacy
Policy lists (so no policy edit, no consent gate): `f2p:index` (the
DataIndex, readable public metadata) and `f2p:records` (one pack per
index entry). A generation is stored only when every shard arrived
packed - the browser never packs - and every pack's IV must be its
entry's sha256 prefix, or the cache is a miss. Both keys go in one
setMany, records first; the old code's two set() calls could leave a
new index next to old records.
- The copy app <= 2.1.x left in idb-keyval's default `keyval-store` is
read like any verified generation until the next one is written,
which delMany's it. A new database is what keeps a tab still running
old code from reading Uint8Arrays as records; indexedDB.databases() is
checked first so nobody gets an empty legacy database.
- games-loader.ts: readCache() hands back the index at once and the
records lazily, so an older cached generation is never decoded just
to compare it; fetchShard returns { plain, pack } and writeCache gets
the packs. The verify-then-cache contract is unchanged.
- The parser worker opens packs (decodeShard), so a cache hit costs the
main thread ~6 ms at most instead of a ~20 ms block (desktop,
measured), for ~45 ms more until the data is ready.
- Found in the browser: Chromium's failed AES-GCM decrypt is a
DOMException with an EMPTY message, and worker-pool's `if (error)`
read "" as success - a damaged pack resolved as a shard with no
records. The worker now always names the error and the pool rejects
on any string; both have tests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
19 Dependabot alerts (6 high) plus what npm audit adds; npm audit and
pip-audit now report none.
- devalue 5.9.2 -> 5.9.4, brace-expansion 2.1.4 -> 2.1.7 and
5.0.9 -> 5.0.12, fast-uri 3.1.7 -> 3.1.8, serialize-javascript
7.1.1 -> 7.1.2: lockfile only, every parent's range already allowed
the fix. devalue's parser ships in the page and the apps; the rest is
build tooling.
- wrangler 4.130.0 -> 4.147.0: miniflare pins undici exactly, and only
wrangler >= 4.144 brings 7.29.1. Dev and deploy tooling only.
- cookie 0.6.0 -> 0.7.2 under @sveltejs/kit via an override. Kit 2.70.3
is the newest 2.x and still asks for ^0.6.0; it imports only
parse/serialize, which 0.7 keeps, and under adapter-static that code
runs only at prerender and in vite dev. npm refuses a range key for a
direct dependency (EOVERRIDE), hence the exact version; CLAUDE.md says
what to do when kit moves. This also ends the Dependabot security
job that failed on every push to main.
- The sharp 0.35.4 override is dropped: miniflare now pins 0.35.4
itself, and an exact override would force a downgrade the day it
pins a newer one.
- urllib3 2.7.0 -> 2.8.0 for the data pipeline (requests 2.34.2 allows
it).
Verified: npm ci, typecheck, 448 tests, web build + verify-dist, Tauri
flavour build + verify-dist, wrangler deploy --dry-run, vite dev with a
Cookie header, 55 Python tests on urllib3 2.8.0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A game's page gets an "All-time peak" row, and the games table a sortable
column ("N/A" sorts to one end, as unrated reviews do); the CSV export
carries the field. The record type mirrors the pipeline's new field.
- The "(peak N)" beside a game's player count is gone. It showed peak_today,
which is the highest of our own occasional samples since the last refetch -
neither a daily peak nor an all-time one - and read like both. Its i18n key
goes with it.
- The Disclaimer's section on player counts names Steam Charts as the source
and says what the number is not: Steam Charts samples periodically, and
for games it does not track the figure is only what this project has seen.
A consent document, so returning visitors see the gate once, showing that
paragraph. The Acknowledgements credit Steam Charts (not a consent
document).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The dataset only knew how many people play a game now. The only peak it had,
peak_today, is not today's: nothing resets it, so it is the highest of our
sparse samples (online games 3x a week, the rest twice a month) since the
last refetch - The First Descendant reads 8,052 against a real all-time peak
of 264,860.
all_time_peak is the most players a game has had at once, and it only ever
goes up (core/peaks.py):
- refresh_peaks.py reads SteamCharts' recorded all-time peak, the only public
source older than our sampling (SteamDB forbids scraping; Valve's APIs only
know today). It takes a crc32 thirtieth of the catalogue a day, so each game
is asked once a month, ~186 pages 2-3 s apart. SteamCharts has no API, no
terms and no robots.txt, so it is read politely (core/steamcharts.py): a
User-Agent that names the project, 500/404 read as "not tracked", and a
403, 429 or Cloudflare challenge stops the run with a warning, keeping
everything raised so far. Measured: 9 of 10 games with a few dozen players
or more are tracked; most of the 0-3 player long tail is not.
- Every run also raises the field from our own samples (peak_today,
current_players) without a request, and apply_players() raises it on every
sample - never from a 0. That seeds 2,329 games on the first run.
- Nothing else is written, last_updated included (player counts never moved
it), and refetch_all.py does not clear the field: it cannot be fetched again.
"Refresh All-Time Peaks" runs daily at 19:30 UTC, between Refresh Store Data
and the snapshot, in the data-write group, committing through
commit_push.sh; a manual run with "backfill" asks about every game (~4 h).
The crc32 rotation moves to core/rotation.py, shared with
refresh_store_data.py. test_refresh_peaks.py holds the rules.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Web app and desktop/Android 2.1.0 -> 2.1.1 (package.json + lock, Cargo.toml
+ the f2p-tracker entry in Cargo.lock, tauri.conf.json, from which the
Android versionCode derives); repo public-facing version 4.1.0 -> 4.1.1.
CHANGELOG's Unreleased section is dated and named, and a fresh empty one
opened above it.
What 2.1.1 brings to the apps: the phone-width layout fixes, the Android
status- and navigation-bar insets, and the Privacy Policy's image-host line
(so the apps show the consent gate once).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The Anti-Cheat, Delisted timeline and Catalogue growth legends wrapped to a
second line on a phone and landed on the axis labels or the plot. They are
scroll legends now: one line, paged when it does not fit, unchanged on a
desktop where it does.
- Value-axis labels printed over each other where the plot is narrow (Top
Online/Offline leave it about 80px beside the game names). hideOverlap on
the horizontal value axes of those, Anti-Cheat, DRM and the dashboard
genres drops the ones that collide.
- The tag cloud skipped any word too big for its box, and words are placed
largest first, so on a phone the most common tags were the ones missing.
shrinkToFit sizes them down instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
targetSdk 36 and MainActivity's enableEdgeToEdge() draw the webview under
both system bars. The React 1.x shell padded all four safe-area insets; the
SvelteKit rewrite kept only <main>'s bottom one, so the top bar of every 2.x
app has sat under the clock, which docs/android-support.md says cannot happen.
- styles/theme.css gains pt-safe, pb-safe, pl-safe, pr-safe and p-safe-or-4
(env(safe-area-inset-*), named after the tailwindcss-safe-area classes).
The shell root carries pt-safe pl-safe pr-safe, <main> pb-safe, the drawer
pt-safe pb-safe pl-safe, and /welcome and the /error pages, which have no
shell, pad themselves.
- The consent gate and the human check use p-safe-or-4 and centre their card
with m-auto instead of items-center: on a short phone a card taller than
the screen lost its top, unreachable (measured at 360x520: the 620px
consent card now scrolls from its top edge).
- Back-to-top and the toasts add the bottom inset; the never-expiring Android
update toast sat on the gesture bar.
- The status-bar icons follow the SYSTEM theme (enableEdgeToEdge() uses
SystemBarStyle.auto), but the app defaults to dark, so a phone in light
mode showed dark icons on a dark page. In the Android app the layout now
puts a status-bar-strip behind them, keyed on prefers-color-scheme and
never on the reader's theme. Its two colours are theme.css's --background
tokens; mobile-layout.test.ts compares them and holds the shell padding.
env() reports these insets only from Android System WebView 136; an older
WebView reads 0 and keeps today's look. The Android docs now say so, and the
themes.xml comments, which still pointed at the React Layout and claimed
light icons, describe what enableEdgeToEdge() actually does.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On a 360px phone (the Android app and mobile browsers) cards ran off the
right edge of Dashboard, Publishers and Developers, and game names vanished
from the Top Online/Offline and studio lists.
- 22 layout grids declared columns only from sm/lg up. Below that a grid has
one implicit auto track sized to its widest item's min-content, and a
truncate name counts at full length there, because the grid item keeps
min-width:auto. Measured at 360px: the dashboard scrolled sideways by
124px, Publishers by 46px with all 300 counts off screen. Every one now
starts at grid-cols-1, which is repeat(1, minmax(0, 1fr)).
- Top Online/Offline and the studio pages hide the genre badge below sm, and
the studio pages the score as Top Online already did: a Badge cannot
shrink below its longest word, and names were squeezed to 0-28px.
- Page titles and a game's name, description and notes wrap long words: some
studio names are raw URLs.
- The header search reserved pr-16 for the Ctrl K chip, which is hidden on
phones, and cut the placeholder to "Search by na".
- /games cards are fixed 96px rows; a long anti-cheat badge wrapped to a
third line and painted over the next card. The card now clips and the
badge truncates.
src/lib/mobile-layout.test.ts fails on a layout grid without a base
grid-cols-N; CLAUDE.md has the rule.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
"Everything the site loads is fetched same-origin" stops being literally true
once the web app loads art from media.free-steam-games.win. The substance does
not change - it is the site's own subdomain, served by Cloudflare like the rest,
and Valve still never sees a visitor's IP - but the policy says precisely what
the browser contacts, so it says this too.
Returning visitors see the consent gate once, showing this one paragraph.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A Worker always runs BEFORE Cloudflare's cache, so no `s-maxage` on /img/*
could ever spare an invocation: every thumbnail and hero view ran the Worker,
and every view the edge cache had not seen read R2. An R2 custom domain is
cached like any origin. On the web, thumbnails and the detail hero now load
from https://media.free-steam-games.win/img/v2/<w>q<q>/<path>@<t>.avif - the
exact key the cron mints - and a repeat view costs neither a Worker run nor an
R2 read.
- shared/img-keys.ts is now the one definition of the key scheme, shared by
the cron, the /img route and the page (it moved out of worker/lib/img-store.ts).
- Every such <img> carries {@attach imgFallback(...)} with the /img URL. A key
that is not minted yet is a 404 on the media host and a browser without AVIF
cannot decode it; both fire `error`, and /img serves Steam's JPEG. A load
that failed before hydration is recognised by complete && naturalWidth === 0.
images.test.ts fails on an image without the fallback, or one built from a
different value.
- An attachment, not an action: on a prerendered <img>, `use:` makes Svelte
write onload/onerror="this.__e=event", which the hash CSP refuses - one CSP
violation per game page. verify-dist.mjs now fails on it anywhere.
- The web CSP lists the media host in img-src; the Tauri one does not, and the
packaged apps keep using /img/* for everything. verify-dist checks both ways.
- The service worker's /img/ rule matched the media host too (same path
prefix). Its responses are opaque no-cors loads the rule can never cache, so
it is same-origin only now; the objects' year of immutable Cache-Control is
what keeps them.
- /img remembers an R2 miss per data centre for one cron tick (15 min), so the
fallbacks and the apps stop paying an R2 read for art the backfill has not
reached.
Measured with the domain not yet connected (so every media load fails): the
hero and all 100 thumbnails on /top-online fell back to /img and rendered,
including lazy images below the fold; none broke.
Merge only once media.free-steam-games.win serves a minted AVIF -
docs/SECURITY_SETUP.md section 5 has the setup and the check.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The previous commit said documentation AND data commits no longer deploy.
Documentation commits do not; data commits still did: 3f9e8cff ("Refresh store
data [2026-10-02]", four files under data/) carries a Workers Builds check
with a new Version ID, 712b4ab8, at 16:54Z. DEPLOYMENT.md and CLAUDE.md now
state the rule rather than claim it is in force, keep the configuration that
stops both, and say how to verify it: the next bot data commit must have no
Workers Builds check.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- DEPLOYMENT: documentation and data commits no longer deploy (watch paths,
2026-10-02) - except that the legal documents are build inputs
(build/legal-versions.ts, lib/server/markdown.ts), so a commit that
changes only them must still trigger a build, or the consent gate keeps
the old text and hash. Gives a watch-path configuration that does both
(excludes are applied before includes) and how to check it.
- CLAUDE.md: the same, plus how static/_headers caches by path and why
pages, sw.js and version.json must keep revalidating.
- CHANGELOG [Unreleased]: the static cache rules (PR #160) and the above.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Measured on production: only /_app/immutable/* had a lifetime; everything
else in static/ went out as max-age=0, must-revalidate, so every page load
re-asked for the icons, favicon, og.png and manifest, and for
workbox-<hash>.js, whose name already changes with its content.
- /workbox-*: a year, immutable (hashed like /_app/immutable/*).
- icons, favicon, apple-touch-icon, og.png, manifest.webmanifest: fresh for
a day, then served from cache while revalidating in the background for up
to a week. They keep their names, so they are not immutable.
- robots.txt, sitemap.xml: an hour.
- HTML, /sw.js and /_app/version.json keep the platform default on purpose:
a deploy, a changed legal document and a new service worker must be
visible on the next load.
Also documents an accepted wart: a missing asset path gets the SPA fallback
(index.html) with the path's immutable header. It only reaches a tab left
open across a deploy, which hooks.client.ts reloads once.
src/lib/cache-headers.test.ts parses _headers and pins all of it, including
that no path gets two Cache-Control rules. Verified with wrangler dev: every
path answers exactly the intended value.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Web app and desktop/Android 2.0.2 -> 2.1.0 (package.json + lock, Cargo.toml
+ the f2p-tracker entry in Cargo.lock, tauri.conf.json, from which the
Android versionCode derives); repo public-facing version 4.0.2 -> 4.1.0.
CHANGELOG's Unreleased section is dated and named, and a fresh empty one
opened above it.
What 2.1.0 brings to the apps: the packed catalogue (/api/data/p1), AVIF
thumbnails and heroes, and the scrollbar setting.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- CHANGELOG [Unreleased]: AVIF art minted into R2, the packed catalogue,
themed and hideable scrollbars, the prerender 404 noise, uncompressed
shards, the Tailwind scrollbar-thin collision, the thumbnail probe, the
data-commit redeploy, and the /cdn-cgi/image billing hole.
- SECURITY_SETUP §5: zone Transformations are OFF (every /cdn-cgi/image/
request answers 404) and the cron kept minting with them off, so the
Images binding does not need them.
- DEPLOYMENT: shard compression depends on the `ndjson-shards` Compression
Rule, a dashboard setting; packed files are deliberately not .jsonl.
- CLAUDE.md: the scrollbar rules (scrollbar-slim, never Tailwind's core
scrollbar-thin; panel/page markers; the stored key), and Transformations
must stay off.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Scrollbars now take the site's warm palette in both themes: a neutral thumb
that warms towards the brand amber on hover and turns amber while dragged,
on a transparent track. Firefox gets the standard scrollbar-color; WebKit
and Chromium get the ::-webkit-scrollbar pseudo-elements.
Why the tables never looked themed: Tailwind 4.3 ships a core
`scrollbar-thin` utility (scrollbar-width: thin), and our own utility of the
same name merged with it. In Chromium 121+ any standard scrollbar property
switches ::-webkit-scrollbar off for that element, so every panel showed the
OS's grey bar. The utility is now `scrollbar-slim`: the standard property only
for browsers without the WebKit pseudo-element, a 6 px themed bar elsewhere.
A test fails on any `scrollbar-thin` in markup (web and admin).
Settings → Scrollbars offers Visible (default) / Hidden in tables and panels
/ Hidden everywhere, stored as `f2p:scrollbars` (only once changed) and
applied as <html data-scrollbars>. Scroll containers opt in with
.scrollbar-panel (games table, card list, sidebar, command palette, the
anti-cheat table) or .scrollbar-page (the main content area); a test fails on
a themed container that opts into neither. Dialogs and the legal documents
keep their bars so a reader can see there is more. Hidden never means
unscrollable.
docs/PRIVACY_POLICY.md lists the new key, so returning visitors see the
consent gate once, showing that one line.
Verified in the dev server: table bars 6 px and themed in dark and light;
"panels" hides them (0 px) while the table still scrolls; "all" also hides
the main area; the choice survives a reload.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With zone Transformations enabled, the zone itself is always an allowed
source and Sources cannot exclude it. /img/* proxies any Steam appid, so
/cdn-cgi/image/<any options>/img/d2/<appid>/header.jpg let anyone bill a new
transformation per option set, outside IMG_TRANSFORM_MONTHLY_CAP. Measured
in production: width=77 on app 440 answered 200 (cf-resized: internal=ok),
and wrangler tail showed the resizer fetching the source with
`Via: 1.1 image-resizing-proxy` and the caller's own User-Agent.
handleImg now answers 403 to any request whose Via names image-resizing.
The site never transforms by URL: only the cron does, through the Images
binding, from Steam directly, so nothing legitimate is refused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first production batch (10 most-played games, 2026-10-02 09:30Z) came
back at the expected sizes - median 40.0 KB JPEG -> 10.9 KB `d`, 3.4 KB `s` -
but Cloudflare's quality scale runs well below libavif's: `d` at q60 scored
SSIM 0.960 against Steam's JPEG (0.937 on Counter-Strike 2 and PUBG), and a
3x crop showed fine background stripes and texture smoothed away. The hero
is enlarged by the browser to up to 768 CSS px, so that softness shows. `s`
(q55, SSIM 0.952) is shown downscaled and stays.
- `d` goes to q80.
- The R2 key and the edge-cache key now carry width AND quality
(img/v2/460q80/...): an old encoding can never be served for a new one by
an edge that cached it, and changing one variant's quality re-mints only
that variant. The v1 objects (the first 10 sources) are simply not read.
- IMG_MINT_PER_TICK 10 -> 40: the backfill finishes in about a day and a
half, still well inside IMG_TRANSFORM_MONTHLY_CAP.
Docs: SECURITY_SETUP §5 and CLAUDE.md now say /cdn-cgi/image/ must not work
on this zone. With zone Transformations on, "This zone only" still accepts
/img/* as a source, and /img/* proxies any Steam appid, so anyone could bill
transformations with arbitrary options outside the monthly cap.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The image PR rewrites the /img route line directly below; inserting the
pack entry above the unchanged shard line keeps the two edits mergeable in
either order.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase A of making the dataset unreadable on the wire while the repository
stays its readable home. /api/data/p1/data_NNN.bin (and removed_games.bin)
is the committed file run through shared/data-pack.ts at the edge:
"F2P\x01" | IV (first 12 bytes of its SHA-256) | AES-GCM(deflate-raw)
under a key that is PUBLIC in this repository. Obfuscation and compression,
not secrecy: curl and DevTools see an opaque blob instead of a ready-made
JSON API, and it is ~15% of the JSONL (data_001: 223,907 bytes against
1,497,828). Native WebCrypto and Compression Streams only - installed apps'
CSP has no 'wasm-unsafe-eval'.
The cache contract does not move: a pack unpacks to the exact committed
bytes, so games-loader.ts is untouched and its sha256 check against
index.json runs on the unpacked bytes before anything is cached. The Worker
verifies `?v=` before packing (the fetch-and-verify step and its mismatch
marker are now shared with the plain versioned path), caches versioned packs
immutably and unversioned ones for five minutes, and answers every error
with CORS. `.bin`, not `.jsonl`, so the zone's .jsonl Compression Rule never
recompresses a pack.
The app fetches packs when it can unpack and falls back to the plain path
for a missing pack or one that will not open - never after a network error.
The plain /api/data/data/*.jsonl paths are unchanged for released apps
(1.4.5 unversioned, 2.0.x ?v=), which cannot unpack.
Verified locally with wrangler dev: all seven shards loaded as p1 packs,
5,568 records verified and cached in IndexedDB, /games shows 5,568 of 5,568.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The game page's hero moves from /img/d2/ to /img/d/ in the AVIF change;
the comments only need to say the crawler follows an <img src="/img/...">.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/img/* used to pass Steam's JPEG straight through (median 36 KB; every
header is 460x215). Thumbnails and the detail hero are now AVIF for every
browser that accepts it: measured locally, 6.9 KB for the 460 px hero and
2.7 KB for the 230 px thumbnail of Counter-Strike 2, against a 34.3 KB JPEG.
How it is split:
- worker/lib/img-mint.ts (cron, every 15 min) is the ONLY place a billed
transformation happens. It builds the source list from shards that hash
to data/index.json (a lagging raw.githubusercontent shard would otherwise
freeze a stale list under the new generation), most-played first, encodes
`s` 230 px q55 and `d` 460 px q60 with the Images binding and writes them
to R2 `f2p-media` under img/v1/<w>/<path>@<t>.avif. The list is kept in a
marker object, so a backfill does not re-download the shards every tick.
- worker/routes/img.ts only READS: Cache API -> R2 -> Steam's JPEG. No
request (unknown appid, forged ?t=, HEAD) can create a transformation or
an R2 object. The old cf.image WebP branch is gone.
- Budget: Images Paid has no spend cap, so IMG_TRANSFORM_MONTHLY_CAP (20,000,
at most $7.50 against the agreed $15/month) is enforced by an atomic D1
counter (locks.ts bumpCounter), counted before each call, fail closed.
Error 9422 stops every isolate until the month turns.
Variants: s/d are negotiated on Accept with Vary: Accept. An AVIF browser
gets the JPEG only as a provisional answer (one day, no X-Img-Final) and the
service worker now caches only X-Img-Final responses, because CacheFirst
ignores Cache-Control. t and d2 stay JPEG: released apps request them and d2
is og:image. Cache keys are normalised, so stray query strings no longer
fork the edge cache, and the t capsule probe no longer runs on hashed paths
where it was two guaranteed 404s.
Client: thumbnails use s, the hero uses d with fetchpriority="high". The
Steam URL parser moves to shared/steam-image.ts so the client, route and
cron cannot disagree. worker-configuration.d.ts regenerated (runtime types
unchanged). Bucket f2p-media already exists (created 2026-10-02).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every production build log was 91% `[404] GET /img/d2/<appid>/...` lines,
one per game page. The prerender crawler follows each page's
<img src="/img/d2/...">; /img/* and /api/* are Worker routes the SvelteKit
app does not contain, so each request rendered the root layout plus the
error page and SvelteKit's DEFAULT server handleError printed the line.
kit.prerender.handleHttpError only decides pass/fail and cannot silence it.
src/hooks.server.ts now answers both prefixes before routing: no render, no
log. The prerenderer still sees the 404 and handleHttpError still ignores
exactly these prefixes, so a broken internal link still fails the build.
The hook only runs at build time and under `vite dev`, whose proxy takes
/api and /img first.
Local build: 0 `[404]` lines (was 5,566), log 294 lines (was 11,590),
verify-dist --web OK (5,610 HTML files, 5,568 game pages).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Web app, desktop and Android 2.0.1 -> 2.0.2 (package.json and lock,
Cargo.toml, the f2p-tracker entry in Cargo.lock, tauri.conf.json); the
[Unreleased] store-refresh and push-retry entries plus the contact addresses
become v4.0.2, "The Right Address Edition".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
contact@ stays the default. Three role aliases go where a reader of that
document will look for them, and nowhere else:
- security@ SECURITY.md, security.txt, SECURITY_SETUP section 8
- privacy@ the Privacy Policy's "Your rights"
- copyright@ LICENSE-DATA (new "If you hold rights" section) and ToS
section 6, one address for copyright, DMCA and takedown notices
security.txt now lists GitHub's private vulnerability reporting first and
security@ second, in RFC 9116 preference order; the links page is not a
security channel and is dropped from it. The About page gains a Website card
(https://poli0981.dev/), two columns at sm and three from md so the email
handle never truncates. AUTHORS, Contact, CONTRIBUTING and username.txt carry
the full map.
The copyright text promises a human reading, not an outcome: an override
cannot blank a field and the store refresh rewrites description monthly.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: ok
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: pass
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: ok
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: ok
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
update_data.py only enriches records that are incomplete, and fetcher.py's
apply_details()/apply_scraped() only fill EMPTY fields. Once a game had its
tags, languages, platforms or header image, nothing looked at them again
short of the manual refetch_all.py. A dry run on three games found all three
with tags that had drifted since they were first fetched.
scripts/refresh_store_data.py re-reads them a slice at a time, daily:
- store page (tags, languages, language_details, has_paid_dlc): every game
once every 7 days;
- appdetails (name, header_image, description, developer, publisher,
release_date, platforms, metacritic, drm_notes): every game once every
30 days.
Measured on the live catalogue: 600-675 store pages and 121-166 appdetails
calls a day, about 40 minutes at the client's throttle, instead of ~8,800
requests in one sitting.
A game is due when crc32(appid) % cycle == day % cycle. Not appid % cycle:
Steam appids are nearly all multiples of 10, which would leave 27 of the 30
monthly slices empty.
These fields were fill-if-empty until now, so the refresh keeps the same
care: it replaces a value only with a non-empty one (a failed request or an
age-gated page changes nothing), never writes MANUAL_FIELDS or notes, reads
has_paid_dlc only from a real store page, compares description as stored
(truncated to DESCRIPTION_MAX), bumps last_updated only on a real change,
and writes through save_main() so overrides and index.json behave as for
every other job. scripts/tests/test_refresh_store_data.py pins each rule and
the even spread of the slices.
"Refresh Store Data" runs at 16:00 UTC: scheduled runs here start 2-5 hours
late, the morning data jobs run 2-4 hours, and the data-write group keeps
only one pending run, so the slot is the one nothing long overlaps. It is in
data-write, commits through bash/commit_push.sh, and is on the CI-failure
notification list. README, CLAUDE.md and the changelog describe it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
purge-unhealthy ran for four hours on 2026-09-21 and then failed on
"push rejected (fetch first)", throwing the whole run away. The data-write
concurrency group serialises the WORKFLOWS, but main still moves under a
long job: a merged pull request, an /admin approval or override the Worker
commits, the extension's push to scripts/temp_info.jsonl.
bash/commit_push.sh does what every wrapper did - add, commit only if
something changed - and then pushes with up to five attempts, rebasing onto
origin/main between them. None of the other writers touch the shards, so
the rebase is clean; a genuine conflict still fails the job. All nine data
wrappers now call it, with their commit messages unchanged (snapshot.sh
keeps its data/snapshots/ pathspec).
Tested against a scratch remote: with main moved by another commit, the
first push is rejected, the rebase lands the job's commit on top, and the
retry succeeds; with nothing to commit it prints "No changes".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Web app and desktop/Android 2.0.0 -> 2.0.1 (package.json and its lockfile,
Cargo.toml and Cargo.lock, tauri.conf.json - the Android versionCode is
derived from it at build time); repo public-facing version 4.0.0 -> 4.0.1.
The changelog's Unreleased section becomes v4.0.1, "The Human Check
Edition": the Turnstile check, legal diffs, Web Analytics, the no-Referer
artwork fix for the apps, and data loads held behind both first-run gates.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The root layout held the catalogue back until consent (and, since the
Turnstile change, the human check), but two pages did not:
/activity and /charts/delisted called load() from $effects of their own,
and the activity feed also refetched on window focus - so both fetched
before the reader had accepted anything.
The gate now lives in Resource itself. An `enabled` option is read at the
top of every load() - the focus refetch and Retry included - and because it
is read inside load(), an $effect that calls load() subscribes to it and
runs again when it turns true: a held-back load starts by itself once the
reader is through. lib/app-ready.ts defines appReady() (consent accepted
AND the check cleared, which the packaged apps do as soon as they hydrate),
the root layout uses it for its own effects, and every Resource passes it.
resource.test.ts checks the option (no load, focus refetch or retry while
closed; open by default), fails on any `new Resource` in src without
`enabled: appReady`, and pins the layout's gated effect. Verified in a
browser: /activity before consent makes no /api/activity request, even on
a focus event; after consent and the check it loads once, by itself.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Legal (both reopen the consent gate for returning visitors, showing only
the changed lines - edited line-locally so that diff stays small):
- PRIVACY_POLICY: a section on the website's Turnstile check - after
acceptance, at most daily, what challenges.cloudflare.com reads (IP,
User-Agent, TLS fingerprint, page signals), that Cloudflare is processor
for the site and controller where it improves its bot detection (the
Turnstile Privacy Addendum), that the Worker forwards the token and IP
and keeps neither; the f2p:human_check storage row. "The only third
party", "the verification step" and "No fingerprinting" are corrected.
- ToS section 9: the check exists; /api/data/*, /img/* and the apps stay
excluded from both human checks.
SECURITY_SETUP:
- section 10 rewritten. It said the apps survived Hotlink Protection only
because their webview sent no Referer (untrue since WebView2 started
sending tauri.localhost), recommended switching the protection off, and
said no allowlist could express the apps' origin - a Configuration Rule
on http.referer can. Now: the per-<img> fix and its test, the rule for
2.0.0 installs, and the check, with the results measured today.
- new section 12: widget settings (hostname, Managed, pre-clearance off),
the TURNSTILE_SECRET secret and rotation, what the check is not, local
testing with Cloudflare's test keys, the optional rate-limit expression.
- the CSP block, the script-src/frame-src prose, "no form posts", the
rule budget (Configuration Rules 1/10), and two stale paths.
CLAUDE.md gains the human-check and <img> invariants and says "after
consent and the human check" where the service worker, analytics and
/welcome used to say "after consent". README, web/README, DEPLOYMENT,
ACKNOWLEDGEMENTs, SECURITY (bypassing the client-side gate is out of
scope), TAURI troubleshooting and the changelog follow. _headers and
worker/lib/http.ts: comments only - why images override Referrer-Policy,
what X-Frame-Options does and does not govern, and the public/_headers
and SITE_ORIGIN references that were stale.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After accepting the terms, each browser now passes a Turnstile widget -
at most once every 24 hours - before the app loads its data. It is an
OVERLAY (lib/common/HumanCheck.svelte), for the consent gate's reason: the
prerendered page underneath is what crawlers index. It opens only after
its state has read storage, so it is never baked into a page, and never
together with the consent gate, because it needs consent.accepted.
Crawlers never consent, so they never meet it.
Soft by design, and lib/human-check.ts says so at the top: it keeps
automated browsers from using the app, and cannot stop anything that reads
the HTML or the API directly - the WAF rules stay the boundary. It
refuses only on a verdict (the Worker's 403, a 300xxx/600xxx widget
error). Everything that is the site's fault - no secret, siteverify down,
a widget configuration error such as an unlisted hostname - and being
offline let the reader through for that page load, unrecorded, so an
installed web app still opens with no network.
- lib/human-check.ts: the pure rules, tested without Svelte - where it
runs (never under Tauri, `npm run dev` or an empty site key), which key
(the real one on the production hostname only, Cloudflare's always-pass
test key elsewhere), pass validity and TTL clamping, and what each reply
and widget error code means.
- lib/human-check-state.svelte.ts: `cleared`, a pass kept in memory as
well as in f2p:human_check, re-read when the tab becomes visible or
another tab stores one.
- lib/turnstile.ts: api.js from Cloudflare's exact URL, once; a timed-out
script is waited on rather than duplicated, a failed one is replaced.
- lib/gates.ts: /error/* and /legal/* are exempt from both gates, in one
place instead of ConsentGate's private regex.
- The root layout starts the catalogue, the service worker, analytics and
the /welcome redirect only when consent.accepted && humanCheck.cleared.
- kit.csp, web flavour only: challenges.cloudflare.com in script-src and a
new frame-src (the widget is an iframe; frames otherwise fall back to
default-src 'self'). The Tauri policy is unchanged, with no frame-src.
- verify-dist.mjs: the web build must allow Turnstile in both directives,
the Tauri build in neither, and no prerendered page may contain the
check's title.
Verified in a browser against `wrangler dev` with the test keys: nothing
from challenges.cloudflare.com before consent; consent -> widget -> one
POST (200) -> pass stored ~24 h ahead -> /welcome; reload within 24 h
does not ask again; /legal/* stays readable with an expired pass; the
always-fail secret shows the refusal with its code, and Retry sends a
fresh token; no secret lets the page through without storing a pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The website is about to ask each browser to pass Cloudflare Turnstile. A
widget token proves nothing until siteverify confirms it, and the secret
that call needs cannot live in the page - so the page posts the token here
and gets a yes or no. That answer is ALL this produces: no cookie, no
session, nothing stored. The pages are prerendered and served without the
Worker, and docs/ToS.md section 9 promises that /api/data/*, /img/* and the
packaged apps are never human-checked, so nothing on the server could or
may require a pass.
- Same-origin only: POST, Origin equal to the request's own, Sec-Fetch-Site
(when sent) same-origin, JSON. No CORS - the apps never run the check.
- The body is read from the stream with a 4 KB cap, because a chunked
request carries no Content-Length; the JSON is parsed locally because a
SyntaxError message would quote the token into the logs.
- siteverify gets the secret, the token and CF-Connecting-IP, with an 8 s
timeout. The action ("enter", shared/human-check.ts, one definition for
both halves) and the hostname must match, except under Cloudflare's
published TEST secrets, whose answers are fixed ("localhost", "test").
- Statuses are chosen for the page, which refuses only on a verdict: 403
when Cloudflare said no; 503 without TURNSTILE_SECRET, so deploy order
never matters, or when a test widget's fixed token meets the real secret
(the site served on a hostname the widget does not know); 502 when
siteverify is unreachable, failing or garbled.
- Never logs the token or the IP; the tests spy on console to hold that.
TURNSTILE_SECRET is declared required in env.d.ts (an optional declaration
would clash with what `wrangler types` emits once .dev.vars defines it) and
checked at runtime. web/.dev.vars.example carries Cloudflare's always-pass
test secret for `wrangler dev`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every game image in the desktop app was a broken icon. Security Events
showed why: WebView2 sends the page origin as the Referer
(http://tauri.localhost/), and the zone's Hotlink Protection 403s /img/*
for any Referer that is not this site - at the edge, before the Worker
runs, so nothing in worker/ could see or answer it. Android's System
WebView sends the same origin. docs/SECURITY_SETUP.md had predicted exactly
this ("the apps survive only because the webview sends no Referer").
Hotlink Protection lets a request with NO Referer through, so every <img>
now carries a literal referrerpolicy="no-referrer" - the admin's Thumb
already did. On the web the requests are same-origin and passed anyway;
the attribute also fixes the thumbnails `npm run dev` could never show
through its production proxy. Measured in Chromium against production from
a foreign origin: default policy -> blocked, no-referrer -> loads.
src/lib/images.test.ts scans every .svelte file (app and admin) with a
brace- and quote-aware tag scanner - an arrow function's "=>" would end a
naive <img[^>]*> match early - and fails on an <img> without the attribute,
or if it finds fewer than eleven.
Installed 2.0.0 apps are covered by a Configuration Rule on the zone
(documented in the docs commit) until they update.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Approved in /admin by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by admin.
Reason: ok
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
THE TWO WAF RULES EXIST NOW. `human-check-pages` (Managed Challenge) and
`blocked-countries` (Block) went live 2026-09-20, so SECURITY_SETUP no
longer reads as instructions for something that has not been done. Section
4 says what is deployed and when, and carries what was measured afterwards:
a plain curl with no browser User-Agent is still served `/`, `/games`,
`/legal/tos`, `/.well-known/security.txt`, `/sitemap.xml` and `/robots.txt`,
the challenge rate has stayed at 0%, and a real browser loads a game page,
the service worker and the beacon uninterrupted. Section 9 records the
analytics beacon returning 200 and its reports 204 on the live site, and
that "Enable with JS Snippet installation" is the only mode this CSP can
ever accept. "Still open" now names the Free-plan rule budget - 1/1 rate
limiting, 2/5 custom - because that is the next thing to run out.
THE DEPENDENCY LIST WAS THE REACT APP'S. ACKNOWLEDGEMENTs credited React 18,
react-router, i18next, Zustand, TanStack Query, Radix, shadcn/ui, cmdk,
OpenPGP.js, Tailwind 3, TypeScript 5 and PostCSS - none of which has
shipped since the v4 rewrite - while omitting Svelte, SvelteKit, Bits UI,
unified and the typefaces that actually do. Rewritten from package.json and
Cargo.toml, with every licence read out of node_modules rather than
remembered: echarts-wordcloud is ISC, not BSD-3-Clause. The claim that
/about carries a "full SPDX list" is gone; it is a curated subset and says
so now.
THIRD_PARTY.md gains svelte-check and vitest, which the pre-publish suite
has been running unlisted, and drops "the TypeScript SPA".
web/README.md documents the two analytics CSP hosts, why automatic
injection can never be used, the navigateFallback fix, and the consent
hashing and diff mechanism - none of which existed when its CSP and PWA
sections were written. Its file tree lists the four new modules.
DEPLOYMENT.md records that a zero-duration "Workers Builds" failure on a PR
branch is a preview-build artefact: it happened twice on PR #130 while the
identical commits deployed from main minutes later, and the GitHub Actions
`check` job already runs the same build, verify-dist and wrangler dry-run.
Also fixes a pre-existing broken curl snippet in section 10, whose
`%{http_code}\n` had been saved with a literal newline in it.
The dead relative links the link checker finds in CHANGELOG.md are left
alone: they are in released sections and name files that existed at the
time. A changelog is a record, not documentation.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
`cspSources(...).includes(host)` is an ARRAY includes - an exact element
match - but CodeQL cannot tell it from `String.prototype.includes` and
filed two high-severity `js/incomplete-url-substring-sanitization` alerts,
failing the PR.
The worry it encodes is a real one for this file, which is why the Tauri
assertion right below was already written as `.some(source => source ===
...)` with a comment saying so. Both now go through one `cspAllows()`
helper, so a reader and an analyser reach the same conclusion and
`https://evil.example/?x=https://cloudflareinsights.com` cannot pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The privacy policy said the site had no analytics, set no cookies, loaded
nothing from a third party and did not have Cloudflare Web Analytics
enabled. Three of those were already shaky and all four had to change, so
this rewrites the affected sections rather than bolting a paragraph on:
what the beacon does and does not do, why it waits for consent, the
human-verification step, and where the site is no longer served. ToS gains
section 9, which did not exist - there was no availability or automated-
access clause at all.
SECURITY_SETUP section 9 is reversed. It recommended turning Web Analytics
OFF; it now records why the automatic mode can never work under a
hash-based CSP, so nobody re-enables it, and what the JS-snippet setup is.
Section 4 keeps "leave Bot Fight Mode off" and adds the two custom rules
that are safe here, each exclusion annotated with what breaks without it,
plus the country block with its real costs: Yandex indexing ends, the
packaged apps stop working there, VPNs evade it trivially.
The verification command for the country block is deliberately NOT the
obvious one. `-H 'CF-IPCountry: CN'` proves nothing: geo.ts reads
request.cf.country first, which cannot be spoofed, and Cloudflare
overwrites that header on ingress. The doc gives the two checks that do
prove something, including the local one whose expected result is 403 on
every Worker route AND 200 on / - which is the whole argument for the WAF
rule.
Also corrected: the CSP transcribed in section 1 was missing both new hosts
and still listed a frame-ancestors this policy has never carried (it is
ignored in a meta CSP; X-Frame-Options covers it).
CLAUDE.md gains four standing rules - the navigateFallback invariant, the
two web-only CSP hosts and why automatic injection is impossible,
per-document consent hashing and why it lives outside prefs.svelte.ts, and
BLOCKED_COUNTRIES being defence in depth rather than the boundary.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three changes to the public app, sharing vite.config.ts, verify-dist.mjs
and the root layout.
THE SERVICE WORKER NEVER WORKED. `navigateFallback: "/200.html"` named the
adapter-static fallback, which generateFallback() writes into dist/ AFTER
workbox has globbed .svelte-kit/output - there is no 200.html under
.svelte-kit at all, so it could never be a precache entry.
createHandlerBoundToURL() threw `non-precached-url` on every page load and
abandoned the rest of the worker's top-level setup. It is now "/", which IS
precached and is exactly what Cloudflare and Tauri already serve for an
unmatched path, so lib/fallback-route.ts recovers the route offline the
same way it does online. Measured with the server stopped: /games/730
renders the game, not the dashboard. verify-dist.mjs now parses dist/sw.js
and fails the build if the bound URL is not in the manifest - nothing
looked at the worker's contents before.
CLOUDFLARE WEB ANALYTICS, and not the way it was configured. Automatic
injection had been enabled for months and collected nothing: it inserts an
inline loader at the edge, after our response, and kit.csp runs in
mode:"hash", where CSP3 makes script-src ignore 'unsafe-inline'. No policy
can ever admit it. lib/analytics.ts appends the beacon itself, from the
$effect that already waits on consent.accepted, never under Tauri, and does
nothing when CF_BEACON_TOKEN is empty. The CSP gains
static.cloudflareinsights.com (script-src) and cloudflareinsights.com
(connect-src) in the WEB flavour only; verify-dist.mjs fails the web build
without them and the Tauri build with them. The dashboard must be switched
to "Enable with JS Snippet installation" or the edge injection returns on
top of this one.
A LEGAL DOCUMENT THAT CHANGES NOW SHOWS THE CHANGE. Each document is
hashed at build time (build/legal-versions.ts serves virtual:legal-versions,
~700 bytes inlined, and virtual:legal-sources, 25 KB imported dynamically
by ConsentGate alone so a normal page load never fetches it). A differing
hash reopens the gate by itself, listing only those documents with a
line diff (lib/diff.ts) against a snapshot in f2p:legal_snapshot, rendered
as text in a <pre> and never {@html}. No snapshot - storage cleared, or an
acceptance older than the feature - falls back to "open it and read it in
full". TERMS_VERSION survives only as the "make everyone re-read all six"
override; it no longer has to be remembered for an ordinary edit.
Consent moved to lib/consent.svelte.ts: prefs.svelte.ts is also compiled by
the admin SPA's own Vite build, which cannot resolve a virtual module, and
leaving it there failed `npm run build:admin` outright.
Also fixes a layout bug the longer privacy hint exposed: the gate's hint
span had no min-w-0, so a flex item's min-width:auto let it claim the whole
row and collapse the document's LABEL to nothing - "Privacy Policy" was
invisible.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
BLOCKED_COUNTRIES ("CN,RU,AR") in wrangler.jsonc, enforced by lib/geo.ts
before any route runs, admin block included. "CN" is mainland China only -
HK, MO and TW are separate codes and stay reachable.
This is NOT the boundary, and the comments say so in both places. The
Worker only ever sees the four `assets.run_worker_first` prefixes, so every
prerendered page is served without invoking it: measured with the list
temporarily extended, all of /api/*, /img/* and /admin answer 403 while /
still answers 200. A WAF custom rule on the zone is what actually blocks a
country (docs/SECURITY_SETUP.md section 4). What this adds is a list that
is reviewable in Git and a refusal that survives the rule being deleted or
mis-scoped.
It FAILS OPEN on an unknown country. request.cf is undefined under Vitest
and under `wrangler dev` without --remote, so failing closed would 403
every test and every local run. request.cf.country wins over CF-IPCountry,
which is why a spoofed header proves nothing - `wrangler dev` supplies its
own cf with country "SG", measured. T1 (Tor) and XX (unplaceable) are
explicitly not countries: XX has the shape of one, so without naming it a
blocklist containing "XX" would quietly refuse everyone the edge could not
locate.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Every approval committed `Approved in /admin by <email>.`, every override
edit `Edited in /admin by <email>.`, and `data/overrides/<appid>.json`
recorded the same address as `set_by`. All three are public forever, and
the Git AUTHOR was already the App's own bot identity - only the body text
named a person.
They now say `admin` (ADMIN_ATTRIBUTION, shared/admin-api.ts). The four
override files that already carried the address are rewritten; `set_by` is
informational, so nothing in the pipeline reads it.
appendLinks() loses its `actor` PARAMETER rather than merely stopping at
the one call site that passed `who.email`: a parameter nobody can supply
cannot be supplied by mistake. A new case in git-commit.test.ts asserts the
generated body contains no `@` at all.
D1 is untouched and still records the acting Access identity in
audit_log.actor, ingest_queue.decided_by, ingest_decisions.decided_by and
commit_jobs.requested_by - 0001_init.sql calls that deliberate, and the
audit view filters on it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
#5 py/incomplete-url-substring-sanitization: _describe_access_redirect()
took any host ending in "cloudflareaccess.com" for an Access login page,
lookalikes such as evilcloudflareaccess.com included. The suffix now needs
the dot; test_discover_new.py covers both cases.
#6, #7 js/incomplete-multi-character-sanitization: the SEO and chart tests
stripped comments from source with a regex replace of "<!--". The i18n test
had its own copy, and its earlier fix (replace until nothing changes) removed
text that was never inside a comment. All three now use one scanner,
src/lib/testing/source.ts, which removes each span once and never rescans its
own output.
#3 js/missing-origin-check stays as it is: jsonl-parser.ts is a dedicated
module worker, only the document that created it can post to it, and its
MessageEvent.origin is empty. The file already says so, and it validates the
message shape instead.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
/admin reported "Your Cloudflare Access session has expired" straight after
signing in, in a private window too. The page and its API were two Cloudflare
Access applications: /admin (AUD ca93...) and /api/admin (AUD a15d..., read
from the kid= of each login redirect). Access issues its session cookie per
application and fetch() cannot follow the sign-in redirect, so the session
for /admin never reached the API. Every call came back as an opaque redirect,
which api.ts correctly reads as an expired session, and a reload only renewed
the page's session. The Worker never answers 401/403 on these routes, so the
redirect could only have come from the edge.
The API now lives at /admin/api/*, under the page's own application:
ADMIN_API_PREFIX in shared/admin-routes.ts, used by the router, both
handlers, the SPA's api() (views pass routes like "queue?...") and the mock
backend. /api/admin/* is no longer served, and its AUD leaves
ACCESS_AUD_ADMIN.
Every existing test called the handlers directly, so none could see this.
worker/index.test.ts drives the real router and Access check with a signed
RS256 token: a reviewer reaches /admin/api/*, a write still needs the header
rather than the cookie alone, another application's token and the old prefix
both get 404. security.test.ts keeps the prefix under /admin and API paths
out of the views. Verified in preview:admin under the production CSP: queue,
stats, me, health and the ping write all answer from /admin/api/*.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
CodeQL analyses .mjs files (alerts #16 and #17 are in
web/scripts/verify-dist.mjs), but the push and pull_request path filters
listed only .js/.jsx, so the commit that fixed those alerts never started a
scan and they stayed open.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Clears CodeQL alerts #16 and #17. visible() removed <script> and <style>
with repeated regex replacement (js/incomplete-multi-character-sanitization),
and the Tauri CSP check looked the site origin up with includes(), which
CodeQL reads as a URL substring check.
The scanner lowercases ASCII only: a character whose lowercase is longer
("İ") would otherwise shift every index it cuts at. On all 3,691 pages of
the current web build it returns exactly what the regex version returned.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
android-v2.0.0 stopped at "Set up Android SDK": setup-android's default
package list still names the legacy `tools` package, which the SDK
repository no longer carries. Install platform-tools only; Gradle fetches
the build-tools and platform it needs.
A manual run now checks out the tag it releases instead of main, and the
release notes name that commit (on a manual run github.sha is main's HEAD).
The tag input has no default any more, because a run replaces the named
release's APK. The notes also stop claiming device testing for a build that
has not been tested yet; docs/android-support.md keeps the device list.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
None of these reach the site - they read our own build output and source
files - but the PR's CodeQL check fails on them, and each has a correct form:
- verify-dist.mjs: strip <script>/<style> until nothing changes, and accept end
tags with trailing whitespace (incomplete multi-character sanitization, bad
tag filter); check the Tauri origin as an exact connect-src source parsed
from the CSP rather than a substring of the page (incomplete URL substring
sanitization); list files with Dirent types instead of stat-then-read.
- emit-worker-bundle.ts: count scripts case-insensitively, with the same end
tag rule, so a second script cannot slip past the one-script check.
- i18n.test.ts: strip HTML comments until nothing changes.
- fallback-route.test.ts: take the entry type from the directory listing
instead of a stat followed by a read (file system race).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Web CI failed on the PR at `npm run build:admin` with ENOENT for
.admin-build/index.html. Two faults, one hiding the other:
- The admin build imports files under web/src, whose tsconfig.json extends
.svelte-kit/tsconfig.json. On a fresh checkout that file does not exist until
SvelteKit has synced, and CI runs typecheck (which starts with build:admin)
before anything else. build:admin and dev:admin now run `svelte-kit sync`
first. Workers Builds was unaffected: its `npm run build` runs the SvelteKit
build, which syncs, before the admin build.
- The emitter read the output directory in `closeBundle`, which Vite also calls
after a FAILED build. Its ENOENT replaced the real error in the log, and on a
machine with an earlier build it could have read that build's files. It now
takes the output from the bundle in `writeBundle`, which only runs after a
successful write.
Reproduced locally by removing .svelte-kit, .admin-build and worker/generated:
the old code failed exactly as CI did (294 modules, then ENOENT); with the fix
typecheck, the 240 tests, build, verify-dist, the wrangler dry run and knip
pass from that state.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- README: SvelteKit rather than React, Cloudflare rather than GitHub Pages, a
resizable self-updating desktop app, the /admin review queue, the real
workflow list, and no in-browser editing or GPG signing (removed in
September).
- web/README.md: the admin app, verified shard generations, prerendered game
pages, the service worker as it is now, and the checks CI runs.
- TAURI.md: the update feed at /api/updates/desktop (drafts are never offered),
settings surviving updates, the Android update check; the OAuth note is gone
with sign-in.
- dev_env (en, vi), CONTRIBUTING, android-support (en, vi): tests exist now,
and the web side is Svelte.
- SECURITY_SETUP: the admin shell's nonce policy, and the report-only CSP that
Cloudflare's Continuous script monitoring adds at the edge (turn it off).
- CLAUDE.md: where old /#/ links still come from and why the upgrade uses
goto; /api/activity sends CORS too.
- CHANGELOG [v4.0.0]: the admin app, verified data, a page per game, the
installable web app, the desktop updater, the new pages, and the live-site
fixes. Deploying needs D1 migration 0002.
- Code comments that still described React, GitHub Pages, hash routing or a
sign-in token.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The locale files still carried the React app's sign-in, GPG, bulk-delete,
maintenance-trigger and per-chart title keys, none of them asked for by
anything: 137 of 530. They are removed, and i18n.test.ts now fails when an
English key is not used anywhere in the app.
Seven Vietnamese values were the English copied across (Developer, Publisher,
Repository, a column header, the offline badge); they are translated. A second
test fails on the next one, with an explicit allowlist for what is meant to be
identical: product names, gaming terms Vietnamese uses as they are, and formats.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Welcome
- The full introduction: three ways in, the language switch, the documents
just accepted, and the reshow hint (eleven keys that nothing rendered).
- Shown once, to a visit that started on the dashboard, right after consent.
replaceState, and the page marks itself seen on mount, so Back cannot loop.
Crawlers never consent, so / stays the indexable page.
Legal
- /legal lists every document, binding ones first.
- An unknown /legal/<slug> matches no route (param matcher) and gets the
translated 404; the host's fallback used to hydrate it as the dashboard.
- Document titles and summaries are i18n keys; they were English everywhere,
including the consent step.
- The rendered document no longer repeats its own title as a second <h1>.
Data views
- /stats: when games went quiet, by month (zero_player_since).
- /charts/time: catalogue growth - games added per month and the running total,
with empty months kept on the axis.
- /charts/anti-cheat/list: a searchable, sortable table with anti-cheat families
as filters and the kernel level per game.
- /health: safe = "?" is its own "not reviewed yet" group instead of burying
the genuinely missing fields under 3,600 of them; groups link to the matching
filtered /games view.
/games
- Safety filter (safe, not safe, not reviewed, never set), normalised the same
way on /games, /stats and /health (lib/safety.ts).
- Filters, sort and page are mirrored into the URL, browser-only, so a filtered
view can be linked and survives a reload.
- The page number lives in the filter store: Back from a game returns to the
same page, and a changed filter starts again at page 1.
Also translated: the table's data-issue tooltips and the About page's stack
descriptions.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The two Worker-rendered admin pages (admin-ui.ts, edit-ui.ts: 1,400 lines of
HTML and script inside template literals) are replaced by a Svelte 5 app in
web/admin/. It is built on its own and embedded in the Worker as the gitignored
worker/generated/admin-bundle.ts, so no admin code ever reaches dist/, the
service worker's precache or the packaged apps. worker/routes/admin-spa.ts
serves the shell with a per-response nonce CSP after the existing Access checks,
serves hashed assets immutably, and 404s any other path under /admin.
Queue
- Rows that are decided (approved, committed, rejected) or whose game is already
published have no checkbox, show a lock and are skipped by select-all. The
rules come from shared/queue-rules.ts, the same module the Worker enforces.
- Decisions confirm every row first and report skipped rows with their reasons.
- Tabs with counts, cross-status search, sort, page size, all kept in the URL.
- Keyboard: j/k, x, a, r, d, e, /, Esc, ?. Ignored while typing or composing.
- Details dialog: payload, durable decision, other rows for the game, Reopen for
a rejected row with the reason when it cannot be reopened.
- Phone layout as cards.
Edit
- One game: every change reviewed in a diff dialog before the commit; retire;
delete a settled override file; unsaved-change guard.
- Several games: any field, set or retire, selection kept across pages and
genres (up to 10), each game shown in the review.
Jobs, Audit and Health get their own paged, filterable pages. Health draws its
table on a 503 too, and Test write proves the write path.
An expired Access session reloads the page once; a refusal that survives the
reload is reported instead of looping. A non-JSON response is a server error,
never "session expired".
Local development: npm run dev:admin runs the real handlers against an in-memory
D1 with demo data, and npm run preview:admin serves the built bundle through the
real serveAdmin with the production CSP. Nothing in worker/ or admin/src imports
the mock, and the Worker has no authentication switch.
Also: design tokens move to src/styles/theme.css, shared by both builds;
verify-dist fails if admin code reaches dist/; vite-plugin-pwa is declared, as
src/app.d.ts references its types; docs/ADMIN.md, DEPLOYMENT.md and CLAUDE.md
describe the new admin.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The server half of the admin rework. The pages still run on it unchanged -
every change here is additive - until the new UI replaces them.
Read-only rows. web/shared/queue-rules.ts holds the queue's rules once, for the
Worker and the UI: a row is locked when it is approved (its request is already
committed to Git), committed (the game was observed in data/) or rejected, and
also when its GAME is already published, since one appid can have several
rows. /api/admin/decide refuses locked rows when it reads them and again in
every UPDATE's WHERE, and reports each refused id with a reason - not-found,
not-decidable, published, open-row-exists, duplicate-in-request, no-op,
changed-concurrently. It used to drop them silently, so a mixed selection
reported fewer decisions than it was sent. The queue listing carries
`published` per row, and status=all searches every tab when there is a query.
Bugs fixed on the way:
- Requeueing or deferring a failed row while another row for the appid was
open broke uq_queue_open_appid inside the batch: a 500 for the whole request.
It is now a skip.
- When an approval's commit landed and the queue update failed, the job's
status was in the same rolled-back batch and stayed 'pending' forever, and
the message promised reconcile would promote rows it never reads. The job is
recorded first, and the message says what is actually true.
- The health endpoint returned 503 without a body the page could render.
New: POST /api/admin/reopen returns one rejected row to pending and deletes
only its 'rejected' decision, in one transaction whose guards refuse a
published game or an appid with another open row - replacing a raw-SQL step in
the runbook. Jobs and audit page with totals and filters. Approval reasons are
recorded in the audit row and the commit body.
Reconcile sweeps pending, deferred and failed rows whose game is already in
data/ to committed (a game published after its approval aged out stayed
'failed' forever), holds a cross-isolate D1 lease, and skips the ~6 MB dataset
fetch while index.json's generation is unchanged. Migration 0002 adds the two
tables; lib/locks.ts treats a missing table as unavailable, so the Worker and
the migration can ship in either order.
Overrides: the Worker can now delete a SETTLED override file - no active field,
every retirement already restored - through createCommitOnBranch deletions,
and every override commit writes a commit_jobs row.
audit_log and commit_jobs are pruned daily after ADMIN_RETENTION_DAYS (180),
which the privacy policy now states.
Tests: the real handlers against the real migrations on node:sqlite
(worker/testing/sqlite-d1.ts), with GitHub and the dataset faked - 57 new
cases across decide, reopen, reconcile, leases, retention, override deletion
and the createCommitOnBranch payload.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The updater plugin, its signing key and its capability shipped with 2.0.0,
but nothing called check(), and its endpoint could not have worked anyway:
releases/latest/download/latest.json follows GitHub's single "latest" release,
and this repository publishes dataset, Android and desktop releases on one page.
- The feed is now /api/updates/desktop. The Worker reads releases.atom (no
anonymous-API rate limit, never lists drafts), takes the highest
desktop-vX.Y.Z, and serves its latest.json only if the version matches the
tag and every artefact URL is this repository's own release download.
Anything unusable is a 204, the updater's "no update". Public, edge-cached,
and - like /api/activity - never touches the GitHub App token.
- The app checks five seconds after launch, once per session and only after
consent, and offers the update in a dialog: plain-text release notes,
download progress, then relaunch through tauri-plugin-process. The npm
plugins match their Rust crates' minor versions, which the Tauri CLI
requires.
That exposed a second bug. purge_stale_webview_data cleared the webview's
storage whenever the stamped version differed from the running one - so every
update would have wiped consent, theme, language and the cached catalogue.
Only builds before 2.0.0 ever registered a service worker, so needs_purge()
now clears only for a missing or pre-2.0 stamp, with unit tests.
Release plumbing: both release workflows use a plain `npm ci` (web-ci.yml
already forbade the `|| npm install` fallback that once hid a broken
lockfile), their notes stop describing a fixed 1400x900 window, GitHub Pages and
raw.githubusercontent, and web-ci builds and verifies the Tauri configuration
on every change. The privacy policy states what each app's update check
contacts.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The 2.0.0 web build generated sw.js and manifest.webmanifest and used
neither: @vite-pwa/sveltekit injects its registration into index.html, and a
SvelteKit build has none, so no page ever registered the worker or linked the
manifest. Only browsers still running the React-era worker had one, and the
site could never be installed.
- lib/pwa-state.svelte.ts registers the worker once consent is given, and
listens from mount for beforeinstallprompt (it fires once, early),
appinstalled, display-mode and connectivity.
- registerType "prompt": a new version waits, and PwaIndicator offers Reload
in a toast instead of the page reloading itself mid-read. Workers already in
the field install the new one as waiting, which activates normally.
- The root layout links the manifest; the topbar and Settings offer
installation when the browser allows it.
- The ten pwa.* strings that had sat unused since the port are in use.
- The Tauri build omits the plugin, so its virtual modules resolve to no-op
stubs there, and verify-dist.mjs fails a Tauri build that links a manifest.
Checked in a browser: the worker registers and precaches after consent, a
rebuilt worker waits and raises the update toast, and Reload activates it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
/games/<appid> was client-rendered only, so the 3,650 pages that describe the
actual catalogue were invisible to search. On the web build each one is now a
real document with its own title, description, social image, JSON-LD
VideoGame record and sitemap entry. The Tauri build prerenders none.
Two constraints shaped how:
- A crawler never accepts the terms, so it never loads the catalogue. The page
must render from data baked in at build time. build/game-seeds.ts reads
../data once in the SSR build and inlines a seed per game - slow-changing
fields only. Players, peak, reviews and metacritic are never baked: data
commits do not rebuild the site, so they always come from /api/data/*.
- It is a UNIVERSAL load, not a server load. With +page.server.ts every client
navigation fetches /games/<appid>/__data.json, and for a game added after the
deploy that is index.html at 200 - parsing fails and the page errors. The
browser half of the load reads the same seed back out of the page's
#game-seed block, so hydration matches, and returns null after a client-side
navigation, where the live catalogue renders.
fallback-route.ts previously re-rendered /games/* on every cold load, which a
prerendered page must not get. Pages that may arrive as the dashboard shell now
announce themselves with markRouteRendered(); recovery runs only when that did
not happen (new games, Tauri, studio pages). A page for a game removed since the
deploy shows "Game not found" with noindex once the catalogue loads, with the
removal reason when there is one.
Measured: 3,649 pages, build 16 s -> 30 s, dist 143 MB, ~38 KB a page. The
service-worker precache ignores them, the crawler ignores 404s for Worker-only
/img/ and /api/ paths and nothing else, and verify-dist.mjs --web checks every
game page carries its seed and JSON-LD and that no __data.json exists.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The screenshots showed "3,666 games · 2026-09-12" on 09-17, while the site
served 3,649 / 09-17. Three client-side paths could produce that, and each is
closed:
1. A tab loaded the catalogue once and never looked again. The layout now
revalidates on visibility, focus and online (at most once a minute) and
every ten minutes while visible: one ~600-byte index request, shards only
when the generation changed. Resource.data is $state.raw, and a check that
finds nothing new returns the same object, so pages do not re-render.
2. The service worker answered /api/data/* NetworkFirst with a 5 s timeout, so
a slow index came back from its cache and was taken as current. That route
is gone; lib/pwa.ts deletes the leftover f2p-data-v3 cache. IndexedDB is the
only offline copy, and the loader now falls back to it when the index
cannot be fetched - which also gives the packaged apps, which have no
service worker, the offline mode their comments already claimed.
3. index.json and the shards are cached independently on the way to the
client, so a new index could arrive with an old shard and be cached as a
pair under the new stamp. Shards are now requested by the sha256 their
index entry records. The Worker serves such a request only if the bytes
hash to it - then caches it for a year, since content addressed by its own
hash cannot go stale - and otherwise answers 503 (remembered for 20 s, so a
wave of retries does not re-pull 1.2 MB each from GitHub, whose CDN does not
honour a query string). The client verifies again, caches only a fully
verified generation, keeps showing the one it holds meanwhile, and retries
with backoff. An index without hashes loads exactly as before.
games-loader.ts is the whole policy as a pure function, with a test for every
branch; data.test.ts covers the Worker side. The topbar says when data is an
offline copy or when newer data is waiting upstream.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
index.json was the client's only freshness signal and it was stamped on every
save. Two failures followed from that:
- A run that changed nothing still produced a new last_updated, so every
visitor re-downloaded all ~6 MB of shards (the 2026-09-16 "Dead link check"
commit touched only index.json).
- Nothing tied an index to the shard bytes it describes. index.json is edge-
cached for 30 s and the shards for 300 s, on top of raw.githubusercontent's
own CDN, so a client could receive the NEW index with an OLD shard and store
that pair in IndexedDB under the new stamp, where it stayed until the next
change.
_save_index() now records the sha256 of each shard's exact bytes and keeps the
previous last_updated when files, counts and hashes are unchanged - leaving
index.json byte-identical, so such a run makes no commit. save_jsonl writes LF
explicitly: on Windows, text mode wrote CRLF, which is not the blob Git stores
or raw.githubusercontent serves, and the hash would have described bytes no
client receives. An index without hashes bumps exactly once.
The pipeline had no tests. scripts/tests/test_index_hash.py pins all of this,
python-tests.yml runs it, and notify-ci-failure now also watches Web CI,
Python Tests, Daily Snapshot and Top Offline, which it silently did not.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- An unknown URL rendered the dashboard. Both hosts answer a miss with the
prerendered index.html at HTTP 200; the router knows no route matched
(page.route.id is null), so the layout now renders the 404 view in place,
noindex. It deliberately does not goto(): navigating to an unmatched URL
falls back to a native load, which the host answers with index.html again,
forever.
- /#/games/730 links from 1.4.x builds changed the address bar and left the
dashboard on screen: the rewrite ran after the router had rendered. It is a
replacing goto now.
- In the desktop and Android apps the table's Steam icon dead-clicked
(window.open is blocked, and the link interceptor only sees <a>), and the
steam:// button was refused by tauri-plugin-shell's default scope, which
allows only mailto/tel/http(s). tauri.conf.json widens `plugins.shell.open`.
- A worker error left every queued shard parse unsettled, so the catalogue
hung on "Loading..."; those shards are now parsed on the main thread.
- The mobile menu is a bits-ui Dialog: focus trap, Escape, focus return.
- hooks.client.ts finally calls the stale-chunk reload that chunk-error.ts has
carried, uncalled, since the port.
- The /stats diagonal reference line never drew: markLine was used and
MarkLineComponent was never registered. charts.test.ts now fails on any
option key whose component is missing.
- About's labels follow a language switch.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Ctrl-K threw the moment it opened. /charts/anti-cheat/list was listed in both
CHART_PAGES and EXTRA, the palette renders routes in a keyed each, and a
duplicate key throws in a Svelte 5 production build. paletteRoutes() now
deduplicates and nav.test.ts holds the lists unique. The palette also gained
the arrow-key and Enter navigation its footer has always advertised, and the
shortcut hint says ⌘K on Apple keyboards.
Every prerendered page was wrong in ways only the built HTML shows:
- The consent dialog was in all of them. The gate rendered whenever
`accepted` was false, which it always is before storage is read, so
returning visitors saw it flash on every full load. It now waits for
consent.hydrated.
- It also covered /legal/*, the documents it asks people to accept, which
therefore could not be read before accepting them.
- `loading && !data` is false before a load starts, so /games shipped "No game
matches these filters.", /health "Nothing flagged" and the chart pages
"None". Resource.pending (no data, no error) replaces all 15 checks.
- Meta descriptions interpolated counts that are zero at build time ("Overview
of 0 F2P Steam games"); they are static now, and the headers show counts
only once data exists.
scripts/verify-dist.mjs reads dist/ in CI and fails on each of these. The
sidebar's "Manage" group is "Project" - nothing in a read-only app is managed -
and /publishers finally has a sidebar entry.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The three screenshots of the live site traced to two bugs, each wider than
the page it was noticed on.
Placeholders. t() leaves {{var}} in place when a variable is missing, and
seven call sites never passed one: "Languages ({{count}})", the peak suffix
"(peak {{peak}})" rendered as a FIELD LABEL through `detail.${f.key}`, the
same suffix as the /stats scatter axis and tooltip, the Steam-icon tooltip on
every /games row, and the prerendered meta description of the anti-cheat
index. i18n.test.ts only proved keys exist; it now reads every call site and
fails on a missing variable, on a placeholder key stored in a lookup table, on
a template-literal key, and on any key-shaped literal that does not resolve.
The four remaining dynamic keys became literal tables.
Colours. chartTheme() emitted space-separated hsl(38 94% 60%). The canvas
paints that, but zrender's own parser splits on commas, so every hover state
derived from it came back undefined and the hovered tile, bar or slice lost
its fill - the blank "Card Game" treemap tile was simply the one under the
cursor. Five pages also passed hsl(var(--x)), which a canvas never paints.
Tokens are converted to the comma form, the semantic tones joined ChartTheme,
and a test runs zrender's real parser over every token in both themes.
Also: the treemap tooltip used the pie-only {d}; every grid used containLabel,
which in echarts 6 ignores axis names (both /stats axis titles were clipped);
option colours now follow a theme switch; review tones follow Steam's bands;
the game page shows Steam's wording beside the score, links its studios, and
says "Game not found"; studio pages no longer decode params twice (URIError on
"90% Studios"); duplicated studio names no longer crash the keyed each.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The Web CI "Unused code report" step failed on the merge. The export and type
backlog was not the cause - knip.json already marks both "warn" - it was this:
Unlisted binaries (1)
python package.json
knip reads package.json's scripts and treats a binary it cannot resolve to a
package as an ERROR, which exits 1 regardless of the warn-level rules. The
`fonts` script (`python scripts/gen-fontface.py`) arrived with the SvelteKit
rewrite, so the failure arrived with it too.
python is a system tool here, not a dependency, so it is declared as ignored
rather than installed.
How this reached main: I had been running `npm run knip | grep ...` locally,
which reports the pipeline's exit status and not knip's, so a red run looked
green every time. Checked with `npm run knip > file; echo $?` now, and that is
what the verification should have been all along.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Version bumps plus the Phase 7 binary work, but the reason this commit is
large is that building an actual 2.0.0 desktop binary and driving it over CDP
found three defects that no amount of reading would have.
## The desktop app was serving the React UI from a dead service worker
The 2.0.0 build launched, in its new 1280x860 window, showing the 1.4.x
React app: a sidebar reading "Steam · v1.0", no Stats or Developers entries.
Measured in the running release binary:
caches: ["workbox-precache-v2-http://tauri.localhost/"]
navigator.serviceWorker.controller: http://tauri.localhost/sw.js
A service worker registered at tauri.localhost can never be updated. Asking
it to, in the packaged app:
TypeError: Failed to update a ServiceWorker for scope
('http://tauri.localhost/') with script ('http://tauri.localhost/sw.js'):
An unknown error occurred when fetching the script.
The update algorithm refetches the worker script bypassing the worker itself,
and Tauri's custom protocol does not satisfy it. So the worker installed by
whatever version a user ran FIRST answers every navigation from its own
precache - index.html included - for the life of the install. Every desktop
and Android release since the PWA landed would have shipped invisible.
No frontend fix exists: the frontend that would unregister the worker is the
part being served from the stale cache. It has to happen before the webview
loads anything, so `purge_stale_webview_data` in lib.rs clears the webview's
storage once per version.
That clear also wipes localStorage and IndexedDB - WebView2's
ClearBrowsingData is all-or-nothing - so an upgrade re-asks for legal consent
and re-downloads the catalogue once. Stated in the code rather than glossed:
being asked for consent again beats silently running last year's app.
It also needs an explicit reload, because setup() runs while the first page is
already loading and clearing storage underneath it leaves an empty body. That
was found the same way - by looking at the window after the first attempt.
The build now omits the PWA plugin entirely when TAURI_ENV_PLATFORM is set.
The packaged apps lose nothing by it: their assets are local files already,
and offline data has always come from the IndexedDB cache in lib/cache.ts.
## The CSP would have bricked both packaged apps
`kit.csp` ships inside the Tauri bundle, and there the page origin is
tauri://localhost - so `connect-src 'self'` means the BUNDLE, not the site.
Every /api/data/* fetch would have been blocked and the apps would have shown
an empty catalogue. Separately, Tauri sends its own CSP as a header, and a
browser enforces the INTERSECTION: its `script-src 'self'` would have won
against SvelteKit's hashed meta policy and blocked the hydration bootstrap -
the same failure the web build hit before the CSP moved.
svelte.config.js now emits a second flavour when TAURI_ENV_PLATFORM is set,
naming the site origin explicitly. The web policy is untouched and still has
no api.github.com in connect-src - removing it was deliberate, /api/activity
proxies it - so the looser sources exist only where they are needed.
Verified in the running binary: consent accepted, 3,666 games loaded
cross-origin, a chart painted, both fonts reporting "loaded". And
/games/730 opened by full page load resolves to Counter-Strike 2, which
finally proves at runtime what CLAUDE.md had only asserted about
tauri::manager::get_asset()'s fallback chain.
## Binary 2.0.0
- The window unlocks: 1280x860, resizable, maximisable, minimum 880x600. It
was pinned to exactly 1400x900 with minWidth == maxWidth, which made a
responsive redesign pointless on the one platform that could not use it.
- tauri-plugin-http is gone, with its `https://github.com/*` capability and
its plugin init. It existed for the GitHub OAuth Device Flow, whose
endpoints send no CORS headers; sign-in was removed, and the only remaining
GitHub call is android-update.ts, a plain fetch to an endpoint that does
send them.
## Docs
web/README.md described React 18, Zustand, TanStack Query, HashRouter, a
GitHub Pages deploy, fetching from raw.githubusercontent.com, PAT sign-in and
client-side GPG signing - and a directory tree in which almost no path still
exists. Rewritten against the code.
The CHANGELOG's v4.0.0 entry says 95 tests because that is what `vitest run`
prints.
check / 95 tests / build / knip / wrangler dry-run clean. Desktop release
binary built, launched, and driven.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Found by walking the built site in a browser rather than by reading it. Four
defects, none of which produced an error, a warning, or a failing build.
## /games/730 rendered the dashboard. So did every studio page.
The three routes that are deliberately not prerendered - /games/[appid],
/developers/[name], /publishers/[name] - have to be answered with an app
shell on a cold load. Both hosts answer with `index.html` SPECIFICALLY, and
neither can be told otherwise: Cloudflare's
`not_found_handling: "single-page-application"` names no file, and Tauri's
get_asset() chain is compiled in. index.html is the PRERENDERED DASHBOARD,
and a prerendered page embeds its own hydration payload - `node_ids: [0, 2]`.
SvelteKit hydrates exactly those.
The router was not confused: page.route.id was "/games/[appid]" and page.url
was right, so the canonical tag and og:url were correct. Only the rendered
components were the dashboard's. HTTP 200, clean console, correct metadata,
wrong page - the single visible symptom was the <h1>.
Two things had to change:
- `paths.relative` off. SvelteKit defaults it on, which gives PRERENDERED
pages "./_app/..." asset URLs. Served as the fallback for /games/730 those
resolve to /games/_app/..., which 404s back into the SPA handler and
returns index.html as text/html. The browser refuses it ("Expected a
JavaScript-or-Wasm module script..."), so the page did not hydrate at all.
Invisible until a route actually fell through, because 200.html was always
absolute.
- fallback-route.ts re-navigates on first mount when the route is one of the
three. Those routes are never prerendered, so a document delivered for one
is always the substituted shell - there is no legitimate case to fight.
`_redirects` was tried first and does not work: Workers Static Assets has no
200-status rewrite, and `/games/* /200.html 200` is honoured as a REDIRECT -
the address bar became /200 and the app 404ed. Measured, not assumed, and
recorded in the module so it is not tried again.
## No page had an Open Graph tag
Every route hand-wrote <title> and <meta description> and nothing else, so a
link shared to X, Discord, Slack or iMessage rendered as a bare grey URL, and
nothing but /games/[appid] had a canonical. One <Seo> component now owns the
head for all 30 routes: OG, Twitter, canonical, optional JSON-LD, and the
site name that had been spelled out in 20 files.
og:image is absolute from a constant, not from page.url.origin - during
prerender that is SvelteKit's internal "http://sveltekit-prerender" host,
which would have been baked into every static page.
ChartPage's `subtitle` becomes required. It was optional, which is what let a
chart page ship with no description and look entirely normal.
## The social card and icons did not work at all
og:image pointed at an SVG - X, Facebook, LinkedIn, Slack and Discord all
refuse SVG previews - and the PWA manifest offered SVG icons only, which
Android's installer and apple-touch-icon do not accept. The old mark drew a
"▶" as an SVG <text> element in font-family="system-ui", i.e. a different
shape on every platform and tofu where no font had the glyph, in the slate
palette the rewrite replaced.
static/icon.svg is now the single source of the mark as real geometry, and
scripts/gen-icons.py derives the PNG icons and a 1200x630 card from it, set
in the actual brand typefaces. theme-color was still slate #0f172a; it is now
two entries, because one value can only ever be right for half the users of
an app with a real light mode.
## sitemap.xml listed four URLs, three of them github.com
And not one of the app's own routes. It is now a prerendered endpoint driven
by import.meta.glob over the route table, so adding a page adds a sitemap
entry with no second list to remember: 33 URLs, all on-site.
## Also
- Both remaining ECharts [Violation] warnings, measured before and after.
"setTimeout took 122ms" is gone: zero long tasks while four charts init,
because IntersectionObserver moved each init out of the shared frame. The
non-passive mousewheel one needed a real fix - zrender binds BOTH `wheel`
and `mousewheel` with no options object, unconditionally, with no dataZoom
anywhere. Four blocking listeners for two charts, measured. EChart.svelte
now swaps addEventListener for exactly the duration of init(). That is
scroll jank, not just console noise: the charts sit inside the page's
scroll container. charts.test.ts asserts no chart uses dataZoom or roam,
since a passive listener cannot preventDefault.
- errors.403 told visitors to "check your token in Settings" and errors.419
was titled "Session expired". Sign-in was removed; there is no token and no
session. 419 is dropped from ERROR_CODES because nothing can produce it,
along with three keys nothing referenced.
- og.png is excluded from the precache. @vite-pwa/sveltekit adds every static
asset regardless of globPatterns, so 145 KB that only crawlers ever fetch
was going into every install.
49 new tests, each one mutation-checked: relative og:image, a route with no
head, and a missing entry in the not-prerendered list were each confirmed to
fail the suite before being restored.
check / 95 tests / build / knip / wrangler dry-run clean. Eleven routes walked
in a real browser with zero console messages.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Four regressions the port had introduced, all found by looking at the running
app and at knip rather than by assuming the migration was complete.
## The app did not hydrate at all
SvelteKit emits exactly one inline <script> per page - the hydration bootstrap
- and offers no way to avoid it. Under _headers' `script-src 'self'` the
browser blocked it, so every page rendered its prerendered HTML and then sat
there completely inert. Measured in a real browser, on every route:
Executing inline script violates ... directive 'script-src 'self''
The CSP now lives in svelte.config.js under kit.csp with mode "hash", so
SvelteKit computes that script's sha256 at build time and emits the whole
policy as a <meta> tag that already trusts it.
The header CSP had to GO, not relax: browsers enforce the INTERSECTION of a
header policy and a meta policy, so leaving `script-src 'self'` in _headers
would have kept blocking the script whatever the meta allowed. One directive
is lost in the move - `frame-ancestors` is ignored in a meta CSP - so
X-Frame-Options: DENY in _headers is now load-bearing rather than
belt-and-braces.
Verified after: hydration confirmed by 26 virtualised rows existing (they only
exist if the client ran), both fonts reporting "loaded", and a fresh tab
walking /about and /charts/genres with ZERO console messages. The font
"preloaded but not used" warnings were a symptom of the same thing and are
gone with it.
## The PWA was simply missing
@vite-pwa/sveltekit was installed and never configured, so the build emitted no
service worker at all - no offline support and no update flow, both of which
the React app had. Configured with the runtime caching carried over verbatim,
including the reasons: NetworkFirst for /api/data/* because index.json carries
last_updated and serving THAT from cache strands every reader on stale records,
and the navigateFallbackDenylist because an installed SW answering /admin from
the app shell would serve the public shell where the Access gate is expected.
## Two modules ported but never wired up
- external-link-interceptor: the Tauri webview blocks window.open() and
target="_blank" to external http(s), so without it every external <a> in the
packaged builds dead-clicks.
- android-update: Android has no native Tauri updater (the plugin is
desktop-only), so the APK checks GitHub Releases itself. Both packaged apps
had silently lost a feature.
## knip was blind to the whole UI
Its project globs were still {ts,tsx} from the React era, so after the
migration it could not see a single .svelte file and reported the entire UI
dependency tree as unused. Fixing that is what surfaced the three items above,
plus two primitives I wrote and never used. No unused files or dependencies
remain.
CLAUDE.md updated: six of its notes described a React app that no longer
exists, which is worse than no note - an agent reading it would go looking for
files that are gone. It now records the four traps this change cost:
the CSP-must-not-be-in-two-places rule, adapter-static's fallback overwriting
index.html, nothing gating markup behind onMount, and $state being required for
a value an $effect must react to.
check / test / build / knip clean. 46 tests.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
All 30 routes now serve: the eleven chart pages, both leaderboards, health,
activity, about, settings, donate, the four new surfaces (/stats, /developers,
/publishers, /games/[appid]) and the in-app /legal/[doc] viewer. Verified
through a real `wrangler dev` - all 30 return 200, and security.txt, robots.txt
and sitemap.xml still serve as static files.
## /legal/* exists, and no markdown code ships
This settles the sanitizer question the plan left open: the answer is that
none of it reaches the browser. +page.server.ts runs ONLY on the server -
here, at build time, because the route is prerendered - so unified/remark/
rehype live in the build and the HTML is baked into the page. Verified the
client bundle contains no markdown library at all. No {@html} of anything
unparsed, no CSP change, nothing to reason about at runtime.
rehype-sanitize is still applied. It costs nothing at build time and the
alternative is a build that silently starts emitting whatever a future
contributor puts in a legal document.
Relative links inside the documents are rewritten: `docs/ToS.md` becomes
/legal/tos where a route exists, everything else goes to GitHub. Without that
the prerenderer follows them and the build dies on `404 /SECURITY.md` - which
it did.
## Two prerendering bugs, both found by reading the output
**Every page shipped an empty body.** The layout gated its markup behind
`{#if ready}`, set from onMount - which does not run during prerender. So the
entire SEO purpose of the migration was defeated: dist/legal/tos.html had 296
bytes of comments, no <h1>, no article text. Removing the gate is safe because
`en` is statically bundled as the i18n fallback, so t() returns real strings
from the first render.
Consequence of that: the consent gate had to stop being a replacement for the
page. It returned children-or-gate, so every prerendered page's HTML would
have been the consent dialog rather than its content. It is an overlay now -
crawlers see the real page, visitors still cannot use the site until they
accept. Measured after: /legal/tos 5,457 chars of text, /about 3,663.
**The home page was overwritten by the SPA fallback.** adapter-static writes
the prerendered pages and then writes the fallback over whatever shares its
name, so `fallback: "index.html"` replaced the prerendered `/` with an empty
shell - the most important page on the site, at 3,403 bytes of comments.
Renamed to 200.html; index.html is now the real dashboard at 45 KB.
## Other things fixed while porting
- The anti-cheat pattern table was duplicated between the list page and the
chart. Extracted to lib/anti-cheat.ts, which also keeps is_kernel_ac's THIRD
state: null means nobody checked, and folding it into "user-mode" would
claim something the data does not say. It is its own bar.
- The tag cloud draws 60 words, not 100, and picks colours deterministically.
The React version called Math.random() per word on every render, so the same
tag changed colour on each repaint and the palette meant nothing - and
wordcloud layout was the biggest contributor to the reported 122ms
setTimeout violation.
- Charts use meaning-bearing tokens (--success/--warning/--destructive) where
a colour carries information, and the accent ramp only for decoration.
- The About page's dependency list was wrong in six places and credited
OpenPGP.js, which is not a dependency at all. It now lists what actually
ships, typefaces included.
- Every leaderboard says "Top 100" and now shows 100; it was showing 40.
The i18n test earned its place twice more: it caught `donate.intro`/`outro`
and `health.allClear`, none of which existed. 457 keys, en and vi in sync.
Left deliberately undone, with the reasoning in the code: /games/[appid] is
NOT prerendered. Doing it needs a build-mode split (3,600 HTML files would
bloat the APK) and only the slow-changing fields could be baked in, since
daily data commits do not trigger a rebuild.
check / test / build clean. 46 tests.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The catalogue's main surface: virtualised table above md, virtualised cards
below it, Fuse search, five facet filters, sortable columns, paging, CSV/JSON
export. Verified against real data at 1440x900 - 3,666 rows, 37 pages.
Column labels are i18n KEYS now. All twelve were hardcoded English inside an
app whose every other visible string was translated, so a Vietnamese reader got
a Vietnamese page wrapped around an English table header.
Sorting parses before comparing, which is not optional here: current_players is
"492,197" and reviews is "86% (Very Positive)", so a raw compare puts "9" above
"1,000,000" and orders reviews alphabetically. Unrated sorts to -1 so "N/A"
clusters at one end instead of interleaving. Release dates go through
parseReleaseDate because "22 Aug, 2012" string-compares by day-of-month.
Third click on a sorted column CLEARS the sort rather than cycling back to
ascending - there was otherwise no way back to the natural order.
## One bug, found by looking at the DOM
Rows rendered blank while the scrollbar was the right height. `getTotalSize()`
was correct and `getVirtualItems()` returned nothing: `getScrollElement` is a
closure, so referencing `viewport` only inside it registers no dependency, and
the virtualizer was built once before `bind:this` had run, measured a null
scroll element and never rebuilt. `$derived.by` that READS `viewport` in its
body fixes it. Same fix in both the table and the mobile cards; the comment
names the symptom, because "correct scrollbar, no rows" does not look like a
reactivity problem.
## The i18n test
Two raw `{{n}}` placeholders reached the screen while building this page:
common.rowsPerPage is "{{n}}/page" and common.page is "{{current}}/{{total}}" -
whole phrases with numbers inside, not standalone labels. And the React table
called t("edit.openOnSteam") where `edit` was not a namespace at all, so that
tooltip rendered the literal key in production with nothing to flag it.
src/lib/i18n.test.ts now scans every .svelte and .ts file for literal t("...")
calls and asserts each key resolves to a string in en.json, that en and vi have
identical key sets, and that a key's placeholder set matches across locales.
Mutation-checked by injecting t("edit.openOnSteam") - the exact key that
shipped broken - which turns it red.
46 tests, up from 39. Locales at 430 keys each, still in sync.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The shell runs end to end against real data: consent gate, sidebar, topbar,
command palette, theme switching, i18n, the catalogue load, and a rendering
ECharts chart. Verified in a browser at 1440x900 and at mobile width.
## Data layer, without TanStack Query
lib/resource.svelte.ts is ~90 lines of runes replacing @tanstack/react-query.
What the app used from that library was isLoading/error/data/refetch, a stale
time and one refetchOnWindowFocus. Caching is deliberately NOT reimplemented:
the catalogue's real cache is IndexedDB keyed on index.json.last_updated, the
only invalidation signal this dataset has, and a memory cache on top would be a
second thing to get wrong. The three-step load (read cache, compare
last_updated, else fetch shards and parse in a worker) is carried over exactly.
## i18n gaps closed rather than carried forward
The plan listed eleven categories of hardcoded English inside an otherwise
translated app. Fixed so far:
- The seven KPI labels, which lived as string literals in KpiCards.tsx.
- formatRelativeDate, which returned "today" / "3d ago" / "2w ago" regardless
of locale. Now Intl.RelativeTimeFormat, which also handles pluralisation -
the part a template string per language cannot do.
- formatNumber, which hardcoded toLocaleString("en-US"), so a Vietnamese
reader saw 1,234,567 where their locale groups as 1.234.567.
- The command palette, whose 17 labels were the only untranslated strings in
the app. It is now built from the nav lists instead of its own array - which
had already drifted, missing /top-offline, /donate,
/charts/anti-cheat/list, /charts/delisted and /welcome.
en.json and vi.json go 353 -> 392 keys, edited together by script with the leaf
sets asserted equal, because hand-editing one is how they stop matching.
## Things fixed on the way through
- Ctrl-K now checks e.isComposing. Without it the shortcut fires mid-IME
composition and steals the keystroke, which made the palette actively
hostile to Vietnamese input - the locale it exists for.
- The theme "system" option now listens for prefers-color-scheme changes. The
React Topbar read matchMedia once and never subscribed, so "system" never
actually reacted.
- The Toaster took the resolved theme instead of a hardcoded "dark", which had
put a dark toast on a white page in light mode.
- The sidebar version is derived from __APP_VERSION__; it said "Steam · v1.0"
while package.json was 1.4.5.
- Distinct icons per nav row: Trophy was used for BOTH leaderboards and Shield
for two anti-cheat entries, which makes an icon useless for finding a row.
- legal.ts said "The 5 binding documents"; the licence split made it six.
- /legal/<slug> links are real links now. Welcome.tsx built that exact href
and then called preventDefault() to bounce to /about, because nothing was
there to receive it.
## Two bugs found by looking, not by guessing
**The chart rendered nothing.** ECharts initialised and created its container
but painted no canvas - which looks exactly like the unregistered-theme
failure CLAUDE.md warns about. It was not that: `chart` was a plain `let`, so
the setOption effect ran once while it was still undefined and never re-ran
when init assigned it. Making it $state fixed it, and the comment now names
both failure modes so the next person does not misdiagnose it the same way.
**Cloudflare Hotlink Protection is ON and the packaged apps survive it by
luck.** Every /img/* request from the dev server came back 403, body
`error code: 1011`. Measured against the live zone: no Referer 200, own-origin
Referer 200, but `http://localhost:5173/` 403, `tauri://localhost/` 403 and
`http://tauri.localhost/` 403 - the two origins the desktop and Android builds
actually load images from. They render today only because the Tauri webview
sends no Referer for <img>, which is not a guarantee anyone made: a WebView
update doing the ordinary spec-compliant thing would blank every image in both
apps with no change on our side. Written up as SECURITY_SETUP.md section 10
with the measurements and a recommendation to turn it off - it restricts
nothing that worker/routes/img.ts's anchored PATH_RE and host allowlist do not
already restrict, and Referer is client-set anyway.
## Still to port
The games table, nine of the eleven chart pages, about/settings/health/
activity/donate, /legal/[doc], and the four new surfaces (/stats,
/developers, /publishers, /games/[appid]). The foundation they all sit on -
routing, data, i18n, theming, charts, consent - is proven working.
check / test / build all clean; the 39 Worker tests are untouched by this.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
First step of the framework switch. The React UI is removed and replaced by a
building SvelteKit 2 / Svelte 5 shell; page porting follows. The React app is
in git at 290b1ad7 and is the reference for every port.
Nothing outside web/src changes: the Worker, wrangler.jsonc, the Python
pipeline and data/ are untouched, and /admin stays Worker-rendered HTML.
## The routing risk is settled, and it went the easy way
The plan named one blocker: SvelteKit has no HashRouter, and the React app used
one under isTauri() because "the Tauri webview has no server-side fallback".
That claim is out of date. tauri::manager::get_asset() resolves a miss through
<path>.html, then <path>/index.html, then index.html - read from tauri-2.11.1,
which is the exact version in Cargo.lock. So the packaged apps serve real paths
already, and adapter-static's fallback output works unmodified on Cloudflare
AND in both apps. No HashRouter, no hash shim, one build shape for two targets.
Written up in docs/plan/15-sveltekit-migration.md, including the honest caveat
that this is read from source and still needs the Phase 7 smoke test.
## Fonts exist now
index.css declared `--font-sans: Inter` and `--font-mono: JetBrains Mono` with
no @font-face, no link tag and no woff2 anywhere in the repo, so the app had
always rendered in system-ui. Three self-hosted variable faces, each with a
job: Bricolage Grotesque (display), IBM Plex Sans (body and the 3,400-row
table), JetBrains Mono (numerals).
scripts/gen-fontface.py generates src/fonts.css from Fontsource's own CSS,
keeping latin, latin-ext and vietnamese and dropping cyrillic, cyrillic-ext and
greek - 91 KB of a 308 KB payload, for scripts an en/vi app cannot render.
unicode-range values are parsed from Fontsource rather than transcribed,
because a mistyped range is a silent rendering bug on one character. Generated
rather than hand-written so a font bump cannot leave a stale range behind.
Verified in a browser: all three faces render, and the Vietnamese subset draws
"Phiêu lưu, nhập vai, chiến thuật" with full diacritics.
**Measured, not assumed:** the plan said to verify IBM Plex Sans has real
tabular figures before committing to it for the table. It does better than
that - every digit already renders at the same advance width (all ten at 24px
at font-size 40), so alignment holds with or without `tnum`. The utility is
kept because it states the requirement and protects a future face swap.
## The palette rework index.css deferred
In its own words: "The palette rework is a separate change." This is it. Off
the stock Tailwind sky-blue, which on Steam's own blue-grey surfaces is exactly
the generic look this was meant to fix; onto a warm amber accent over
warm-hued neutrals. Meaning-bearing colours (review scores, safety, anti-cheat)
deliberately do NOT follow the accent - they have to stay distinguishable.
Token format is unchanged (raw HSL channels), because two things depend on it:
@theme inline needs them bare for bg-primary/15 to resolve through color-mix(),
and lib/chart-theme.ts reads them with getComputedStyle at call time.
Also added three things index.css never had: a :focus-visible rule, a
prefers-reduced-motion block, and a skip link.
## Ported, not rewritten
lib/ is framework-agnostic and carries over as-is. The three files that were
not:
- lazy.ts -> chunk-error.ts. lazyWithRetry is gone (SvelteKit falls back to a
full page load itself), but the DETECTION stays, with the reason spelled out:
a deleted hashed chunk does not 404 on either host - Cloudflare's SPA
fallback and Tauri's get_asset both answer index.html at HTTP 200 - so the
check has to match the MIME-type message, not a status.
- chart-nav.ts - lucide-react -> @lucide/svelte.
- i18n/index.ts -> lib/i18n.svelte.ts. Replaces i18next + react-i18next +
the language detector with ~90 lines of runes. The locale JSON is untouched
byte for byte: converting 353 keys x 2 for Paraglide would have been 706
chances to typo text nobody proofreads. Keeps en statically bundled (it is
the fallback - a lazily-fetched fallback that failed would render raw keys),
vi dynamic, the same detection order, and the _one/_other convention.
## Housekeeping
public/ -> static/ (SvelteKit's convention). Verified _headers and
.well-known/security.txt still land in dist/. tsconfig now extends the
generated config; skipLibCheck restored deliberately - src/workers has a
`reference lib="webworker"` that clashes with lib.dom, and TypeScript resolves
`cookie` to the hoisted 1.1.1 from wrangler->miniflare->youch while SvelteKit
uses its own nested 0.6.0 at runtime.
check / typecheck / test / build / wrangler --dry-run all clean.
39 tests still pass - the Worker suite is unaffected by any of this.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
/admin had four API endpoints with no UI at all and a set of controls that
lied about what they would do. This closes both.
## Views that did not exist
/api/admin/audit, /api/admin/health and /api/admin/me had no consumer, and
/api/admin/stats returned commit_jobs counts the page fetched and discarded -
so the one table that records a commit attempt BEFORE it is made, the evidence
that a commit died mid-flight, was only readable through `wrangler d1
execute`. Added a view switcher with Queue / Commit jobs / Audit log / Health,
plus a /api/admin/jobs endpoint to back it.
## Controls that lied
- Approve and Reject stayed enabled on the approved/committed/rejected tabs,
where DECIDABLE guards both the server-side read and every UPDATE, so the
click always returned 409 with no hint why. Now disabled, with the bar
saying those rows are already decided.
- Reconcile had no busy state, so a double-click fired two ~6MB runs.
- Retire (edit page) had no guard at all, and the page had no busy flag: tab
switching, Discard, Load and the genre picker all stayed live mid-commit.
- Retiring a field with no override is a server-side no-op, and the page still
said "Retired genre". It now says nothing was committed.
- setMode() never cleared the other mode's state, so One -> Bulk -> One left
`dirty` populated while the counter reported bulk.sel.size - the count and
the payload disagreed.
- loadGenres() swallowed every error into an empty list with no message, so a
failure left both pickers empty and bulk mode silently inert.
- No beforeunload guard: an unsaved edit vanished on navigate.
## Search was a lie too
The filter box filtered the 60 loaded rows, so an appid on page 3 reported
"Nothing on this page matches that filter" - indistinguishable from "not in
the queue". Search is now server-side, with LIKE ... ESCAPE so a name
containing % or _ is matched literally. Verified against a local D1: the
escaped form matches 1 row where the unescaped form matches 2.
Also added sort (newest/oldest/players/reviews/name) as a closed set mapped to
fixed SQL, and rendered reviews_pct and current_players_num - both selected by
the API since the schema was written, with a comment saying they exist "so the
review screen can sort", and never once displayed. NULLS LAST verified in D1.
payload_json, stored verbatim on every insert and never surfaced, now has a
details dialog. MAX_DECIDE comes from the API instead of a client literal.
## The "Session expired" lie, and the third console error
Both pages treated ANY non-JSON response as an expired session. Combined with
the Worker having had no top-level try/catch, that meant every server crash
was reported to the reviewer as a login problem. They now distinguish the
cases, and use `redirect: "manual"` so an expired Access session is OBSERVED
as a redirect rather than followed to cloudflareaccess.com - which is exactly
what produced the reported
Connecting to 'https://polished-hall-48fd.cloudflareaccess.com/cdn-cgi/...'
console error: the CSP is connect-src 'self', so the cross-origin hop from
fetch() was blocked. Re-auth is now a full-page reload, which is the only way
Access can run its login flow.
## Tests
/admin cannot be loaded locally - it is behind Access and there is no way to
mint a JWT offline - so admin-ui.test.ts asserts everything checkable without
a browser: the nonce appears in both the header and the script tag and differs
per response, the actor is escaped (a hostile actor string does not survive as
markup), and crucially the emitted inline script PARSES. That last one is not
theoretical: the page lives inside a TypeScript template literal, so a
backtick in a comment silently ends it and a literal newline inside a JS
string is a parse error tsc cannot see. Both mistakes were made while writing
this change and caught by these tests; mutation-checked afterwards by
re-introducing each.
39 tests, up from 19.
## docs/ADMIN.md
Four corrections, all places the doc described something that does not exist:
the edit-drafts table (no such table - also fixed in wrangler.jsonc), the
`f2p-discovery` service-token NAME check (impossible - Cloudflare reports the
opaque Client ID - and it contradicted the accurate account earlier in the
same file), the parity test (now real, so it says what it actually is), and
"what is not built yet", which listed only audit pruning and now lists the
Worker's inability to delete an override file, single-field bulk mode,
selection loss across pages, un-rejecting being raw SQL, and the absence of a
cross-isolate reconcile lock.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
docs/ADMIN.md:473 says the CLI/Worker override parity is "asserted by a parity
test". There were NO tests in this repository at all - no *.test.ts, no
test_*.py, no vitest config, no test script. That claim is now true.
## The security defects, worst first
**Negative limit disabled the SQL bound.** admin.ts x2 and edit.ts all used
`Math.min(Number(raw) || fallback, max)`. Number("-1") is -1, which is truthy,
so `|| fallback` never fired and Math.min(-1, 200) is -1 - and SQLite treats a
negative LIMIT as NO limit. `/api/admin/audit?limit=-1` returned the entire,
never-pruned audit log; `?status=pending&limit=-1` the whole queue. Replaced
with clampLimit/clampOffset, which also truncate fractions (`?limit=1.9` bound
a non-integer). Table-tested, including a mutation run confirming the old
expression fails the new tests.
**exp was optional.** `typeof claims.exp === "number" && claims.exp < now`
accepts a token with no exp, or exp as a string - and such a token then never
expired. exp is now required; nbf, if present, must be numeric.
**CSRF was one heuristic deep.** access.ts accepts the JWT from the
CF_Authorization cookie, which a browser attaches to cross-site requests too,
so the fail-open Sec-Fetch-Site sniff was the only thing between a forced
cross-site POST and a repository write. State-changing requests now accept the
JWT ONLY from the Cf-Access-Jwt-Assertion header, which browsers never attach
on their own. curl and the discovery service token send it explicitly and are
unaffected; the Sec-Fetch-Site check stays as defence in depth.
**A key rotation locked everything out for an hour.** An unknown `kid` returned
null with no refetch against a 1-hour JWKS cache, so a Cloudflare rotation
denied admin AND ingest as an opaque 404. Now refetches once on a miss, floored
at 60s so junk kids cannot make this Worker hammer Cloudflare.
**An outage looked like a bad token.** A failed JWKS fetch threw inside the
catch-all and became 404. It is now AccessUnavailableError -> 503.
**Every server crash was reported as "Session expired".** fetch() had no
try/catch, so any throw became a Cloudflare 1101 with an HTML body - and both
admin pages sniff Content-Type and report exactly that string. The single most
misleading diagnostic in the admin surface, and it hid real D1 and GitHub
failures. Dispatch moved into route(); fetch() wraps it and logs the detail.
**A failed audit row reported a successful write as failed.** audit() was
awaited AFTER the commit landed and outside any try, so a D1 hiccup told the
reviewer the approval failed when it had already committed - and they would
retry it. Now best-effort with a loud log. edit.ts had its own copy of the
INSERT with the same defect; both use lib/audit.ts.
**A reject could downgrade an approval.** reconcile.ts writes
ingest_decisions('approved') only after observing the appid in data/, using DO
NOTHING; reject used a bare DO UPDATE, so the two disagreed about who may
overwrite whom. Added `WHERE ingest_decisions.decision <> 'approved'`, verified
against a real local D1: the approved row keeps its decision, reason and
attribution, the rejected row still updates.
**header_image was unvalidated.** Length-capped only, then rendered in an <img>
on the review screen; the page CSP happened to block it, which is the wrong
thing to rely on. Now must be a Steam CDN URL. Caught while testing: 100% of
the 3,665 real header_image values carry `?t=<mtime>`, so a pattern without it
would have blanked every queued game's image. All 3,665 pass; evil.com,
javascript:, data:, and the steamstatic.com.evil.com suffix trick do not.
**Concurrent reconciles.** The 15-min cron and the manual button could both run
a ~6MB fetch, and the button has no busy state. Added a per-isolate in-flight
guard, with a comment honest about its scope: cross-isolate overlap is still
possible and is left alone because every write there is idempotent.
**/api/admin/health echoed raw D1 and GitHub error text**, the latter including
GitHub's response body via github-app.ts. Now a status enum; detail to logs.
## Tests
19 tests. override-doc.test.ts round-trips the four REAL committed
data/overrides/*.json files - all Python-written - through the TypeScript
serialiser and asserts byte equality, which tests the actual property against
actual production data rather than a fixture written to match the code. edit.ts
now calls that shared serialiser instead of an inlined copy, so the test covers
the path that runs.
Verified the tests can fail: three mutations (old clamp expression, dropped
trailing newline, indent 4) each turned them red.
Wired into web-ci.yml, and into check-overrides.yml - which did not trigger on
web/worker/routes/edit.ts, so the "change one, change the other" mirror had no
CI enforcement in either direction.
## knip was blind to the entire Worker
knip.json's project globs were src/** only. Adding worker/** immediately found
five dead exports in the module holding the repo-write credential: commitFile
(deleted - an unused wrapper), readHeadAndFile, installationToken,
MANUAL_FIELDS and adminCsp (all now module-private). worker/env.d.ts is
ignored: it is an ambient declaration nothing imports by design.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Fixes two of the five reported console errors, and narrows the site CSP to
connect-src 'self' as a consequence.
## The avatar error
Loading the image 'https://avatars.githubusercontent.com/in/15368?v=4'
violates the following Content Security Policy directive: "img-src ..."
Activity.tsx rendered commit.author.avatar_url straight from the GitHub API.
avatars.githubusercontent.com appears in NONE of this repo's four CSPs
(_headers, admin-ui, edit-ui, tauri.conf.json), so every avatar on /activity
was blocked - in the browser and in both packaged apps. `in/15368` is the
pipeline's GitHub App; verified live, the page requests exactly three avatars
(in/15368, in/29110, u/127664709).
Widening img-src was the smaller diff and the wrong call: it puts a
third-party host back in the page and hands every visitor's IP to GitHub,
which PRIVACY_POLICY.md says does not happen. Instead /img/gh/{u|in}/{id}
proxies them, reusing the existing /img/ prefix so run_worker_first and the
service-worker CacheFirst rule both needed no change. Anchored regex, digits
only, fixed 56px size (a caller-chosen size is unbounded cache keys).
## /api/activity
The commits fetch was the last third-party request the public app made. It now
goes through the Worker, which also lets connect-src drop to 'self'.
Two things the proxy deliberately drops, both found by reading live output:
- commit.author.email, which GitHub returns for every commit and the page
never used. Forwarding it would make this a bulk email-harvesting endpoint
for everyone who has ever contributed.
- the commit message BODY. Only the subject line is rendered, and the bodies
here carry Co-Authored-By trailers with real addresses - the first version
of this route shipped them to every visitor from a publicly edge-cached
response. Sending the subject only also cut the payload 98,203 -> 30,324
bytes.
Edge-cached 5 minutes, keyed on the path alone so `?x=1` cannot mint cache
entries and walk past that. This bounds upstream traffic to ~12 calls/hour
against GitHub's anonymous budget of 60/hour, which a pass-through would
exhaust immediately since a Worker egresses from a shared address. It is NOT
authenticated: the GitHub App token is a repo-write credential and has no
business on a public route. Carries ACAO: * for the same reason /api/data/*
does - the Tauri builds read it cross-origin from tauri://localhost.
## security.txt
web/public/.well-known/security.txt (RFC 9116). It had to be a real file:
not_found_handling is "single-page-application", so a request for it returned
dist/index.html at HTTP 200 and scanners got a web page with no error.
Verified it now returns text/plain. Expires 2027-09-01; renewal is logged as a
recurring task in SECURITY_SETUP.md.
## Header gaps found while in here
- worker/index.ts's unauthenticated /admin 404 shipped NO security headers -
it was the one response built by hand instead of through jsonError. It now
uses withSecurityHeaders(), which was exported and never called.
- admin-ui.ts and edit-ui.ts contained byte-identical copies of the CSP for
the only origin holding a repository-write credential. Extracted to
adminCsp()/adminHtmlResponse() in lib/http.ts; a hardening change applied to
one copy and not the other is invisible. Adds an explicit object-src and the
Cross-Origin-Opener-Policy the SPA had and these pages did not.
- SITE_ORIGIN was duplicated in fetcher.ts and image.ts with the same comment.
A third caller made lib/site.ts the right shape.
## Two things the maintainer must do, both dashboard-only
Recorded in SECURITY_SETUP.md sections 2 and 9:
- HSTS preload: the header already carries `preload` and the domain passes
hstspreload.org's preloadable check with {"errors": [], "warnings": []},
port 80 301s to HTTPS. Status is still "unknown" = not submitted. Submission
is irreversible on any useful timescale, so it is yours to make.
- Cloudflare Web Analytics is ON and injecting static.cloudflareinsights.com's
beacon at the edge, which our own script-src 'self' blocks - two CSP errors
on every page load of the live site, and analytics that have never collected
anything. Not in the repo; curl of the deployed HTML shows no such tag.
Recommend turning it off rather than allowlisting, since the privacy policy
promises no third-party resources.
Verified against a local `wrangler dev`: avatars 200 through the proxy, all
malformed avatar paths 404, Steam variants unaffected, /api/activity
unauthenticated and 200, /api/data CORS intact, /admin 404 now carrying
headers, and zero requests to any GitHub host from the browser. typecheck,
build, wrangler --dry-run and knip all pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Nine maintainer channels collapse to two: the email, and
https://poli0981.dev/links/ as the single source of truth for everything
else. Handles now live off-repo so a retired account cannot strand a dead
link in a shipped build — which had already happened three times.
Replaced lopop05905@proton.me at all 6 sites (AUTHORS.md, SECURITY.md,
docs/Contact.md, username.txt, and both the handle and the mailto: href in
About.tsx). Edited by hand rather than by regex: a naive email pattern
misses the 10 `github-actions[bot]@` occurrences and matches things that
must not change (the you@example.com placeholder, 128x128@2x.png, the
data/overrides set_by identities, ~200 `uses: …@v6` action pins).
Stale content removed or corrected while in here:
- CONTRIBUTING.md carried a whole WARNING block about whitelisting a
Telegram user_id for a bot that no longer exists. Replaced with a
general "public and permanent" privacy note.
- docs/Contact.md had an orphaned bullet body (lines 17-19) left behind
when the Telegram ingest bot was deleted — no title line, dangling
arrows. Section rewritten; it now says outright that the bot and the
issue template are gone and the extension is the only submission path.
- docs/ADMIN.md credited temp_info.jsonl's appends to "the issue workflow
and the Telegram bot". Both are gone; the producers are the extension
and this Worker.
- README.md described CONTRIBUTING as covering "web-app sign-in, Telegram
bot flow" (both removed) and ToS.md as holding Telegram user_id rules
(it no longer mentions them).
- CODE_OF_CONDUCT.md had no reporting address at all. Added one.
- Two legacy /#/about URLs now point at the real /about path.
- Deleted the dead Telegram QR assets and the About page card that
displayed one.
Licensing claims corrected in AUTHORS.md and twice in About.tsx: all
three still said the whole repo including data was MIT. The dataset moved
to CC BY 4.0 in LICENSE-DATA and these were the last places asserting
otherwise.
SECURITY.md's parenthetical claimed the address was published in
CONTRIBUTING.md — it never was, only a pointer. Replaced with the real
list plus a forward reference to the security.txt added next.
typecheck and build pass; knip reports only the pre-existing backlog.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Edited in /admin by k30021424@gmail.com.
Reason: change to RTS
Standing instruction re-applied by save_main() on every write to data/. See scripts/core/overrides.py.
App 1.4.4 -> 1.4.5 (web, desktop, Android); repo 3.4.2 -> 3.4.3. Same files
the previous release commits touched: package.json, package-lock.json,
Cargo.toml, Cargo.lock, tauri.conf.json, the README badge, and a CHANGELOG
entry covering everything since v3.4.2 - the move to free-steam-games.win, the
discovery + /admin review flow, durable overrides, the CC BY data licence,
description truncation, real URLs, security headers, and the Tauri CSP + CORS.
The Android versionCode is derived by Tauri from `version`, so
build.gradle.kts is untouched. Both binary workflows publish DRAFT releases;
the packaged builds must be smoke-tested before they are published.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The setup guide recommended two rate-limiting rules at one minute each with
Managed Challenge. The Free plan allows exactly ONE rule and fixes most of it:
IP counting only, a 10-second period, a 10-second timeout, path and
verified-bot fields only, cached requests counted. Rewritten as the single rule
this site should have: /img/* and /api/data/* together, 150 requests per 10
seconds, Block, verified bots excluded. Block is tolerable precisely because
the Free timeout is fixed at 10 seconds — a false positive costs ten seconds of
missing thumbnails, not a lockout.
It also said to turn Bot Fight Mode on. That was wrong for this site.
Cloudflare documents that it "may challenge API or mobile app traffic" and that
it cannot be bypassed with WAF custom rules or Page Rules. The desktop and
Android apps fetch /api/data/* with plain fetch() and the discovery workflow
calls /api/ingest/* from GitHub Actions — a challenge page would break both,
with no way to exempt them short of allowlisting GitHub's runner ranges. The
guide now says to leave it off, and why.
HSTS: the guide and web/public/_headers now say where it comes from. It is set
by the Cloudflare zone and stamps every response, static and Worker alike,
verified live on /, /api/data/* and /assets/*. It is deliberately not repeated
in code, which would risk a second Strict-Transport-Security header — browsers
honour only the first.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
## The regression
The desktop and Android apps fetch the catalogue with plain fetch() from
https://free-steam-games.win/api/data/*. Their origin is http://tauri.localhost
(Windows/Android) or tauri://localhost (macOS/Linux), so that is a cross-origin
request. Before the Cloudflare migration they fetched raw.githubusercontent.com,
which answers every origin with `Access-Control-Allow-Origin: *`. The Worker
proxy that replaced it sent no CORS header at all.
Verified with real Origin headers against production: raw.githubusercontent
returns `*`; free-steam-games.win returned nothing for either Tauri origin.
The released apps were never affected: desktop-v1.4.1 and android-v1.4.4 were
built before the migration and still read raw.githubusercontent directly. The
bug was latent — ANY build made from main since the migration could not load
the catalogue, so it would have shipped in the very next release. This fix is
therefore a prerequisite for tagging 1.4.5, not a repair of the field.
/api/data/* now sends `Access-Control-Allow-Origin: *`. `*` is right for
exactly this route: it is the same public dataset raw.githubusercontent serves
to everyone with `*`, and no credentials ride on it. Verified locally that both
Tauri origins get it and that /api/admin/* still returns no CORS header at all
— it must never be copied there. Images need nothing: they load through <img>,
which does not use CORS, and nothing in the app sets crossOrigin.
## The CSP
tauri.conf.json had `csp: null`. It now has a policy mirroring the web one,
plus what the webview specifically needs:
- `connect-src ipc: http://ipc.localhost` is REQUIRED. Without it every
invoke() — shell:open, the updater, the http plugin — fails silently, and
none of that reproduces under `tauri dev`.
- https://free-steam-games.win in connect-src and img-src, since in Tauri the
data and /img/* are cross-origin rather than 'self'.
- script-src 'self' is safe: Tauri appends nonces/hashes for its own injected
scripts at compile time.
`cargo check` passes, so the config parses and the capability ACLs resolve.
What it cannot prove is runtime behaviour in a packaged build; that needs a
smoke test before the next desktop-v* tag — open the app, confirm the
catalogue loads, click an external link (shell:open), and let the updater run.
Committing this does not ship a binary; releases are tag-driven.
Also corrects bundle.longDescription, which still claimed 1,200+ games, an
editor, and data read from raw.githubusercontent.com.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Every URL was /#/games/730. Hash routes are not shareable in any meaningful
sense and are not indexable: search engines drop the fragment, so the whole
catalogue collapsed to one page in their eyes.
The router is chosen per platform. The web gets BrowserRouter, which works
because the Worker's `not_found_handling: "single-page-application"` serves
index.html for any path — verified: /charts/genres, /games/730 and /about all
return 200 text/html. Tauri keeps HashRouter, because its webview serves the
bundle from its own asset protocol with no such fallback, and a real path
would 404 on refresh.
Old links keep working. upgradeLegacyHashUrl() rewrites /#/charts/genres?x=1
to /charts/genres?x=1 before the router first reads the URL, with
replaceState so Back does not bounce to the old form. Only `#/…` is rewritten;
an in-page anchor like /charts/anti-cheat/list#vac is left alone. Both
verified in a browser on a full page load — the upgrade runs on load, which is
exactly when a bookmark or a search result is opened.
Two hardcoded hrefs assumed the hash router: "#/health" in the game drawer and
`#/games?search=…` on the Health page. Under BrowserRouter those resolve to
the current page plus a fragment, i.e. they silently stop navigating. Both are
router <Link>s now, which render /health on the web and #/health in Tauri.
The service worker needed no change: its navigateFallbackDenylist already
excludes /api, /img and /admin, so a navigation to /admin still reaches the
Worker instead of being answered with the cached SPA shell.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The field held each publisher's store blurb verbatim — median 213 characters,
longest 340. At that length it reproduced whole blurbs rather than quoting from
them, which is not what LICENSE-DATA claims it does when it calls them "short
identifying quotations" and excludes them from the CC BY grant. This makes the
claim true.
Measured: 2,156 of 3,426 rows (63%) shortened, data/ 671 KB -> 517 KB (-23%),
no stored value now exceeds 180 characters.
Truncation happens in exactly ONE place — save_main(), the same choke point
apply_overrides() uses. `description` has three write paths (apply_details in
fetcher.py, merge_extension_data and the legacy desc->description migration in
data_store.py), so putting it at any of them would have left the others
producing full-length values and the shards flip-flopping between writers.
save_main() is the only code that writes data/data_*.jsonl, so covering it
covers everything, including any future writer.
Idempotent by construction: the result is always <= the cap, so a second pass
returns it unchanged. Verified on the real catalogue — a second run reports 0
records changed. That property is load-bearing rather than nice-to-have,
because this runs on EVERY write to data/; without it the truncator would nibble
a character off every description on every run and rewrite all five shards
forever.
Cuts on a word boundary when one falls in the last 40% of the budget, so a
blurb whose tail has no spaces keeps its text instead of losing most of it, and
the ellipsis is included in the 180 rather than pushing past it. Verified
byte-level: U+2026, e2 80 a6, not a mojibake three-dot.
Deliberately does NOT bump each record's last_updated. That field means the
game's data changed; shortening how much of a publisher's blurb this repository
stores is a change to our representation, not news about the game. Bumping it
would have shown ~2,150 games as freshly updated on the Activity and Health
pages on the day this first ran.
Ordered before apply_overrides() so a human decision always has the last word —
no override can set `description` today, but the ordering should not depend on
that staying true. Confirmed the live override (Draw Party, genre) survived the
full-catalogue rewrite intact.
The blurb is now attributed where it is actually read, not only in
LICENSE-DATA: the detail drawer carries a "Blurb by the publisher, via Steam —
shortened" line, translated in both locales. LICENSE-DATA's figures updated to
match the new shape.
Note this rewrites every shard, so index.json.last_updated moves and every
client's IndexedDB cache invalidates at once. That is expected and is why this
is its own commit.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The site had NO Content-Security-Policy. Static assets carried only HSTS (added
by Cloudflare at the edge) and X-Content-Type-Options; Worker responses carried
three headers. That is the gap this closes.
web/public/_headers covers static assets, worker/lib/http.ts covers everything
the Worker generates, and neither inherits from the other — a header that must
hold everywhere has to be added twice. Said so in both files.
The CSP was VERIFIED, not assumed: built the app, served it under the policy,
and walked /games, four chart pages, /about and /health. Zero console errors,
zero violations, images and lazy chunks all loading.
Two directives are shaped by measurement:
- style-src needs 'unsafe-inline'. Radix positions popovers and dialogs with
inline style attributes and ECharts sizes its canvas the same way — /games
alone renders 471 inline-styled elements. It is the acceptable half of the
trade: no user-supplied HTML is ever rendered, and script-src stays strict,
which is the directive that actually stops execution.
- script-src 'self' is safe despite an inline <script> in index.html: it is
type="application/ld+json", a data block that is never executed, so
script-src does not govern it. Checked the BUILT output, not the source.
Cross-Origin-Resource-Policy is deliberately static-only. Setting it on Worker
responses would have broken the Tauri desktop and Android builds, which run on
tauri://localhost and fetch /api/data/* and /img/* from this origin cross-site
(SITE_ORIGIN in src/lib/fetcher.ts and src/lib/image.ts) — every image blank,
catalogue never loading. Caught before shipping; the reason is in the code.
docs/SECURITY_SETUP.md documents what remains, each item with a command to
check it, because a setting you believe is on and is not is worse than one you
know is off. Two findings in it are worth surfacing here:
- HSTS is already max-age=31536000; includeSubDomains; preload — the maximum.
The domain is NOT on the preload list (hstspreload.org status: "unknown"),
but the list accepts submissions from ANYBODY for a domain whose header
advertises `preload`. Leaving the directive in means a third party can put
the domain on a list that takes months and a browser-vendor process to leave.
Either submit deliberately or drop the directive.
- Rate limiting belongs in a WAF rule, not in the Worker. A dashboard rule
rejects at the edge before the Worker runs; a Worker-side limiter has already
paid for the request by the time it says no, which is backwards for cost
control. Thresholds given (600/min for /img/*, 120/min for /api/data/*) are
derived from a measured session — /games issues index.json + 5 shards + ~30
thumbnails in one burst — not from a template.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
## /admin/edit
Genre is a dropdown instead of free text, built from the genres ACTUALLY in
use with their counts — the counts are the point, since they are how a vague
bucket announces itself ("Action" holds 287 games, "Adventure" 232). A
"Custom…" option still allows a value the catalogue has never used, and the
game's current genre is always offered even when absent from that list, so
loading a game can never silently change it.
New "Bulk by genre" mode: pick a genre, see everything carrying it, retag up
to ten in ONE commit. The cap is enforced in the UI (remaining checkboxes
disable, with "limit reached") and again on the server.
Supporting work:
- commitFiles() replaces commitFile(): several files in one commit, reading
the head and every file in ONE aliased GraphQL query so expectedHeadOid
still means what it says across ten files. Ten commits would be ten pushes,
ten workflow triggers and ten chances to land half a change.
- listByGenre() and genreCounts() in records.ts. Genres are counted by regex
over shard TEXT rather than parsing 3,426 records — verified to agree with a
full parse exactly (92 distinct, 3,426 games). listByGenre prefilters by
substring and only then parses, so cost scales with matches, not catalogue
size; an exact field check rejects the substring appearing in a description.
Found by driving the page: renderBulk() rebuilt all 60 cards on every checkbox
click, replacing the element just clicked and losing keyboard focus. Selection
now updates in place.
## Ingest: extension only
Removed the GitHub-issue and Telegram paths. Kept the browser extension, which
pushes to scripts/temp_info.jsonl directly, plus the /admin approve flow that
appends to the same file.
Deleted: bot-ingest.yml, ingest-from-issue.yml, ISSUE_TEMPLATE/add_games.yml,
docs/telegram-bot.md, and both copies of the bot QR.
Four things would have broken, and a fifth was already broken:
- BUILD BREAK. web/tsconfig.json sets noUnusedLocals, so removing the Telegram
and add-games UI orphans the PlusCircle and Bot icon imports — four TS6133
errors, web-ci red, site unbuildable.
- A live button. About.tsx linked issues/new?template=add_games.yml; GitHub
silently ignores an unknown template and drops the user on a blank form.
- CommandPalette linked "/add" — a route that does not exist. Every
`<Route path=…>` in web/src confirms it: left behind when sign-in and
in-app editing were removed, so selecting it navigated to the 404 page.
- notify-ci-failure.yml matches by exact workflow NAME and its own comment
warns a stale entry breaks silently.
- ALREADY BROKEN: README and CONTRIBUTING both linked
poli0981/free-steam-games-list-extension, which does not exist
(`gh repo view` → "Could not resolve"). The real repo is
poli0981/steam-f2p-extension. That was the link to the one path being kept.
README's Contribute section and CONTRIBUTING §2 still documented signing into
the web app with a Classic PAT — removed months ago. Both rewritten: the
extension is the submission route, issues are for reports, and discovery plus
/admin is how most games actually arrive now.
docs/ToS.md §5.1 governed sending a Telegram user_id to a bot that no longer
exists; removed, and TERMS_VERSION bumped 2 → 3 because ConsentGate exists to
re-ask when the terms change. Workflow counts corrected 24 → 23 in README and
SECURITY.md.
Kept deliberately: the maintainer's own @SkullMute0011 DM row and its QR, with
the "whitelist requests" framing dropped — that is a contact channel, not part
of the ingest path.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Stage 2. The Worker writes the same artifact scripts/edit_game.py writes,
data/overrides/<appid>.json, so the two producers are interchangeable and this
screen is presentation over a mechanism that already worked without it. The
Worker still never touches data/.
GET /api/admin/game?appid= current values + any existing override
POST /api/admin/edit set and/or retire fields
/admin/edit the page, linked from the review queue
Reading one record out of 6 MB. worker/lib/records.ts fetches shards as TEXT,
finds the literal `/app/<appid>/`, slices that line to its newline boundaries
and JSON.parses only it — the needle is anchored on both sides by the canonical
link format, so it cannot match a longer appid or hit text inside a
description, and the record is re-checked against its own `link` because the
needle can legitimately appear in a note. Shard names come from index.json
rather than being hardcoded, and which shard a record was found in is never
retained: save_main() re-chunks the catalogue every run, so that fact is true
only for one request.
git-commit.ts gains a generic commitFile() sharing appendLinks' retry, and an
anchored path ALLOWLIST. The App credential can write anywhere in the
repository; WRITABLE is what stops a bug upstream from turning that into a
general-purpose commit engine. data/ shards are not on it and must never be.
commitFile()'s builder is re-run on every retry against the file's current
text, so losing a race merges rather than clobbers.
Two properties are asserted rather than assumed, because both fail silently:
- The Worker's JSON output is BYTE-IDENTICAL to save_override()'s. Verified at
651 bytes each on a document containing non-Latin text, quotes, a backslash
and an embedded newline. Had the formatting differed, every edit alternating
between the CLI and the UI would have produced a whole-file diff.
- The Worker's validateValue() agrees with Python's validate_value() on 23
cases, including the ones that matter: `is_kernel_ac` as the STRING "true"
is rejected by both, a numeric genre is rejected by both, and both refuse an
empty value with the same reason.
The Worker's validator is deliberately the weaker copy. Python is
authoritative, runs on every pipeline write, and check-overrides.yml runs it on
every push — and because the App token is not GITHUB_TOKEN, an override commit
triggers that workflow. So a file the UI accepts but Python would reject fails
CI within a minute instead of sitting inert.
`was` is read server-side from the catalogue and never taken from the request.
It is the value Retire restores, so a client-supplied one would let a crafted
request rewrite history.
Verified by driving the real page in a browser against a stubbed API, which
caught a bug reading alone did not: save() set the result banner and the reload
that followed wiped it — the same defect fixed earlier in admin-ui.ts, and it
was present on both the save and retire paths. Also confirmed: dirty tracking
clears when a field is typed back to its original, the boolean select sends a
real `true` rather than the string, an unknown appid surfaces the API error
instead of a blank form, and the `<script>` payload in a game name renders as
text.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Stage 1 of editing existing games. Python only: no Worker, no D1, no new
credential, no UI. The client is the command line.
The problem it solves. MANUAL_FIELDS (anti_cheat, anti_cheat_note,
is_kernel_ac, notes, type_game, safe, genre) are protected only by
fill-if-empty — a scrape will not overwrite a non-empty value. That cannot
tell a human correction from earlier scraper output, so
`normalize_genres.py --apply`, which rewrites genre for EVERY game, silently
reverts a fix, and refetch_all.py re-fetches everything. Nothing in the repo
recorded that a human had ever decided anything.
So an override is not a one-time edit. It is a standing instruction at
data/overrides/<appid>.json, and apply_overrides() is called from inside
save_main() — verified to be the single choke point: 11 scripts call it and
grep finds nothing else writing data/data_*.jsonl. The correction is therefore
re-imposed as the last act of every write, and no script needs to know this
layer exists. Any future dataset writer inherits it for free.
Four designs were explored independently and all four converged on this same
hook, which is the main reason to trust it. Direct shard-writing from the
Worker was rejected by every judge: shard identity is unstable (save_main
re-chunks from scratch, so a game moves between shards), the commit must carry
a whole file, and index.json has to be bumped in the same commit.
Three rules that are not obvious, each of which is a real trap:
- An override may NOT set a field empty. The next scrape would refill it and
this layer would blank it again, rewriting shards on every run forever.
Clearing is what retiring is for; empty values are refused with that message.
- Retiring is not deleting. Deleting the file leaves the field pinned to the
human value, because fill-if-empty never restores the old one. A retired
entry keeps `was`, writes it back once, then permanently no-ops because the
values no longer match — self-cleaning and idempotent by construction.
- `notes` is shared with the pipeline, which appends its own segments
(Dead game / Delisted / No longer free!). Those appends are ONE-WAY:
mark_dead_games.py only calls append_note_idempotent() while is_dead is
False, so once a game is flagged the marker is never re-added. A plain
whole-value override of notes would erase it permanently, with nothing able
to restore it. preserve_machine_notes() re-attaches any marker the human
value would drop; the marker strings are asserted against their real
producers.
Deliberately tolerant at apply time: an unknown field, a bad value, a game no
longer in the catalogue, or a malformed file is counted and reported, never
raised — a typo must not abort a run that has already spent two hours scraping.
That tolerance is also why silence would be dangerous, so
.github/workflows/check-overrides.yml validates every override on push and PR.
Verified against the real dataset: 20 assertions covering apply, idempotency
(a second pass rewrites nothing and does not re-bump last_updated), survival of
a simulated refetch and of normalize_genres, marker preservation on appid
3632680 (a genuinely dead game carrying the marker), retire-then-inert,
rejection of all four bad-input classes, orphans, and one malformed file not
stopping the others. An end-to-end `--apply` on the live catalogue produced
exactly one changed line in one shard plus index.json.last_updated — no shard
churn. With no overrides present the hook costs one isdir() and returns.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
games/ held 1.8 MB of markdown regenerated from data/*.jsonl on every data
change: 18 all-games_part*.md files, anti-cheat-list.md, a README index of
them, and a .gen-hash checksum whose only purpose was to make regenerating
them cheaper. The web app has been the way to browse the catalogue since v3.0,
so these were a second rendering of the same records that had to be rebuilt,
committed and reviewed forever.
Kept: games/top-online.md and games/top-offline.md.
Removed with them, because nothing else used them:
scripts/generate_tables.py, scripts/generate_anti_cheat_list.py
.github/workflows/update-daily.yml ("Generate Markdown Tables")
.github/workflows/anti-cheat-list.yml
bash/daily.sh, bash/anti_cheat.sh
and the generate_tables call inside ingest.sh, purge.sh, refetch_all.sh and
ingest-from-issue.yml.
Nothing depended on the anti-cheat markdown: /charts/anti-cheat reads
data/*.jsonl, not that file.
Four references would have broken, two of them user-visible:
- web/public/sitemap.xml advertised all-games_part1.md to search engines, and
About.tsx had an "All games (markdown)" button. Both would now 404. The
sitemap entry is gone; the button points at data/ instead.
- .github/workflows/mark-dead-games.yml ended with
`gh workflow run "Generate Markdown Tables"`. That command exits non-zero
against a workflow that does not exist, so every successful dead-games run
would have finished red.
- notify-ci-failure.yml's allowlist is matched by exact workflow NAME, and the
file's own comment warns that a stale entry breaks silently.
Also fixed the stale poli0981.github.io URL in the bug-report template while
removing its games/*.md option.
Verified: typecheck, build, all 24 workflow YAML files parse, sitemap.xml is
well-formed, and no reference to the removed files survives outside CHANGELOG
and docs/plan (both historical).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Approved in /admin by k30021424@gmail.com.
Queued for scripts/ingest_new.py, which decides whether each game is actually free, reachable and not already present. This commit is a request, not a publication.
Re-ran the review that had 27 of 49 verifier agents die on a usage limit, this
time adjudicating each unverified claim against current code. 22 agents, none
failed. Most of the outstanding claims did not survive; four did.
**The retry was dead code.** appendLinks classified a stale-head rejection by
regex over GitHub's prose, requiring the literal substring "oid". GitHub
actually answers with type "STALE_DATA" and the message `Expected branch to
point to "<sha>" but it did not. Pull and try again.` — where the only variable
span is a hex sha, whose alphabet contains neither 'o' nor 'i'. So the pattern
could never match, the first lost race rethrew immediately, and MAX_ATTEMPTS
was unreachable for the one purpose the module documents it for. Worse, the
alternation DID match `Ref cannot be updated` — a permanent branch-protection
rejection — burning four round trips before reporting it as a race.
Now classified by fact rather than wording: the machine-readable "STALE_DATA"
type as a fast path, falling back to re-reading the head and comparing. If the
branch moved we lost a race and retrying is right; if it did not, the failure
will repeat identically and belongs in front of the operator now.
**reject and defer/requeue could overwrite a decided row.** approve carried
`AND status IN ('pending','deferred','failed')` on its UPDATE; the other two
used a bare `WHERE id=?`. Rows are pre-filtered by DECIDABLE when read, but
that is TOCTOU — an admin page held open across a reconcile, or two reviewers
acting at once, and a stale page could reject a game whose approval had already
been committed to Git, or one already published. All branches now carry the
guard, with a note at DECIDABLE saying why it is enforced twice.
**A reconcile that failed outright looked like success.** The "ok" argument sat
outside the ternary, so `index unreachable` and `shard unreachable` painted the
green banner. Split on the row count rather than the message — bail() always
reports checked >= 1 and the benign idle skip reports 0 — so it will not drift
when the wording changes. The banner now also reports aged-out rows and says
what to do about them, which the API returned and the UI discarded.
**docs/ADMIN.md never caught up with the per-route AUD refactor.** It still told
operators to add new AUDs to `ACCESS_AUD`, a var that no longer exists, and
still documented `INGEST_SERVICE_PRINCIPAL` and a `ingest: principal not
allowed` log line that were both removed in ed30c5da. Following it would
produce exactly the `aud mismatch` the section exists to prevent. Corrected,
with the two per-route vars tabulated, plus a table of the three
`reject_reason` values a `failed` row can carry and what each requires.
One correction the adjudicator made to itself, kept: renaming the service token
is NOT harmless. The Worker-side name check is gone, but the name still has to
match the Service Token rule in the Access policy.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Completes the human side of the ingest pipeline. 646 discovered games were
sitting in D1 with no way to act on them except wrangler d1 execute.
/admin review screen, served BY THE WORKER
POST /api/admin/decide approve / reject / defer / requeue, in bulk
POST /api/admin/reconcile run the reconciler now
GET /api/admin/stats per-status counts for the tabs
worker/lib/git-commit.ts GraphQL createCommitOnBranch -> temp_info.jsonl
worker/lib/reconcile.ts promotes 'approved' only after seeing data/
scheduled() the same pass, every 15 minutes
The page is served by the Worker rather than added to the SPA. The public app
has no sign-in and no editing — that was removed deliberately — so admin markup
and endpoint names have no business in a bundle every visitor downloads, and
/admin cannot fall through to the public shell if a route changes. It ships its
own CSP with a per-response nonce; every value from Steam or D1 is written with
textContent.
The three actions are deliberately asymmetric:
reject final and local. Writes ingest_decisions('rejected'), which is what
actually stops tomorrow's sweep re-offering the game — the partial
unique index only covers OPEN rows.
defer parks the row while keeping the appid blocked.
approve does NOT publish. It appends to scripts/temp_info.jsonl and stops.
Approve stopping there is the whole design. ingest_new.py still decides whether
a game is real, free and reachable, so a commit is a REQUEST, not an outcome.
Only reconcile.ts, after observing the appid in data/, may write
ingest_decisions('approved') — because /api/ingest/known feeds decided appids
back to the discovery sweep, and marking something decided that never got
published makes it invisible to every future sweep.
Commits use createCommitOnBranch so GitHub signs them (Verified), carry
expectedHeadOid so a concurrent pipeline commit is retried against the newer
file rather than overwritten, and APPEND — the issue workflow and Telegram bot
write to that file too. Because the App installation token is not GITHUB_TOKEN,
the push triggers Ingest New Game Links on its own.
Verified before committing: the page was rendered and driven in a real browser
against a stubbed API (Access makes /admin unreachable to anything but the
owner's login). That caught three bugs a read-through did not — the commit
confirmation being wiped by the reload that followed it, the master checkbox
staying ticked with nothing selected, and unsequenced loads letting a stale
response paint under the wrong tab.
An adversarial review of this code found more, of which the serious ones:
- A game could be lost permanently and silently. ingest_new.py SKIPS an entry
that hits a network error, writes nothing to removed_games.jsonl, then clears
temp_info.jsonl regardless — so the request is gone and the game is in
neither file. The row would sit in 'approved' forever, and since
/api/ingest/known counts 'approved' as known, no future sweep would ever
offer that appid again. No UI action could reach it either: 'approved' is not
in DECIDABLE. Approvals unobserved after 12h now age out to 'failed', which
is decidable, and re-approving re-commits the link. 12h, not less: ingest-new
shares the data-write concurrency group with ~115-minute jobs.
- removed_games.jsonl is unpruned history going back to March. Matching on
appid alone marked a fresh approval 'failed' on the strength of a months-old
entry, so a game that stopped being free and later became free again could
never be re-added. Now requires removed_at > decided_at.
- 'failed' is outside uq_queue_open_appid, so a failed row can coexist with a
new pending row for the same appid. Approving both violated the index inside
a D1 batch AFTER the commit had landed. Rival open rows are now stood down in
the same batch, before the promotion, and a desync is reported rather than
swallowed.
- appendLinks deduplicates its input; approving two rows sharing an appid wrote
the link twice.
- A no-op approval returned the branch head as its commit sha, so commit_jobs
and audit_log attributed an unrelated commit to the approval.
- "Select all on this page" ignored the active filter: filtering to one game
and ticking it selected all 60 loaded rows, 59 of them invisible, and the
next click would have approved them.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
`wrangler tail` settled what Cloudflare does not document: a service token's
identity arrives as its opaque Client ID —
ingest: principal not allowed { got: 'a5d1053e...access',
expected: 'f2p-discovery' }
— not its friendly name. The obvious fix was to paste that Client ID into
INGEST_SERVICE_PRINCIPAL, but that publishes half of a credential pair in a
public repo to shore up a check that was the weaker half of the design anyway.
The real defect is that ACCESS_AUD was ONE pooled list. verifyAccessJwt accepted
any AUD in it for any route, so the three credentials were interchangeable at
the JWT layer: an admin session satisfied /api/ingest/*, and the unattended
discovery token satisfied /api/admin/* — which holds the GitHub App credential
that can write to this repository. The name pin existed only to paper over that,
and a string comparison is a poor substitute for not accepting the token at all.
Now verifyAccessJwt takes the AUDs valid FOR THAT ROUTE:
ACCESS_AUD_ADMIN /admin, /api/admin/* (email policies)
ACCESS_AUD_INGEST /api/ingest/* (Service Auth, f2p-discovery)
A token minted for the wrong application now fails signature verification
rather than being caught downstream, so credential crossing is structurally
impossible instead of merely checked for. A second guard rejects the wrong
credential CLASS per route — service tokens are unattended and must never drive
admin; a human session must never drive ingest.
Neither AUD is a secret: any Access-covered path 302s to a login URL carrying
its own AUD as the `kid=` parameter, readable with an unauthenticated curl.
That is how both were obtained, and it is why they can live in the repo while
the Client ID should not.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
All three present as "the endpoint is broken" and each has a different fix.
Cloudflare documents the Service Auth requirement explicitly; the AUD
allowlist and the principal pin are this repo's own additions and were
undocumented.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The pin compared the JWT's `common_name` against the service token's friendly
name, but Cloudflare documents neither what `common_name` holds for a service
token nor how to find out — the friendly name and the Client ID are
indistinguishable from the Worker's side. A wrong guess 404s a correctly
configured caller, with the same bare 404 that means "no Access application
covers this path", so there is nothing to debug from.
Two changes, neither of which widens what is trusted:
- INGEST_SERVICE_PRINCIPAL is now comma-separated, so both spellings of the
SAME token can be pinned rather than betting on one. The credential still has
to be a service token and still has to be that token.
- A rejection now logs the identity Access actually supplied, so `wrangler
tail` answers the question instead of trial and error.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
`urlopen` follows redirects, so an Access login page arrived as HTTP 200
text/html and the script reported "expected JSON, got text/html" — which reads
as a broken endpoint when the real fact is that Access refused the credential.
Redirects are now surfaced rather than followed, and an Access login URL is
decoded from its own `meta` JWT, so the failure states what Access decided:
Cloudflare Access redirected to its LOGIN PAGE instead of accepting the
service token [aud=bd54655abb62... service_token_status=False
auth_status=NONE].
That separates the three failures that previously looked alike:
404, no redirect no Access application covers the path
302 to login page application exists, policy refuses service tokens
aud mismatch (in tail) application exists, ACCESS_AUD is stale
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Third Access application, third AUD. ACCESS_AUD is an allowlist the Worker
checks against the token's `aud` claim, so the application alone was not
enough — requests through it would have been refused with `access: aud
mismatch`, a failure that appears only once the application starts working and
reads as an unrelated bug.
Also moves the ACCESS_AUD comment back above ACCESS_AUD (it had drifted above
INGEST_SERVICE_PRINCIPAL) and records which tag belongs to which application,
plus how to read a tag off the Access login redirect without the dashboard.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
You spotted .wrangler cache in the repo. It was not a one-off: the root
.gitignore had no .wrangler rule at all (only web/.gitignore did), so anything
run with wrangler from the REPO ROOT rather than web/ lands unignored. That is
how .wrangler/cache/wrangler-account.json — Cloudflare account id and account
email — reached a public repo.
Auditing outward from that found three more credential shapes with no rule,
all of which this project's own docs tell you to create:
- .dev.vars / .dev.vars.* `wrangler dev` reads GH_APP_PRIVATE_KEY from here,
and the PEM is INLINE, so the existing *.pem and *.key rules never see it.
That App can commit to this repo. Highest-consequence gap of the three.
- *.jks / *.keystore / *.p12 / *.pfx web/src-tauri/TAURI.md walks you through
`keytool -genkeypair -keystore f2p-tracker-release.jks` using a RELATIVE path
inside gen/android/, and reassures you keystore.properties is ignored — while
the keystore itself was covered by nothing. Leak it and Android signing is
compromised; lose it and the app can never be updated.
- .env.production / .env.development matched none of .env, .env.local or
.env.*.local.
Two rules were silently hiding real source, verified with check-ignore:
- `env/` and `ENV/` are unanchored Python-virtualenv rules, so they matched
web/worker/env/ at ANY depth — Worker source would vanish from `git add .`.
(On this Windows checkout core.ignorecase makes ENV/ match env/ as well.)
- `[Nn]otes.md` matched docs/notes.md and docs/i18n/*/notes.md, the likeliest
filename for real documentation in a repo whose output is markdown.
Both anchored to the repo root. `build/`, `dist/` and the one-off script rules
anchored for the same reason; web/dist stays covered by web/.gitignore.
Two rules did not do what their comments claimed:
- `*.log` matches scripts/dead_games.log, which mark-dead-games.yml explicitly
stages and mark_dead_games.py appends to. It survives only because ignore
rules do not apply to already-tracked files — rename or recreate it once and
it disappears with no error. Now an explicit negation with the reason.
- `.vscode/` excludes the DIRECTORY, and git will not descend into an excluded
directory, so the four `!.vscode/*.json` negations under it were dead code.
Changed to `.vscode/*` so the exceptions actually apply.
Untracked (files left on disk, none referenced by any build):
- .wrangler/cache/wrangler-account.json account id + email, the reported file
- web/src-tauri/.tauri-signing.key.pub minisign F6E36504EAE8E3A2, which is
NOT the updater key in tauri.conf.json (9F39774AE5453C53). A stale pre-
rotation public key that web/src-tauri/.gitignore already forbids.
- .idea/.gitignore tracked despite the .idea/ rule
Verified: 21 check-ignore assertions both ways; the index delta is exactly
those three deletions (386 -> 383 files); no remaining tracked file is matched
by any ignore rule; nothing untracked is left unignored.
Also documents in docs/ADMIN.md that every new Access application needs its AUD
appended to ACCESS_AUD — omitted before, and it fails only after the
application starts working, which makes it look like an unrelated bug.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
docs/ADMIN.md offers `gh workflow run "Discover New Games" -f dry_run=true` as
the check to run after setting up the service token. It was not one. Both the
/api/ingest/ping and /api/ingest/known calls sat behind `if not args.dry_run`,
so a dry run exercised Steam, the search parser and the filters — everything
that was already working — and never touched the credential, which is the only
new and only fragile part. A dry run against a completely wrong token passed.
Both calls are read-only, so running them under --dry-run keeps it dry.
Credentials absent (a local dry run) now says so instead of silently skipping.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
sharp 0.35.2 reaches the tree only as a transitive dependency of
wrangler -> miniflare, so it is build-time only and never ships in dist/.
It still counts as an open high alert on the default branch, and the alert is
what people act on.
`npm update sharp` cannot move it: miniflare pins an exact "sharp": "0.35.2",
so the range admits nothing else. An override is the only lever short of
waiting for a miniflare release.
The 311-line lockfile diff is sharp's ~30 platform-specific @img/sharp-*
packages plus the @emnapi/@napi-rs WASM fallback runtime its wasm32 build
depends on -- nothing outside sharp's own subtree changes.
Verified: npm install clean, typecheck, build, and `wrangler deploy --dry-run`
all pass; `npm audit --audit-level=high` reports 0.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Actions evaluates ${{ }} anywhere in the workflow file, shell comments in a
`run:` block included. A comment explaining why an expression fallback was the
wrong tool here quoted the rejected form verbatim, and the quoted contexts do
not exist — so the whole file failed to parse and every push produced a failed
run with no jobs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three defects on the same path, all of which fail silently.
1. A queued request could vanish. The only commit came AFTER
`python scripts/ingest_new.py`, so a transient Steam failure aborted the job
with the appended line living nowhere but the runner's disk. Nothing was
committed, nothing retried, and the reporting step never ran to say so. The
queue entry is now committed BEFORE the ingest is attempted, so a failure
leaves a durable request instead of nothing.
2. The issue was answered "Game added!" for games that were not added. The
check was `temp_info.jsonl === ''`, but clear_temp() empties that file at
the end of every ingest_new.py run - including one where every entry was
rejected as duplicate, dead, or unreachable. It now asks the dataset, and
distinguishes "added" from "already in the catalogue" by snapshotting which
appids were present before the run.
3. The reporting step had no `if: always()`, so it only ever ran on the happy
path - the one case that needed no explanation.
Also gives `Ingest New Game Links` a 3-hourly schedule. This is orphan
recovery, not polling: `data-write` keeps at most ONE run pending and cancels
the older one, so an ingest queued behind a ~115-minute data job is evicted the
moment any other data-write workflow queues, and nothing retries it. Re-running
on a clear file is free - ingest_new.py returns immediately and
`git diff --staged --quiet` skips the commit - so it is idempotent by
construction, and it is what makes fix 1's "will be retried" true.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The repo had no code that could find a new game. update_data.py only enriches
records that already exist and ingest_new.py only reads a file a human filled
in, so "surface new releases within a day" needed a producer, not rewiring.
Three pieces, split so that discovery is automated and publication is not:
/api/ingest/* service-token-authenticated producer surface. Writes rows
with status='pending' and can do nothing else - it cannot
approve, commit, or reach the repository.
discover_new.py daily. Walks store search newest-first, stops after two
fully-known pages.
backfill_discover TEMPORARY. Sweeps one release window at a time to close
the historical gap, then gets deleted.
Measured today: Steam lists 16,668 free games under the catalogue's own
filters; data/ holds 3,424.
The backfill locates a window by BINARY SEARCH over search offsets rather than
walking from page 0. The store sort is Released_DESC, so offset is the date
axis and page_date() is monotonic - about 8 fetches to reach a 2024 window
instead of 90. Verified against live Steam: 2025Q4 located at page 21 in 7
probes.
Both scripts run under `permissions: contents: read` plus a grep step that
fails the run if either references save_main/save_jsonl/clear_temp/fetch_full.
The permission alone would block a push; the grep names the reason, which a
403 from git does not.
Fixes found while building this:
- _RE_RELEASED required a `col ` prefix the live markup does not have
(`<div class="search_released responsive_secondrow">`), so every search row
came back with an empty date. The cheap "Coming soon" skip therefore never
fired and each such title cost a full appdetails call to reject.
- Game names are publisher-controlled and routinely non-Latin. print() of one
raised UnicodeEncodeError on a cp1252 console, killing the sweep after every
Steam request had already been paid for.
The two Access credentials are pinned apart on both sides: verifyAccessJwt
accepts any configured AUD, so without an explicit principal check an admin
session would satisfy /api/ingest/* and - far worse - the ingest token would
satisfy /api/admin/*.
Neither workflow can run until a Cloudflare Access service token named
`f2p-discovery` exists and its credentials are repository secrets; they fail
loudly rather than skipping, and docs/ADMIN.md §7 has the setup.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Both found while designing the admin write path, both already in production,
and both lose data with no error anywhere.
ingest-from-issue.yml overwrote scripts/temp_info.jsonl with fs.writeFileSync.
That file is a shared queue with more than one producer — the Telegram bot
appends to it, and the admin Worker is about to — so a single [add-game] issue
destroyed every queued entry not yet consumed. The diff just showed a cleared
file. It now appends, and validates that each line of the issue's json block is
one complete JSON object before writing, because a pretty-printed block would
trip the second bug below.
load_jsonl wrapped its entire read loop in one try, so the first malformed line
ended the read and returned only the lines before it. ingest_new.py then
processed that partial list and called clear_temp(), truncating the file and
deleting every unread line after the bad one. A bad line is now skipped and
reported with its line number; only an OSError aborts the read.
The logging in that handler is deliberately ASCII. The first version used the
same warning glyph as the surrounding code and raised UnicodeEncodeError on a
cp1252 console — from inside the except block, which escaped the handler and
aborted the whole read, reintroducing exactly the loss being fixed. Logging in
an error path must not be able to throw.
Verified rather than assumed: the generated workflow JS passes node --check,
appending preserves a pre-existing queue entry, and load_jsonl now returns both
good lines from a file whose middle line is garbage.
Also saves the four design and adversarial-review documents behind this work to
docs/plan/.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
/api/admin/health returned 404 to an authenticated admin. Access had
authenticated the request correctly; the Worker then rejected the token.
Each Cloudflare Access application has its own AUD tag, and this Worker sits
behind two — one covering /admin, one covering /api/admin/*. ACCESS_AUD held
only the first, so tokens minted for the API application failed the aud check.
The page worked and every API call failed, which is a confusing shape for the
same underlying cause:
/admin -> aud ca93cf2c... (configured)
/api/admin/health -> aud a15d6e93... (not configured)
ACCESS_AUD is now a comma-separated list and verification passes if the token
carries any known tag. The check itself stays — dropping it would accept a
token minted for any other application in the same Access organisation.
Also makes this class of failure diagnosable. The client response is
deliberately opaque, and returning an identical 404 for "token rejected" and
"no such route" is what made a configuration problem look like a routing bug.
Both paths now log to Workers Logs — the aud mismatch reports what it got
versus what it allows, and a failed verification reports whether the request
even carried a token. Nothing extra is revealed to the caller.
Confirmed separately from the installation screenshot: the GitHub App is
installed on this repository with metadata read and contents read/write, so
the App itself was never the problem.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The prerequisites were already in place: the GitHub App secrets are set on the
Worker, and Cloudflare Access gates /admin and /api/admin/*. This adds the
Worker side.
AUTHENTICATION HAPPENS ONCE, IN THE ROUTER. worker/index.ts verifies the Access
JWT before dispatching to any admin handler, rather than leaving each handler
to remember. Access already gates these paths at the edge, so this looks
redundant — it is not. The path is not the security boundary; the credential
behind it is. A misconfigured route, a preview hostname, or a future refactor
would otherwise deliver an unauthenticated request to code holding
repository-write access.
Verification checks the signature against the team JWKS and, critically, the
`aud` claim. Without the aud check any token minted for any other application
in the same Access organisation would be accepted here. Issuer, exp and nbf are
checked too, and service tokens (which carry `common_name` rather than `email`)
are recognised as machine callers.
Unauthenticated admin requests get 404, not 401 — they learn nothing about what
exists, and Access has already redirected real humans to a login. /admin also
answers explicitly rather than falling through to the SPA handler, which would
serve the PUBLIC app shell at an admin URL.
GITHUB APP TOKENS. The App's private key never expires while the tokens it
mints last about an hour — the point of using an App rather than a PAT, given
a silently expired PAT stalled this pipeline for a month. One trap handled in
code: GitHub issues PKCS#1 keys ("BEGIN RSA PRIVATE KEY") and Web Crypto
imports only PKCS#8, so the Worker wraps the DER itself instead of leaving an
openssl step in a runbook for someone to skip. The app JWT backdates `iat` by
60s because Workers' clock can sit slightly ahead of GitHub's.
D1 SCHEMA (migration 0001). ingest_queue with a partial unique index allowing
at most one OPEN row per appid; ingest_decisions as long-term memory so a
rejected appid does not reappear in tomorrow's sweep; commit_jobs, written
before a commit is attempted so a crash mid-flight leaves evidence; and
audit_log, which records the acting Access identity and the target and
deliberately nothing about visitors — no IP, no User-Agent, no country. That
matches what docs/PRIVACY_POLICY.md states; the two must stay agreed.
Game records are NOT in D1. data/*.jsonl in Git remains the source of truth,
which is what makes losing this database survivable.
Endpoints are read-only for now: /me, /health, /queue, /audit. approve/reject
write to Git and are deliberately absent rather than half-working. /health
reports D1 and GitHub separately so a failure names itself, and its GitHub
probe exercises the private key, the installation and its permissions in one
call.
wrangler.jsonc also gains migrations_dir, which was missing — wrangler looked
in web/migrations and reported "no migrations present" while the file sat in
worker/migrations.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The previous commit staged these with `git add -A`; both had been left
uncommitted because they were wrong, so correct them rather than carry them.
username.txt said the Telegram QR codes were untracked. They are tracked —
assets/qr/telegram-bot.png and assets/qr/telegram-user.png — and CONTRIBUTING.md
and AUTHORS.md already link to those paths.
.gitignore carried a block ignoring app/dist, app/release and friends under the
heading "F2P Tracker desktop app (Electron + Vite)". There is no app/ directory
in this repo and the desktop shell is Tauri 2 with a Rust backend, so the block
ignored nothing and described the wrong technology. Replaced with the paths
Tauri actually produces. Verified the new rules match no already-tracked file.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The docs had drifted badly from the code. This makes them true.
LICENCE SPLIT. Code stays MIT; the dataset moves to CC BY 4.0 in a new
LICENSE-DATA, which is explicit about what the project cannot license: the
`description` field is the publisher's own store blurb stored verbatim (median
213 characters), `header_image` is a URL to publisher artwork, and game names
are trademarks used nominatively. Blanket-MIT over that material was a claim
the project was never entitled to make. Facts — player counts, review
percentages, platform support — are noted as unownable; the CC BY grant covers
the compilation and the project's own derived fields.
PRIVACY POLICY, rewritten rather than patched. The previous one said "no
backend, no server-side log, no cookies, no server other than GitHub's CDN".
Every clause of that is now false: the site runs on a Cloudflare Worker that
processes IP and User-Agent and keeps operational logs. It also documents the
one honest exception — the Activity page still calls api.github.com and loads
GitHub avatars from the browser, so GitHub sees a visitor's IP there while no
other page does — and lists every localStorage, IndexedDB and Cache Storage key
with why it exists.
SECURITY.md, rewritten. The old one claimed "no executable code, no
dependencies, no backend, no user data" and said there was no contact address,
while four other files publish one. It also told people to report
vulnerabilities in public issues. There is now a real scope (the Worker, the
proxies, D1, Actions secrets, the Tauri signing key), a private channel via
GitHub's vulnerability reporting, and specific things worth probing.
EULA corrected on two counts: it asserted a single MIT licence over everything,
and claimed there is "no installable software" despite the signed desktop and
Android builds. ToS and DISCLAIMER updated for the licence split, the new
domain, and the removal of in-browser editing and GPG signing — the disclaimer
described a signing flow that no longer exists.
README contradictions fixed: 1.2k games -> 3,424 across 5 shards not 2, 11
workflows -> 24, two scripts listed that were never in the tree, a TanStack
Table dependency the project does not use, and nine links to the old Pages URL.
New: docs/DEPLOYMENT.md (how a push becomes a deploy, the two wrangler.jsonc
fields that silently break it, and the stale-service-worker trap when verifying)
and docs/ADMIN.md (Cloudflare Access plus the GitHub App, with the exact
permission set — Contents write and Metadata only, and why Actions and
Workflows are deliberately withheld).
Two live fixes came out of writing this. GitHub Pages was serving a blank page:
it had the new index.html, which references assets at `/`, while Pages serves
under /free-steam-games-list/, so every asset 404'd — and deploy-pages.yml kept
redeploying it. That workflow now publishes a redirect that preserves the #/
fragment, since Pages cannot issue a 301. And CI pinned Python at 3.11, 3.12
and 3.14 across different workflows while the docs claimed 3.12 was pinned;
all fourteen references are now 3.12, which makes the claim true.
TERMS_VERSION 1 -> 2, so everyone re-consents. A privacy policy that now
discloses edge logging where it previously promised none is not a change to
apply silently.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Visual refresh, in three parts.
Palette. Replaces the stock shadcn slate/blue tokens with a deliberately
chosen set: a deeper, less saturated background, a brighter primary that reads
as its own colour rather than framework default, and a larger radius
(0.5 -> 0.625rem). Adds the semantic tokens the components had been
approximating with raw Tailwind classes — success, warning, info — plus
surface-2 and border-strong for elevation. Both themes get real values; the
light palette is no longer an afterthought.
Charts. They hardcoded roughly eighteen hex colours, so they ignored the theme
entirely and would have clashed with any palette change — and never responded
to the light/dark switch. A new chart-theme module resolves the CSS custom
properties at render time and supplies ECharts' default categorical palette
along with tooltip, text and grid colours. Colours that carry MEANING are
deliberately left alone: review-score green/amber/red and the platform brand
colours are data semantics, not decoration.
Information architecture. Eleven chart entries in the sidebar crowded out
everything else, and /charts merely redirected into /charts/genres, which hid
the other ten. The sidebar now has one Charts entry beside the leaderboards,
and /charts is a real index page describing each view. Both read from one
shared chart-nav list so they cannot drift apart.
Two subtitles were left describing removed features — Settings claimed
"Authentication, theme, and preferences" and Health advertised "maintenance
triggers". Both corrected in each locale.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The public app now offers viewing and interaction only — search, filter, sort,
charts, export — with no authentication surface at all. Editing moves behind
Cloudflare Access and a server-side GitHub App, which is the admin work that
follows; none of it belongs in a bundle every visitor downloads.
This deletes 32 files: the four auth panels, the auth and GPG stores, the
GitHub API client, OAuth device flow, the commit machinery (edits, git-data,
optimistic, verify-commit, jsonl-shard), the owner/commit hooks, the Add page,
the edit and bulk-edit drawers, DiffViewer, and the vendored openpgp copy.
The security argument is the main one. The old model kept a GitHub PAT *and* an
armored GPG private key in localStorage on a public origin, and gated write UI
purely client-side. Deleting it removes that exposure outright rather than
hardening it.
Surfaces that survive, with their auth dependencies severed:
- Activity keeps the commit feed, now fetched unauthenticated. Its "mine"
filter is gone: with no signed-in identity there is no "me" to filter on.
- Health keeps the validation report; the workflow-dispatch buttons go, since
triggering a run needs a write-scoped token.
- Settings keeps language and the introduction toggle.
- The games table loses its selection checkboxes, which existed only to feed
bulk edit and delete.
- The Android update check drops its Authorization header; the release list is
public and the anonymous rate limit is ample for a once-per-launch check.
Also removes openpgp, two Radix packages and @tauri-apps/plugin-http, now
unreferenced, plus the five i18n groups whose entire UI is gone (add, edit,
bulk, diff, verify — 102 keys per locale). Leaf-level i18n pruning was
deliberately NOT attempted: many keys are referenced dynamically, such as
nav entries via t(item.i18n), so a static sweep reports live keys as dead.
One trap worth recording: src/types/openpgp.d.ts carried the
vite-plugin-pwa triple-slash type references, despite its name having nothing
to do with them. Deleting it with the signing stack silently broke the types
for virtual:pwa-register/react. They now live in vite-env.d.ts.
Bundle effect: the precache drops from 1,992 KiB to 1,462 KiB across 53 rather
than 60 entries, and the 386 kB openpgp chunk is gone.
Primary locale is now English: index.html declares lang="en" and og:locale
en_US, with vi_VN as the alternate.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Radix logged a console error — not a warning — every time the mobile drawer
opened: DialogContent requires a DialogTitle for screen reader users. The
drawer had none, because sheet.tsx never exported a SheetTitle at all. The
three Dialog-based drawers were already correct.
Adds SheetTitle and SheetDescription mirroring dialog.tsx, and gives
MobileSidebar an sr-only title so the drawer is announced without changing
what anyone sees. aria-describedby={undefined} declares the absent description
as deliberate, which is what silences the companion warning.
Verified with the drawer open: aria-labelledby resolves to "Navigation" and
the console is clean.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A short introduction shown after the legal gate, never instead of it: the
consent gate still wraps the whole app, and /welcome is an ordinary route
inside it.
Content is deliberately limited to what someone needs before relying on the
list: what it is, the honest framing the project already takes in
docs/DISCLAIMER.md (inclusion is not a recommendation, the derived fields are
best-effort, no warranty), how often the data refreshes, three ways in, the
language switch, and the documents just accepted.
The seen-flag is versioned separately from f2p:legal_consent. They answer
different questions, and coupling them would re-run the introduction on every
legal edit, which reads as a factory reset. Settings gains a "show the
introduction again" action that clears the flag as well as navigating, so
leaving the page without pressing Continue does not silently re-arm it.
The page never blocks on the dataset: the count and last-updated date fill in
if useGames already has them and are simply absent otherwise, so first paint
does not wait on a network fetch. The count is run through formatNumber rather
than i18next's {{count}} — the raw form rendered "3424 games" two lines under a
topbar reading "3,424", and {{count}} additionally carries plural-selection
semantics that do not apply to a preformatted string.
Copy is written in both locales rather than English-only with a Vietnamese
fallback.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three problems, all introduced by the Cloudflare work in the previous commits
and all caught by the CI gate on its first real run.
1. `npm run dev` was broken. Moving the dataset and images onto /api/data/* and
/img/* meant `vite dev` answered both with the SPA shell, since it serves
index.html for any unmatched path. The dataset fetch then parsed HTML as
JSON, threw, and React Query retried in a loop — over a thousand requests in
one session — while every image resolved to text/html. A dev-server proxy to
the deployed Worker restores real data and real images with HMR intact.
Worker source itself still needs `npx wrangler dev`, which is noted inline.
2. `wrangler` was an unlisted binary. package.json scripts and web-ci.yml call
`npx wrangler`, but it was never a dependency, so CI would have resolved an
arbitrary version on every run. Pinned as a devDependency.
3. knip reported tailwindcss and tw-animate-css as unused because its project
glob covered only ts/tsx, and both are reached solely through @import in
src/index.css. Added CSS to the entry and project globs so those edges
resolve, rather than suppressing the finding.
Worth recording: knip was added to CI on the claim that it exits 0. That was
measured before these changes and was wrong — `exports` and `types` are
warn-only in knip.json, but unused files, unused dependencies and unlisted
binaries are not, and it correctly failed on all three.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Stages 0-2 of the free-steam-games.win migration.
Stage 0 — unblocked a pipeline that had been dead since 2026-08-13 and closed
two live problems: `npm ci` failed on an echarts peer conflict, and
ingest-from-issue.yml let any user commit to main via an issue title.
Stage 1 — React 19, react-router 7, Tailwind 4, i18next 26, TypeScript 6.0.3,
quinn-proto. All 18 npm advisories and the Rust one are cleared; npm audit
reports zero at every severity.
Stage 2 — the Cloudflare Worker, wrangler.jsonc, and same-origin /api/data/*
and /img/* proxies. This also fixes what the domain was actually serving: an
unbuilt index.html pointing at /src/main.tsx, with the whole web/ source tree
publicly readable.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The Worker name was "f2p-tracker", but the Worker holding the
free-steam-games.win custom domain is named "free-steam-games-list" (created
today, has_assets: true, production environment). Deploying under the old name
would have created a second Worker with no domain attached and left the live
site serving the current broken build, with nothing obviously wrong in the
build logs to explain it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Adds the deployment config and Worker that Cloudflare Workers Builds runs.
There is deliberately no deploy workflow — pushing main is what deploys.
Context for the base-path change, which the plan had scheduled later: the
domain is already live and already broken. It currently serves the repo's
web/ directory unbuilt, so `/` returns an index.html pointing at
/src/main.tsx (TypeScript the browser cannot execute) and the whole source
tree is publicly readable. `assets.directory: "./dist"` plus `base: "/"` is
what fixes that, and neither is useful without the other, so they land here.
wrangler.jsonc:
- Lives in web/ because Workers Builds detects the package manager from a
lockfile in its root directory, and there is no root package.json.
- workers_dev: false — a zone-scoped Access policy does not cover the
workers.dev hostname, which would later expose /admin and the repo-write
credential behind it on an unprotected origin.
- run_worker_first covers /api/*, /img/*, /admin and /admin/*. /img/* must be
listed or images fall through to the SPA handler and return index.html as
text/html; /admin must be listed or the SPA fallback serves the public shell
where Access is expected. /assets/* is deliberately absent — routing hashed
bundles through the Worker would bill every JS and CSS request.
/api/data/* proxies the dataset that stays canonical in Git, against an
anchored allowlist of exactly the three paths the app fetches. Proxying rather
than shipping data/ inside dist/ keeps the daily pipeline commits decoupled
from deploys: as build output, every data commit would force a full rebuild,
and if watch paths ever excluded data/ the site would serve a frozen dataset
with no error anywhere. index.json is sent no-cache because it carries
last_updated, the client's only cache-invalidation signal.
/img/* replaces the images.weserv.nl hop, so no visitor request reaches a
third party. It allowlists both Steam CDN hosts — akamai and fastly, the
latter being ~44% of records, which the old service-worker rule missed
entirely. Thumbnails prefer Steam's capsule asset and fall back to the header
when it does not exist (verified: 3,634 b vs 37,878 b on a cold appid, and the
hashed-path records fall back correctly). Transformations are OFF: they bill
separately from Workers Paid and Cloudflare has no spend cap, so real /img/*
volume gets measured first.
Also: tsconfig.worker.json, because tsconfig.json only includes ["src",
"vite.config.ts"] and the Worker would otherwise ship untyped; web-ci.yml now
runs both typechecks plus `wrangler deploy --dry-run`; 404.html is deleted as
not_found_handling replaces it; and index.html, robots.txt and sitemap.xml
stop declaring the GitHub Pages URL canonical now that this origin serves the
site.
Verified against a local `wrangler dev`: static assets, SPA fallback, all
three data paths with correct cache headers, all three image variants, and
404s for unknown variants, non-numeric appids, non-allowlisted data paths and
encoded traversal attempts.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
isChunkLoadError only matched the three "failed to fetch dynamically imported
module" style messages. Those cover a 404 on a stale chunk, but not what a
host with an SPA fallback returns: a request for a deleted hashed chunk is
answered with index.html at HTTP 200 and Content-Type: text/html, so the
browser rejects it on MIME type instead. The message looks nothing like a
fetch failure, so the reload-once recovery would silently stop working the
moment the site moves behind Cloudflare's not_found_handling. Added the
"failed to load module script" / "expected a javascript module script"
patterns and lifted the regex to a named constant.
Python installs now go through requirements.txt at all 11 sites — nine
bash/*.sh scripts and the two inline workflow steps — instead of a bare
`pip install requests`. The bare install silently ignored the urllib3 pin,
so CI was resolving a dependency the requirements file was trying to
constrain. mark-dead-games.yml already did this correctly.
requirements.txt and requirements-dev.txt move from `>=x,<y` ranges to exact
`==` pins: the pipeline should install identical versions on every run, and
Dependabot does not raise PRs for range-specified dependencies, so the new
pip ecosystem entry in dependabot.yml would otherwise have had nothing to do.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
typescript 5.9.3 -> 6.0.3.
Deliberately not 7.0.2, which is the current `latest` tag. TS 7 is the native
Go rewrite rather than an incremental release, so it is a much larger change
than a version bump implies and is worth landing on its own once the rest of
the migration has settled. 6.0.3 is the newest stable of the JS-based line.
TS 6 deprecates `baseUrl` (and 7 removes it), which surfaced as an error
rather than a warning. Rather than silencing it with `ignoreDeprecations`,
`baseUrl` is simply dropped: since TS 5 the `paths` mapping resolves relative
to tsconfig.json, so the `@/*` alias keeps working and continues to mirror the
Vite `resolve.alias` entry. Worth noting the alias currently has zero call
sites in src/ — it is kept only so the two configs stay in agreement.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
tailwindcss 3.4.19 -> 4.3.3, plus @tailwindcss/vite, tw-animate-css and
tailwind-merge 3.6.0. Removes tailwindcss-animate, autoprefixer and postcss
as direct dependencies, along with tailwind.config.ts and postcss.config.js.
Deliberately mechanical: the 17 HSL channel triples in :root/.dark are copied
across unchanged, so this migration is visual-neutral and revertable on its
own. The palette rework is a separate change and does not belong here.
Config moves from JS to CSS:
- `darkMode: ["class"]` becomes `@custom-variant dark (&:where(.dark, .dark *))`
- `theme.extend` becomes `@theme inline`. `inline` matters: it keeps opacity
modifiers such as the sidebar's `bg-primary/15` resolving through
color-mix(), and lets .dark re-resolve per element.
- Tailwind runs as a Vite plugin rather than a PostCSS one; @tailwindcss/vite
handles prefixing, so autoprefixer is redundant.
Two v4 removals needed real handling rather than a rename:
- `theme.container` config is gone. The replacement `@utility container`
reproduces the previous output exactly — centred, 1rem gutter, and the same
breakpoint steps with 2xl pinned to 1400px — rather than the fluid version,
so container widths between breakpoints do not shift.
- `max-w-screen-*` no longer exists. Layout.tsx's `max-w-screen-2xl` was
already inert (1536px against the container's own 1400px cap), so dropping
it changes nothing.
tailwindcss-animate is v3-only; tw-animate-css supplies the animate-in /
slide-in-from-* utilities the Radix dialog, sheet and popover depend on.
command-palette.css needed no changes — it is plain CSS reading the same
custom properties.
Verified in the browser rather than only via a green build: dark tokens, card
borders and radius, the KPI grid, the container width, the mobile Sheet's
slide-in animation, and the active nav item's bg-primary/15 tint all render as
before.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
i18next 23.16.8 -> 26.4.2, react-i18next 15.7.4 -> 17.0.13,
i18next-browser-languagedetector 8.0.0 -> 8.2.1.
react-i18next 17 is required rather than optional: its peer range is
`i18next >= 26.2.0`, so the two majors move together. The detector stays on
v8, which already supports i18next 26.
No source changes were needed. src/i18n/index.ts uses only APIs that are
stable across these majors — init, hasResourceBundle, addResourceBundle,
changeLanguage, resolvedLanguage, and the languageChanged event — and the
per-locale lazy-loading scheme around them is untouched.
Verified the path that actually matters, since a broken switch would be
invisible to typecheck: switching to Vietnamese loads the lazily-imported
vi.json bundle, persists `f2p:lang`, updates `<html lang>` via the
languageChanged listener, and re-renders every string (page titles, filters,
table chrome). English round-trips the same way.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
react + react-dom 18.3.1 -> 19.3.0, @types/react + @types/react-dom -> 19.3.0.
The removed-API surface was checked before upgrading and this codebase touches
none of it: no defaultProps or propTypes on function components, no
ReactDOM.render/hydrate, no findDOMNode, and no string refs (an initial grep
for `ref="` matched only `href="`). forwardRef is deprecated in 19 but not
removed, so the nine shadcn primitives in components/ui/ are unaffected.
Every React-dependent dependency already declares a v19 peer range — the Radix
primitives, @tanstack/react-query and react-virtual, cmdk 1.1.1, sonner 1.7.4,
react-i18next and echarts-for-react — so nothing else needed bumping and
`npm ls react` reports no invalid peers.
One real type break, fixed at the definition rather than the call site:
React 19 types make useRef<T>(null) return RefObject<T | null>, so Layout's
mainRef no longer satisfied BackToTop's `scrollRef: RefObject<HTMLElement>`.
BackToTop already dereferences defensively (`scrollRef.current?.scrollTo`), so
widening the prop to `RefObject<HTMLElement | null>` only makes the type match
the behaviour that was always there.
Verified at runtime under StrictMode, which is where the double-invoke risk
sits (the i18n bootstrap in main.tsx and the sessionStorage chunk-reload flag
in lib/lazy.ts): dashboard, games + detail drawer, health, about, the chart
pages and the Ctrl+K command palette all render, and a fresh load logs no
errors.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
react-router-dom 6.30.4 -> 7.18.3, with no source changes required. The app
uses only the declarative API (Routes/Route/Link/NavLink/useNavigate/
useLocation/useParams/useSearchParams/Outlet) — no data router, no loaders or
actions — and v7 keeps react-router-dom as a re-export, so every import site
is unchanged.
The two v7 behaviour changes were checked rather than assumed:
- v7_relativeSplatPath is a no-op here: every `to=` in src/ is absolute, so
there are no relative links inside the splat route to re-resolve.
- v7_startTransition was verified at runtime against the lazy routes, which
are the part that could plausibly regress (lazyWithRetry + Suspense inside
Layout). Games, Activity, Settings, the chart pages and the /games/:appid
deep link all render, and a fresh page load logs no warnings or errors.
HashRouter is deliberately retained for now; the BrowserRouter switch is a
separate one-line change once the site is served by Cloudflare, so a routing
regression stays distinguishable from a dependency regression.
cargo update -p quinn-proto pulls 0.11.14 -> 0.11.17, clearing the remote
memory-exhaustion advisory. It arrives transitively via reqwest. cargo check
passes.
`npm audit` now reports 0 vulnerabilities at every severity, closing the last
of the 18 npm advisories alongside the Rust one.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
CLAUDE.md captures the load-bearing facts that are easy to violate and
expensive to discover: appid is derived from `link` rather than stored,
numeric-looking fields are formatted strings, MANUAL_FIELDS survive refetch,
shard assignment is unstable because save_main() re-chunks from scratch,
index.json.last_updated is the only cache-invalidation signal, and the
echarts theme trap above. Every claim was checked against the code.
docs/plan/ holds the seven design documents and three adversarial critiques
behind the Cloudflare migration, including the wrangler layout adjudication,
the D1 schema, and the 67-row documentation contradiction table.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bumpedIndexFile() rebuilt data/index.json from a hardcoded four-key list and
each file entry from {name, count}, so every other key was deleted on write —
despite the docstring claiming "Other fields stay as the pipeline left them".
Harmless today only because nothing else writes keys there yet; the moment
licence metadata or a content hash is added, one routine edit through the UI
would strip it and the site would break with no error. Switched to spreading,
which is a prerequisite for the planned index.json additions.
updateBranchRef() carried an unused `force` parameter wired straight into the
update-ref body. No call site passes it, and a force push here would erase
whatever the data pipeline committed in between — the existing
RefAdvancedError retry is the correct response to a moved ref. Removed the
parameter so it cannot be reached for later.
jsonl-parser.ts now validates the message shape. CodeQL flags this handler as
js/missing-origin-check, but an origin check is the wrong fix: it is a
dedicated module worker, so the only sender is the document that constructed
it and MessageEvent.origin is the empty string. Validating {id, text} is the
hardening that actually applies — a malformed post now rejects the pending
promise instead of throwing unhandled inside the worker.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The scheduled pipeline has been failing daily since 2026-08-13 (last successful
`Auto update` was e8b7d1b2). Root cause: `secrets.GH_TOKEN`, a PAT, expired.
Every workflow passing it to actions/checkout dies at fetch with exit 128.
No workflow actually needs a PAT. Each already declares
`permissions: {contents: write}`, so the built-in GITHUB_TOKEN has push rights —
proven by mark-dead-games.yml, the only green data workflow and the only one
with a bare checkout. Removed the `token:` input from all 12 sites. This also
ends the silent-expiry failure mode rather than rescheduling it a year out.
`workflow_run` triggers are unaffected: GITHUB_TOKEN suppression applies to
push/issues/release events, and update-daily.yml plus the three notify-*
workflows all key off workflow_run, which the Actions service emits on run
completion regardless of the checkout token.
Also in this commit:
- ingest-from-issue.yml gated on `author_association`. Without it, any user
could open an issue titled [add-game] and have their JSON committed and
pushed to main with `contents: write`. A title match is not an authorization
check. Its `&&`/`||` commit chain is also parenthesised — left-associativity
meant it pushed even when there was nothing staged.
- bot-ingest.yml's final step deleted. It referenced `secrets.BOT_TOKEN` while
the rest of the file uses TELEGRAM_BOT_TOKEN, `cat`-ed a result.txt no step
creates, ran under `if: always()`, and interpolated a secret straight into a
shell command line. The Python step above it already does the same Telegram
callback correctly. `secrets.BOT_TOKEN` is now unreferenced.
- The snapshot feature is committed. snapshot-daily.yml gains the
`concurrency: {group: data-write}` guard every other data-writing workflow
has — without it a 23:00 run can push against jobs that take ~2 hours. The
`pip install requests` in bash/snapshot.sh is dropped: snapshot.py and
scripts/core/* import only stdlib.
- New web-ci.yml. deploy-pages.yml was the only thing running `npm run
typecheck`, so deleting it during the Cloudflare migration would leave the
frontend unchecked. Uses a plain `npm ci` — the old `npm ci || npm install`
fallback is what let the lockfile conflict above go unnoticed.
- New dependabot.yml. NOTE: an in-repo config replaces the one in repo
settings and supersedes open PR #111. Groups security updates so the
transitive backlog collapses into one PR instead of one per package.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Two coupled bugs — fixing either alone leaves the site broken.
1. `npm ci` has failed since 2026-08-13 with ERESOLVE: the lockfile resolves
echarts 6.1.0 while echarts-wordcloud@2.1.0 declares a peer of echarts@^5.
That peer is stale metadata, not a real incompatibility — every legacy API
the plugin uses (extendSeriesModel, extendChartView, List, and the four
helper.* functions) is still exported by echarts 6.1.0, verified against
the runtime exports. Added an `overrides` entry pinned to the root echarts
version via npm's `$echarts` syntax so it cannot drift.
2. With npm ci working, echarts 6 actually runs for the first time — and
`theme="dark"` blanks every series. `echarts/core` registers no themes
(only the full `echarts` bundle self-registers them); echarts 5 ignored an
unknown theme name, echarts 6 drops all series rendering instead. Axes,
grid and legend still paint, so charts look empty rather than broken and
nothing is logged. Confirmed by bisect: removing the prop restores pie,
bar, line and wordcloud immediately.
Dropping the theme regressed tooltips to echarts' light default, so the dark
tooltip styling it used to supply is now set explicitly — spread so per-chart
`formatter`/`trigger` still win.
Production was never exposed: the deploy for the echarts bump failed on this
same ERESOLVE, so the live site still serves the last pre-bump build.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- minSdk 24 -> 30: OS-level install gate (INSTALL_FAILED_OLDER_SDK) drops EOL
Android 7-10 (no Google OS patches, stale WebView vs the React 19 bundle);
minSdk 30 still reaches ~87% of active devices.
- Hide the steam:// "Steam Desktop" button on the Android app / sub-768px
viewport via a new reactive useIsMobile hook; the Web button stays.
- Docs: new docs/android-support.md (+vi mirror) with requirement, rationale,
tested devices (emulator 11-16, real vivo 1907 on Android 12) and a sourced
version-share/EOL table; update TAURI.md, pc_spec.md (+vi), the
release-android.yml notes, and the README badge/links.
- Bump 1.4.3 -> 1.4.4 (repo 3.4.1 -> 3.4.2) + Cargo.lock/package-lock sync.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- themes.xml (values + values-night): transparent system bars + light status/nav
icons for the dark-by-default web UI under edge-to-edge (targetSdk 36), with
contrast enforcement disabled.
- gradle.properties: kotlin.incremental=false to dodge the cross-drive cache
relativization crash (Cargo registry on C:, project on E:) that forced a slow
non-incremental Kotlin compile + noisy stack trace every build. Negligible
cost (tiny Kotlin surface); harmless on single-drive CI.
- Bump to 1.4.3 (versionCode -> 1004003) across the six version slots.
Verified: debug APK builds and the Kotlin "different roots" error is gone.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* feat(android): touch-zoom charts + in-app update check
- ECharts: on touch devices (pointer: coarse) inject an inside dataZoom on each
cartesian chart's category axis, so cramped many-category bar/line/heatmap
charts pinch-zoom and pan on mobile. Centralized in EChart.tsx; desktop
(pointer: fine) is untouched — no wheel-zoom hijacking page scroll.
Pie/treemap/wordcloud (no axes) are skipped.
- Android update check: the Tauri updater plugin is desktop-only, so on Android
the app polls GitHub Releases once per launch for a newer android-v* tag and
shows a toast linking to the new APK. Exposes the package.json version to the
bundle as __APP_VERSION__ (Vite define). New: lib/android-update.ts,
hooks/useAndroidUpdateCheck.ts, isAndroid() helper, appUpdate i18n keys (en/vi).
Verified: typecheck + web build pass; __APP_VERSION__ is replaced at build time.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* chore(release): bump version to 1.4.2
Android release carrying the touch-zoom charts + in-app update check (PR #102).
versionCode auto-derives to 1004002. Synced across package.json,
package-lock.json, tauri.conf.json, Cargo.toml, Cargo.lock.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* feat(android): scaffold Tauri 2 Android build — first working APK
Adds Android as a build target for the existing web app via Tauri 2 mobile.
A debug arm64 APK builds successfully on Windows (NDK 30 + JDK 21).
- gen/android: committed Tauri-mobile Gradle project (`tauri android init`).
Build artefacts (build/, .gradle, jniLibs *.so, keystore.properties,
tauri.properties) stay ignored via the nested .gitignore files.
- capabilities: split updater:default into a desktop-only capability
(updater.json, platforms = win/linux/macOS) so the Android ACL resolution
doesn't fail on the updater plugin that's gated out of mobile builds.
- external links: global capture-phase interceptor routes external <a>/links
through the Tauri shell on desktop + Android (the webview blocks
window.open to external HTTPS); convert the two window.open call sites
(DeviceFlowPanel, Health) to openExternal.
- npm scripts: build:mobile + tauri:android:{init,dev,build}.
- src-tauri/.gitignore: gen/ -> gen/schemas/ so gen/android is committable.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* feat(android): native-HTTP OAuth + mobile UX polish
- OAuth Device Flow: route the two github.com/login/* endpoints (which send
no CORS headers) through @tauri-apps/plugin-http so they work inside the
Android System WebView, which — unlike desktop — enforces CORS. Falls back
to window.fetch (+ optional VITE_GH_OAUTH_PROXY) on the plain web build.
Adds the Rust tauri-plugin-http plugin + an http:default capability scoped
to github.com / api.github.com.
- Layout: apply env(safe-area-inset-*) padding — edge-to-edge is forced on
targetSdk 36 / Android 15, so the chrome must dodge the status/nav bars.
No-op on web/desktop (insets are 0).
- Command palette: openable on touch via a mobile topbar button dispatching a
custom event, since the soft keyboard can't send the Ctrl/Cmd+K chord.
Verified: typecheck, web build, and a debug arm64 APK build all pass; the
http:default ACL scope resolves on Android.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* ci(android): release signing config + GitHub Actions release workflow
- app/build.gradle.kts: add a `release` signingConfig sourced from
gen/android/keystore.properties (gitignored). Guarded by the file's
existence, so a keyless checkout still configures and unsigned/debug builds
keep working; the release buildType signs only when the keystore is present.
- .github/workflows/release-android.yml: build a signed universal release APK
on `android-v*` tags (JDK 17, Android SDK, NDK r27, the four Rust android
targets), decoding the keystore from repo secrets into keystore.properties,
then attach the APK to a draft GitHub Release. Documents the four required
secrets (ANDROID_KEYSTORE_BASE64 / _PASSWORD / KEY_ALIAS / KEY_PASSWORD).
Verified the gradle DSL parses via a debug APK build. Signing itself is
exercised once the keystore exists (user-generated, kept out of the repo).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* docs(android): document the Tauri 2 Android build, signing, and CI
Extend TAURI.md (now "desktop + Android") with an Android section: SDK/NDK/JDK
prerequisites, build commands, keystore signing + backup warning, the
release-android.yml CI secrets, and notes on the desktop-only updater,
edge-to-edge safe areas, the plugin-http OAuth bridge, and the Kotlin
cross-drive incremental-compile fallback.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* docs(web): describe v3.4.1 build stack as Vite 8 + Rolldown
The web build migrated from Vite 7 (rollup + esbuild) to Vite 8, which
uses the Rolldown bundler; esbuild and standalone rollup are no longer in
the dependency tree. Reconcile the stack documentation with reality:
- docs/ACKNOWLEDGEMENTs.md: "Vite 7" -> "Vite 8 + Rolldown" in the
Runtime & build list.
- web/src/pages/About.tsx: bump the in-app "Stack & third-party" list
entry "Vite 7" -> "Vite 8 (Rolldown)" and add a Rolldown row.
- web/README.md: Stack line now reads "Vite 8 (Rolldown bundler)".
- web/src/gpgauth/README.md: stale "Rollup" bundler note -> "Rolldown".
Docs-only / content cleanup follow-up to v3.4.1. No canonical version
files, source logic, or CHANGELOG history touched. typecheck + build
pass; knip shows only pre-existing unused exports.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* chore(web): sync package-lock version to 1.4.1
The v3.4.1 bump updated web/package.json to 1.4.1 but left
web/package-lock.json at 1.4.0, so `npm install` kept re-touching the
lockfile. Sync the lockfile `version` fields to match. No dependency
graph changes — only the two version lines.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The Vite 8 / Rolldown migration (#95) introduced a production regression:
every chart tab threw React error #130 ("Element type is invalid... got:
object") and failed to render — all pages/charts/* plus the Dashboard.
Root cause: EChart.tsx imported the wrapper from
`echarts-for-react/lib/core` (the CommonJS build). Under Rolldown the
CJS default-interop wraps `module.exports = class` into a namespace
object, so <ReactEChartsCore/> received an object instead of a
component. Switched to the ESM build `echarts-for-react/esm/core`, which
has a clean `export default`. echarts core / echarts-wordcloud were
already ESM, so this single import was the only offender.
Verified at runtime against the production (Rolldown) build (the step
skipped in #95): bar, pie/donut, line, treemap, heatmap and wordcloud
charts all render with zero console errors; echarts/openpgp stay lazy
async chunks (not eager-preloaded).
Also documents the glib Dependabot advisory (GHSA-wrw7-89jp-8q8g,
medium, Linux-only) as accepted: it cannot be fixed within Tauri 2.x
(webkit2gtk 2.0.2 pins glib ^0.18; Tauri 3 unreleased) and the deployed
surfaces are unaffected. Alert to be dismissed as tolerable risk.
Version: repo 3.4.0 -> 3.4.1; web + desktop 1.4.0 -> 1.4.1.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
PR #92 (nominally an esbuild security bump) silently upgraded vite 7→8
and @vitejs/plugin-react 4→6. Vite 8 switches the bundler from
rollup+esbuild to Rolldown, which dropped the object form of
`build.rollupOptions.output.manualChunks`. That broke `tsc -b` typecheck
in the Deploy Web (GitHub Pages) workflow, failing every push since the
merge and freezing the live site.
Replace the object-form manualChunks with Rolldown's
`advancedChunks.groups`, keeping the three vendor groups (react / query /
table) and deliberately NOT grouping echarts/openpgp so they stay behind
their dynamic-import boundaries (verified: neither is modulepreloaded in
dist/index.html).
esbuild is no longer in the dependency tree under Vite 8 (npm ci reports
0 vulnerabilities), so the dev-only advisory GHSA-g7r4-m6w7-qqqr is
resolved without an override.
Verified locally: npm ci, typecheck, build, build:desktop all pass; PWA
service worker generated; echarts/openpgp remain separate async chunks.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Web/in-app first-run consent gate (ConsentGate wrapped around <App/> inside
HashRouter): full-screen card, checkbox-gated Continue, explicit Decline
(desktop quits via getCurrentWindow().close(); web shows a blocking notice).
Acceptance persisted in localStorage (f2p:legal_consent) and versioned via a
TERMS_VERSION constant so terms changes re-prompt everyone; incognito tabs get
a fresh partition so the gate re-shows there with no extra code. Error routes
(#/error/*) pass through. Doc links open via the existing openExternal() helper
so they work inside the Tauri webview.
Lifted LEGAL_DOCS out of About.tsx into a shared lib/legal.ts (LEGAL_DOCS,
CONSENT_DOCS, legalDocUrl); About now imports it. New consent.* i18n keys in
en.json + vi.json.
Windows installer license page: bundle.licenseFile -> LICENSE_AGREEMENT.rtf
(ASCII, no BOM) — mandatory "I Agree" page on both NSIS .exe and WiX .msi.
Added @tauri-apps/api dep (lazy-imported, desktop decline only) and
core:window:allow-close capability.
Version bump 1.3.0 -> 1.4.0 (package.json, tauri.conf.json, Cargo.toml,
Cargo.lock); repo 3.3.0 -> 3.4.0 (CHANGELOG, README badge). typecheck/knip/
build/vulture/pip-audit clean.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Tag pushes (v*, desktop-v*) match the paths filter against an empty base,
so every release fired the ingest on a detached HEAD and failed with exit
128 (lesson 23 was only "resolved" by a lucky no-op .gen-hash). branches:
[main] excludes tag refs from the trigger entirely.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two mobile-viewport regressions from the v3.2.5 responsive overhaul.
- **AC Index table**: `web/src/pages/AntiCheatList.tsx` per-family table wrapper was `overflow-hidden`, clipping the right-hand columns on a 390 px viewport with no scroll affordance. Changed to `overflow-x-auto` — table scrolls horizontally when wider than the card, scrollbar hidden when it fits.
- **Mobile card thumbnail**: `web/src/components/games/table/MobileGameCards.tsx` `<img>` loads the `capsule_184x69.jpg` variant via `headerToCapsule()`; Steam's CDN lacks that variant for some games → blank thumbnail. Ported the `onError` fallback from the desktop column (`table/columns.tsx`) — swaps `src` to the original `header.jpg` on 404, guarded against an infinite loop. `GameDetailDrawer` uses `g.header_image` directly, hence images always showed once a card was tapped.
- Version bump `1.2.5` → `1.2.6` (`web/package.json`, `web/src-tauri/Cargo.toml` + Cargo.lock, `tauri.conf.json`). README badge `3.2.5` → `3.2.6`.
Verification: `npm run build` (2418 modules), `cargo check` (v1.2.6 compiles).
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-20 08:44:09 +07:00
852 changed files with 743875 additions and 23823 deletions
# Slug of the discussion category to post into. The category must
# already exist on the repo (Settings → General → Features →
@@ -80,7 +80,7 @@ jobs:
'',
'---',
'',
'*(Auto-posted by `.github/workflows/announce-release-discussion.yml`. Reply with feedback, install issues, or feature requests — full bug reports still go through the [issue templates](../../issues/new/choose).)*',
'*(Auto-posted by `.github/workflows/announce-release-discussion.yml`. Reply with feedback or install issues. The project is in maintenance mode, so feature requests are not taken — bug reports and data changes go through the [issue templates](../../issues/new/choose).)*',
Desktop builds of the F2P Tracker — a fixed-size 1400×900 window wrapping the same web UI deployed at https://poli0981.github.io/free-steam-games-list/.
Desktop builds of the F2P Tracker — a resizable window around the same app as https://free-steam-games.win.
**Installation**
- Windows: download the `.msi` and run.
- Windows: download the `.msi` or `-setup.exe` and run.
- macOS: download the `.dmg`, drag to Applications. Universal binary (Intel + Apple Silicon).
- Linux: `.AppImage` (run directly) or `.deb` (Debian/Ubuntu).
**Auto-update**: from v1.0 onwards the desktop app polls this Releases page on launch and offers to download + verify (minisign) the next signed build. To take updates, install via the official binaries — sideloaded copies won't see the prompt.
**Updates**: from 2.0.0 the app checks free-steam-games.win for a newer desktop release a few seconds after launch and offers to install it. The download comes from this Releases page and is verified against the app's minisign key before it installs. Publishing this draft is what makes it visible to that check.
See `docs/DISCLAIMER.md` for accuracy caveats. The desktop app reads data live from `raw.githubusercontent.com`; offline functionality matches the PWA.
The app reads its data from free-steam-games.win (`/api/data`) and keeps the last verified copy for offline use. See `docs/DISCLAIMER.md` for accuracy caveats.
Compiled from commit `${{ github.sha }}`.
releaseDraft:true
prerelease:false
includeUpdaterJson:true
uploadUpdaterJson:true
args:${{ matrix.args }}
# tauri-action v1 writes each artefact's API URL into latest.json
# (api.github.com/repos/<repo>/releases/assets/<id>), and has no setting to
# change that. /api/updates/desktop (worker/routes/updates.ts) accepts only
# this release's download URLs and answers 204 - "no update" - to anything
# else, so desktop-v2.2.1, the first release built with v1, was offered to
# no installed app until its latest.json was fixed by hand. Once every
# platform has added its entries, scripts/updater_json.py rewrites them; it
# refuses an entry whose signature is not its file's .sig.
updater-json:
needs:build
permissions:
contents:write
runs-on:ubuntu-latest
steps:
- uses:actions/checkout@v6
# updater_json.py is stdlib-only, but it runs on the pipeline's Python
# like every other script, not on whatever the runner image ships.
This file is about using this project with a keyboard, a screen reader, zoom,
high contrast or reduced motion, or with anything else that is not a mouse and
a default screen. It covers:
- the website, <https://free-steam-games.win/>;
- the desktop and Android apps, which are the same interface running in the
system's web view;
- the data as plain text: [`data/`](data/) (JSONL), the CSV/JSON export on the
Games page, and the Markdown leaderboards in [`games/`](games/).
It does not cover Steam's own pages, Cloudflare's Turnstile widget (the
website's human check) or GitHub itself. Those belong to Valve, Cloudflare and
GitHub.
One person maintains this as a hobby, and nobody has audited it. So this is not
a certificate. It is a list of what is known to work, what is known not to, and
how to say so when something gets in your way.
## The goal
**[WCAG 2.2](https://www.w3.org/TR/WCAG22/) Level AA** is the target. It is a
target, not a claim: the app has not been audited against it, and the
limitations below mean it does not meet it today.
What matters most, in this order:
1. Finding and opening a game (search, filters, the games list, a game's page)
with a keyboard, a screen reader or zoom.
2. Nothing said with colour alone, or only in a mouse-hover tooltip.
3. No traps, including the first-run screens every visitor has to get past.
4. The reader's own settings win: language, reduced motion, light or dark,
zoom.
## What works today
Checked against the code on 2026-11-09, for the website and the desktop and
Android apps 2.5.1.
- **Language.** The page declares its language, and changes it when you
switch between English and Vietnamese.
- **Structure.** "Skip to content" is the first thing the keyboard reaches.
The header and both navigation menus are labelled, and the menus mark the
page you are on. Each page has one main heading and its own title, and
moving to another page announces the new title.
- **Keyboard.** Links and controls show a focus ring.
<kbd>Ctrl</kbd>/<kbd>⌘</kbd>+<kbd>K</kbd> opens a command palette that
works like a search box with a list: arrow keys, <kbd>Enter</kbd>,
<kbd>Esc</kbd>. The menu drawer on small screens, the palette and the
desktop update dialog keep focus inside while they are open, close with
<kbd>Esc</kbd>, and put focus back where it was.
- **The games table.** A screen reader hears a table: column headers
(including names for the image, data-issue and Steam columns), the total
number of rows and columns, and the position of each row, even though only
the rows on screen exist. Each row is one stop for <kbd>Tab</kbd>, the
game's name, and the whole row lights up when it has focus. Clicking
anywhere on a row still opens the game. On a phone the cards are a list
that says how many games it holds and where you are in it.
- **The first-run screens.** The terms screen and the human check are
dialogs. Focus moves into them, and the page behind is out of reach for the
keyboard and for screen readers until you are through. The command palette
shortcut does nothing while they are open.
- **Names.** Buttons that only show an icon have a text name. Switches (the
language and theme buttons, the scrollbar options, the choices on *Random
games*, the anti-cheat families) say whether they are on.
- **Colour and contrast.** In both themes, text is at least 4.5:1 against its
background, badges and the current menu item included, and the edges of
text boxes and drop-downs are at least 3:1. Kernel-level anti-cheat carries
a shield icon as well as its red, and the words "Kernel-level". They are
spelled out on a game's page and read out by screen readers in the table,
the cards and *Random games*. A test computes these ratios from the theme's
colours, so a later colour change cannot quietly undo them.
- **Charts.** Each chart is announced as an image named by its title. Some
also give the numbers as text: *Top online* and *Top offline* list 100 games
under their charts, *Genres* lists the top 24, *Tags* writes out 40 of its
60 words with their counts, and the anti-cheat chart links to a real table
that also says, in words, which anti-cheat runs at kernel level.
- **Images, sound and motion.** Game art is decorative (`alt=""`); the game's
name is always written next to it. Nothing plays sound or video. With your
system's *reduce motion* setting on, page animations and transitions are cut
short, and scrolling jumps instead of gliding, "back to top" included.
- **Zoom and small screens.** The website never blocks pinch-zoom, and the
games list keeps a usable height at 400% zoom. The desktop app zooms with
<kbd>Ctrl</kbd>/<kbd>⌘</kbd> and <kbd>+</kbd> / <kbd>−</kbd>. Below tablet
width the games table turns into cards, and a test checks that every grid
falls back to one column on a phone.
- **Settings.** Theme (dark by default, light, or follow the system), English
or Vietnamese, and hidden scrollbars. Hidden scrollbars still scroll from
the keyboard.
- **Plain text.** Every game has its own page. The Games page exports what you
have filtered as CSV or JSON. The whole dataset is plain JSONL in
[`data/`](data/), and the two leaderboards are Markdown tables in
[`games/`](games/).
## Known limitations
Known, and not fixed yet. Where there is another way to get the same thing, it
says so.
- **Charts.** Values, tooltips and legends are drawn on a canvas and need a
pointer. Several charts have no text version: DRM, languages, platforms,
players, reviews, release years, delisted games, most of *Stats*, and the
genre chart on the dashboard. Several tell categories apart by colour alone.
Chart animations ignore *reduce motion*.
*Instead:* the CSV/JSON export, or the raw data.
- **The games table is virtualised.** Only the rows on screen exist in the
page. A screen reader is told the full count, but the browser's
find-in-page only sees those rows.
*Instead:* narrow the list with search and the filters, or export to
CSV/JSON.
- **The human check is Cloudflare Turnstile,** in a frame this project does
not control. If it says your browser is unsupported, there is no retry
button.
*Instead:* the desktop and Android apps never show it, and everything in
the catalogue is readable on GitHub.
- **Hover-only hints.** To sighted readers, the 💀 on a dead game and the
warning icon in a table row explain themselves only in a mouse-hover
tooltip. Screen readers get the words.
*Instead:***Hide dead** on the Games page takes dead games out of the
list.
- **Changes that are not announced:** the number of results after you filter,
the page number, and loading or error messages. The pop-up notifications'
own labels ("Notifications", "Close toast") stay in English when the app is
in Vietnamese.
- **Text in another language is not marked as such.** The legal documents
exist only in English. Game names and descriptions are in whatever language
the developer wrote them. None of it is tagged, so a screen reader reads it
in the interface language's voice.
- **Contrast themes** (Windows' forced colours) get no special support.
- **Zoom.** Long values are cut off with "…", and a few small labels have
fixed pixel sizes. As far as the code shows, the Android app does not
pinch-zoom.
*Instead:* game pages and the CSV/JSON export, the website in a browser, or
your system's magnifier or text size.
- **Automated checks are static.** A test holds the fixes above in place and
computes the theme's contrast, but nothing runs a screen reader or an
accessibility scanner, and Svelte's accessibility warnings do not fail the
build.
## Supported environments
| Where | Runs on | Checked by hand |
| --- | --- | --- |
| Website | Any current browser | Chrome, Edge, Firefox and Brave on Windows 11; Safari, Chrome and Brave on iOS 26 (iPhone 14 Pro, iPhone 13 Pro Max) |
| Desktop app | WebView2 (Windows), WKWebView (macOS), WebKitGTK (Linux) | Windows 11. The macOS and Linux builds are not checked by hand. |
| Android app | Android System WebView, Android 11 or newer | Emulator (Android 11 to 16) and a vivo 1907 (Android 12) |
The apps get their accessibility from the system's web view. What a screen
reader can do in them is roughly what it can do in Edge on Windows, Safari on
macOS, or Chrome on Android. The full device list is in
[`docs/pc_spec.md`](docs/pc_spec.md).
**Assistive technology used so far:** the keyboard alone, and the Narrator and
NVDA screen readers on Windows. VoiceOver on a real iPhone 14 Pro (iOS 26),
in Safari, Chrome and Brave, with the interface in English and in Vietnamese:
passed (2026-11-09).
**Not tried yet:** JAWS, VoiceOver on macOS, TalkBack (Android), Orca
(Linux). Reports from any of them are especially welcome.
This file lives at the repo root so the author can be found without digging into the docs. The canonical handle map is also in [`username.txt`](username.txt) (machine-readable) and rendered in the web app's [About page](https://poli0981.github.io/free-steam-games-list/#/about).
This file lives at the repo root so the author can be found without digging into the docs. The canonical handle map is also in [`username.txt`](username.txt) (machine-readable) and rendered in the web app's [About page](https://free-steam-games.win/about).
## Maintainer
@@ -9,19 +9,23 @@ This file lives at the repo root so the author can be found without digging into
| Test devices | iPhone 14 Pro · iPhone 13 Pro Max · iOS 26.x (Chrome / Brave / Safari) |
| Test devices | Windows 11 (Chrome / Edge / Firefox / Brave) · iPhone 14 Pro and 13 Pro Max, iOS 26.x (Safari / Chrome / Brave) · Android 11–16 emulator + vivo 1907 (Android 12) — full list in [`docs/pc_spec.md`](docs/pc_spec.md) |
## Contributors
Anyone who's filed an issue, opened a PR, or used the Add-Games template is implicitly thanked. The full list is whatever GitHub renders on the [contributors page](https://github.com/poli0981/free-steam-games-list/graphs/contributors).
Anyone who's filed an issue, opened a PR, or suggested a game in Discussions is implicitly thanked. The full list is whatever GitHub renders on the [contributors page](https://github.com/poli0981/free-steam-games-list/graphs/contributors).
## AI assistants (full disclosure)
About **~70 %** of the code in this repository was generated with help from large-language-model assistants:
- **Claude (Anthropic)** — v2 refactor, full data layer, the React/Vite web app, the Tauri 2 desktop wrapper, the GPG-signing path, the legal docs, and most recent commits.
- **Claude (Anthropic)** — v2 refactor, full data layer, the web app (React/Vite first, SvelteKit since v4), the Cloudflare Worker and `/admin`, the Tauri 2 desktop and Android apps, the legal docs, and most recent commits.
Generated code is reviewed and tested before each commit. No user data is sent to any LLM at runtime — LLM calls happen on the maintainer's dev machine, never from your browser.
## Licensing
Everything in this repo (data, code, docs, web app) is [MIT-licensed](LICENSE) — fork freely; please keep the credit.
Code, docs and the web app are [MIT-licensed](LICENSE). The **dataset** (`data/**`, `games/**`) is licensed separately under [CC BY 4.0](LICENSE-DATA). Fork freely; please keep the credit.
go to [`changelog/beta/`](changelog/beta/) - none has been published. What is
not released yet is under [Unreleased] below; a release moves it into its own
file and adds the release to the table of its major version.
Patch release on top of v3.2.4. One reported bug fix + three quality-of-life polish items. **Bug:** clicking any "Family" link in the Anti-Cheat Index sidebar redirected to the Dashboard instead of scrolling to the matching family table — `HashRouter` was treating the `<a href="#vac">` anchor as a route navigation. **Polish:** the `GamesTable` (1318 px wide) now degrades to a virtualised card list below the `md` breakpoint so mobile no longer needs horizontal scroll; the `AntiCheatList` sidebar drops to `md` instead of `lg` and exposes a horizontal chip nav on phones; `KpiCards` adds `md`/`lg` rungs to avoid uneven grid jumps. **Cleanup:** 93 per-genre markdown files in `games/` are removed (the web app's `/games?genre=X` filter has replaced them since v3.0); `generate_tables.py` now skips regeneration when game data hasn't actually changed via a `.gen-hash` checksum, cutting daily catalogue commits to roughly the days that move records. **New:** floating back-to-top button on the main scroll container, fades in past 400 px. Web app + desktop bumped `1.2.4` → `1.2.5`. Repo public-facing version `3.2.4` → `3.2.5`. Tag `v3.2.5` is GPG-signed; companion desktop tag is `desktop-v1.2.5`.
## [Unreleased]
### 🔗 AC Index sidebar navigation fix
## v4
- [web/src/pages/AntiCheatList.tsx](web/src/pages/AntiCheatList.tsx): swap `<a href="#anchor">` for `<button onClick>` that calls `document.getElementById(id).scrollIntoView({ behavior: "smooth", block: "start" })`. The `id={anchor}` attribute on each family `<Card>` stays the same — only the click target changes.
- Root cause: `main.tsx:24` uses `HashRouter`. Anchor links inside a hash-routed page produce URLs like `#/charts/anti-cheat/list#vac`. HashRouter parses the trailing `#vac` as a fresh route, the regex doesn't match, and the `<Route path="*" element={<Navigate to="/" replace />}>` fallback in `App.tsx` sends the user to the Dashboard.
- Same fix applied to the new mobile chip nav (below) so behaviour is uniform across viewports.
### 📱 Mobile responsive
- New `web/src/components/games/table/MobileGameCards.tsx` — virtualised card list rendering one card per game with thumb, name, genre/type/AC/status badges, review %, current players, and a Steam-link icon. Shares filter/sort/page state with the desktop table via the existing `useFilters` store.
- [`GamesTable.tsx`](web/src/components/games/GamesTable.tsx) wraps the desktop scroll container in `hidden md:block` and renders `<MobileGameCards>` inside `md:hidden`. No new state, no behaviour drift between views.
- [`AntiCheatList.tsx`](web/src/pages/AntiCheatList.tsx) sidebar changes from `hidden w-48 shrink-0 lg:block` to `hidden md:block md:w-40 lg:w-48` — visible on tablets too. Below `md`, a horizontal scrollable chip rail above the content provides the same family-jump nav.
- [`KpiCards.tsx`](web/src/components/charts/KpiCards.tsx) grid `sm:grid-cols-2 lg:grid-cols-3 xl:grid-cols-7` → `sm:grid-cols-2 md:grid-cols-3 lg:grid-cols-4 xl:grid-cols-7`. Inserts `md` (tablet, 3 cols) and `lg` (small laptop, 4 cols) rungs so the 7 KPIs don't double-stack awkwardly.
### 🧹 `games/` cleanup + smart regen
- **Deleted 93 per-genre `<genre>.md` files** (`action.md`, `fps.md`, `visual-novel.md`, …). Web app `/games?genre=X` is the canonical genre filter since v3.0; no inbound link audit hit anything beyond `games/README.md` (regenerated) and the now-stale "By Genre" section in the index. Files kept: 11 ×`all-games_part*.md`, `top-online.md`, `top-offline.md`, `anti-cheat-list.md`, `README.md`.
- [`scripts/generate_tables.py`](scripts/generate_tables.py) drops the genre loop entirely and rewrites the `games/README.md` template to point at part files + leaderboards + AC list, with a one-line note about the web-app genre filter.
- **Smart regen via `.gen-hash`** — script computes `sha256` of sorted `(link, name, genre, reviews, current_players, anti_cheat, is_kernel_ac, status)` tuples and writes the digest to `games/.gen-hash`. Subsequent runs short-circuit (`Skip: no semantic changes (hash=...)`) when the hash is unchanged. Order-invariant, ignores timestamps embedded in MD output, so daily workflow ticks only commit when game data actually moves.
### ⬆️ Back-to-top button
- New `web/src/components/common/BackToTop.tsx` — a fixed-position icon button bottom-right of the viewport. Listens for `scroll` events on the passed scroll container ref (passive listener), fades in (`opacity-100`) past 400 px, becomes pointer-events-none below to avoid blocking click-through.
- [`Layout.tsx`](web/src/components/layout/Layout.tsx) creates a `useRef<HTMLElement>` on `<main>`, passes it as `scrollRef`. Single mount, no per-page wiring.
- i18n: `common.backToTop` added to `en.json` ("Back to top") and `vi.json` ("Lên đầu trang") for `aria-label` + `title`.
Patch release on top of v3.2.3, landed as two PRs. **PR #74 (cleanup):** two dead scripts removed, `EditGameDrawer.tsx` (718 LOC) and `GamesTable.tsx` (568 LOC) split into focused sub-modules, two new charts (`TopOfflineBar`, `AddedPerMonthBar`) wired to a fresh `/top-offline` page and the existing `/charts/time` page. **PR #75 (features):** the `scripts/removed_games.jsonl` log now passes through a `dedup_removed()` filter on every write (a one-time migration trimmed 6 historical duplicates), Top Online leaderboard expanded `50 → 100` to match Top Offline, a generated `games/anti-cheat-list.md` plus a `/charts/anti-cheat/list` web page group active games by anti-cheat family, and a new `/charts/delisted` page renders a timeline + reason breakdown of every removed-from-catalogue title. Web app + desktop bumped `1.2.3` → `1.2.4`. Repo public-facing version `3.2.3` → `3.2.4`. Tag `v3.2.4` is GPG-signed; companion desktop tag is `desktop-v1.2.4`.
### 🧹 Dead-script removal
-`scripts/discord_notify.py` deleted — superseded by the `poli0981/.github` reusable workflow; no `.github/workflows/*.yml` or `bash/*.sh` referenced it.
-`scripts/migrate_to_shards.py` deleted — one-shot v2.2 migration tool, completed and unreferenced. The 10-script "unreferenced in workflows" audit confirmed the other eight (`check_dead_links`, `delete_game`, `normalize_genres`, `purge_unhealthy`, `top_offline`, `top_online`, `update_data`, `update_reviews`) all have live `bash/*.sh` wrappers and stay.
### 🪓 Component splits
-`web/src/components/games/EditGameDrawer.tsx` (718 LOC) → 7 focused files under `edit/`:
-`EditGameDrawer.tsx` keeps the save handler, dialog shell, view-toggle wiring.
-`EditFormFields.tsx`, `EditJsonView.tsx` (with `JsonDiff`), `EditChangePreview.tsx`, `ViewToggle.tsx` extract the four UI regions.
-`web/src/components/games/GamesTable.tsx` (568 LOC) → container + 5 files under `table/`:
-`GamesTable.tsx` keeps the virtualizer (`useVirtualizer` ownership at container level so row-height stays single-source), filters, fuzzy search, sort, and paging.
-`TableHeader.tsx`, `TableRow.tsx` (memoised with `React.memo`), `TableToolbar.tsx`, `ExportMenu.tsx` extract the visual regions.
- No behaviour change — same virtual scrolling, same sort/filter wiring, same selection store.
### 📊 New charts
-`web/src/components/charts/TopOfflineBar.tsx` — mirror of `TopOnlineBar` but with offline-tier thresholds (20k/1.5k/300) calibrated to the `top_offline.py` scale instead of the online-only 100k/10k/1k palette. Filters `type_game !== "online" && status === "active"`, top 100 by `current_players`.
-`web/src/pages/TopOffline.tsx` — new page at `/top-offline`, layout mirror of `TopOnlinePage`, registered in `App.tsx` and `Sidebar.tsx` (Trophy icon).
-`web/src/components/charts/AddedPerMonthBar.tsx` — aggregates `records[*].added_at` into `YYYY-MM` buckets, renders an ECharts bar. Added as a third card to the existing `charts/Time.tsx` page alongside `ReleaseYearHistogram` + `AddedCumulativeLine`.
### 🗑️ Removed-games dedup
-`scripts/core/data_store.py` — new `dedup_removed(records)` keeps the latest entry per appid (compared by `removed_at` ISO timestamp, lexicographic order matches chronological for `YYYY-MM-DDTHH:MM:SSZ`). Records without a resolvable appid are dropped.
-`scripts/purge_unhealthy.py:41-43` and `scripts/ingest_new.py:106-108` — both call sites now write `dedup_removed(existing + log)` instead of `existing.extend(log)`. Same `save_jsonl` atomic-rename transaction, so partial writes can't leave duplicates.
-`scripts/dedup_removed_games.py` (new) — one-shot CLI that loads, dedups, and rewrites the file. Run once locally as part of this release; idempotent, safe to re-run.
- Result: existing log trimmed `43 → 37` records. Verified zero duplicate appids post-migration.
-`games/top-online.md` regenerated with 100 rows on next workflow tick; format unchanged (10-column table preserved).
-`web/src/pages/TopOnline.tsx` — `<TopOnlineBar limit={100} height={1800}>` to match the new row count.
- i18n strings `topOnline.{subtitle,cardTitle}` updated `Top 50 → Top 100` in both `en.json` and `vi.json`.
### 🛡️ Anti-cheat list
-`scripts/generate_anti_cheat_list.py` (new) — buckets active games by canonical AC name (`ANTI_CHEAT_PATTERNS` keys), with substring-match fallback for free-text values. Unrecognised values land in an `Other` bucket with a stderr warning. Output `games/anti-cheat-list.md`: H1 + TOC + per-family H2 sections, each a 6-column table sorted by `current_players` desc.
-`bash/anti_cheat.sh` + `.github/workflows/anti-cheat-list.yml` (new) — weekly Sunday 06:00 UTC cron + manual dispatch. Uses the same `data-write` concurrency group as the other table-generation workflows.
-`web/src/pages/AntiCheatList.tsx` (new) — `/charts/anti-cheat/list` page mirrors the MD: collapsible per-family sections + sticky AC-name sidebar nav. Uses existing `useGames` hook; canonicalises client-side via a TS port of the Python patterns table. i18n keys `antiCheatList.*` added to en + vi.
### 📉 Delisted charts
-`web/src/hooks/useRemovedGames.ts` (new) — fetches `scripts/removed_games.jsonl` from raw.githubusercontent.com, parses lines, deduplicates client-side (same logic as the Python dedup). TanStack Query with 5-minute staleTime.
-`web/src/components/charts/DelistedTimeline.tsx` (new) — ECharts stacked bar, x = `YYYY-MM` of `removed_at`, stacked by `status_code` (`not_free` / `unavailable` / fallback `other`).
-`web/src/components/charts/DelistedReasonBreakdown.tsx` (new) — ECharts donut by `status_code`.
-`web/src/pages/charts/Delisted.tsx` (new) — `/charts/delisted` page renders both charts. Sidebar nav link with `WifiOff` icon.
-`web/src/components/charts/KpiCards.tsx` — new optional `removedCount` prop; when set, renders a 7th "Removed (all-time)" KPI alongside the existing in-catalog "Delisted" badge. Wired from `Dashboard.tsx` via `useRemovedGames().data?.length`. Grid bumps from `xl:grid-cols-6` to `xl:grid-cols-7`.
### 📝 Docs
- README: removed the duplicate "Quick Links" section (the comprehensive 11-row "Quick links" table at the top covers everything the 4-row duplicate listed).
- README: added `🎯 Top offline (md)` row to the main Quick links table.
## [v3.2.3] – 2026-05-17 (The "View Commit Toast + Offline AC Lock" Edition)
Patch release on top of v3.2.2. Three user-reported fixes: the "View commit" action button in success toasts (now reachable + cross-platform), an editor lock that prevents anti-cheat fields from being set on offline games, and a broken `Mark dead games` workflow setup-python step. Web app + desktop bumped `1.2.2` → `1.2.3`. Repo public-facing version `3.2.2` → `3.2.3`. Tag `v3.2.3` is GPG-signed; companion desktop tag is `desktop-v1.2.3`.
- Migrated the eight `window.open(commit.htmlUrl, "_blank")` action handlers in `EditGameDrawer.tsx` (2), `Add.tsx` (2 inside `reportToast`), `BulkEditDrawer.tsx` (2), and `BulkActionBar.tsx` (2) to `openExternal()` from `web/src/lib/external-open.ts` — completes the follow-up migration flagged in v3.2.2's CHANGELOG. The Tauri webview was silently blocking the raw `window.open(...)` for external HTTPS URLs, so "View commit" did nothing on desktop.
- Each `toast.success(...)` with a "View commit" action now sets `duration: 15000` (was Sonner's 4 s default). On web the old toasts auto-dismissed before the user could read the description + click the action button.
- Handler now accepts the click event and calls `event.preventDefault()` so the toast stays visible after click (Sonner's default is to dismiss on action click — undesirable when the user wants to glance at the SHA after opening the commit).
- The fix applies to both the initial `toast.success` and the follow-up emit fired by `pollCommitVerification(...).then(...)` (same toast `id`, so `duration` must be set on the update too — otherwise the second emit rebounds to the 4 s default).
### 🔒 Anti-cheat fields lock on offline games
-`web/src/components/games/EditGameDrawer.tsx` — `FormFields` derives `lockAC = form.type_game === "offline"` and threads `disabled={lockAC}` to the AC `<select>`, the custom-AC `<Input>`, the three kernel `<Button>`s, and the AC note `<Textarea>`. A muted hint is rendered under the AC note when locked, explaining how to re-enable.
-`update()` setter now auto-resets `anti_cheat=""`, `anti_cheat_note=""`, `is_kernel_ac="unknown"` when `key === "type_game" && value === "offline"`. This keeps the `formToPatch()` diff honest — switching an online game with AC populated to offline now produces an explicit AC-clear in the commit instead of orphan anti-cheat data on an offline record.
-`web/src/pages/Add.tsx` — same pattern in `OverrideFields` + the `SingleAdd.setOv()` setter. `OverrideFields` combines the existing busy-state `disabled` prop with the new lock via `acDisabled = disabled || lockAC`, so the global "form is submitting" disable still wins. BulkAdd uses raw text / JSON input, so no UI lock needed there.
-`type_game === ""` (unknown) deliberately does **not** lock — only an explicit `"offline"` triggers the gate. The existing `validation.ts` "kernel?" badge rule for online + missing-kernel is untouched.
- New i18n key `edit.acLockedOffline` added to `web/src/i18n/locales/en.json` and `vi.json`, rendered as a `text-xs text-muted-foreground` hint under the AC note when `lockAC` is true.
### 🪦 `Mark dead games` workflow path fix
-`.github/workflows/mark-dead-games.yml` — `cache-dependency-path: scripts/requirements.txt` and the subsequent `pip install -r scripts/requirements.txt` both pointed at a path that doesn't exist. The file lives at the repo root (`requirements.txt`), consistent with the path `codeql.yml:25` already uses.
- Fix: both lines now reference `requirements.txt` at the root. The `setup-python` cache lookup no longer errors with `No file in /home/runner/work/free-steam-games-list/free-steam-games-list matched to [scripts/requirements.txt or **/pyproject.toml]`, and the install step actually finds the deps.
- Workflow is scheduled Mon + Thu 04:30 UTC; the next scheduled run will be the first end-to-end verification, but `workflow_dispatch` with `dry_run=true` is also available for ad-hoc validation.
## [v3.2.2] – 2026-05-11 (The "Bug Fix Quartet" Edition)
Patch release on top of v3.2.1. Four user-reported bug fixes touching the Ctrl+K command palette on desktop, the Health → Games navigation flow, Tauri process-stacking on every launch, and the `type_game` scraper that was defaulting every new game to `"offline"`. Web app + desktop bumped `1.2.1` → `1.2.2`. Repo public-facing version `3.2.1` → `3.2.2`. Tag `v3.2.2` is GPG-signed; companion desktop tag is `desktop-v1.2.2`.
### 🔗 Desktop Ctrl+K external link
- New `web/src/lib/external-open.ts` — lazy-detects the Tauri runtime via `__TAURI_INTERNALS__`, opens external URLs through `@tauri-apps/plugin-shell` on desktop (capability `shell:allow-open` already granted in `web/src-tauri/capabilities/default.json`), falls back to `window.open(url, "_blank", "noopener,noreferrer")` on web/PWA. Plugin module is lazy-imported, so the web bundle never pays for the Tauri code path.
-`web/src/components/common/CommandPalette.tsx` — Ctrl+K game results now route through `openExternal()`. The Tauri webview was silently blocking the raw `window.open(r.link, "_blank")` for external HTTPS URLs, so clicking a search result on desktop did nothing.
- Six other `window.open(...)` call sites (Health workflow link, Add, BulkActionBar, BulkEditDrawer, EditGameDrawer, DeviceFlowPanel) are flagged for follow-up migration to `openExternal()` — same desktop silent-fail will hit them when triggered.
### 🩺 Health → Games filter restoration
-`web/src/pages/Games.tsx` — adds `useSearchParams` + a `useEffect` that mirrors the URL `?search=` parameter into `useFilters.search` on mount. The Health page already linked rows to `#/games?search=<name>`, but Games never read the param, so the table stayed unfiltered and the Topbar input stayed empty. The store binding to Topbar means visual feedback is automatic once the filter is set.
- Guard `if (term !== null)` (instead of `if (term)`) lets `?search=` explicitly clear the filter — useful for shareable "no filter" links.
### 🪟 Tauri single-instance enforcement
-`web/src-tauri/Cargo.toml` — adds `tauri-plugin-single-instance = "2"` under the existing desktop-only `cfg(not(any(target_os = "android", target_os = "ios")))` block, matching the updater plugin's gating pattern.
-`web/src-tauri/src/lib.rs` — registers single-instance as the **first** plugin so it short-circuits duplicate launches before any other state initialises. The dup-launch callback calls `unminimize()` + `show()` + `set_focus()` on the existing `main` window. Without this, every Start-menu / shortcut / file-association invocation spawned a fresh `f2p-tracker.exe` that lingered in Task Manager.
- No capability changes needed — plugin runs entirely Rust-side, no frontend command exposed.
### 🎮 `type_game` online inference
-`scripts/core/fetcher.py` — new `_infer_type_game(categories)` reads `data.get("categories", [])` and returns `"online"` when any description contains `online`, `mmo`, `massively multiplayer`, `cross-platform multiplayer`, or `multi-player`. Pure `shared/split screen` descriptions are treated as local-only and skipped unless paired with another online signal.
- Wired into `apply_details()` next to the existing anti-cheat category loop, guarded by `is_empty(game.get("type_game"))` so manual prefills in `temp_info.jsonl` remain authoritative — the `MANUAL_FIELDS` merge in `data_store.merge_extension_data()` and the override re-apply in `ingest_new.py` are unchanged.
- The legacy default-to-`"offline"` at the end of `fetch_full()` stays as the final safety net for games with no multiplayer signal in Steam categories. New ingests of online F2P games now classify correctly instead of all-offline.
## [v3.2.1] – 2026-05-11 (The "Genre Cleanup" Edition)
Patch release on top of v3.2.0. Normalizes inconsistent `genre` values across the dataset (31 records, 10 canonical mappings) and broadens the webapp's genre combobox with 14 additional suggestions. Web app + desktop bumped `1.2.0` → `1.2.1`. Repo public-facing version `3.2.0` → `3.2.1`. Tag `v3.2.1` is GPG-signed; companion desktop tag is `desktop-v1.2.1`.
### 🧹 Genre normalization script
- New `scripts/normalize_genres.py` — local one-shot tool with `--apply` flag (dry-run by default). Reuses `core.data_store.load_main` / `save_main` so writes are atomic + sharded.
- Idempotent — second run reports "data already canonical".
- Comma-separated values like `"Action RPG, Gacha"` (Wuthering Waves, Honkai Impact 3rd) are flagged in a "Manual review needed" section rather than auto-split, since the schema is single-genre.
- All `games/*.md` regenerated via `scripts/generate_tables.py`; affected genre files include the new sentence-case slugs (`turn-based-strategy.md`, `top-down-shooter.md`, `third-person-shooter.md`, `roguelite.md`, etc.).
- Sentence-case style matches the normalized data values.
- Dropdown filter on `web/src/pages/Games.tsx` is facet-driven (auto-updates from the records), so it now shows the deduplicated canonical names. The `EditGameDrawer` combobox suggests the 14 new entries while still accepting free-text input.
## [v3.2.0] – 2026-05-11 (The "SEO + Donate + Auto-Discussion + Health Polish + Dev Docs" Edition)
Single-PR bundle (#64) shipping eight features on top of v3.1.0. Web app + desktop bumped from `1.1.0` → `1.2.0`. Repo public-facing version `3.1.0` → `3.2.0`. Tag `v3.2.0` is GPG-signed; companion desktop tag is `desktop-v1.2.0`.
- New `web/public/robots.txt` (allow all + sitemap pointer) and `web/public/sitemap.xml` (5 entries: site root, GitHub repo, all-games / top-online / changelog markdown).
- New hook `web/src/hooks/useDocumentTitle.ts` — sets `document.title` to `<page> · Steam F2P Tracker` and re-runs on language change. Wired into all 18 routes (Dashboard / Games / TopOnline / Health / Activity / Add / About / Donate / Settings / 9 charts).
- VitePWA already emits `manifest.webmanifest` from `vite.config.ts`; no manual manifest needed.
### 💬 Auto-create GitHub Discussion on release
- New `.github/workflows/announce-release-discussion.yml` — fires on `release: published` (plus `workflow_dispatch` with a `tag` input for re-runs).
- Implemented via `actions/github-script@v8` + GraphQL `createDiscussion` (REST has no equivalent).
- Resolves the discussion category by slug — defaults to `Announcements`, falls back to `General` with a logged warning, then to the first available category.
- **Idempotent**: a GraphQL search runs first; if a discussion with the same title exists, the workflow skips with `core.notice()` and returns the existing URL via output. Re-running `workflow_dispatch` is therefore a no-op.
- Permissions: `contents: read`, `discussions: write` — both granted by `GITHUB_TOKEN` defaults once Discussions is enabled on the repo.
### 💖 Donate page
- New `web/src/pages/Donate.tsx` route at `/donate` — grid of 5 platform cards (GitHub Sponsors, Ko-fi, Buy Me a Coffee, Patreon, PayPal) sourced from `.github/FUNDING.yml`.
- Each card has a tinted icon ring, label, short description, and an "Open" button (`target="_blank" rel="noopener noreferrer"`).
- New nav item in `web/src/components/layout/Sidebar.tsx` SECONDARY group (between About and Settings); `Heart` icon from lucide.
- Full EN + VI i18n keys under `donate.*` (title / subtitle / cta / footnote + per-platform label & desc).
- New `web/src-tauri/TAURI.md` — desktop build prerequisites (incl. CI's exact `apt-get` line), local + production build commands, signing + auto-update notes, troubleshooting.
-`AUTHORS.md` — new "Dev info" table (GitHub handle, IDE channel, toolchain versions, link map to all the above).
- README "Docs" section — links the four new docs.
### 🤖 Telegram bot user-guide pointer
- New `docs/telegram-bot.md` — one-page pointer to the external [`telegram-scraper-bot/docs/USER_GUIDE.md`](https://github.com/poli0981/telegram-scraper-bot/blob/main/docs/USER_GUIDE.md), bot source repo, plus a paragraph each on what the bot does and the whitelist lifecycle.
-`CONTRIBUTING.md` — section 3 (`@my_skull_bot`) gets a 3-line callout with the user guide link, bot source URL, and the new in-repo summary doc.
-`web/src/pages/About.tsx` — Maintainer card's privacy note now includes a "Bot user guide & source" sub-card with the same three links.
### 🩺 Health bucket split
-`web/src/pages/Health.tsx` — `gatherIssues()` adds a fifth `IssueGroup`: `OnlineAcUnknown` for games with `type_game === "online"` and `anti_cheat ∈ {"", "-"}`. Previously these games were silently dropped from all categories; now they have a discoverable home.
- Edge-case fix: the existing "Kernel" filter compared `(r.anti_cheat ?? "-") !== "-"`, missing the empty-string case. Both filters now use a normalised `(r.anti_cheat ?? "").trim()`.
-`ShieldQuestion` icon (lucide). EN + VI i18n keys: `health.groupOnlineAcUnknown` + `…Desc`.
### 🎮 Steam Desktop direct link
- New helper `web/src/lib/steam-link.ts` — `steamProtocolUrl(appid)` returns `steam://store/<appid>`, `steamWebUrl(appid)` returns the regular HTTPS store URL.
-`web/src/components/games/GameDetailDrawer.tsx` — single store link replaced by two buttons rendered side-by-side: a primary "Steam Desktop" (`steam://`) and an outline "Web" (`https://`). Tooltip on the desktop button explains the fallback path.
- Works in both web build (browser shows protocol prompt if Steam is installed, silent fail otherwise — Web button is the safety net) and Tauri build (Tauri 2 allows `steam://` navigation by default; no allow-list change needed).
- EN + VI i18n: `detail.openOnSteamDesktop`, `detail.openOnSteamDesktopHint`, `detail.openOnSteamWeb`.
### 🛌 Bi-weekly offline-player leaderboard
- New `scripts/top_offline.py` — clones the `top_online.py` shape but filters `_is_offline(g)` (non-empty `type_game ≠ "online"`). Emits `games/top-offline.md` (top 100 single-player F2P concurrents, 10-column format identical to top-online).
- New `bash/offline.sh` matches the shape of `bash/online.sh` (pip install requests → run script → conditional commit).
- New `.github/workflows/top-offline.yml` — cron `0 5 1,15 * *` (1st + 15th of each month at 05:00 UTC) plus `workflow_dispatch`. Shares the unified `data-write` concurrency group.
- Health page (`web/src/pages/Health.tsx`) — new manual trigger button "Top offline" (next to the existing "Top online" trigger).
- **Bug fix during implementation**: `scripts/core/fetcher.py:update_players_only()` had a hardcoded `type_game == "online"` filter that would have made the offline workflow refresh zero rows. Extended with a `type_filter` kwarg (`"online"` default for backward compat, `"offline"`, or `"all"`); `top_offline.py` passes `type_filter="offline"` (excludes both online and empty/unclassified type).
## [v3.1.0] – 2026-05-09 (The "Less CI Noise, Lighter Images, Dead-Game Detection" Edition)
Four PRs landed in this release plus a refresh of the docs and the contributor surface around the new Telegram bot. Web app + desktop app bumped from `1.0.0` → `1.1.0`. Repo public-facing version `3.0.1` → `3.1.0`. Tag `v3.1.0` is GPG-signed; companion desktop tag is `desktop-v1.1.0`.
### 🛠️ CI hygiene — notify wrappers (#60)
- The 3 notify wrappers (`notify-ci-failure`, `notify-deploy`, `notify-release-pipeline`) used to trigger on `workflow_run: workflows: ["*"]` and were filtered out by their reusable callee's `if:` — 95–100 % of runs showed as "skipped". Replaced the catch-all with explicit lists of source workflow `name:` strings per wrapper, plus job-level `if:` to short-circuit non-matching conclusions. Drops skip rate to <10 %.
- Trade-off documented in each file: renaming a source workflow's `name:` field silently breaks notifications; comment warns about the coupling.
-`scripts/generate_tables.py:68` — markdown thumbnails now use `capsule_184x69.jpg` instead of `header.jpg` (~80 % bandwidth reduction at the same 120 px render width).
- Web app `GamesTable` + `CommandPalette` — capsule swap with explicit `width`/`height` to eliminate CLS, plus `onError` fallback to `header.jpg` for the ~5 % of games without a capsule variant.
-`GameDetailDrawer` — `<picture>` element with WebP source via `images.weserv.nl` proxy + JPEG fallback. Lazy-loaded, explicit dimensions.
-`vite.config.ts` — new `CacheFirst` runtime cache for `images.weserv.nl` (`statuses: [200]` only — opaque 0-status would cache proxy errors).
- New helper `web/src/lib/image.ts` — `headerToCapsule()` + `webpProxyUrl()`.
- New cron `Mon + Thu 04:30 UTC` flags **online games released >1 year ago** whose `current_players == 0` for **≥14 days** (configurable via `DEAD_GAME_DAYS` env or `--days` CLI). On trigger: `is_dead = true` + `"💀 Dead game"` appended to `notes` (idempotent).
- **State model**: ISO timestamp `zero_player_since` (robust against schedule drift), not a streak counter.
- **Mark mechanism**: additive `is_dead: bool` + note. `status` stays `"active"` so the existing enum / Top Online filter / chart groupings don't break. Web app gains a "Hide dead" filter toggle and a 💀 emoji prefix on dead rows.
- **Dry-run available**: `python scripts/mark_dead_games.py --dry-run --days 0` for auditing without writes.
- New helper `append_note_idempotent()` in `scripts/core/data_store.py`. Retrofitted onto `check_dead_links.py` to fix duplicate `"💀 Delisted"` accumulation on reruns.
- Schema migration via `_SKELETON_TEMPLATE` only (no one-shot script). Both the Python pipeline and the React app inherit defaults via existing `migrate_record()` / `migrateRecord()` loops.
### 🔄 Concurrency unification
All data-mutating workflows now share `concurrency: { group: data-write, cancel-in-progress: false }`:
Prevents races on `git push` to `data/` shards. Bot-ingest moved from its own `bot-ingest` group to the unified group.
### 📝 Docs + contributor surface (this PR)
- **`AUTHORS.md`** at repo root — handle map for the maintainer, AI-assistant disclosure, MIT licensing reminder.
- **`username.txt`** extended with `telegram bot`, `telegram user`, and `email` lines (canonical machine-readable handle map mirrored by `AUTHORS.md`).
- **`assets/qr/`** — QR-code PNGs for `@my_skull_bot` and `@SkullMute0011` (mirrored to `web/public/qr/` so the SPA can serve them). Generated via `python -m qrcode`.
- **`web/src/pages/About.tsx`** — Maintainer card now lists Telegram bot + Telegram DM (with QR thumbnails inline) + Email. New "Telegram QR codes" card with full-size scannable codes. Privacy note about Telegram `user_id` handling.
- **`CONTRIBUTING.md`** rewrite — adds the `@my_skull_bot` flow as a first-class contribution path (find `user_id` → DM maintainer privately → whitelist → run when bot's online → follow prompts). Loud privacy warning at the top.
- **`docs/PRIVACY_POLICY.md`** — new "Telegram bot" section covering the `user_id` data flow, where it's stored, retention/removal, and the maintainer's commitment.
- **`docs/ToS.md`** — new section 5.1 "Sharing personal information when contributing" with non-negotiable rules about private vs public channels.
- **`docs/Contact.md`** — Telegram bot + DM entries added at the top.
- **README** badges and feature list refreshed (version bumped, dead-game workflow listed, About-page QR card mentioned).
Same-day post-v3.0.0 maintenance covering Phase 9 (auto-update foundations + CVE bumps + Device Flow scaffold), Phase 10 (Tauri build break + i18n full coverage + deps audit), and Phase 10.1 (minisign keypair rotation). The desktop release pipeline is now end-to-end green — `desktop-v1.0.0` finally produces signed `.msi` / `.exe` / `.dmg` / `.AppImage` / `.deb` / `.rpm` artefacts with a valid `latest.json` for auto-update.
## v1
### 🖥️ Phase 9 — auto-update foundations (#56)
-`tauri-plugin-updater` wired into `web/src-tauri/`. Endpoint pinned to the Releases page so installed clients fetch `latest.json` on launch.
- Updater pubkey embedded in `tauri.conf.json` (gated behind a no-op for mobile builds via `#[cfg(not(any(target_os="android", target_os="ios")))]`).
- GitHub Device Flow scaffold added to Settings: signed-in users no longer have to paste a long-lived PAT — they kick off `https://github.com/login/device`, type the user_code, and the app polls until token issuance. Falls back to PAT for the offline path.
- Dependency CVE bumps (vite 5 → 7, vite-plugin-pwa 0.20 → 1.x). Path-traversal fix in source-map handling. No source changes required for the bumps.
- More i18n: a chunk of edit-drawer / activity / dashboard chrome got proper translation keys.
- **Tauri lib-name regression fixed.** Phase 9's auto-updater work introduced a `f2p_tracker_lib::run()` call in `main.rs` without declaring `[lib]` in `Cargo.toml`. Cargo's implicit lib name is `f2p_tracker` (hyphens → underscores from the package name) so the call failed to resolve and `cargo build` blew up. Added the explicit Tauri-2-template-style block:
```toml
[lib]
name = "f2p_tracker_lib"
crate-type = ["staticlib", "cdylib", "rlib"]
```
The triple crate-type keeps the door open for future `tauri ios init` / `tauri android init` work that `lib.rs`'s `#[cfg_attr(mobile, tauri::mobile_entry_point)]` already implies.
- **i18n now reaches every chrome surface** (~150 new keys across new namespaces `charts`, `activity`, `add`, `system`, `cmdk`, `about`, `bulk`, `detail`, `diff`, `dialogs`, `health`). All 9 chart pages, Activity, Add, Health, Top Online, About headings, drawers (Edit / BulkEdit / Diff / GameDetail), `PwaIndicator`, `QueryState`, `GpgQuickUnlock`, `Topbar` tooltips/aria-labels, `Settings` rate-limit panel, `BulkActionBar` confirm dialog, `GamesTable` tooltips, and `CommandPalette` resolve through `useTranslation`. Long-form About prose stays English per the `settings.languageHint` policy. Enum values (anti-cheat / genre / type_game / safe) stay dataset-stable.
- **Third-party deps audit.** Walked `web/package.json` against `About → Stack & third-party` and `docs/ACKNOWLEDGEMENTs.md`. Added missing entries: `react-router-dom`, the i18next stack (`i18next` + `react-i18next` + `i18next-browser-languagedetector`), Tauri 2 + plugins (shell / updater / process), `echarts-for-react`, the styling utilities (`class-variance-authority` / `clsx` / `tailwind-merge` / `tailwindcss-animate`), and PostCSS + autoprefixer. Vite version corrected 5 → 7 (was already bumped by Phase 9; About just hadn't caught up).
- `ACKNOWLEDGEMENTs.md` restructured into grouped sections (runtime/build, styling, UI primitives, routing & i18n, data & state, charts, crypto & PWA, desktop) with deep links + SPDX licences.
- `web/src-tauri/Cargo.lock` now committed for reproducible desktop builds.
- `desktop-v1.0.0` was failing at the final sign-updater-bundle step:
```
failed to decode secret key: incorrect updater private key password:
Missing comment in secret key
```
minisign formats the error so the inner "Missing comment" is the symptom of a wrong password — when the password is wrong, decryption returns garbage and the expected `untrusted comment: minisign encrypted secret key` header bytes don't appear. The original keypair's password was lost, so the GH secret could no longer decrypt the key.
- Re-keyed via `npx tauri signer generate --ci -p ""` with no password. Stored at `~/.tauri/f2p-tracker{,.pub}` on the maintainer's box; `web/src-tauri/.gitignore` extended (`*.key`, `f2p-tracker{,.pub}`) as a guardrail in case keys ever land in `src-tauri/` during dev.
- New pubkey baked into `tauri.conf.json` `plugins.updater.pubkey`. GH secrets `TAURI_SIGNING_PRIVATE_KEY` and `TAURI_SIGNING_PRIVATE_KEY_PASSWORD` rotated via `gh secret set` (password = empty string).
- **Trade-off**: any user already on a build signed with the old key would have their auto-update break. Nobody hit that path because Phase 9 / Phase 10 release runs both failed before publishing artefacts. Phase 10.1's rebuild is the first actually-shipped `desktop-v1.0.0`.
### 🏷️ Tag handling
- `desktop-v1.0.0` was force-pushed twice in this cycle as the workflow input commit advanced (Phase 9 → Phase 10 → Phase 10.1). The triggering tag is GPG-signed each time. Once the auto-update story is real users-on-it, future fixes should bump `desktop-v1.0.x` instead of force-pushing.
### 📝 Docs (this release)
- `CHANGELOG.md` — this entry.
- `web/src-tauri/Cargo.toml` + `tauri.conf.json` + `.gitignore` — Phase 10 / 10.1 changes documented in their own commit messages and PR bodies (#57, #58).
---
## [v3.0.0] – 2026-05-07 (The "It Has a Website Now" Edition)
The repo is no longer just a list. It is a **list + a React/Vite web app + a Tauri desktop app**, all reading the same Python-pipeline-maintained data.
### 🌐 Web app — `web/` + GitHub Pages
Built across phases 1 → 7. Live at <https://poli0981.github.io/free-steam-games-list/>.
- **Phase 2** — PAT-based GitHub auth, single-record edit drawer for the 8 manual fields, diff viewer, single + bulk Steam-link queue into `scripts/temp_info.jsonl`, conflict-retry, sonner toasts.
- **Phase 3** — client-side OpenPGP signing via Git Data API: switched all writes from Contents API to `commitFile(getHead → createBlob → createTree → buildCommitContent → openpgp.sign → createCommit → updateRef)`. Settings panel with passphrase unlock + lock indicator. Earlier claim that PATs auto-sign was wrong — Contents API commits land Unverified.
- **Phase 4** — fixed GPG salt-notation incompatibility (`config.nonDeterministicSignaturesViaNotation: false`) so OpenPGP.js v6 signatures parse on GitHub. Bulk edit + bulk delete in one signed multi-shard commit. 8 remaining charts (tags wordcloud, AC stacked, languages heatmap, release-year histogram, catalog-growth cumulative line, reviews histogram, online player tiers pie, DRM/DLC bars). Health page with workflow_dispatch buttons. ⌘K command palette (cmdk).
- **Phase 4.1** — GPG signature payload fix: dropped trailing `\n` after the commit message so our signed bytes match `verification.payload` byte-for-byte. Verified via `gh api .../commits/{sha}.commit.verification.reason → valid`.
- **Phase 6** — curated enums (`ANTI_CHEAT_ENUM`, `GENRE_ENUM`) + dropdowns, JSON-editor toggle in the edit drawer (full-record replace), manual-field overrides on Add (single + bulk JSON mode propagates `genre/type_game/anti_cheat/notes/safe` straight into `temp_info.jsonl`), GamesTable pagination 50/100/200/500/all + hidden scrollbar + per-row validation badge, per-game permalinks `/games/:appid` with friendly 404 drawer, verify-after-commit polling (toast updates with `verification.reason` once GitHub confirms), CSV/JSON export of the filtered subset, About page (repo + dev info from `username.txt` + 3rd-party stack + issue templates), topbar GPG quick-unlock popover, owner-gate (`useIsOwner` + `OWNER_LOGIN`) hides edit/add/delete UI from non-owners.
- **Phase 6.1** — Edit Always Failing fix: Contents API caps `content` at 1 MB; `data/data_001.jsonl` is 1.49 MB so the read came back empty and every edit threw "Record not found". New `getRepoFileText()` helper falls back to the `/git/blobs/{sha}` endpoint for oversize files.
- **Phase 6.2** — stale-after-edit fix: bumped `data/index.json.last_updated` in every shard-modifying commit AND switched the SW cache to `NetworkFirst` (raw.github CDN is Fastly-cached for 5 min). Plus optimistic-update helpers (`optimisticEdit/Replace/BulkEdit/BulkDelete`) write straight to TanStack + IndexedDB so the editor sees their own change instantly without waiting for the CDN.
- **Phase 7** — date-column sort fix (`parseReleaseDate`), hamburger mobile nav (Sheet drawer, auto-close on route change), About expansion (Heads-up caveats + AI disclosure + legal links + per-third-party SPDX licence badges), legal docs rewritten (DISCLAIMER + EULA + ToS + PRIVACY) with the four caveats from `notes.txt` (genre best-effort, English-only, test-data leakage, unsigned-commit dev artefacts), refreshed `bug_report.yml`, workflow Node 20 → 24 + actions versions bumped.
- Auto-detect from `navigator.language` on first load; persistent override via Settings → Language.
- Sidebar nav, Topbar, Settings, Dashboard, Top Online, common buttons, common toast strings translated. Long-form legal copy stays English by design (legal review hard to mirror exactly across two languages).
- `CHANGELOG.md` — this entry consolidating phases 1 → 8.
- `docs/ACKNOWLEDGEMENTs.md` — refreshed with phase-by-phase AI assistance breakdown (Grok v1; Claude for v2 + the entire web/desktop layer + this changelog).
- `web/README.md` — phase 8 status appended.
### 🛠️ Pipelines unchanged
- All 9 v2.x Python pipeline workflows (update-json, generate-tables, top-online, update-reviews, dead-link-check, purge-unhealthy, ingest-new, ingest-from-issue, refetch-all) keep their schedules and behaviour. Two new workflows added: `deploy-pages.yml` (Phase 1) and `release-desktop.yml` (Phase 8).
---
## [v2.1.0] - 2026-03-28 (The "Extension-Ready + Performance" Edition)
### 💥 Breaking Changes
- `desc` field **removed** from schema. Use `description` only. Migration script handles upgrade automatically.
- `free_type` field removed (unreliable from API, extension handles classification client-side).
- `jsonlines` pip dependency dropped – all I/O now uses stdlib `json` (faster, zero deps).
- `fetcher.py` function renamed: `_process_batch()` → `process_batch()` (public API).
### 🏗️ Schema v2.1 (Extension-Compatible)
- **7 new fields** added to every game record, matching Chrome extension output:
- `publisher` (list) – e.g. `["Square Enix", "Feral Interactive (Mac)"]`
- `platforms` (list) – e.g. `["Windows", "macOS", "Linux"]`
- `languages` (list) – e.g. `["English", "French", "Japanese"]`
- **Be inclusive:** Everyone's welcome, regardless of skill level (especially noobs on Easy mode).
- **Be inclusive:** Everyone's welcome, regardless of skill level (especially noobs on Easy mode), and however you use the site: mouse, keyboard, screen reader, zoom. If something keeps you out, see [`ACCESSIBILITY.md`](ACCESSIBILITY.md).
- **No malware/fake links:** Instant ban from contributing. I have trust issues already.
- **Disagreements?** Keep it calm in Issues/PRs. If it gets heated, I'll just close it and go play a game.
### Enforcement
I'm the only maintainer (with Grok as backup), so violations = close issue/PR, block if needed. No appeals – life's too short.
I'm the only maintainer (with an AI assistant as backup), so violations = close issue/PR, block if needed. No appeals – life's too short.
**Reporting:** if something needs raising privately rather than in the Issue
thread it happened in, email **contact@poli0981.dev**. One person reads it, so
expect a slow reply rather than none. Security holes do not belong here — use
GitHub’s private vulnerability reporting, see [`SECURITY.md`](SECURITY.md).
This is based on the Contributor Covenant, but shortened because who reads long docs?
Yo, thanks for stopping by! This repo is a hobby project by a broke, unemployed Vietnamese dev (20-something, introvert max level, dropped out uni year 3, mooching off family, Steam library 400+ games 80% under $10 sale addiction). Powered ~70% by AI assistants — Grok for v1, Claude for v2+ — the only non-judgmental friends keeping this alive while I play Easy mode only :))
Want to help? Awesome — no strict rules, life's hard enough. Pick whichever path below is least-friction for you.
Want to help? Awesome — life's hard enough, so the rules are short.
## Project status: stable, maintenance only
Since 2026-11-11 the project is finished rather than abandoned. The pipeline
still refreshes the list every day and the site and apps stay up, but the code
is no longer growing:
- **No new features.** Feature requests are not taken, as issues, discussions
or pull requests. A pull request that adds one is closed, however good it is.
- **Code changes only for** security advisories (CVEs), runtime and dependency
updates (Node, Python, Rust, the npm / pip / cargo packages, the GitHub
Actions), and whatever those break. Dependabot opens most of them.
- **Issues and pull requests are for the data:** adding a game, correcting one,
removing one.
- Something **broken** (the site, an app, a wrong number) or an
**accessibility barrier** can still be reported. It gets a fix, not a
redesign.
- A **vulnerability** goes through [`SECURITY.md`](SECURITY.md), never a public
issue.
Forks are welcome to go further: the code is MIT and the dataset CC BY 4.0.
## Maintainer contact
The canonical handle list is in [`AUTHORS.md`](AUTHORS.md) at the repo root (mirror of [`username.txt`](username.txt) for human reading). Web-app version: <https://poli0981.github.io/free-steam-games-list/#/about>.
The canonical contact list is in [`AUTHORS.md`](AUTHORS.md) at the repo root
(machine-readable mirror: [`username.txt`](username.txt); the chatty version is
Short version: **contact@poli0981.dev** for anything private,
**security@poli0981.dev** for a vulnerability (after GitHub's private
reporting, see [`SECURITY.md`](SECURITY.md)), and <https://poli0981.dev/> or
<https://poli0981.dev/links/> for everything else.
> [!WARNING]
> **Privacy first.**When sending your Telegram `user_id` (needed for the bot whitelist below), **DM the maintainer privately**. Do **not** post it in:
> - Public Discord channels (including the project's own `#general`).
> - Public Telegram groups or super-groups.
> - GitHub issues, PR comments, or commit messages.
> - Public posts on X / Bluesky / Mastodon / YouTube comments.
>
> Personal info — Telegram `user_id`, email, real name, etc. — should travel through DM only. The maintainer will not ask you for anything beyond the `user_id` for the bot.
> **Privacy first.**Issues, PR comments and commit messages are public and
> permanent — GitHub keeps them in the fork network even after deletion. Keep
> personal information (email, real name, account IDs) out of them and send it
> by email instead. The maintainer will never ask you for an account ID, a
> token, or a password: there is no whitelist to join and nothing to verify.
---
## How to contribute
### 1. Quick + lazy: open an issue (preferred for most users)
### 1. Open an issue
Go to the [Issues tab](https://github.com/poli0981/free-steam-games-list/issues/new/choose) and pick a template:
Go to the [Issues tab](https://github.com/poli0981/free-steam-games-list/issues/new/choose) and pick a form:
- ➕**Add new games**(max 15 links per issue)
- ➖**Delete game**(max 10 per issue)
- 🐛 **Bug report**
- 💡 **Feature request / improvement**
- 📢 **Feedback / rant**
- ❓ **Off-topic**
- ➕**Add game**— a free game that is still missing (max 10 per issue)
- ✏️**Edit game**— a published game with something wrong: genre, type, anti-cheat, notes, safe
- ➖**Delete game** — paid now, not a game, malware, duplicate (max 10 per issue)
- 🐛 **Bug report** — something that is broken
- ♿ **Accessibility barrier** — something you can't use with a keyboard, a screen reader or zoom (see [`ACCESSIBILITY.md`](ACCESSIBILITY.md))
Fill the form (checkboxes, dropdowns, short descriptions). The `Ingest from Issue` workflow auto-runs on the `[add-game]` template, validates, fetches Steam metadata, and closes the issue with a status comment. Other templates are reviewed manually when caffeine hits.
Blank issues are off. Every form is reviewed by hand when caffeine hits — none of them auto-run a workflow.
### 2. Sign in to the web app (for owner-equivalents)
New free games are found on Steam automatically every day and reviewed before they are listed, so most turn up on their own. Use **Add game** for one that is still missing a few days after it went free.
If you have repo write access:
### 2. Open a pull request (data)
1. Open <https://poli0981.github.io/free-steam-games-list/>.
2. Settings → paste a Classic GitHub PAT (scopes: `repo` + `workflow`).
3. Optionally unlock a GPG private key in Settings to sign commits → **Verified ✓** badges.
4. Add via the `Add` page (single + JSON bulk) or edit/delete via the table drawers.
Fork → branch → one of these → push → open the PR. The template has a short checklist.
The web app commits via the Git Data API + GPG signing path. The optimistic-update layer means edits show up instantly without waiting for the Fastly CDN.
**Add a game:** append store links to `scripts/temp_info.jsonl`.
### 3. Scraper Info Game bot — `@my_skull_bot` on Telegram
Quick path for users who don't want a GitHub PAT but do want to add games. The bot wraps the same `ingest-new` pipeline behind a Telegram chat.
A queued line is a link and nothing else (full URL, short URL or bare appid): any other key is ignored, and the game is fetched from Steam and checked (free, a game, reachable) before it is published.
**Correct a game:** add an override. It is a standing instruction in `data/overrides/<appid>.json` that every pipeline run keeps.
> **One-time setup (whitelist your Telegram `user_id`)**
>
> 1. **Find your Telegram `user_id`.** Easiest way: DM `@userinfobot` on Telegram and it replies with your numeric `user_id`. Other options: `@RawDataBot`, `@getmyid_bot`, or any "what's my Telegram ID" bot of your choice.
> 2. **DM the maintainer privately** with that `user_id`. Channels that work:
> - X DM, Discord DM (NOT public channels), or any other private channel listed in [`AUTHORS.md`](AUTHORS.md).
>
> **Strictly forbidden:** posting your `user_id` in any public channel — Discord `#general`, Telegram groups, GitHub issues, public X/Bluesky posts. The bot rejects messages from non-whitelisted IDs, so leaking the ID to randoms doesn't grant them access — but it still leaks your Telegram identity to anyone watching that channel.
> 3. Maintainer adds your `user_id` to the bot's whitelist. You only do this **once**.
```bash
python scripts/edit_game.py 730 --show
python scripts/edit_game.py 730 --set genre="FPS" --reason "Steam's genre is too coarse"
```
> **Each session (when you want to add games)**
>
> 4. **Check whether the bot is online.** The bot runs **locally on the maintainer's machine via Docker**, ~2–5 hours per day depending on availability. If it's offline, your messages will sit unread until it comes back up. There is no SLA.
> 5. **Open the bot:** [@my_skull_bot](https://t.me/my_skull_bot) ([QR code](assets/qr/telegram-bot.png)).
> 6. **Send Steam URLs** (one per line, or one per message — bot accepts either). Full URLs, short URLs, and bare appids all work:
> ```
> https://store.steampowered.com/app/730/
> 570
> https://store.steampowered.com/app/440/
> ```
> 7. **Follow the bot's prompts.** It validates URLs, fetches metadata via the Steam API, optionally lets you set manual fields (`type_game`, `genre`, `notes`, `safe`), and dispatches the `Bot Ingest` GitHub Actions workflow with your queue.
> 8. **Wait for the workflow to finish.** The bot edits its own message with the result — `✅ Steam ingest done` + summary line, or `❌ Steam ingest failed` with a link to the workflow run for debugging.
Only the human-judged fields can be overridden: `genre`, `type_game`, `safe`, `notes`, `anti_cheat`, `anti_cheat_note`, `is_kernel_ac`. Everything else (name, tags, languages, reviews, players…) is whatever Steam says and is refreshed from Steam.
The bot itself is open-source companion code (separate repo). The workflow it dispatches lives in [`.github/workflows/bot-ingest.yml`](.github/workflows/bot-ingest.yml).
**Remove a game:** add a blocklist line. The reason and the note are public.
### 4. Chrome extension (for power users)
```bash
python scripts/delete_game.py 730 --reason not_free --note "paid since 2026-11"
```
The companion [Chrome extension](https://github.com/poli0981/free-steam-games-list-extension) detects F2P games on Steam store pages and pushes pre-fetched metadata to `scripts/temp_info.jsonl`. The `Ingest New Game Links` workflow merges and dedupes on push.
Leave out `--apply` in both commands, and **never edit `data/data_*.jsonl` or `data/index.json` by hand**: the pipeline rewrites them on its next run and an edit there is lost (and breaks the hashes the apps check). `Check Overrides` validates an override or blocklist change on the pull request.
For code changes or bigger data edits:
### 3. Pull requests that touch code
1. Fork → branch.
2. Edit code in `scripts/` / `web/src/` / docs, or append rows to `scripts/temp_info.jsonl`:
3. Push → open PR. Reviewer (= me) will look when caffeine hits.
Only two kinds are merged now:
Manual fields preserved through the ingest pipeline: `type_game`, `genre`, `anti_cheat`, `anti_cheat_note`, `is_kernel_ac`, `safe`, `notes`.
- a **security fix** — report it privately first ([`SECURITY.md`](SECURITY.md));
- a **runtime or dependency update**, or the repair of what one broke.
`npm run typecheck && npm test && npm run build && node scripts/verify-dist.mjs --web` must pass in `web/`, and `python -m pytest scripts/tests` for the pipeline. Dependencies are pinned and hashed; the rules are in [`CLAUDE.md`](CLAUDE.md) ("CI installs only what is pinned").
The companion browser extension ([steam-f2p-extension](https://github.com/poli0981/steam-f2p-extension)) is archived and no longer a way in.
---
## Tips for smooth contributions
- **Games must be free-to-play on Steam.** No demos, no paid-now games, no malware-flagged ones.
- **Notes / safe fields** are optional but useful. Examples: `"safe": "y"`, `"notes": "Toxic max"`, `"notes": "Grind phê Easy mode"`.
- **Spam / off-topic** issues get closed without comment. Don't be that person.
- **Code style:** match the surrounding file. No hard rules. The Python pipeline is intentionally low-ceremony; the React/Vite side is TS-strict.
- **Tests:** there's no formal test suite for the data pipeline. For web changes, `npm run typecheck && npm run build` must pass.
- **Notes / safe** are worth mentioning in an Add or Edit request ("safe to play", "Toxic max", "Grind phê Easy mode"); the maintainer records them as overrides.
- **Spam / off-topic / feature-request** issues get closed without comment. Don't be that person.
- **Questions and chit-chat** go to [Discussions](https://github.com/poli0981/free-steam-games-list/discussions), not issues.
## Code of conduct
@@ -115,4 +122,4 @@ Manual fields preserved through the ingest pipeline: `type_game`, `genre`, `anti
Thanks for making this noob repo better! Star if you find a hidden gem, or buy me a coffee via [FUNDING.yml](.github/FUNDING.yml) to fuel instant noodles + more sale games ✨
Questions? Open an issue — that's contributing too :))
Questions? [Discussions](https://github.com/poli0981/free-steam-games-list/discussions) — that's contributing too :))
A **curated list** of free-to-play games on Steam — now ~1,200 of them — no quality guarantees, no endorsements, just pure listings by a broke, unemployed Vietnamese dev with too much free time and a Steam library full of sale games (80% under $10).
A **curated list** of free-to-play games on Steam — the badge above has today's count — no quality guarantees, no endorsements, just pure listings by a broke, unemployed Vietnamese dev with too much free time and a Steam library full of sale games (80% under $10).
**v3.0.0** is the version that grew limbs. It is no longer a list. It is also:
**v4.0.0** is the version that got rebuilt from the ground up. It is still a list. It is also:
- a **React web app** at <https://poli0981.github.io/free-steam-games-list/> with a virtualised 1.2k-row table, 12 charts, fuzzy search, faceted filters, owner-gated bulk edit/delete with **GPG-signed commits**, queue-based add (single + JSON bulk), CSV/JSON export, validation badges, command palette, PWA / offline cache, **vi/en i18n**, and per-game permalinks;
- a **desktop app** (Tauri 2, fixed-size 1400 × 900 window — see Releases for Win/Mac/Linux installers);
- a **web app** at <https://free-steam-games.win/> (SvelteKit, served by a Cloudflare Worker) with a virtualised table of every game, charts, fuzzy search, filters you can link to, CSV/JSON export, a command palette, a page per game that search engines can read, **en/vi i18n**, and an installable offline mode. It is read-only for visitors: there is no sign-in;
- a **desktop app** (Tauri 2, resizable window, updates itself from GitHub Releases — Win/Mac/Linux installers);
- an **Android app** (sideloaded APK, Android 11+);
- an **admin** at `/admin`, behind Cloudflare Access: a review queue for the games the daily discovery sweep finds (approved by the maintainer, or in capped daily batches by a rule the maintainer turns on), corrections to published games, and removals;
- the same **Python pipeline** that has run daily under GitHub Actions since v1.
**Powered ~70 % by AI** (Grok for v1, Claude for v2 + the entire web/desktop layer) — code is reviewed and tested, but mistakes happen. See the [Disclaimer](docs/DISCLAIMER.md) for the specific accuracy caveats (genre best-effort, English-only assumptions, test-data leakage, unsigned-commit dev artefacts).
**Wallet safe (for now). Play at your own risk.**
### Project status
> [!NOTE]
> **Stable, maintenance only (since 2026-11-11).** The project does what it set
> out to do, so it is finished rather than abandoned: the pipeline keeps the
> list fresh every day, and the site and apps stay up.
>
> - **No new features.** Feature requests are not taken, as issues or as pull requests.
> - **Code changes only for** security advisories (CVEs), runtime and dependency
> updates, and whatever those break.
> - **Issues and pull requests are for the data:** adding a game, correcting
> one, removing one. Something broken or an accessibility barrier can still be
> reported; it gets a fix, not a redesign.
> - A vulnerability goes through [`SECURITY.md`](SECURITY.md), never a public issue.
>
> Details in [`CONTRIBUTING.md`](CONTRIBUTING.md).
| 🏆 Top online (md) | [games/top-online.md](games/top-online.md) |
| 🎯 Top offline (md) | [games/top-offline.md](games/top-offline.md) |
| 🏷️ By genre | [games/](games/) — separate file per genre |
| 📦 Raw data | [data/data_001.jsonl](data/data_001.jsonl) + [data/data_002.jsonl](data/data_002.jsonl) (sharded JSONL) |
| 📖 Index | [games/README.md](games/README.md) |
| 🛠️ About | <https://poli0981.github.io/free-steam-games-list/#/about> (in-app) |
| 📦 Raw data | [data/](data/) — JSONL shards of 800 games each (`data_001.jsonl` …), listed with a SHA-256 each in [`data/index.json`](data/index.json) |
| 🛠️ About | <https://free-steam-games.win/about> (in-app) |
| 🤖 Telegram bot | [`@my_skull_bot`](https://t.me/my_skull_bot) — Scraper Info Game bot, see [`CONTRIBUTING.md`](CONTRIBUTING.md) |
| ♿ Accessibility | [`ACCESSIBILITY.md`](ACCESSIBILITY.md) — what works with a keyboard, screen reader and zoom, what doesn't yet, how to report a barrier |
### What's new in v3.0.0
### What's in v4
<details>
<summary><b>Web app at <code>poli0981.github.io/free-steam-games-list/</code></b></summary>
<summary><b>Web app at <code>free-steam-games.win/</code></b></summary>
A React/Vite SPA hosted on GitHub Pages, fetching data live from `raw.githubusercontent.com`. Features:
A SvelteKit 3 / Svelte 5 app, prerendered and served by a Cloudflare Worker that also proxies the dataset (`/api/data/*`) and Steam artwork (`/img/*`; on the website the art comes from the site's own media host, `media.free-steam-games.win`), so your browser talks to this site only — apart from Cloudflare's analytics beacon and its Turnstile human check, both loaded only after you accept the terms. Features:
- **Charts** — 12 charts via Apache ECharts: KPI overview, top-online bar, genre treemap, platform donut, language heatmap, tag word cloud, anti-cheat stacked, release-year histogram, catalog-growth cumulative line, review histogram, online player tiers pie, DRM/DLC bars.
- **Edit / add / delete** (owner-only) — single edit drawer with form / JSON-editor toggle, bulk edit + delete in one signed commit, Steam-link queue (single + JSON bulk) into `scripts/temp_info.jsonl`, diff viewer, conflict-retry, optimistic local cache update so edits show up instantly without waiting for the Fastly CDN.
- **GPG signing** — paste your OpenPGP private key, unlock per-session, every edit commit gets a detached binary signature → GitHub verifies them as ✓. Multi-UID picker, idle auto-lock 5/15/30/60 min.
- **PWA** — installable, offline browse via a Workbox NetworkFirst service worker.
- **i18n** vi / en — Vietnamese + English UI, auto-detected from `navigator.language`, switchable in Settings.
- **Per-game permalinks**`/games/:appid` — share-friendly deep links into the detail drawer.
- **Activity feed** — recent commits with verified badges, filter Me / Bots / All.
- **Health page** — validation badges + workflow_dispatch buttons for the six maintenance pipelines.
- **Owner-gate** — non-owner visitors see read-only browse + charts, no edit affordances.
- **Browse** — virtualised table (TanStack Virtual), filters for genre, type, platform, status, anti-cheat and safety, Fuse.js fuzzy search, sortable columns, 50/100/200/500/all pages. Filters live in the URL, so a filtered view can be shared.
- **Charts** — Apache ECharts: dashboard KPIs, genres, platforms, languages, tags, anti-cheat (chart and a searchable index), reviews, player tiers, releaseyears and catalogue growth, DRM/DLC, delisted games, plus a stats page (Metacritic, retention, games that went quiet).
- **A page per game** — `/games/:appid` is prerendered for search engines and filled with live player counts and reviews in the browser.
- **Random games** — `/random` rolls one to five games when you cannot decide: online, offline or either, dead games only if you ask, never one marked unsafe. Roll again for a new set; opening a game and coming back keeps the picks.
- **Fresh data, verified** — `data/index.json` carries a SHA-256 per shard; the app only caches a generation it could verify, keeps the last good one offline, and re-checks when you come back to the tab.
- **Installable** — a web app you can install, with an offline mode and an update prompt.
- **i18n** vi / en — auto-detected, switchable from the welcome page or Settings.
- **⌘K command palette**, **first-run introduction**, and the legal documents rendered in the app.
Site is rebuilt and re-deployed automatically on every commit to `data/**` or `web/**`. See [`web/README.md`](web/README.md) for stack details and the per-phase changelog.
Cloudflare Workers Builds deploys from `main`; which commits trigger a build is in [`docs/DEPLOYMENT.md`](docs/DEPLOYMENT.md). Pipeline commits to `data/**` do not need a rebuild: the data is proxied, not bundled.
</details>
<details>
<summary><b>Desktop app (Tauri 2)</b></summary>
<summary><b>Desktop and Android apps (Tauri 2)</b></summary>
A native shell around the same web app, distributed via [GitHub Releases](https://github.com/poli0981/free-steam-games-list/releases):
- Windows `.msi`, macOS `.dmg` (universal Apple Silicon + Intel), Linux `.AppImage` and `.deb`.
- Fixed 1400 × 900 window, no maximise, no resize — keeps the layout consistent.
- Dark theme, stays in standalone mode.
- Same data path as the web app (reads `raw.githubusercontent.com` live), same offline cache.
- Windows `.msi` and `-setup.exe`, macOS `.dmg` (universal Apple Silicon + Intel), Linux `.AppImage`, `.deb` and `.rpm`, and an Android `.apk`.
- Resizable window; `steam://` links open the Steam client.
- The desktop app checks for a signed update on start and installs it when you say so, keeping your settings.
- Same data path as the web app (`/api/data/*` on free-steam-games.win), same offline cache.
Built by `.github/workflows/release-desktop.yml` (matrix Win/Mac/Linux via `tauri-apps/tauri-action`), triggered by pushing a `desktop-v*` tag or a manual workflow run. Each release auto-attaches its installers as draft assets.
Built by `.github/workflows/release-desktop.yml` (matrix Win/Mac/Linux via `tauri-apps/tauri-action`) and `release-android.yml`, triggered by a `desktop-v*` / `android-v*` tag or a manual run. Each release is created as a draft.
```bash
# from web/, locally:
@@ -79,16 +111,22 @@ npm run tauri:build # release binary into web/src-tauri/target/release/bundle
</details>
<details>
<summary><b>The admin at <code>/admin</code></b></summary>
`Discover New Games` sweeps the Steam store daily for free games in every language, not only the ones that support English, and proposes candidates into a Cloudflare D1 queue. The maintainer reviews them in a small Svelte app embedded in the Worker (never shipped to visitors): approving commits the store link to `scripts/temp_info.jsonl`, and the pipeline does the rest, checking every game again (free, a game, reachable) before it is published. Approval can also run on its own, in batches with a daily cap, once the maintainer turns it on. Decided and already-published rows are read-only. Corrections to published games are saved as override files that survive every pipeline run, and a removed game goes into `data/blocklist.jsonl`, which keeps it out of the catalogue until it is restored. An overview, the pipeline's runs and a data-quality report complete it. See [`docs/ADMIN.md`](docs/ADMIN.md).
</details>
<details>
<summary><b>v2.x foundations still here</b></summary>
The Python pipeline that powered v2 is untouched and runs daily as before:
- Schema v2.2 (23 + manual fields per record), MIT-licensed, sharded data in `data/data_*.jsonl` (cap 800 records/shard, current total ~1,230) plus a `data/index.json` manifest.
- Extension-compatible: the [Chrome extension](https://github.com/poli0981/free-steam-games-list-extension) pushes pre-fetched rich data straight into `scripts/temp_info.jsonl`; the ingest workflow merges and dedupes.
- HTML scraper for accurate language tables, DLC pricing, and user tags — single GET per game.
- Health-checked: dead-link sweep every 5 days, full purge every Monday.
- Reviews-only refresh every 2 days; full refresh daily.
- Schema v2.2 (23 + manual fields per record), CC BY 4.0 (see [LICENSE-DATA](LICENSE-DATA)), sharded data in `data/data_*.jsonl` (cap 800 records/shard) plus a `data/index.json` manifest with a SHA-256 per shard.
- HTML scraper for accurate language tables, DLC pricing, user tags and the developer's anti-cheat disclosure — single GET per game.
- Health-checked daily: Steam's store API screens every game, and a game is removed only when appdetails agrees.
- Reviews refreshed daily from Steam's own summaries; full refresh daily. Every data job queues for its turn and has a time budget, so a growing catalogue slows a refresh down instead of breaking it ([plan](docs/plan/18-pipeline-scale.md)).
</details>
@@ -98,14 +136,15 @@ The Python pipeline that powered v2 is untouched and runs daily as before:
| **Top Offline** | 1st + 15th of month 05:00 UTC | Bi-weekly leaderboard for single-player F2P concurrents |
| **Announce Discussion** | On release `published` | Auto-create a GitHub Discussion in `Announcements` per release |
| Top Offline | 1st + 15th of month 05:00 UTC | Leaderboard for single-player F2P concurrents |
| Update Reviews | Daily 06:00 UTC | Every game's review summary from Steam's store API |
| Refresh Store Data | Daily 16:00 UTC | Rotating re-fetch: tags, languages, DLC flag weekly; name, image, description, developer/publisher, release date, platforms, Metacritic, DRM monthly. Then every game's anti-cheat from Steam's disclosure (committed separately; manual run with `only: anticheat` does just that) |
| Refresh All-Time Peaks | Daily 19:30 UTC | `all_time_peak` from SteamCharts, every game once a month, plus our own samples; manual run with `backfill` asks about every game |
| Purge Unhealthy | Daily 07:00 UTC | Store API screen of every game; removal once appdetails agrees |
| Mark Dead Games | Mon + Thu 04:30 UTC | Online + >1y + 0 players ≥14d → `is_dead=true` + 💀 note |
| Daily Snapshot | Daily 23:00 UTC | Per-game players and reviews into `data/snapshots/` |
| Force Re-fetch | Manual only | Re-fetch games from scratch, one part (`1/8` … `8/8`) a run |
| Web CI / Python Tests | On `web/**`/`scripts/**` change | Type check, tests, build and output checks |
| Release Desktop / Android | On `desktop-v*`/ `android-v*` tag | Build the apps into a draft release |
| Announce Discussion | On release `published` | Auto-create a GitHub Discussion in `Announcements` |
Also in `.github/workflows/`:
- **CodeQL**, **SonarCloud** and **Qodana** (Python, JS/TS, Rust): code scanning on pushes and pull requests.
- **Check Overrides**: pull requests that touch the override or blocklist files.
- **Backfill Discovery**: temporary; a weekly re-sweep of older release windows into the same `/admin` queue.
- **Announce Release to Discord**: posts each published release.
- Three **Notify** workflows: CI failures, the Pages deploy, the release pipeline.
- **Deploy Web (GitHub Pages)**: it only serves a redirect to the new site now.
The site itself is deployed by Cloudflare Workers Builds, not by a workflow.
### Contribute
**The easy way — open an issue.** Pick the [Add games](.github/ISSUE_TEMPLATE/add_games.yml) template and paste up to 15 Steam links. Workflow auto-ingests, validates, health-checks, fetches metadata, and closes the issue with a status comment. The [Bug report](.github/ISSUE_TEMPLATE/bug_report.yml), [Feature request](.github/ISSUE_TEMPLATE/feature_request.yml), [Delete game](.github/ISSUE_TEMPLATE/delete_game.yml), and [Feedback](.github/ISSUE_TEMPLATE/feedback.yml) templates are also pre-filled.
The repository is in [maintenance mode](#project-status): contributions are
about the **data**.
**The web app way — sign in.** If you have repo write access, sign into the web app with a Classic GitHub PAT (scopes: `repo` + `workflow`) and use the Add or Edit drawers. Optionally unlock a GPG key in Settings to get **Verified ✓** commits.
New games arrive on their own: `Discover New Games` sweeps the Steam store
daily, in every language, into a review queue, and the maintainer approves them at `/admin` — by
hand, or with an auto-approve rule that has a daily cap and is off until turned
on. Discovery only proposes, and every approved game is checked again by the
pipeline (free, a game, reachable) before it is published.
**The Telegram bot way — `@my_skull_bot`.** No GitHub PAT needed. One-time: DM the maintainer privately with your Telegram `user_id` (NEVER post it in public Discord / Telegram groups / GitHub issues — see [`CONTRIBUTING.md`](CONTRIBUTING.md)) → maintainer adds you to the whitelist → chat with the bot when it's online (~2–5 hrs/day, runs in Docker locally) and follow its prompts. QR codes for the bot and DM live at [`assets/qr/`](assets/qr/).
**The extension way.** The companion Chrome extension detects F2P games on Steam store pages and pushes pre-fetched metadata to `scripts/temp_info.jsonl`.
**The manual way.** Fork, append to `scripts/temp_info.jsonl`, and push:
| You want to | Issue form | Or a pull request that |
| --- | --- | --- |
| **Add** a free game that is still missing a few days after it went free | [Add game](.github/ISSUE_TEMPLATE/add_game.yml) | appends its store link to `scripts/temp_info.jsonl` |
| **Correct** a published game (genre, type, anti-cheat, notes, safe) | [Edit game](.github/ISSUE_TEMPLATE/edit_game.yml) | adds an override with `python scripts/edit_game.py <appid> --set field=value --reason "…"` |
| **Remove** a game (paid now, not a game, malware, duplicate) | [Delete game](.github/ISSUE_TEMPLATE/delete_game.yml) | adds a blocklist line with `python scripts/delete_game.py <appid> --reason <code>` |
Accepts a full URL, short URL, or bare appid. Optional manual fields: `type_game`, `genre`, `anti_cheat`, `anti_cheat_note`, `is_kernel_ac`, `safe`, `notes`. The ingest pipeline preserves these on top of whatever it fetches from Steam.
A queued line accepts a full URL, short URL, or bare appid, and is a link and nothing else: any other key is ignored, and the game is fetched from Steam. Never edit `data/data_*.jsonl` or `data/index.json` by hand: the pipeline rewrites them, and an edit there is lost.
Two more forms stay open, for things that are broken rather than wished for:
[Bug report](.github/ISSUE_TEMPLATE/bug_report.yml) and
[Accessibility barrier](.github/ISSUE_TEMPLATE/accessibility.yml). All reviewed by hand.
The companion browser extension, [steam-f2p-extension](https://github.com/poli0981/steam-f2p-extension),
is archived and no longer a way in.
See [CONTRIBUTING.md](CONTRIBUTING.md) for the full flow.
@@ -206,7 +280,9 @@ Unemployed, introvert max level, dropped out uni year 3, mooching off family. Ne
- v1 was spaghetti.
- v2.0 was organised spaghetti.
- v2.1 was spaghetti with proper seasoning. It got a scraper.
- **v3.0 is spaghetti with a website on top, a desktop app, and bilingual menus.** Still spaghetti underneath. Still a hobby.
- v3.0 was spaghetti with a website on top, a desktop app, and bilingual menus.
- **v4.0 is the same spaghetti, rebuilt, with a review queue so it stops needing to be cooked by hand.** Still a hobby.
- v4.7 is where the cooking stops: the dish is served, and from here it is only kept warm.
> [!WARNING]
> **Disclaimer.** Quality / fun / safety: who knows. The maintainer only vouches for games personally played (`safe` column: `y` = yes, `?` = dunno, `n` = nope). Problems with a game are between you, Valve, and the developer of that game — not the maintainer. See [`docs/DISCLAIMER.md`](docs/DISCLAIMER.md) for the specific accuracy caveats.
@@ -214,22 +290,27 @@ Unemployed, introvert max level, dropped out uni year 3, mooching off family. Ne
- [Telegram bot](docs/telegram-bot.md) — pointer to the external bot user guide + how it integrates with this repo.
- [DISCLAIMER](docs/DISCLAIMER.md) — accuracy caveats, no-warranty, the broke-maintainer note.
- [Terms of Use](docs/ToS.md) — usage agreement, contributions, governing law, **rules for sharing your Telegram `user_id`**.
- [EULA](docs/EULA.md) — supplemental to the MIT licence.
- [Privacy Policy](docs/PRIVACY_POLICY.md) — zero personal data collected by the site; **Telegram-bot data flow** documented separately.
- [Terms of Use](docs/ToS.md) — usage agreement, contributions, governing law.
- [EULA](docs/EULA.md) — plain-language commentary on both licences.
- [Privacy Policy](docs/PRIVACY_POLICY.md) — no accounts, no tracking cookies, no profile; what Cloudflare logs as the host, the one cookieless page-view count, and where the site is not served.
- [Deployment](docs/DEPLOYMENT.md) — how a push becomes a deploy, and how to verify or roll one back.
- [Admin setup](docs/ADMIN.md) — Cloudflare Access and the GitHub App behind `/admin`.
- [Acknowledgements](docs/ACKNOWLEDGEMENTs.md) — credits, AI assistants, third-party libraries.
- [Third-party dev tooling](docs/THIRD_PARTY.md) — dead-code / lint / audit tools + the pre-publish check suite.
- [Contact](docs/Contact.md) — where to find the maintainer.
- [CODE OF CONDUCT](CODE_OF_CONDUCT.md) — be chill.
- [Security setup](docs/SECURITY_SETUP.md) — the operational side: headers, WAF, rate limits, Access, each with a check command.
- [ACCESSIBILITY](ACCESSIBILITY.md) — what works with a keyboard, screen reader and zoom, what doesn't yet, and how to report a barrier.
- [Android support](docs/android-support.md) ([VI](docs/i18n/vi/android-support.md)) — why Android 11+, and what the APK is tested on.
- [`web/README.md`](web/README.md) — web stack, data paths, CSP, PWA, i18n, build and checks.
Licensed under [MIT](LICENSE) — do whatever; keep the credit if you fork. Star if you find a hidden gem ✨
Code is [MIT](LICENSE); the dataset is [CC BY 4.0](LICENSE-DATA) with carve-outs for fields the project does not own (`description`, `header_image`). Keep the right licence with you if you fork. Star if you find a hidden gem ✨
Last auto-update: daily via GitHub Actions. Manual runs from the [Actions tab](../../actions) or the web app's Health page.
Last auto-update: daily via GitHub Actions. Manual runs from the [Actions tab](../../actions).
This repo is literally just a Markdown list of free-to-play Steam games + some JSON maybe later. No executable code, no dependencies, no backend, no user data. The biggest security risk is probably adding a game with toxic chat or aggressive microtransactions.
## What this project actually is
But hey, GitHub recommends it, and I'm paranoid enough after writing all those disclaimers.
The previous version of this file said the repository was "just a Markdown
list… no executable code, no dependencies, no backend, no user data." That was
wrong on every count, so here is the real picture:
### Reporting a Vulnerability
If you somehow find a "security issue" (like a broken link, a game that's actually paid now, or a listing that offends your soul):
- Open an Issue with the title starting with "[SECURITY]" or something.
- Describe it clearly: What game? What link? Why is it bad?
- I'll fix it when I wake up from my nap (or when Grok reminds me).
- a **Cloudflare Worker** serving the site. It holds a D1 binding, an R2
bucket for the game art (public at `media.free-steam-games.win`), a
15-minute cron (reconcile, auto-approve, and minting the art into that
bucket), and, for the admin path, a credential that can write to this
repository
- a **SvelteKit / Svelte 5 web app**, prerendered to static pages, with a few
dozen npm dependencies, plus the `/admin` app embedded in the Worker
- a **Tauri 2 desktop and Android app**, signed, with an auto-updater
- a **Python pipeline** run by GitHub Actions. The data jobs push to `main`
with the built-in `GITHUB_TOKEN`; the release jobs hold the app signing keys
**Do NOT** report fake/malware links here expecting me to click them – that's on you, bro. Steam's client is your friend.
Operational hardening (headers, HSTS, rate limiting, WAF) is documented in
[`docs/SECURITY_SETUP.md`](docs/SECURITY_SETUP.md), with a check command for
each item.
No bounties, no fame, no money – I'm broke. Just a "thanks" in the ACKNOWLEDGEMENTS if you're lucky.
There is genuinely something to attack here. Hence a real policy.
If it's actually serious (lmao unlikely), email... wait, I don't have one for this. Just open an issue.
## Reporting
Thanks for keeping the list safe-ish. Peace out.
**Use GitHub's private vulnerability reporting**, which is enabled on this
repository: *Security → Report a vulnerability*. It is private between you and
the maintainer.
If that does not work for you, email **security@poli0981.dev**. The same
address is published in [`AUTHORS.md`](AUTHORS.md),
[`docs/Contact.md`](docs/Contact.md), [`username.txt`](username.txt) and
# v3.0.0 – 2026-05-07 (The "It Has a Website Now" Edition)
[All versions](../../../CHANGELOG.md)
The repo is no longer just a list. It is a **list + a React/Vite web app + a Tauri desktop app**, all reading the same Python-pipeline-maintained data.
## 🌐 Web app — `web/` + GitHub Pages
Built across phases 1 → 7. Live at <https://poli0981.github.io/free-steam-games-list/>.
- **Phase 2** — PAT-based GitHub auth, single-record edit drawer for the 8 manual fields, diff viewer, single + bulk Steam-link queue into `scripts/temp_info.jsonl`, conflict-retry, sonner toasts.
- **Phase 3** — client-side OpenPGP signing via Git Data API: switched all writes from Contents API to `commitFile(getHead → createBlob → createTree → buildCommitContent → openpgp.sign → createCommit → updateRef)`. Settings panel with passphrase unlock + lock indicator. Earlier claim that PATs auto-sign was wrong — Contents API commits land Unverified.
- **Phase 4** — fixed GPG salt-notation incompatibility (`config.nonDeterministicSignaturesViaNotation: false`) so OpenPGP.js v6 signatures parse on GitHub. Bulk edit + bulk delete in one signed multi-shard commit. 8 remaining charts (tags wordcloud, AC stacked, languages heatmap, release-year histogram, catalog-growth cumulative line, reviews histogram, online player tiers pie, DRM/DLC bars). Health page with workflow_dispatch buttons. ⌘K command palette (cmdk).
- **Phase 4.1** — GPG signature payload fix: dropped trailing `\n` after the commit message so our signed bytes match `verification.payload` byte-for-byte. Verified via `gh api .../commits/{sha}.commit.verification.reason → valid`.
- **Phase 6** — curated enums (`ANTI_CHEAT_ENUM`, `GENRE_ENUM`) + dropdowns, JSON-editor toggle in the edit drawer (full-record replace), manual-field overrides on Add (single + bulk JSON mode propagates `genre/type_game/anti_cheat/notes/safe` straight into `temp_info.jsonl`), GamesTable pagination 50/100/200/500/all + hidden scrollbar + per-row validation badge, per-game permalinks `/games/:appid` with friendly 404 drawer, verify-after-commit polling (toast updates with `verification.reason` once GitHub confirms), CSV/JSON export of the filtered subset, About page (repo + dev info from `username.txt` + 3rd-party stack + issue templates), topbar GPG quick-unlock popover, owner-gate (`useIsOwner` + `OWNER_LOGIN`) hides edit/add/delete UI from non-owners.
- **Phase 6.1** — Edit Always Failing fix: Contents API caps `content` at 1 MB; `data/data_001.jsonl` is 1.49 MB so the read came back empty and every edit threw "Record not found". New `getRepoFileText()` helper falls back to the `/git/blobs/{sha}` endpoint for oversize files.
- **Phase 6.2** — stale-after-edit fix: bumped `data/index.json.last_updated` in every shard-modifying commit AND switched the SW cache to `NetworkFirst` (raw.github CDN is Fastly-cached for 5 min). Plus optimistic-update helpers (`optimisticEdit/Replace/BulkEdit/BulkDelete`) write straight to TanStack + IndexedDB so the editor sees their own change instantly without waiting for the CDN.
- **Phase 7** — date-column sort fix (`parseReleaseDate`), hamburger mobile nav (Sheet drawer, auto-close on route change), About expansion (Heads-up caveats + AI disclosure + legal links + per-third-party SPDX licence badges), legal docs rewritten (DISCLAIMER + EULA + ToS + PRIVACY) with the four caveats from `notes.txt` (genre best-effort, English-only, test-data leakage, unsigned-commit dev artefacts), refreshed `bug_report.yml`, workflow Node 20 → 24 + actions versions bumped.
- Auto-detect from `navigator.language` on first load; persistent override via Settings → Language.
- Sidebar nav, Topbar, Settings, Dashboard, Top Online, common buttons, common toast strings translated. Long-form legal copy stays English by design (legal review hard to mirror exactly across two languages).
- `CHANGELOG.md` — this entry consolidating phases 1 → 8.
- `docs/ACKNOWLEDGEMENTs.md` — refreshed with phase-by-phase AI assistance breakdown (Grok v1; Claude for v2 + the entire web/desktop layer + this changelog).
- `web/README.md` — phase 8 status appended.
## 🛠️ Pipelines unchanged
- All 9 v2.x Python pipeline workflows (update-json, generate-tables, top-online, update-reviews, dead-link-check, purge-unhealthy, ingest-new, ingest-from-issue, refetch-all) keep their schedules and behaviour. Two new workflows added: `deploy-pages.yml` (Phase 1) and `release-desktop.yml` (Phase 8).
# v3.0.1 – 2026-05-07 (The "Desktop Actually Ships This Time" Edition)
[All versions](../../../CHANGELOG.md)
Same-day post-v3.0.0 maintenance covering Phase 9 (auto-update foundations + CVE bumps + Device Flow scaffold), Phase 10 (Tauri build break + i18n full coverage + deps audit), and Phase 10.1 (minisign keypair rotation). The desktop release pipeline is now end-to-end green — `desktop-v1.0.0` finally produces signed `.msi` / `.exe` / `.dmg` / `.AppImage` / `.deb` / `.rpm` artefacts with a valid `latest.json` for auto-update.
## 🖥️ Phase 9 — auto-update foundations (#56)
- `tauri-plugin-updater` wired into `web/src-tauri/`. Endpoint pinned to the Releases page so installed clients fetch `latest.json` on launch.
- Updater pubkey embedded in `tauri.conf.json` (gated behind a no-op for mobile builds via `#[cfg(not(any(target_os="android", target_os="ios")))]`).
- GitHub Device Flow scaffold added to Settings: signed-in users no longer have to paste a long-lived PAT — they kick off `https://github.com/login/device`, type the user_code, and the app polls until token issuance. Falls back to PAT for the offline path.
- Dependency CVE bumps (vite 5 → 7, vite-plugin-pwa 0.20 → 1.x). Path-traversal fix in source-map handling. No source changes required for the bumps.
- More i18n: a chunk of edit-drawer / activity / dashboard chrome got proper translation keys.
- **Tauri lib-name regression fixed.** Phase 9's auto-updater work introduced a `f2p_tracker_lib::run()` call in `main.rs` without declaring `[lib]` in `Cargo.toml`. Cargo's implicit lib name is `f2p_tracker` (hyphens → underscores from the package name) so the call failed to resolve and `cargo build` blew up. Added the explicit Tauri-2-template-style block:
```toml
[lib]
name = "f2p_tracker_lib"
crate-type = ["staticlib", "cdylib", "rlib"]
```
The triple crate-type keeps the door open for future `tauri ios init` / `tauri android init` work that `lib.rs`'s `#[cfg_attr(mobile, tauri::mobile_entry_point)]` already implies.
- **i18n now reaches every chrome surface** (~150 new keys across new namespaces `charts`, `activity`, `add`, `system`, `cmdk`, `about`, `bulk`, `detail`, `diff`, `dialogs`, `health`). All 9 chart pages, Activity, Add, Health, Top Online, About headings, drawers (Edit / BulkEdit / Diff / GameDetail), `PwaIndicator`, `QueryState`, `GpgQuickUnlock`, `Topbar` tooltips/aria-labels, `Settings` rate-limit panel, `BulkActionBar` confirm dialog, `GamesTable` tooltips, and `CommandPalette` resolve through `useTranslation`. Long-form About prose stays English per the `settings.languageHint` policy. Enum values (anti-cheat / genre / type_game / safe) stay dataset-stable.
- **Third-party deps audit.** Walked `web/package.json` against `About → Stack & third-party` and `docs/ACKNOWLEDGEMENTs.md`. Added missing entries: `react-router-dom`, the i18next stack (`i18next` + `react-i18next` + `i18next-browser-languagedetector`), Tauri 2 + plugins (shell / updater / process), `echarts-for-react`, the styling utilities (`class-variance-authority` / `clsx` / `tailwind-merge` / `tailwindcss-animate`), and PostCSS + autoprefixer. Vite version corrected 5 → 7 (was already bumped by Phase 9; About just hadn't caught up).
- `ACKNOWLEDGEMENTs.md` restructured into grouped sections (runtime/build, styling, UI primitives, routing & i18n, data & state, charts, crypto & PWA, desktop) with deep links + SPDX licences.
- `web/src-tauri/Cargo.lock` now committed for reproducible desktop builds.
## 🔑 Phase 10.1 — minisign keypair rotation (#58)
- `desktop-v1.0.0` was failing at the final sign-updater-bundle step:
```
failed to decode secret key: incorrect updater private key password:
Missing comment in secret key
```
minisign formats the error so the inner "Missing comment" is the symptom of a wrong password — when the password is wrong, decryption returns garbage and the expected `untrusted comment: minisign encrypted secret key` header bytes don't appear. The original keypair's password was lost, so the GH secret could no longer decrypt the key.
- Re-keyed via `npx tauri signer generate --ci -p ""` with no password. Stored at `~/.tauri/f2p-tracker{,.pub}` on the maintainer's box; `web/src-tauri/.gitignore` extended (`*.key`, `f2p-tracker{,.pub}`) as a guardrail in case keys ever land in `src-tauri/` during dev.
- New pubkey baked into `tauri.conf.json``plugins.updater.pubkey`. GH secrets `TAURI_SIGNING_PRIVATE_KEY` and `TAURI_SIGNING_PRIVATE_KEY_PASSWORD` rotated via `gh secret set` (password = empty string).
- **Trade-off**: any user already on a build signed with the old key would have their auto-update break. Nobody hit that path because Phase 9 / Phase 10 release runs both failed before publishing artefacts. Phase 10.1's rebuild is the first actually-shipped `desktop-v1.0.0`.
## 🏷️ Tag handling
- `desktop-v1.0.0` was force-pushed twice in this cycle as the workflow input commit advanced (Phase 9 → Phase 10 → Phase 10.1). The triggering tag is GPG-signed each time. Once the auto-update story is real users-on-it, future fixes should bump `desktop-v1.0.x` instead of force-pushing.
## 📝 Docs (this release)
- `CHANGELOG.md` — this entry.
- `web/src-tauri/Cargo.toml` + `tauri.conf.json` + `.gitignore` — Phase 10 / 10.1 changes documented in their own commit messages and PR bodies (#57, #58).
# v3.1.0 – 2026-05-09 (The "Less CI Noise, Lighter Images, Dead-Game Detection" Edition)
[All versions](../../../CHANGELOG.md)
Four PRs landed in this release plus a refresh of the docs and the contributor surface around the new Telegram bot. Web app + desktop app bumped from `1.0.0` → `1.1.0`. Repo public-facing version `3.0.1` → `3.1.0`. Tag `v3.1.0` is GPG-signed; companion desktop tag is `desktop-v1.1.0`.
## 🛠️ CI hygiene — notify wrappers (#60)
- The 3 notify wrappers (`notify-ci-failure`, `notify-deploy`, `notify-release-pipeline`) used to trigger on `workflow_run: workflows: ["*"]` and were filtered out by their reusable callee's `if:` — 95–100 % of runs showed as "skipped". Replaced the catch-all with explicit lists of source workflow `name:` strings per wrapper, plus job-level `if:` to short-circuit non-matching conclusions. Drops skip rate to <10 %.
- Trade-off documented in each file: renaming a source workflow's `name:` field silently breaks notifications; comment warns about the coupling.
- `scripts/generate_tables.py:68` — markdown thumbnails now use `capsule_184x69.jpg` instead of `header.jpg` (~80 % bandwidth reduction at the same 120 px render width).
- Web app `GamesTable` + `CommandPalette` — capsule swap with explicit `width`/`height` to eliminate CLS, plus `onError` fallback to `header.jpg` for the ~5 % of games without a capsule variant.
- `GameDetailDrawer` — `<picture>` element with WebP source via `images.weserv.nl` proxy + JPEG fallback. Lazy-loaded, explicit dimensions.
- `vite.config.ts` — new `CacheFirst` runtime cache for `images.weserv.nl` (`statuses: [200]` only — opaque 0-status would cache proxy errors).
- New helper `web/src/lib/image.ts` — `headerToCapsule()` + `webpProxyUrl()`.
- New cron `Mon + Thu 04:30 UTC` flags **online games released >1 year ago** whose `current_players == 0` for **≥14 days** (configurable via `DEAD_GAME_DAYS` env or `--days` CLI). On trigger: `is_dead = true` + `"💀 Dead game"` appended to `notes` (idempotent).
- **State model**: ISO timestamp `zero_player_since` (robust against schedule drift), not a streak counter.
- **Mark mechanism**: additive `is_dead: bool` + note. `status` stays `"active"` so the existing enum / Top Online filter / chart groupings don't break. Web app gains a "Hide dead" filter toggle and a 💀 emoji prefix on dead rows.
- **Dry-run available**: `python scripts/mark_dead_games.py --dry-run --days 0` for auditing without writes.
- New helper `append_note_idempotent()` in `scripts/core/data_store.py`. Retrofitted onto `check_dead_links.py` to fix duplicate `"💀 Delisted"` accumulation on reruns.
- Schema migration via `_SKELETON_TEMPLATE` only (no one-shot script). Both the Python pipeline and the React app inherit defaults via existing `migrate_record()` / `migrateRecord()` loops.
## 🔄 Concurrency unification
All data-mutating workflows now share `concurrency: { group: data-write, cancel-in-progress: false }`:
Prevents races on `git push` to `data/` shards. Bot-ingest moved from its own `bot-ingest` group to the unified group.
## 📝 Docs + contributor surface (this PR)
- **`AUTHORS.md`** at repo root — handle map for the maintainer, AI-assistant disclosure, MIT licensing reminder.
- **`username.txt`** extended with `telegram bot`, `telegram user`, and `email` lines (canonical machine-readable handle map mirrored by `AUTHORS.md`).
- **`assets/qr/`** — QR-code PNGs for `@my_skull_bot` and `@SkullMute0011` (mirrored to `web/public/qr/` so the SPA can serve them). Generated via `python -m qrcode`.
- **`web/src/pages/About.tsx`** — Maintainer card now lists Telegram bot + Telegram DM (with QR thumbnails inline) + Email. New "Telegram QR codes" card with full-size scannable codes. Privacy note about Telegram `user_id` handling.
- **`CONTRIBUTING.md`** rewrite — adds the `@my_skull_bot` flow as a first-class contribution path (find `user_id` → DM maintainer privately → whitelist → run when bot's online → follow prompts). Loud privacy warning at the top.
- **`docs/PRIVACY_POLICY.md`** — new "Telegram bot" section covering the `user_id` data flow, where it's stored, retention/removal, and the maintainer's commitment.
- **`docs/ToS.md`** — new section 5.1 "Sharing personal information when contributing" with non-negotiable rules about private vs public channels.
- **`docs/Contact.md`** — Telegram bot + DM entries added at the top.
- **README** badges and feature list refreshed (version bumped, dead-game workflow listed, About-page QR card mentioned).
# v3.2.0 – 2026-05-11 (The "SEO + Donate + Auto-Discussion + Health Polish + Dev Docs" Edition)
[All versions](../../../CHANGELOG.md)
Single-PR bundle (#64) shipping eight features on top of v3.1.0. Web app + desktop bumped from `1.1.0` → `1.2.0`. Repo public-facing version `3.1.0` → `3.2.0`. Tag `v3.2.0` is GPG-signed; companion desktop tag is `desktop-v1.2.0`.
- New `web/public/robots.txt` (allow all + sitemap pointer) and `web/public/sitemap.xml` (5 entries: site root, GitHub repo, all-games / top-online / changelog markdown).
- New hook `web/src/hooks/useDocumentTitle.ts` — sets `document.title` to `<page> · Steam F2P Tracker` and re-runs on language change. Wired into all 18 routes (Dashboard / Games / TopOnline / Health / Activity / Add / About / Donate / Settings / 9 charts).
- VitePWA already emits `manifest.webmanifest` from `vite.config.ts`; no manual manifest needed.
## 💬 Auto-create GitHub Discussion on release
- New `.github/workflows/announce-release-discussion.yml` — fires on `release: published` (plus `workflow_dispatch` with a `tag` input for re-runs).
- Implemented via `actions/github-script@v8` + GraphQL `createDiscussion` (REST has no equivalent).
- Resolves the discussion category by slug — defaults to `Announcements`, falls back to `General` with a logged warning, then to the first available category.
- **Idempotent**: a GraphQL search runs first; if a discussion with the same title exists, the workflow skips with `core.notice()` and returns the existing URL via output. Re-running `workflow_dispatch` is therefore a no-op.
- Permissions: `contents: read`, `discussions: write` — both granted by `GITHUB_TOKEN` defaults once Discussions is enabled on the repo.
## 💖 Donate page
- New `web/src/pages/Donate.tsx` route at `/donate` — grid of 5 platform cards (GitHub Sponsors, Ko-fi, Buy Me a Coffee, Patreon, PayPal) sourced from `.github/FUNDING.yml`.
- Each card has a tinted icon ring, label, short description, and an "Open" button (`target="_blank" rel="noopener noreferrer"`).
- New nav item in `web/src/components/layout/Sidebar.tsx` SECONDARY group (between About and Settings); `Heart` icon from lucide.
- Full EN + VI i18n keys under `donate.*` (title / subtitle / cta / footnote + per-platform label & desc).
- New `web/src-tauri/TAURI.md` — desktop build prerequisites (incl. CI's exact `apt-get` line), local + production build commands, signing + auto-update notes, troubleshooting.
- `AUTHORS.md` — new "Dev info" table (GitHub handle, IDE channel, toolchain versions, link map to all the above).
- README "Docs" section — links the four new docs.
## 🤖 Telegram bot user-guide pointer
- New `docs/telegram-bot.md` — one-page pointer to the external [`telegram-scraper-bot/docs/USER_GUIDE.md`](https://github.com/poli0981/telegram-scraper-bot/blob/main/docs/USER_GUIDE.md), bot source repo, plus a paragraph each on what the bot does and the whitelist lifecycle.
- `CONTRIBUTING.md` — section 3 (`@my_skull_bot`) gets a 3-line callout with the user guide link, bot source URL, and the new in-repo summary doc.
- `web/src/pages/About.tsx` — Maintainer card's privacy note now includes a "Bot user guide & source" sub-card with the same three links.
## 🩺 Health bucket split
- `web/src/pages/Health.tsx` — `gatherIssues()` adds a fifth `IssueGroup`: `OnlineAcUnknown` for games with `type_game === "online"` and `anti_cheat ∈ {"", "-"}`. Previously these games were silently dropped from all categories; now they have a discoverable home.
- Edge-case fix: the existing "Kernel" filter compared `(r.anti_cheat ?? "-") !== "-"`, missing the empty-string case. Both filters now use a normalised `(r.anti_cheat ?? "").trim()`.
- `ShieldQuestion` icon (lucide). EN + VI i18n keys: `health.groupOnlineAcUnknown` + `…Desc`.
## 🎮 Steam Desktop direct link
- New helper `web/src/lib/steam-link.ts` — `steamProtocolUrl(appid)` returns `steam://store/<appid>`, `steamWebUrl(appid)` returns the regular HTTPS store URL.
- `web/src/components/games/GameDetailDrawer.tsx` — single store link replaced by two buttons rendered side-by-side: a primary "Steam Desktop" (`steam://`) and an outline "Web" (`https://`). Tooltip on the desktop button explains the fallback path.
- Works in both web build (browser shows protocol prompt if Steam is installed, silent fail otherwise — Web button is the safety net) and Tauri build (Tauri 2 allows `steam://` navigation by default; no allow-list change needed).
- EN + VI i18n: `detail.openOnSteamDesktop`, `detail.openOnSteamDesktopHint`, `detail.openOnSteamWeb`.
## 🛌 Bi-weekly offline-player leaderboard
- New `scripts/top_offline.py` — clones the `top_online.py` shape but filters `_is_offline(g)` (non-empty `type_game ≠ "online"`). Emits `games/top-offline.md` (top 100 single-player F2P concurrents, 10-column format identical to top-online).
- New `bash/offline.sh` matches the shape of `bash/online.sh` (pip install requests → run script → conditional commit).
- New `.github/workflows/top-offline.yml` — cron `0 5 1,15 * *` (1st + 15th of each month at 05:00 UTC) plus `workflow_dispatch`. Shares the unified `data-write` concurrency group.
- Health page (`web/src/pages/Health.tsx`) — new manual trigger button "Top offline" (next to the existing "Top online" trigger).
- **Bug fix during implementation**: `scripts/core/fetcher.py:update_players_only()` had a hardcoded `type_game == "online"` filter that would have made the offline workflow refresh zero rows. Extended with a `type_filter` kwarg (`"online"` default for backward compat, `"offline"`, or `"all"`); `top_offline.py` passes `type_filter="offline"` (excludes both online and empty/unclassified type).
# v3.2.1 – 2026-05-11 (The "Genre Cleanup" Edition)
[All versions](../../../CHANGELOG.md)
Patch release on top of v3.2.0. Normalizes inconsistent `genre` values across the dataset (31 records, 10 canonical mappings) and broadens the webapp's genre combobox with 14 additional suggestions. Web app + desktop bumped `1.2.0` → `1.2.1`. Repo public-facing version `3.2.0` → `3.2.1`. Tag `v3.2.1` is GPG-signed; companion desktop tag is `desktop-v1.2.1`.
## 🧹 Genre normalization script
- New `scripts/normalize_genres.py` — local one-shot tool with `--apply` flag (dry-run by default). Reuses `core.data_store.load_main` / `save_main` so writes are atomic + sharded.
- Idempotent — second run reports "data already canonical".
- Comma-separated values like `"Action RPG, Gacha"` (Wuthering Waves, Honkai Impact 3rd) are flagged in a "Manual review needed" section rather than auto-split, since the schema is single-genre.
- All `games/*.md` regenerated via `scripts/generate_tables.py`; affected genre files include the new sentence-case slugs (`turn-based-strategy.md`, `top-down-shooter.md`, `third-person-shooter.md`, `roguelite.md`, etc.).
- Sentence-case style matches the normalized data values.
- Dropdown filter on `web/src/pages/Games.tsx` is facet-driven (auto-updates from the records), so it now shows the deduplicated canonical names. The `EditGameDrawer` combobox suggests the 14 new entries while still accepting free-text input.
# v3.2.2 – 2026-05-11 (The "Bug Fix Quartet" Edition)
[All versions](../../../CHANGELOG.md)
Patch release on top of v3.2.1. Four user-reported bug fixes touching the Ctrl+K command palette on desktop, the Health → Games navigation flow, Tauri process-stacking on every launch, and the `type_game` scraper that was defaulting every new game to `"offline"`. Web app + desktop bumped `1.2.1` → `1.2.2`. Repo public-facing version `3.2.1` → `3.2.2`. Tag `v3.2.2` is GPG-signed; companion desktop tag is `desktop-v1.2.2`.
## 🔗 Desktop Ctrl+K external link
- New `web/src/lib/external-open.ts` — lazy-detects the Tauri runtime via `__TAURI_INTERNALS__`, opens external URLs through `@tauri-apps/plugin-shell` on desktop (capability `shell:allow-open` already granted in `web/src-tauri/capabilities/default.json`), falls back to `window.open(url, "_blank", "noopener,noreferrer")` on web/PWA. Plugin module is lazy-imported, so the web bundle never pays for the Tauri code path.
- `web/src/components/common/CommandPalette.tsx` — Ctrl+K game results now route through `openExternal()`. The Tauri webview was silently blocking the raw `window.open(r.link, "_blank")` for external HTTPS URLs, so clicking a search result on desktop did nothing.
- Six other `window.open(...)` call sites (Health workflow link, Add, BulkActionBar, BulkEditDrawer, EditGameDrawer, DeviceFlowPanel) are flagged for follow-up migration to `openExternal()` — same desktop silent-fail will hit them when triggered.
## 🩺 Health → Games filter restoration
- `web/src/pages/Games.tsx` — adds `useSearchParams` + a `useEffect` that mirrors the URL `?search=` parameter into `useFilters.search` on mount. The Health page already linked rows to `#/games?search=<name>`, but Games never read the param, so the table stayed unfiltered and the Topbar input stayed empty. The store binding to Topbar means visual feedback is automatic once the filter is set.
- Guard `if (term !== null)` (instead of `if (term)`) lets `?search=` explicitly clear the filter — useful for shareable "no filter" links.
## 🪟 Tauri single-instance enforcement
- `web/src-tauri/Cargo.toml` — adds `tauri-plugin-single-instance = "2"` under the existing desktop-only `cfg(not(any(target_os = "android", target_os = "ios")))` block, matching the updater plugin's gating pattern.
- `web/src-tauri/src/lib.rs` — registers single-instance as the **first** plugin so it short-circuits duplicate launches before any other state initialises. The dup-launch callback calls `unminimize()` + `show()` + `set_focus()` on the existing `main` window. Without this, every Start-menu / shortcut / file-association invocation spawned a fresh `f2p-tracker.exe` that lingered in Task Manager.
- No capability changes needed — plugin runs entirely Rust-side, no frontend command exposed.
## 🎮 `type_game` online inference
- `scripts/core/fetcher.py` — new `_infer_type_game(categories)` reads `data.get("categories", [])` and returns `"online"` when any description contains `online`, `mmo`, `massively multiplayer`, `cross-platform multiplayer`, or `multi-player`. Pure `shared/split screen` descriptions are treated as local-only and skipped unless paired with another online signal.
- Wired into `apply_details()` next to the existing anti-cheat category loop, guarded by `is_empty(game.get("type_game"))` so manual prefills in `temp_info.jsonl` remain authoritative — the `MANUAL_FIELDS` merge in `data_store.merge_extension_data()` and the override re-apply in `ingest_new.py` are unchanged.
- The legacy default-to-`"offline"` at the end of `fetch_full()` stays as the final safety net for games with no multiplayer signal in Steam categories. New ingests of online F2P games now classify correctly instead of all-offline.
# v3.2.3 – 2026-05-17 (The "View Commit Toast + Offline AC Lock" Edition)
[All versions](../../../CHANGELOG.md)
Patch release on top of v3.2.2. Three user-reported fixes: the "View commit" action button in success toasts (now reachable + cross-platform), an editor lock that prevents anti-cheat fields from being set on offline games, and a broken `Mark dead games` workflow setup-python step. Web app + desktop bumped `1.2.2` → `1.2.3`. Repo public-facing version `3.2.2` → `3.2.3`. Tag `v3.2.3` is GPG-signed; companion desktop tag is `desktop-v1.2.3`.
## 🍞 View commit toast — clickable + desktop-safe
- Migrated the eight `window.open(commit.htmlUrl, "_blank")` action handlers in `EditGameDrawer.tsx` (2), `Add.tsx` (2 inside `reportToast`), `BulkEditDrawer.tsx` (2), and `BulkActionBar.tsx` (2) to `openExternal()` from `web/src/lib/external-open.ts` — completes the follow-up migration flagged in v3.2.2's CHANGELOG. The Tauri webview was silently blocking the raw `window.open(...)` for external HTTPS URLs, so "View commit" did nothing on desktop.
- Each `toast.success(...)` with a "View commit" action now sets `duration: 15000` (was Sonner's 4 s default). On web the old toasts auto-dismissed before the user could read the description + click the action button.
- Handler now accepts the click event and calls `event.preventDefault()` so the toast stays visible after click (Sonner's default is to dismiss on action click — undesirable when the user wants to glance at the SHA after opening the commit).
- The fix applies to both the initial `toast.success` and the follow-up emit fired by `pollCommitVerification(...).then(...)` (same toast `id`, so `duration` must be set on the update too — otherwise the second emit rebounds to the 4 s default).
## 🔒 Anti-cheat fields lock on offline games
- `web/src/components/games/EditGameDrawer.tsx` — `FormFields` derives `lockAC = form.type_game === "offline"` and threads `disabled={lockAC}` to the AC `<select>`, the custom-AC `<Input>`, the three kernel `<Button>`s, and the AC note `<Textarea>`. A muted hint is rendered under the AC note when locked, explaining how to re-enable.
- `update()` setter now auto-resets `anti_cheat=""`, `anti_cheat_note=""`, `is_kernel_ac="unknown"` when `key === "type_game" && value === "offline"`. This keeps the `formToPatch()` diff honest — switching an online game with AC populated to offline now produces an explicit AC-clear in the commit instead of orphan anti-cheat data on an offline record.
- `web/src/pages/Add.tsx` — same pattern in `OverrideFields` + the `SingleAdd.setOv()` setter. `OverrideFields` combines the existing busy-state `disabled` prop with the new lock via `acDisabled = disabled || lockAC`, so the global "form is submitting" disable still wins. BulkAdd uses raw text / JSON input, so no UI lock needed there.
- `type_game === ""` (unknown) deliberately does **not** lock — only an explicit `"offline"` triggers the gate. The existing `validation.ts` "kernel?" badge rule for online + missing-kernel is untouched.
- New i18n key `edit.acLockedOffline` added to `web/src/i18n/locales/en.json` and `vi.json`, rendered as a `text-xs text-muted-foreground` hint under the AC note when `lockAC` is true.
## 🪦 `Mark dead games` workflow path fix
- `.github/workflows/mark-dead-games.yml` — `cache-dependency-path: scripts/requirements.txt` and the subsequent `pip install -r scripts/requirements.txt` both pointed at a path that doesn't exist. The file lives at the repo root (`requirements.txt`), consistent with the path `codeql.yml:25` already uses.
- Fix: both lines now reference `requirements.txt` at the root. The `setup-python` cache lookup no longer errors with `No file in /home/runner/work/free-steam-games-list/free-steam-games-list matched to [scripts/requirements.txt or **/pyproject.toml]`, and the install step actually finds the deps.
- Workflow is scheduled Mon + Thu 04:30 UTC; the next scheduled run will be the first end-to-end verification, but `workflow_dispatch` with `dry_run=true` is also available for ad-hoc validation.
Patch release on top of v3.2.3, landed as two PRs. **PR #74 (cleanup):** two dead scripts removed, `EditGameDrawer.tsx` (718 LOC) and `GamesTable.tsx` (568 LOC) split into focused sub-modules, two new charts (`TopOfflineBar`, `AddedPerMonthBar`) wired to a fresh `/top-offline` page and the existing `/charts/time` page. **PR #75 (features):** the `scripts/removed_games.jsonl` log now passes through a `dedup_removed()` filter on every write (a one-time migration trimmed 6 historical duplicates), Top Online leaderboard expanded `50 → 100` to match Top Offline, a generated `games/anti-cheat-list.md` plus a `/charts/anti-cheat/list` web page group active games by anti-cheat family, and a new `/charts/delisted` page renders a timeline + reason breakdown of every removed-from-catalogue title. Web app + desktop bumped `1.2.3` → `1.2.4`. Repo public-facing version `3.2.3` → `3.2.4`. Tag `v3.2.4` is GPG-signed; companion desktop tag is `desktop-v1.2.4`.
## 🧹 Dead-script removal
- `scripts/discord_notify.py` deleted — superseded by the `poli0981/.github` reusable workflow; no `.github/workflows/*.yml` or `bash/*.sh` referenced it.
- `scripts/migrate_to_shards.py` deleted — one-shot v2.2 migration tool, completed and unreferenced. The 10-script "unreferenced in workflows" audit confirmed the other eight (`check_dead_links`, `delete_game`, `normalize_genres`, `purge_unhealthy`, `top_offline`, `top_online`, `update_data`, `update_reviews`) all have live `bash/*.sh` wrappers and stay.
## 🪓 Component splits
- `web/src/components/games/EditGameDrawer.tsx` (718 LOC) → 7 focused files under `edit/`:
- `EditGameDrawer.tsx` keeps the save handler, dialog shell, view-toggle wiring.
- `EditFormFields.tsx`, `EditJsonView.tsx` (with `JsonDiff`), `EditChangePreview.tsx`, `ViewToggle.tsx` extract the four UI regions.
- `GamesTable.tsx` keeps the virtualizer (`useVirtualizer` ownership at container level so row-height stays single-source), filters, fuzzy search, sort, and paging.
- `TableHeader.tsx`, `TableRow.tsx` (memoised with `React.memo`), `TableToolbar.tsx`, `ExportMenu.tsx` extract the visual regions.
- No behaviour change — same virtual scrolling, same sort/filter wiring, same selection store.
## 📊 New charts
- `web/src/components/charts/TopOfflineBar.tsx` — mirror of `TopOnlineBar` but with offline-tier thresholds (20k/1.5k/300) calibrated to the `top_offline.py` scale instead of the online-only 100k/10k/1k palette. Filters `type_game !== "online" && status === "active"`, top 100 by `current_players`.
- `web/src/pages/TopOffline.tsx` — new page at `/top-offline`, layout mirror of `TopOnlinePage`, registered in `App.tsx` and `Sidebar.tsx` (Trophy icon).
- `web/src/components/charts/AddedPerMonthBar.tsx` — aggregates `records[*].added_at` into `YYYY-MM` buckets, renders an ECharts bar. Added as a third card to the existing `charts/Time.tsx` page alongside `ReleaseYearHistogram` + `AddedCumulativeLine`.
## 🗑️ Removed-games dedup
- `scripts/core/data_store.py` — new `dedup_removed(records)` keeps the latest entry per appid (compared by `removed_at` ISO timestamp, lexicographic order matches chronological for `YYYY-MM-DDTHH:MM:SSZ`). Records without a resolvable appid are dropped.
- `scripts/purge_unhealthy.py:41-43` and `scripts/ingest_new.py:106-108` — both call sites now write `dedup_removed(existing + log)` instead of `existing.extend(log)`. Same `save_jsonl` atomic-rename transaction, so partial writes can't leave duplicates.
- `scripts/dedup_removed_games.py` (new) — one-shot CLI that loads, dedups, and rewrites the file. Run once locally as part of this release; idempotent, safe to re-run.
- Result: existing log trimmed `43 → 37` records. Verified zero duplicate appids post-migration.
- `games/top-online.md` regenerated with 100 rows on next workflow tick; format unchanged (10-column table preserved).
- `web/src/pages/TopOnline.tsx` — `<TopOnlineBar limit={100} height={1800}>` to match the new row count.
- i18n strings `topOnline.{subtitle,cardTitle}` updated `Top 50 → Top 100` in both `en.json` and `vi.json`.
## 🛡️ Anti-cheat list
- `scripts/generate_anti_cheat_list.py` (new) — buckets active games by canonical AC name (`ANTI_CHEAT_PATTERNS` keys), with substring-match fallback for free-text values. Unrecognised values land in an `Other` bucket with a stderr warning. Output `games/anti-cheat-list.md`: H1 + TOC + per-family H2 sections, each a 6-column table sorted by `current_players` desc.
- `bash/anti_cheat.sh` + `.github/workflows/anti-cheat-list.yml` (new) — weekly Sunday 06:00 UTC cron + manual dispatch. Uses the same `data-write` concurrency group as the other table-generation workflows.
- `web/src/pages/AntiCheatList.tsx` (new) — `/charts/anti-cheat/list` page mirrors the MD: collapsible per-family sections + sticky AC-name sidebar nav. Uses existing `useGames` hook; canonicalises client-side via a TS port of the Python patterns table. i18n keys `antiCheatList.*` added to en + vi.
## 📉 Delisted charts
- `web/src/hooks/useRemovedGames.ts` (new) — fetches `scripts/removed_games.jsonl` from raw.githubusercontent.com, parses lines, deduplicates client-side (same logic as the Python dedup). TanStack Query with 5-minute staleTime.
- `web/src/components/charts/DelistedTimeline.tsx` (new) — ECharts stacked bar, x = `YYYY-MM` of `removed_at`, stacked by `status_code` (`not_free` / `unavailable` / fallback `other`).
- `web/src/components/charts/DelistedReasonBreakdown.tsx` (new) — ECharts donut by `status_code`.
- `web/src/pages/charts/Delisted.tsx` (new) — `/charts/delisted` page renders both charts. Sidebar nav link with `WifiOff` icon.
- `web/src/components/charts/KpiCards.tsx` — new optional `removedCount` prop; when set, renders a 7th "Removed (all-time)" KPI alongside the existing in-catalog "Delisted" badge. Wired from `Dashboard.tsx` via `useRemovedGames().data?.length`. Grid bumps from `xl:grid-cols-6` to `xl:grid-cols-7`.
## 📝 Docs
- README: removed the duplicate "Quick Links" section (the comprehensive 11-row "Quick links" table at the top covers everything the 4-row duplicate listed).
- README: added `🎯 Top offline (md)` row to the main Quick links table.
# v3.2.5 – 2026-05-20 (The "AC Nav + Mobile + Games Cleanup" Edition)
[All versions](../../../CHANGELOG.md)
Patch release on top of v3.2.4. One reported bug fix + three quality-of-life polish items. **Bug:** clicking any "Family" link in the Anti-Cheat Index sidebar redirected to the Dashboard instead of scrolling to the matching family table — `HashRouter` was treating the `<a href="#vac">` anchor as a route navigation. **Polish:** the `GamesTable` (1318 px wide) now degrades to a virtualised card list below the `md` breakpoint so mobile no longer needs horizontal scroll; the `AntiCheatList` sidebar drops to `md` instead of `lg` and exposes a horizontal chip nav on phones; `KpiCards` adds `md`/`lg` rungs to avoid uneven grid jumps. **Cleanup:** 93 per-genre markdown files in `games/` are removed (the web app's `/games?genre=X` filter has replaced them since v3.0); `generate_tables.py` now skips regeneration when game data hasn't actually changed via a `.gen-hash` checksum, cutting daily catalogue commits to roughly the days that move records. **New:** floating back-to-top button on the main scroll container, fades in past 400 px. Web app + desktop bumped `1.2.4` → `1.2.5`. Repo public-facing version `3.2.4` → `3.2.5`. Tag `v3.2.5` is GPG-signed; companion desktop tag is `desktop-v1.2.5`.
## 🔗 AC Index sidebar navigation fix
- [web/src/pages/AntiCheatList.tsx](../../../web/src/pages/AntiCheatList.tsx): swap `<a href="#anchor">` for `<button onClick>` that calls `document.getElementById(id).scrollIntoView({ behavior: "smooth", block: "start" })`. The `id={anchor}` attribute on each family `<Card>` stays the same — only the click target changes.
- Root cause: `main.tsx:24` uses `HashRouter`. Anchor links inside a hash-routed page produce URLs like `#/charts/anti-cheat/list#vac`. HashRouter parses the trailing `#vac` as a fresh route, the regex doesn't match, and the `<Route path="*" element={<Navigate to="/" replace />}>` fallback in `App.tsx` sends the user to the Dashboard.
- Same fix applied to the new mobile chip nav (below) so behaviour is uniform across viewports.
## 📱 Mobile responsive
- New `web/src/components/games/table/MobileGameCards.tsx` — virtualised card list rendering one card per game with thumb, name, genre/type/AC/status badges, review %, current players, and a Steam-link icon. Shares filter/sort/page state with the desktop table via the existing `useFilters` store.
- [`GamesTable.tsx`](../../../web/src/components/games/GamesTable.tsx) wraps the desktop scroll container in `hidden md:block` and renders `<MobileGameCards>` inside `md:hidden`. No new state, no behaviour drift between views.
- [`AntiCheatList.tsx`](../../../web/src/pages/AntiCheatList.tsx) sidebar changes from `hidden w-48 shrink-0 lg:block` to `hidden md:block md:w-40 lg:w-48` — visible on tablets too. Below `md`, a horizontal scrollable chip rail above the content provides the same family-jump nav.
- [`KpiCards.tsx`](../../../web/src/components/charts/KpiCards.tsx) grid `sm:grid-cols-2 lg:grid-cols-3 xl:grid-cols-7` → `sm:grid-cols-2 md:grid-cols-3 lg:grid-cols-4 xl:grid-cols-7`. Inserts `md` (tablet, 3 cols) and `lg` (small laptop, 4 cols) rungs so the 7 KPIs don't double-stack awkwardly.
## 🧹 `games/` cleanup + smart regen
- **Deleted 93 per-genre `<genre>.md` files** (`action.md`, `fps.md`, `visual-novel.md`, …). Web app `/games?genre=X` is the canonical genre filter since v3.0; no inbound link audit hit anything beyond `games/README.md` (regenerated) and the now-stale "By Genre" section in the index. Files kept: 11 ×`all-games_part*.md`, `top-online.md`, `top-offline.md`, `anti-cheat-list.md`, `README.md`.
- [`scripts/generate_tables.py`](../../../scripts/generate_tables.py) drops the genre loop entirely and rewrites the `games/README.md` template to point at part files + leaderboards + AC list, with a one-line note about the web-app genre filter.
- **Smart regen via `.gen-hash`** — script computes `sha256` of sorted `(link, name, genre, reviews, current_players, anti_cheat, is_kernel_ac, status)` tuples and writes the digest to `games/.gen-hash`. Subsequent runs short-circuit (`Skip: no semantic changes (hash=...)`) when the hash is unchanged. Order-invariant, ignores timestamps embedded in MD output, so daily workflow ticks only commit when game data actually moves.
## ⬆️ Back-to-top button
- New `web/src/components/common/BackToTop.tsx` — a fixed-position icon button bottom-right of the viewport. Listens for `scroll` events on the passed scroll container ref (passive listener), fades in (`opacity-100`) past 400 px, becomes pointer-events-none below to avoid blocking click-through.
- [`Layout.tsx`](../../../web/src/components/layout/Layout.tsx) creates a `useRef<HTMLElement>` on `<main>`, passes it as `scrollRef`. Single mount, no per-page wiring.
- i18n: `common.backToTop` added to `en.json` ("Back to top") and `vi.json` ("Lên đầu trang") for `aria-label` + `title`.
# v3.2.6 – 2026-05-20 (The "Mobile Hotfix" Edition)
[All versions](../../../CHANGELOG.md)
Hotfix on top of v3.2.5. Two mobile-viewport regressions introduced by the v3.2.5 responsive overhaul. Web app + desktop bumped `1.2.5` → `1.2.6`. Repo public-facing version `3.2.5` → `3.2.6`. Tag `v3.2.6` is GPG-signed; companion desktop tag is `desktop-v1.2.6`.
## 🐛 AC Index table — horizontal scroll on mobile
- `web/src/pages/AntiCheatList.tsx` — the per-family table wrapper was `<div className="overflow-hidden rounded-md border">`. On a 390 px viewport the 5-column table (`# / Game / Genre / Kernel / Players`) is wider than the card, and `overflow-hidden` clipped the right-hand columns with no way to scroll to them.
- Fix: `overflow-hidden` → `overflow-x-auto`. The table now scrolls horizontally when it exceeds the viewport, and the scrollbar stays hidden when it fits.
## 🖼️ Mobile game cards — thumbnail fallback
- `web/src/components/games/table/MobileGameCards.tsx` — the card `<img>` loads `headerToCapsule(g.header_image)` (the smaller `capsule_184x69.jpg` variant, ~10 KB vs ~50 KB). Steam's CDN doesn't host that variant for every game, so those cards rendered a blank thumbnail.
- The desktop table column (`table/columns.tsx`) already had an `onError` handler that falls back to the original `header.jpg`; the v3.2.5 mobile card component didn't port it. `GameDetailDrawer` uses `g.header_image` directly, which is why the image always appeared once a card was tapped.
- Fix: add the same `onError` fallback to the mobile card `<img>` — on a 404 it swaps `src` to `g.header_image`, with an `el.src !== g.header_image` guard against an infinite error loop.
Maintenance release on top of v3.2.6. A small, useful batch: the Python pipeline now rejects unreleased ("coming soon") games at ingest instead of listing titles nobody can play yet; a one-time dead-code sweep across the web app and the pipeline; and three dev-tooling additions (knip, vulture, pip-audit) so future releases can run the same checks. Web app + desktop bumped `1.2.6` → `1.2.7`. Repo public-facing version `3.2.6` → `3.2.7`. Tag `v3.2.7` is GPG-signed; companion desktop tag is `desktop-v1.2.7`.
## 🚧 Coming-soon games rejected at ingest
- `scripts/core/health_checker.py` — new `COMING_SOON` status, added to the `REMOVABLE` set. `check_game_health()` now reads the Steam `appdetails` flag `release_date.coming_soon` right after the API response resolves (before the `is_free` check) and returns `HealthResult(COMING_SOON, …)` for unreleased titles.
- Effect: `ingest_new.py` rejects coming-soon entries from the queue and logs them to `removed_games.jsonl` with reason "Not yet released (coming soon)" — the same path `NOT_FREE` already uses. `purge_unhealthy.py`'s weekly scan likewise evicts any coming-soon title already in the dataset.
- Rationale: an F2P *games* tracker should list playable titles. A coming-soon game has zero players, no reviews, and an unconfirmed price (it can launch paid). The API flag is used instead of scraping the `game_area_comingsoon` HTML block — it's already fetched during the health check and is authoritative. No schema change.
## 🧹 Web dead-code cleanup (knip)
- New `knip` sweep (config in `web/knip.json`). Removed two unused files: `src/components/common/UpdateChecker.tsx` — the Tauri auto-update component, never wired into `Layout.tsx` since Phase 9, so the frontend update check never actually ran — and `src/components/ui/switch.tsx`, an unused shadcn primitive.
- Removed 11 unused dependencies from `web/package.json`: 7 Radix primitives (`react-dropdown-menu`, `react-scroll-area`, `react-select`, `react-switch`, `react-tabs`, `react-toast`, `react-tooltip`), `@tanstack/react-table` (the virtualised table uses only `@tanstack/react-virtual`), and 3 Tauri packages (`@tauri-apps/api`, `@tauri-apps/plugin-process`, `@tauri-apps/plugin-updater` — the last two were referenced only by the removed `UpdateChecker`).
- `vite.config.ts` — dropped the now-stale `@tanstack/react-table` entry from the `manualChunks.table` group.
- knip's remaining "unused export" findings inside the `src/lib/*` port modules are intentional API surface; they're set to `warn` so `npm run knip` stays green.
## 🧹 Python dead-code cleanup (vulture)
- Deleted `scripts/dedup_removed_games.py` — the one-shot v3.2.4 migration, completed and now redundant (`dedup_removed()` runs inside the pipeline on every write). Same rationale as v3.2.4's removal of `migrate_to_shards.py`.
- `scripts/core/data_store.py` — dropped the unused `EXTENSION_FIELDS` import. The constant stays defined in `constants.py` as the documented MANUAL/ARRAY/EXTENSION field-class trio (mirrored in `web/src/lib/schema.ts`).
- **knip** — `web/package.json` devDependency + `npm run knip` script + `web/knip.json`. Finds unused files / exports / dependencies in the TypeScript SPA.
- **vulture** + **pip-audit** — new `requirements-dev.txt`; vulture config in a new root `pyproject.toml` (`[tool.vulture]`, `min_confidence = 80`). Python dead-code detection + dependency CVE audit.
- All three run at dev time only — nothing new ships in the pipeline, web bundle, or desktop app.
## 📄 Docs
- New `docs/THIRD_PARTY.md` — documents the dev tooling above (purpose, license, where declared) and the canonical pre-publish check suite. Linked from the README "Docs" section.
- Synced the third-party dependency lists to the removals above — `docs/ACKNOWLEDGEMENTs.md`, the in-app `/about` page (`web/src/pages/About.tsx`), and `web/README.md` no longer list the dropped Radix primitives, `@tanstack/react-table`, or `@tauri-apps/api`.
# v3.3.0 – 2026-06-12 (The "Lazy-Load + Error Pages" Edition)
[All versions](../../../CHANGELOG.md)
Feature release on top of v3.2.7, two themes: a web-app performance overhaul (route-level code splitting, lazy echarts/openpgp/locale chunks — first-load JS drops from ~574 KB to ~163 KB gzipped, −72%) and a proper error-page system (403/404/419/5xx/offline pages, React error boundaries, a real GitHub Pages `404.html`). Web app + desktop bumped `1.2.7` → `1.3.0`. Repo public-facing version `3.2.7` → `3.3.0`. Tag `v3.3.0` is GPG-signed; companion desktop tag is `desktop-v1.3.0`.
## ⚡ Lazy-loading overhaul
- **Route splitting** — [web/src/App.tsx](../../../web/src/App.tsx): every page except `Dashboard` (the landing route) is now `React.lazy` via a new `lazyWithRetry` helper ([web/src/lib/lazy.ts](../../../web/src/lib/lazy.ts)). The `<Suspense>` boundary sits inside [Layout.tsx](../../../web/src/components/layout/Layout.tsx) around `<Outlet/>`, so the sidebar/topbar stay mounted during navigation; fallback reuses the existing `LoadingState`.
- **echarts (~666 KB raw)** — new [LazyEChart.tsx](../../../web/src/components/charts/LazyEChart.tsx) wrapper is the single dynamic boundary for `EChart.tsx` (which keeps the `echarts.use([...])` registration). All 15 chart components swap one import line; a fixed-height `animate-pulse` skeleton prevents layout shift. echarts now downloads only when a chart mounts.
- **openpgp (~391 KB raw)** — [web/src/lib/gpg.ts](../../../web/src/lib/gpg.ts) switches to a type-only import + memoized `await import("openpgp")`. All exports were already async, so zero caller changes; visitors without a saved GPG key never download the crypto chunk at all.
- **Per-locale i18n** — [web/src/i18n/index.ts](../../../web/src/i18n/index.ts): `en.json` stays bundled (it's `fallbackLng` — a missing key can never render raw), `vi.json` becomes a dynamic import. `initI18n()` preloads the detected locale before `i18n.init`, and [main.tsx](../../../web/src/main.tsx) awaits it before first render — no flash of raw keys, verified with a hard reload under `f2p:lang=vi`. `setLanguage()` is now async and loads the bundle *before* switching. Also syncs `<html lang>` (was hardcoded `vi` for everyone).
- **manualChunks fix** — forcing `echarts`/`openpgp` into `manualChunks` made Rollup hoist shared helpers (tslib) *into* the echarts chunk, which the eager graph then statically imported — echarts was being modulepreloaded on first paint, nullifying the lazy boundary. Both entries are removed from [vite.config.ts](../../../web/vite.config.ts); the dynamic-import boundaries split them naturally. `dist/index.html` now modulepreloads only `react` + `query`.
- Net effect: eager JS `~1746 KB → ~494 KB` raw (`~574 → ~163 KB` gzip). The PWA still precaches everything in the background, but first paint no longer waits for charts + crypto.
- New [web/src/pages/errors/ErrorPage.tsx](../../../web/src/pages/errors/ErrorPage.tsx) — one config-driven component: per-code lucide icon + tone (neutral/warn/destructive, reusing the exact `ErrorState`/`PwaIndicator` palettes), mono `ERROR {{code}}` badge, i18n'd title/description, and three actions (Go home / Reload / Report issue → GitHub Issues). Full `errors.*` key blocks added to both [en.json](../../../web/src/i18n/locales/en.json) and [vi.json](../../../web/src/i18n/locales/vi.json). Kept in the eager bundle on purpose — error UI must not live in a lazy chunk.
- Routing — `#/error/:code` deep links via `ErrorCodeRoute` (unknown codes render 404 in place, no redirect), and the catch-all `<Route path="*">` now shows a real 404 page instead of silently redirecting to the Dashboard.
- **GitHub Pages `404.html`** — new [web/public/404.html](../../../web/public/404.html): standalone dark page (inline CSS, no JS deps), bilingual via a one-liner that respects the app's own `f2p:lang`, `noindex`, absolute link back to `/free-steam-games-list/#/`. Excluded from the SW precache via `globIgnores` in [vite.config.ts](../../../web/vite.config.ts) — SW-controlled clients get `navigateFallback` and never see it.
## 🛡️ Error boundaries + stale-deploy resilience
- New [ErrorBoundary.tsx](../../../web/src/components/common/ErrorBoundary.tsx) (own ~40-line class, no new dep) with a `resetKey` prop — navigating away clears a stuck error *without* remounting the page subtree on every navigation (which `key` would do, destroying table scroll/selection state).
- Two mounts: route-level inside `Layout` (chunk-load error → 503 page with "new version deployed, reload" copy; render crash → 500 page, error message shown in dev only), and a top-level [AppErrorBoundary](../../../web/src/components/common/AppErrorBoundary.tsx) outside the router with inline styles + hardcoded bilingual strings — immune to i18n/Tailwind/router failures.
- `lazyWithRetry` handles the deploy-mid-session case: a chunk 404 triggers ONE auto-reload per tab (`sessionStorage` flag, try/catch-guarded for lockdown webviews) which also picks up the waiting service worker; a second failure throws to the boundary.
## 🔌 Real error flows wired in
- [QueryState.tsx](../../../web/src/components/common/QueryState.tsx) `ErrorState` upgraded in place (contract preserved): offline detection swaps in the `errors.offline.*` copy + `WifiOff` icon, plus Retry / Report-issue action buttons. All 17 call sites now pass `onRetry={() => void q.refetch()}`.
- Expired/revoked token on session restore ([stores/auth.ts](../../../web/src/stores/auth.ts) `hydrate()` catch) now fires a Sonner toast with the shared `errors.419.*` copy and an "Open Settings" action (10 s duration — the 4 s default is too short for action toasts). Deliberately a toast, not a redirect: don't hijack whatever page the user opened. Auth gating on `/add` stays as-is.
## 🖼️ Images
- `decoding="async"` added to every `<img>` (10 sites: table thumbs, mobile cards, command palette, detail drawer, avatars, About QRs) — keeps image decode off the main thread during virtualised scrolling.
- Detail drawer header image now goes through a new `preferWebp()` ([web/src/lib/image.ts](../../../web/src/lib/image.ts)): weserv WebP transcode (~50 KB → ~20 KB) on web, **direct Steam URL on Tauri desktop** (no third-party calls from the bundled app), with an `onError` fallback to the original. Replaces the old `<picture><source>` markup, which only falls back on unsupported *type* — a weserv outage would have shown a broken image. Thumbnails intentionally stay on direct Steam capsules (~10 KB, SW-cached); `webpProxyUrl` is no longer exported.
## ⌨️ Search responsiveness
- [GamesTable.tsx](../../../web/src/components/games/GamesTable.tsx): the Fuse.js search input is wrapped in `useDeferredValue` — typing stays per-keystroke responsive while filtering ~1.2k records lags at React's low priority. No debounce timer (deferral only delays when the machine is actually busy). Same treatment + `useMemo` for the command palette's game scan.
# v3.4.0 – 2026-06-13 (The "Legal Consent Gate" Edition)
[All versions](../../../CHANGELOG.md)
Feature release on top of v3.3.0 adding an explicit, up-front acceptance of the project's legal documents on both surfaces: a first-run consent gate in the app (web + desktop) and a real license-agreement page in the Windows installer. No backend, no cookies — acceptance is a single `localStorage` flag, versioned so it can re-prompt when the terms change, and naturally fresh in incognito/private tabs. Web app + desktop bumped `1.3.0` → `1.4.0`. Repo public-facing version `3.3.0` → `3.4.0`. Tag `v3.4.0` is GPG-signed; companion desktop tag is `desktop-v1.4.0`.
## ⚖️ First-run consent gate (web + desktop)
- New [ConsentGate.tsx](../../../web/src/components/common/ConsentGate.tsx) — a full-screen card (styled like the error pages, eager bundle, no flash) that blocks the main UI until the user ticks a checkbox and clicks **Continue**. Mounted inside `AppErrorBoundary` + `HashRouter` in [main.tsx](../../../web/src/main.tsx), wrapping `<App/>` (the `<Toaster/>` stays a sibling). A gate crash is still caught by the top-level boundary.
- **Decline path** — explicit **Decline** button: on desktop (Tauri) it quits the app via `getCurrentWindow().close()`; on web it shows a blocking "you need to accept" notice with a way back to the gate.
- **Persistence** — new [stores/consent.ts](../../../web/src/stores/consent.ts) (Zustand, same pattern as `stores/gpg.ts`): `localStorage` key `f2p:legal_consent` holding `{ version, acceptedAt }`. A `TERMS_VERSION` constant gates validity — bump it when the legal docs change materially and everyone is re-prompted. Incognito tabs get a fresh storage partition, so the gate re-shows there with zero extra code. No cookie is used anywhere (there is no server to read one).
- **Error routes pass through** — the gate lets `#/error/*` render even before consent, so a mid-session chunk-load 503, the Pages `404.html` redirect, or an `#/error/:code` deep link still reaches the user instead of being swallowed.
- **Doc links** — the gate's five binding documents (MIT License, EULA, Privacy Policy, Disclaimer, Terms of Use) open through the existing [external-open.ts](../../../web/src/lib/external-open.ts) `openExternal()` helper, so they work inside the Tauri webview (which blocks `window.open` to external HTTPS) as well as on the web.
- **Shared legal list** — the `LEGAL_DOCS` array (label / path / hint) was lifted out of [About.tsx](../../../web/src/pages/About.tsx) into a reusable [lib/legal.ts](../../../web/src/lib/legal.ts) (`LEGAL_DOCS`, `CONSENT_DOCS`, `legalDocUrl()`); About now imports it instead of holding a private copy.
- New `consent.*` i18n keys added to both [en.json](../../../web/src/i18n/locales/en.json) and [vi.json](../../../web/src/i18n/locales/vi.json). Long-form legal copy stays English (the doc labels come from `LEGAL_DOCS`); only the gate chrome is bilingual.
## 🪟 Windows installer license page
- [tauri.conf.json](../../../web/src-tauri/tauri.conf.json) now sets `bundle.licenseFile` to a new [LICENSE_AGREEMENT.rtf](../../../web/src-tauri/LICENSE_AGREEMENT.rtf). Tauri v2 surfaces this as a mandatory "I Agree" license page in **both** Windows targets built by `targets: "all"` — the NSIS `-setup.exe` (MUI license page) and the WiX `.msi` (which requires RTF). The RTF is plain ASCII with no BOM to avoid the known NSIS license-encoding bug.
- The installer gate (install-time, desktop-only) and the in-app gate (first-run, web + desktop, re-promptable) are intentionally both kept: the auto-updater replaces the binary without re-running the installer, so the in-app `TERMS_VERSION` mechanism is the only way to re-prompt updated installs.
- Desktop window-close on decline needs the `core:window:allow-close` permission, now added to [capabilities/default.json](../../../web/src-tauri/capabilities/default.json). New dependency `@tauri-apps/api` (official, lazy-imported only on the desktop decline path — no web-bundle bloat).
## 🧰 Tooling & misc
- Version bumped across the three desktop files ([web/package.json](../../../web/package.json), [tauri.conf.json](../../../web/src-tauri/tauri.conf.json), [Cargo.toml](../../../web/src-tauri/Cargo.toml)) → `1.4.0`; the stale README version badge corrected `3.2.7` → `3.4.0`.
# v3.4.1 – 2026-06-14 (The "Chart Hotfix" Edition)
[All versions](../../../CHANGELOG.md)
Patch release fixing a production regression introduced by the Vite 8 / Rolldown deploy hotfix (#95): every chart tab threw a blank **React error #130** and failed to render. Web app + desktop bumped `1.4.0` → `1.4.1`; repo public-facing version `3.4.0` → `3.4.1`.
## 🐛 Charts render again (React #130)
- [EChart.tsx](../../../web/src/components/charts/EChart.tsx) imported the chart wrapper from `echarts-for-react/lib/core` — the **CommonJS** build. Under Vite 8's Rolldown bundler the CJS default-interop wraps `module.exports = class` into a namespace object, so `<ReactEChartsCore/>` received an object instead of a component → React error #130 on **every** chart page (all [pages/charts/*](../../../web/src/pages/charts) + the [Dashboard](../../../web/src/pages/Dashboard.tsx)). Switched the import to the **ESM** build `echarts-for-react/esm/core`, which has a clean `export default`. echarts core and echarts-wordcloud were already ESM, so this single import was the only offender.
- Verified at **runtime against the production (Rolldown) build** (the step skipped in #95): bar, pie/donut, line, treemap, heatmap and wordcloud charts all render with zero console errors. `echarts`/`openpgp` remain lazy async chunks (not eager-preloaded in `index.html`).
- The Dependabot alert for the `glib` crate ([GHSA-wrw7-89jp-8q8g](https://github.com/advisories/GHSA-wrw7-89jp-8q8g), medium, Linux-only) cannot be resolved within Tauri 2.x: the latest `webkit2gtk` crate (2.0.2) pins `glib ^0.18`, `tao`/`wry` pin `gtk ^0.18`, and Tauri 3 is not released. Only the Linux build links glib (Windows = WebView2, macOS = Cocoa) and the app does not call the affected API, so the alert is dismissed as tolerable risk. Will revisit when the upstream stack adopts gtk-rs 0.20. See [TAURI.md](../../../web/src-tauri/TAURI.md).
# v3.4.2 – 2026-06-15 (The "Android Floor" Edition)
[All versions](../../../CHANGELOG.md)
Android-focused release that raises the APK's minimum OS, hides a desktop-only
affordance on phones, and documents the support policy with sourced numbers. Web
app + desktop/Android bumped `1.4.3` → `1.4.4`; repo public-facing version
`3.4.1` → `3.4.2`. Tag `v3.4.2` is GPG-signed; the Android APK ships from
`android-v1.4.4`.
## 🤖 Minimum Android raised to 11 (API 30)
- [build.gradle.kts](../../../web/src-tauri/gen/android/app/build.gradle.kts) `minSdk``24` → `30`. Android's package installer refuses to install the APK below this (`INSTALL_FAILED_OLDER_SDK`), so the version floor doubles as the OS-level install gate — no in-app check, no bypass. Don't re-run `tauri android init` (it would reset it).
- **Why 11, not lower:** Android 7–10 are deeply end-of-life — Google ships OS security backports only for 14/15/16 as of mid-2026 — and tend to carry an outdated System WebView that breaks the modern ES2022 / React 19 output of the Vite 8 / Rolldown bundle. A `minSdk 30` floor still reaches ~87% of active Android devices (StatCounter, May 2026) while dropping only the dead tail. Android 11–13 install but no longer get Google OS patches — called out explicitly in the docs.
## 📱 "Steam Desktop" button hidden on mobile
- The `steam://` "Steam Desktop" button in [GameDetailDrawer.tsx](../../../web/src/components/games/GameDetailDrawer.tsx) can't reach a Steam client on a phone, so it's now hidden on the Android app **or** a sub-768px viewport; the "Web" button stays. Gated by a new reactive [useIsMobile.ts](../../../web/src/hooks/useIsMobile.ts) hook (`useSyncExternalStore` + `matchMedia("(max-width: 767px)")`, OR the existing `isAndroid()` from [external-open.ts](../../../web/src/lib/external-open.ts)) — re-renders on resize / rotation. No new i18n strings.
## 📚 Docs & transparency
- New [docs/android-support.md](../../../docs/android-support.md) (+ Vietnamese mirror [i18n/vi/android-support.md](../../../docs/i18n/vi/android-support.md)): minimum requirement, full rationale (security/EOL, WebView/React compatibility, edge-to-edge), tested-device matrix (emulator Android 11→16, real **vivo 1907** on Android 12), and a worldwide version-share + security-EOL table with **cited sources** ([apilevels.com](https://apilevels.com/), [StatCounter](https://gs.statcounter.com/android-version-market-share/mobile/worldwide/), [endoflife.date](https://endoflife.date/android), [Android Security Bulletins](https://source.android.com/docs/security/bulletin)). Reused as the GitHub Discussion announcement.
- Updated [TAURI.md](../../../web/src-tauri/TAURI.md), [pc_spec.md](../../../docs/pc_spec.md) (+ VN mirror) with the new Android test-device section, the [release-android.yml](../../../.github/workflows/release-android.yml) release-notes template, and the [README](../../../README.md) (version badge `3.4.1`→`3.4.2`, new Android 11+ badge + Quick-links row).
# v4.2.0 – 2026-10-03 (The "All-Time High" Edition)
[All versions](../../../CHANGELOG.md)
Every game now shows the most players it has ever had at once, the catalogue
the site and the apps keep for offline use is a fraction of its old size and
no longer readable as text, and every open dependency alert is closed. Web
app + desktop/Android bumped `2.1.1` → `2.2.0`; repo public-facing version
`4.1.1` → `4.2.0`.
On the website all of this is already live. The desktop app offers 2.2.0
through its updater once the release is published; on Android, install the
new APK over the old one. The apps also pick up the Disclaimer's new
paragraph on where player numbers come from, so they show the consent gate
once, with that paragraph; the website already did.
## ✨ Added
- **All-time peak players.** Every game shows the most players it has ever had
at once: "All-time peak" on its page, and a sortable column in the games
table and the CSV export. The number is the peak Steam Charts has recorded,
which for a game it tracks goes back to the launch, read about once a month
per game; for the many small games Steam Charts does not track, it is the
most this project's own samples have seen. It only ever goes up. The
"(peak N)" beside the player count is gone: it was the highest of our own
occasional samples since the last full re-fetch, not a daily or all-time
peak, and it read like one. The Disclaimer names the new source, so
returning visitors see the consent gate once, showing that paragraph.
## 🗜️ A smaller, opaque offline cache
- **The catalogue your browser or app keeps for offline use is now stored as
the packed shards it downloads**, not as thousands of readable records:
about 1.4 MB instead of roughly 9.5 MB, and opaque bytes in DevTools.
Like the packed downloads, this is compression and obfuscation, not
protection: the key is public, and the dataset stays readable in Git. The
copy an earlier version saved keeps working until the data next changes,
then it is replaced and deleted. Same storage keys, so the Privacy Policy
and the consent gate are unchanged.
- Opening the cached catalogue happens off the main thread now: on a
desktop the longest freeze while loading it fell from about 20 ms to 6 ms,
for about 45 ms more until the data is ready. The two cache keys are now
written in one transaction, so a failed write can no longer leave a new
index next to old data, and a cache that will not open is simply
downloaded again.
## 🧰 Pipeline
- `scripts/refresh_peaks.py` and the daily "Refresh All-Time Peaks" workflow
(19:30 UTC) ask Steam Charts about a thirtieth of the catalogue a day, a
page every two to three seconds, and stop for the day if it ever refuses;
every run also raises the field from the pipeline's own player counts. A
manual run with `backfill` ticked asks about every game at once, in about
four hours.
## 🔐 Security
- **Every open dependency alert is closed** (19 from Dependabot, plus the few
`npm audit` adds); `npm audit` reports none. Only two of the packages run in
production: `devalue`, whose parser is in the page and the apps (5.9.2 →
5.9.4), and `urllib3` in the data pipeline (2.7.0 → 2.8.0). The rest are
build and development tools: `undici` comes up to 7.29.1 with wrangler
4.147.0, and `brace-expansion`, `fast-uri` and `serialize-javascript` are
lockfile-only bumps. SvelteKit 2 still asks for `cookie` 0.6, whose fix is
only in SvelteKit 3, so an npm override gives it 0.7.2 (same API; with the
static adapter that code only runs while the site is built). The `sharp`
override is gone: wrangler's own pin now holds the patched version.
Loaded 100 of 852 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.