Fight activity and optional browser returns are live

Fighter’s source-owned aggregate report now separates fight starts, terminal results and observed active gameplay from tab visits. A deliberate same-tab Quick Fight replay has its own definition. Settings offers returning-browser recognition as a separate choice, off by default; the reviewed release includes immediate revocation when persistent storage fails. Custom UTC windows and collection boundaries are visible in Woodhouse.

Fight activity and optional browser returns are live
Project
Fighter
Snapshot
Built to be used · 16 October 2026
Review date
2026-10-16

What this record says

Fighter’s source-owned aggregate report now separates fight starts, terminal results and observed active gameplay from tab visits. A deliberate same-tab Quick Fight replay has its own definition. Settings offers returning-browser recognition as a separate choice, off by default; the reviewed release includes immediate revocation when persistent storage fails. Custom UTC windows and collection boundaries are visible in Woodhouse.

The next useful proof

Use comparable post-collection history to see whether players finish fights and deliberately launch another. Keep improving whole-game presentation and observe physical phone play, audio balance and native sharing.

Where the proof stops

Exact production and scoped browser receipts were reviewed; Woodhouse did not repeat a game playthrough. Opted-in browsers are not people or cohort retention. Earlier unmarked QA history remains visible but is excluded from clean growth/record comparisons. Independently releasable game variants remain proposed.

Read the Fighter project dossier · Read the reviewed snapshot

Chronology

This status belongs to one reviewed snapshot. Later reviews should add a new status record and keep this one as history.