fix(website): remove game branding from public pages #193
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!193
Loading…
Reference in a new issue
No description provided.
Delete branch "bibiburl/Longshot:fix/website-game-branding"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The public website currently displays game titles, console branding and named characters/places. This emergency change replaces that wording with neutral descriptions while retaining technical product names and usable instructions.
What changed
website/src/lib/public-copy.ts: normalize imported settings descriptions and activity text before publishing HTML, search content andprogress-feed.json. Preserve source URLs, IDs, versions and original repository records.website/scripts/check-site.ts: reject listed game-brand terms in generated prose and public activity fields. New tests cover neutral wording, retained technical names and unmodified source records.Flags and settings
None. Published descriptions change; runtime settings, values and defaults do not.
Measurements
Baseline: main @
000f19fmain:
000f19f(2026-11-13)This PR: fix/website-game-branding @
d54ce8fEnvironment: local Linux, Node v22.23.4; deterministic source/output checks, no game run or performance measurement.
000f19fd54ce8fThe seven sources are
LongshotHero.astro,LongshotHome.astro,Footer.astro,about.mdx,requirements.mdx,docs/common-issues.mdandCONTRIBUTING.md. Count the named terms incheck-site.tscase-insensitively in each revision. This is a deterministic copy check, not an FPS comparison or a claim about trademark status.Build the website, then run
npm run checkto audit generated public prose and feed fields:Testing
Tested: Production website build; all seven website test files; generated page/feed branding guard; local links, assets, anchors and edit links; source comparison above;
git diff --check. Technical names and exact record IDs/URLs are covered by regression tests.Not tested: Full
python -I -B tests/run_all.pyruntime suite, game execution, visual browser inspection and screenshots. This is scoped to website copy/imports. Browser capture is unavailable in this session. No claim of visual or runtime verification is made.Needs other testers: None required before this emergency review under the user's explicit exception. A desktop/mobile visual follow-up should inspect the shortened headline and neutral settings labels for readability and unchanged navigation.
Screenshots
Unavailable: browser capture was not available. Generated HTML was inspected, but this does not replace visual review.
Risk and rollback
Neutral descriptions can be less specific than original report titles/menu labels; each source report remains linked. A newly introduced unrecognized term may require another mapping, and a listed unmapped term will fail the output check. Revert this commit to restore prior website wording. No game, launcher or download behavior changes.
Reviewer notes
This is a separate emergency branch from current main. The local install-download-version preview remains paused and is not included. Website deployment still requires maintainer review/merge. This PR does not remove names from runtime code, historical Git records, external destinations or technical paths required by users.
Emergency readiness exception: the requesting user explicitly approved “Mark ready for emergency review” using the completed website checks, without the full runtime test suite or screenshots. The incomplete checklist items below remain unticked to preserve an accurate validation record; runtime timing comparisons are inapplicable to this copy-only website change.
Issues
User-requested emergency website cleanup; no linked issue.
Checklist
For everyone
type(scope): description).main.python -I -B tests/run_all.pyrun and passing (any failure that also fails onmainis named above). Not run: website-only validation for this emergency change.third_party/untouched (a new folder with aPROVENANCE.mdinstead).If applicable
Assisted-by:/Co-Authored-By:trailers.mainand passing here. The generated-output guard rejects pre-change branding; the new normalization tests pass.