Preservation and later cleanup

This handoff is a curated, reproducible team delivery. It does not claim to be a disk image or a complete copy of every raw diagnostic artifact. No original files are deleted by its build scripts.

Included

• The final Windows runtime wrapper, exact sealed dev58 input, team1 historical fallback and dev57 percentage-attendance fallback.
• Current non-arena first-party source, schemas, SDKs, tests, tools and framework documentation.
• Exact accepted crowd native/API checkpoints, exact Roster Studio deployed-source checkpoint and a member-hash-verifiable RG presentation checkpoint.
• Primary non-arena knowledge-base guides, research/source inventories, dated checks and immediate milestone evidence. Large run dumps and repeated staged build trees are represented by their original manifests/receipts rather than copied wholesale.
• Third-party dependency notices that accompany retained first-party tools, source attribution and exact upstream package/lockfile identities.

Outside the public archive

Arenas, venue projects/kits, Blender arena tooling, court artwork/templates, original EXE/IFF/ISO/crack packages, standalone third-party installers/help packages, personal saves/rosters, credentials, browser-service accounts/workspaces and bulk raw process captures remain outside the hosted handoff. The developer source retains the attributed field-reference text actually imported by the roster editor and the exact original-instruction fixtures used by RG. It also contains generic asset-overlay and IFF-codec code because those are part of the extension platform.

SOURCE-MANIFEST.json and EVIDENCE-MANIFEST.json identify retained members. CHECKPOINTS.json records exact source archive identities and original-fixture omissions. The reports/ directory in the local handoff root records selection policy and exclusions. The original workspace, its external support storage and existing service remain intact.

Arena preservation is a dependency boundary

Before any later deletion, trace arena imports and build commands into tools, native/iff, assets, original donor files, shared fixtures, add-ons, support toolchains, Python environments and external-storage routing. A path outside arena-projects can still be required by an arena. Preserve every arena's source, packed scenes, editable art, releases, donors, exact-pair receipts and restore guides, plus the dependencies they actually use.

Do not remove shared private Cloudflare/R2 data, workspace compatibility links or running app logs under an assumption that they are disposable 2K14 files. Public R2 downloads are independent of the local workspace; the live roster service has its own durable private state and is not automatically retired by this handoff.

Keep at least one independently downloaded and fully hashed copy of all final ZIPs outside any later deletion set. A working external-drive relocation is not an independent backup. The exact RG instruction fixtures are included for reproduction; the supported game and its system/runtime dependencies remain separately supplied inputs.

Continuation priorities

1. Integrate an independent consumer using the bundled real HTTP scenarios and durable result/ACK flow.
2. Run a fresh installed-final-ZIP acceptance campaign on the team's own supported Windows game.
3. Close presentation resource/context/callback semantics and lifecycle before claiming complete framework acceptance.
4. Revalidate changed FT awards, physical controllers, fullscreen/device reset and broad mod combinations only as explicitly scoped work.
5. Back up and verify private Roster Studio data before any service retirement.

This handoff does not approve deletion. The later cleanup should produce a concrete retained/deleted manifest and prove the arena dependency closure first.