_verification/WORKLOG.md

Game archive verification worklog

Bucket: https://huggingface.co/buckets/smodusermc/offline-games

Scope

• Keep small scripts, manifests, logs, and verification evidence locally.
• Stage game assets only under /tmp/game-verify-stage; remove after each game.
• Credentials are supplied through the process environment, never project files.
• Geometry Dash is excluded.

Verification meanings

• Storage audit: bucket objects exist and their recorded sizes match. Not proof of completeness.
• SHA-256 checked: staged bytes match a recorded hash. A difference is recorded, not silently declared fixed.
• Menu/intro observed: visually reviewed browser evidence shows actual game output, not only an engine loader.
• Input smoke passed: a narrowly defined input assertion passed. This is not a complete playthrough.
• Inconclusive/resource limit: the 2 GiB test host could not safely finish. Not proof that a game is broken.

Browser tests use a local HTTP mirror with outside browser requests blocked. The repair phase can fetch missing resources server-side; the subsequent verification phase cannot. Routing absolute source URLs and supported runtime-library URLs to the local mirror happens in the HTTP response only. This is NOT a test of opening an unmodified HTML file from file://, nor a promise that the whole archive consists of self-contained HTML files.

Initial findings

• Old regex-crawler error lists contain many false positives from bundled code and internal module names.
• Several games already reach menus with their captured assets.
• Shared Flash runtime dependencies were missing from some per-game inventories and are being added from observed browser requests.
• Eleven entry-page sizes differ from their old snapshot metadata. These existing bucket edits are being preserved, not overwritten to match older files.
• A console-emulator startup stalled the host. Further tests are isolated with RSS and elapsed-time watchdogs.

Progress and individual outcomes are recorded in reports/verification-*.json; final human-reviewed classifications will be in reports/verification-summary.md.