"Editing .razor safely (shell/emoji mojibake)"

• Hotbar / toast / button emoji become garbage (🥚, etc.).
• Em-dashes in copy become —.
• Panel still compiles but looks broken; git diff is unreadable noise.

.razor files are UTF-8 (often BOM-less) and frequently contain emoji as icons (20–30px font-size is a common HUD pattern). PowerShell 5.1 Get-Content/Set-Content re-encodes them as ANSI — same trap as general source corruption (powershell-mojibake-utf8).

Do:

• Edit .razor / .razor.scss in a real editor (Cursor/VS), or
• Python / byte-safe .NET read-modify-write:

$f = "Code\UI\Hud.razor"
$c = [System.Text.Encoding]::UTF8.GetString([System.IO.File]::ReadAllBytes($f))
# edit $c
[System.IO.File]::WriteAllBytes($f, [System.Text.Encoding]::UTF8.GetBytes($c))

Don't:

# destroys emoji
(Get-Content $f) -replace 'old','new' | Set-Content $f

If already corrupted: restore from git if possible; otherwise apply the cp1252 round-trip recovery on a copy first (powershell-mojibake-utf8).

After edits: confirm @namespace, and that BuildHash() still covers markup reads (ui-frozen-buildhash).

Razor source is plain UTF-8 text the compiler feeds to the UI generator. Shell tools that assume the system ANSI code page mutate bytes before the compiler ever sees them — byte-preserving APIs leave the emoji codepoints intact.