9 Commits
Author SHA1 Message Date
poli0981andClaude Fable 5.2 fa8dbaf92b docs: put the project in maintenance mode
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>
2026-11-11 20:49:27 +07:00
poli0981andClaude Opus 5.5 2b4b988cc7 docs: sync the community docs with the repository
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>
2026-11-09 08:43:39 +07:00
poli0981andClaude Opus 5.5 a74a004e19 docs: publish role contact addresses and the maintainer's website
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>
2026-09-29 23:31:09 +07:00
poli0981andClaude Opus 5.5 fa8b81fd9b docs: the Turnstile check and the Referer fix, and what they made untrue
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>
2026-09-23 21:47:01 +07:00
poli0981andClaude Opus 5 56559a13f6 docs(contact): move to contact@poli0981.dev and one links page
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>
2026-09-12 11:53:40 +07:00
poli0981andClaude Opus 5 3b4ece183c feat(security): CSP and hardening headers, plus a verifiable setup guide
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>
2026-09-11 00:41:20 +07:00
poli0981andClaude Opus 5 122075c9bf feat(admin): genre dropdown, bulk retag; ingest reduced to the extension
## /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>
2026-09-11 00:31:27 +07:00
poli0981andClaude Opus 5 5ab4f27347 docs: split the licence, correct the legal docs, add deployment and admin guides
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>
2026-09-10 16:09:04 +07:00
poli0981 6dc9f75945 add initial documentation files including acknowledgements, code of conduct, and policies 2025-12-19 21:23:30 +07:00