11 Commits
Author SHA1 Message Date
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 ee146dd023 docs: the TypeScript 7 / Node 26 / Python 3.15 move, and a runbook for 7.1
- 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>
2026-10-22 10:19:52 +07:00
poli0981andClaude Opus 5.5 e5365b3b6e feat(web): show the all-time peak; drop the misleading "(peak N)"
- 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>
2026-10-03 07:15:48 +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 7d0025112b docs: record the WAF rules as live, and replace the React-era dependency list
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>
2026-09-20 20:21:58 +07:00
poli0981andClaude Opus 5 5dfd9dd36e docs: analytics, the two WAF rules, and the claims they made false
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>
2026-09-20 20:01:28 +07:00
poli0981andClaude Opus 4.8 8bb3a5f042 docs(web): describe v3.4.1 build stack as Vite 8 + Rolldown (#99)
* 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>
2026-06-14 20:47:17 +07:00
poli0981 138e5186be v3.2.7: coming-soon guard, dead-code cleanup, dev tooling (#84)
Coming-soon games rejected at ingest (health_checker COMING_SOON status). Dead-code cleanup via knip + vulture: 2 unused web files, 11 npm deps, the one-shot dedup_removed_games.py. New knip/vulture/pip-audit dev tooling + docs/THIRD_PARTY.md. Bump 3.2.6 -> 3.2.7 (desktop 1.2.6 -> 1.2.7).
2026-05-22 23:17:10 +07:00
poli0981andClaude Opus 4.7 42d3f01763 Phase 10: Tauri lib-name fix + full i18n coverage + third-party deps audit (#57)
Fixes the desktop build break introduced after Phase 9 (`f2p_tracker_lib`
unresolved) and extends i18n to every user-facing surface that was still
hard-coded English.

src-tauri/Cargo.toml: declare `[lib]` with `name = "f2p_tracker_lib"` and
`crate-type = ["staticlib", "cdylib", "rlib"]`. Matches the Tauri 2
official template; main.rs / lib.rs untouched. Cross-platform mobile
crate-types kept for the future-proofing already implied by
`#[cfg_attr(mobile, tauri::mobile_entry_point)]` in lib.rs.

i18n: ~150 new keys across new namespaces (charts, activity, add,
system, cmdk, about, bulk, detail, diff, dialogs, health) plus
extensions to games/edit. All chart pages, Activity, Add, Health,
Top Online, About headings, all drawers (Edit/BulkEdit/Diff/GameDetail),
PwaIndicator, QueryState, GpgQuickUnlock, Topbar tooltips/aria-labels,
Settings rate-limit panel, BulkActionBar confirm dialog, GamesTable
tooltips, and CommandPalette now resolve through `useTranslation`.
Long-form About prose stays English per `settings.languageHint` policy.
Enum values (anti-cheat names, genre, type_game, safe) stay
dataset-stable.

About / ACKNOWLEDGEMENTs: audited `web/package.json` against the
in-app dep list and the credits doc; added 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. ACKNOWLEDGEMENTs.md restructured into grouped sections
(runtime/build, styling, UI primitives, routing & i18n, data & state,
charts, crypto & PWA, desktop) with deep links + SPDX licences.

src-tauri/Cargo.lock: now committed for reproducible desktop builds.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-07 18:59:11 +07:00
poli0981andClaude Opus 4.7 ee917b255a Phase 8: i18n vi/en + Tauri 2 desktop + release workflow + v3.0.0 docs refresh (#55)
i18n (vi / en)
  react-i18next + i18next-browser-languagedetector. Two resource bundles
  in web/src/i18n/locales/{en,vi}.json covering sidebar, topbar,
  dashboard, top-online, settings, common buttons (save / cancel / edit
  / delete / search / filter / clear), common toasts (saved / failed /
  verifying), the four PWA-related toasts, and the language picker
  itself. ~110 keys.

  Auto-detects from navigator.language on first load (English fallback);
  override persists in localStorage as `f2p:lang`. New Settings card with
  flag-emoji buttons.

  Long-form legal copy on /about and the static docs/* files intentionally
  stays English — translating legal wording across languages risks
  weakening the meaning, and the maintainer isn't in a position to have a
  bilingual lawyer review both bundles.

Tauri 2 desktop scaffold
  web/src-tauri/ with tauri.conf.json, Cargo.toml, build.rs, src/main.rs,
  src/lib.rs, capabilities/default.json, and PNG/ICO/ICNS icons generated
  from a Pillow-rendered source via `npx tauri icon`.

  Window: fixed 1400 × 900, resizable=false, maximizable=false,
  decorations=true, theme=Dark, centred, single instance ("main").
  Bundles `tauri-plugin-shell` so the embedded SPA can shell-open Steam
  links + GitHub URLs without granting broader native capability.

  package.json gets new scripts:
    tauri        — pass-through CLI
    tauri:dev    — dev build with hot reload from vite
    tauri:build  — release binary into src-tauri/target/release/bundle
  Plus a `build:desktop` that builds the SPA with base="/" instead of
  the GitHub Pages base.

Release workflow (.github/workflows/release-desktop.yml)
  Matrix `ubuntu-latest` / `windows-latest` / `macos-latest`. Triggers
  on push of a `desktop-v*` tag or a manual workflow_dispatch (with a
  configurable tag input).

  Steps: checkout v5 → install Linux build deps when relevant → setup
  Node 24 + npm cache → install Rust stable (with universal targets on
  macOS) → Swatinem/rust-cache → npm ci → tauri-apps/tauri-action@v0
  with releaseDraft=true so the maintainer reviews + publishes after
  smoke-testing.

  Outputs per platform:
    Windows  → .msi
    macOS    → .dmg (universal: aarch64 + x86_64)
    Linux    → .AppImage + .deb

Versioning
  Repo version badge bumped 2.1.0 → 3.0.0.
  web/package.json 0.1.0 → 1.0.0.
  src-tauri/Cargo.toml + tauri.conf.json ship at 1.0.0.
  Sidebar version label "Steam · v0.1" → "Steam · v1.0".

Docs refresh
  README.md — full rewrite of the top section: v3.0 framing (list +
  web app + desktop), refreshed quick-links table, three What's-new
  sections (web app phase summary, desktop, v2.x foundations), updated
  architecture diagram including web/ + src-tauri/, refreshed
  workflows table, refreshed contribute paths, refreshed docs index.
  CHANGELOG.md — new v3.0.0 entry consolidating phases 1 → 8 with
  per-phase one-liner summaries (including the four bug-fix points
  6.1 / 6.2 / 4.1 / 7's date-sort).
  docs/ACKNOWLEDGEMENTs.md — phase-by-phase AI-assistance table
  (Grok v1, Claude v2 + the entire v3 stack), explicit third-party
  list (Python deps + headline web/desktop deps), trademark note for
  Steam / GitHub.
  web/README.md — phases 6.1, 6.2, 7, 8 added; new Desktop builds and
  i18n sections; PWA strategy note updated to NetworkFirst.

Build 3.84 s; index chunk 113 → 136 KB gz (+22 KB for i18n + Tauri
shell wrapper). PWA precache 1.66 MiB.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-07 11:32:27 +07:00
poli0981 6dc9f75945 add initial documentation files including acknowledgements, code of conduct, and policies 2025-12-19 21:23:30 +07:00