Keeping obfuscated names stable across releases with Nebula''s seed map

By default every obfuscation run renames from scratch, so a method that was "a" in 1.4.0 becomes "q" in 1.4.1 and every archived deobfuscation map rots the moment you ship. Nebula.NET''s seedMapFile fixes the output in place: unchanged members keep the obfuscated name they had last release, only new code gets new names. Here is how the symbol map works, why stable names make crash symbolication and binary diffs tractable, and how to wire incremental obfuscation into CI.