main
14
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
14d052a943 |
docs(privacy): artwork also loads from the site's own image host
"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> |
||
|
|
659df7c169 |
feat(web): themed scrollbars, and a setting to hide them
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> |
||
|
|
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>
|
||
|
|
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> |
||
|
|
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> |
||
|
|
1b6ad7be47 |
feat(admin): read-only decided and published rows, reopen, reconcile sweep, retention
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> |
||
|
|
75c5fcb8ab |
feat(desktop): a working auto-updater, and updates that no longer reset the app
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> |
||
|
|
c8f17d8efa |
feat(web): verified shard generations, offline fallback, and revalidation
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> |
||
|
|
3525554eb6 |
feat(worker): proxy GitHub avatars and the commit feed, add security.txt
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> |
||
|
|
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> |
||
|
|
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> |
||
|
|
16eabcbbf5 |
docs(v3.1.0): Telegram bot flow, AUTHORS at root, version bumps (#63)
- AUTHORS.md (new) at repo root — maintainer + canonical handle map
+ AI disclosure. Mirror of `username.txt` (now includes telegram bot,
telegram user, email).
- assets/qr/ (new) — QR PNGs for `@my_skull_bot` and `@SkullMute0011`,
mirrored to web/public/qr/ so the SPA serves them.
- About page (web): new Maintainer entries (Telegram bot + DM with
inline QR thumbnails + Email) and a dedicated "Telegram QR codes"
card with full-size scannable codes. Privacy note added.
- CONTRIBUTING.md rewrite: explicit `@my_skull_bot` flow as a
first-class path (find user_id → DM maintainer privately → whitelist
→ run when bot's online → follow prompts). Loud warning about
NEVER posting Telegram user_id in public channels.
- docs/PRIVACY_POLICY.md: new "Telegram bot" section covering data
flow, storage, retention, and the maintainer's commitment.
- docs/ToS.md: new section 5.1 with non-negotiable rules about private
vs public channels for personal info.
- docs/Contact.md: Telegram bot + DM entries at the top.
- README: version badge 3.0.0 → 3.1.0; quick links + workflow table
+ contributor section + docs index updated; Mark Dead Games and
Bot Ingest workflows listed.
- CHANGELOG: v3.1.0 entry covering PRs #60-#62 + this docs PR.
- Versions bumped:
web/package.json 1.0.0 → 1.1.0
web/src-tauri/Cargo.toml 1.0.0 → 1.1.0
web/src-tauri/Cargo.lock 1.0.0 → 1.1.0
web/src-tauri/tauri.conf.json 1.0.0 → 1.1.0
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|
|
00d9dc0fb5 |
Phase 7: date-sort fix + hamburger nav + About expansion + legal rewrite + Node 24 (#54)
date-sort fix
Steam release_date strings ("22 Aug, 2012", "Dec 19, 2025", "Coming
Soon", "TBA", year-only "2025"…) were sorted as strings, which mixes
alphabet-first chars ahead of numeric prefixes and scrambles years.
New parseReleaseDate() in lib/utils.ts hands back a comparable
timestamp via Date.parse with a 4-digit-year fallback. Unparseable /
TBA values get -Infinity so they cluster out of the way regardless of
sort direction. GamesTable's released column now uses it.
hamburger mobile nav
Sidebar was hidden below the lg breakpoint with no way back. New
ui/sheet.tsx Radix-Dialog-based drawer that slides in from the left,
Sidebar refactored into shared SidebarBody + desktop / mobile wrappers,
Topbar gets a Menu button (mobile-only). Drawer auto-closes on route
change so tapping a nav entry doesn't require an extra X click.
About page expansion
• New "Heads-up before you trust this" card with the four accuracy
caveats from the maintainer's notes:
- genre is best-effort (tags+description heuristic)
- English-only assumption (regional storefronts can break parsing)
- test data may have leaked in during development
- "unsigned" Activity entries are dev artefacts, not malicious
• New "AI disclosure" card naming Grok (v1) + Claude (v2+) and noting
that LLM calls only happen on the maintainer's dev machine, never
from the visitor's browser at runtime.
• New "Legal & license" card linking MIT + DISCLAIMER + ToS + EULA +
PRIVACY + ACKNOWLEDGEMENTs + Contact, all opening on GitHub.
• Per-third-party SPDX licence badges in the stack list, each linking
to the dep's actual LICENSE file.
• Added echarts-wordcloud + idb-keyval to the deps roster.
Legal docs rewrite (DISCLAIMER, EULA, ToS, PRIVACY)
Tightened wording while keeping the casual voice. Each doc now
explicitly references the four accuracy caveats, the third-party
trademark situation (Steam, Akamai, GitHub), and the AI-assistance
status. PRIVACY_POLICY enumerates exactly what the static site does
and does not do (no analytics, no fingerprinting, lists the four
third-party endpoints touched at runtime + their privacy links).
EULA + ToS now name-check Steam Subscriber Agreement / Akamai
appropriately rather than just shrugging.
Node 24 / refreshed actions
Phase 5+ deploy-pages was running on Node 20 (which deprecates June
2026). Bumped:
actions/checkout v4 → v5
actions/setup-node v4 → v5 (node-version 20 → 24)
actions/upload-pages-artifact v3 → v4
actions/deploy-pages v4 → v5
notes.txt
The maintainer's local working notes that they explicitly didn't want
pushed. Added [Nn]otes.txt / [Nn]otes.md to .gitignore (the existing
rule only matched the singular [Nn]ote.txt).
Build 4.87 s; bundle index 113 KB gz (+4 KB for Sheet primitive +
About expansions). All other chunks unchanged.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|
|
6dc9f75945 | add initial documentation files including acknowledgements, code of conduct, and policies |