Add Hegemony unit corps release

[ael-dev3]

Summary

• Catalog the complete Hegemony infantry, ranged, and cavalry corps.
• Add privacy sanitization, provenance, licensing, checksums, and a four-image gallery.
• Declare three separately downloadable, verifier-compatible release attachments.
• Carry the controlling no-separate-open-license and trademark boundary inside every detached ZIP.

Asset scope

• 12 units across 3 corps
• 48 four-LOD runtime GLBs
• 15 editable Blender sources
• 39 PNGs
• 173/173 supplied runtime QA checks passed

Review repair

Independent review found that detached archives lost the repository-level license boundary and that the existing mutable release is anchored to the unsigned original PR commit.

Exact repair head: efc11024ad936ad9e93a3dd0a67baddbf49478f8.

• Each package now includes a root PACKAGE-NOTICE.md.
• All three nested checksum sidecars contain and verify the notice.
• Manifests, inventories, byte counts, compressed sizes, and outer SHA-256 sidecars are refreshed.
• The source manifest now matches the release manifest exactly while preserving the immutable source inventory.
• Every pre-existing payload remains byte-identical except the intended nested checksum sidecar.
• The package update is deterministic.

After the signed squash lands on main, release immutability will be enabled before the release is recreated on that exact signed commit. The existing published tag will not be moved while its mutable release is present.

Verification

• python3 scripts/verify_release.py --manifest releases/hegemony-unit-corps-2026-08-03/manifest.json --asset-dir <downloads>
• python3 -m unittest discover -s tests -q (35 tests)
• Source and release attachment metadata match exactly; source inventory is preserved.
• All 126 package checksum entries passed.
• Deterministic repeat update preserved all three attachment hashes.
• All runtime GLBs remain byte-identical to their validated sources.
• All public Blend files reopen in Blender 5.2 with matching path-insensitive semantic fingerprints.
• Fresh required CI is running for exact head efc11024ad936ad9e93a3dd0a67baddbf49478f8.

Large Blend/GLB masters remain outside normal Git history and are distributed through the tag-specific GitHub Release.