# Original installation storage cleanup

Date: 2026-10-11. Repository: `nmarshall/urt-rs` (model repository, Git/Xet storage).

## Verified local preparation

- All 39 `.cache/UrbanTerror43/` files match their original sizes and SHA-256 values in `docs/inventory/snapshot.json`.
- All 39 copied files are removed from `assets/original/`; that directory is ignored and forbidden by the staged-content guard.
- The same guard rejects original installation-file SHA-256 pointers under other asset paths.
- All 23 PK3s are unpacked and independently verified: 9,835 file occurrences, 743 directory metadata records and 3,125,455,778 uncompressed bytes.
- The set of extracted payload hashes has **no intersection** with the 39 installation-file hashes. Deleting those remote objects cannot delete one of the new extracted objects by shared identity.
- Before cleanup, the remote main was `6a7403c116fcab4f91be34b532f65cf7d3e6770c`. The Hub listed 40 stored objects: 39 originals plus the asset README. The README object is excluded from deletion.

## Remote execution status

The user approved permanent deletion of exactly 39 original objects and their historical references. The signed-in Hub operation completed with history rewriting enabled. Immediately afterward, its large-file inventory contained only the excluded 544-byte README object (`2f2d302ee6bed775d99b82459dbe4e9558c6d86621f1031ce4d8f901fcc2f460`).

Fetching the rewritten remote changed `main` to `5ed96bc1fbfa36bb1969988df718ad53e3650e26`. All reachable asset blobs were checked: no `assets/original/` path or original installation-file payload pointer remained. The extraction commit is based on that cleaned parent; its identity is available in Git history. A cache-only Git bundle preserves the former local metadata without publishing those references.

Deletion is scoped to this repository. Shared provider-level physical chunks and delayed quota accounting are not asserted to have been erased. The original installation remains verified in `.cache/UrbanTerror43/`; extracted files are new, distinct payload objects uploaded through Xet.