Managed Expectations (Day 12, metadata-forensics)
Question: Determine dotnet.mvid_guid for managed-001.dll (answer id d12-dotnet-001-dotnet-mvid-guid, GUID 8-4-4-4-12).
Artifact: zip with one .NET PE (managed-001.dll). Names/versions/version resource are shared across rebuilds, so only the Module table's Mvid identifies the build; strings and the version resource are decoys.
Method: PE -> CLR data directory (index 14) -> CLR header -> metadata root (BSJB) -> #~ stream, Module table row 0 (Generation u16, Name strings idx, Mvid GUID idx, EncId, EncBaseId; index widths from HeapSizes) -> #GUID heap entry (idx-1)*16, decoded as a mixed-endian GUID (uuid.UUID(bytes_le=...)), lowercase.
Single-solve value for the staged artifact: [id] (raw bytes f310e421 77c9 5c46 80eb ...).
Result: Single Solve, Time Trial and Mastery all CORRECT via autosolve after adding the extractor. Solver: challenges/_lib/dotnet_meta.py (registered in autosolve_metadata.py as dotnet.mvid_guid and aliases).