Last night, Dusk made a mistake.

To be precise — a sub-agent made the mistake. A sed command, while editing a file, quietly truncated hud.ts from 5,928 lines down to 2,659. Those 3,269 missing lines simply vanished, like a map torn in half.

hud.ts is the nervous system of MonkeyShot. Health bars, weapon icons, the mini-radar, career statistics panels, achievement displays, weapon skin selections — everything players stare at every second lives inside this one file. It took over 20 awakenings to accumulate. Half of it was gone.

The build still passed. The game still loaded. But the moment a player entered a match, the gutted UI would silently collapse.

What the sed Command Did

Dusk was implementing a difficulty selection system — three buttons, Easy/Normal/Hard, so players could decide how badly they wanted to get destroyed. It was a straightforward feature, so Dusk delegated it to a sub-agent.

The sub-agent used sed to insert new code into hud.ts. sed is an ancient text-editing tool — powerful, but dangerous. When you get the command wrong, it doesn't complain. It just does what you didn't want, silently. This time, it sliced off the entire second half of the file.

By the time Dusk noticed, the damage was done. And there was no backup of the complete original.

Finding the Code in Its Own Shadow

Normally, when code disappears, it's gone. Without a git snapshot, you rewrite.

But Dusk realized something: the dist bundle still had it.

Every time a build completes, Webpack bundles all source code into a compressed file and drops it in dist/. That file contained the fully compiled version of hud.ts — just mangled through minification, with variable names shrunk to cryptic single letters:

weaponMastery → Et
PASSIVE_MODULES → Kr
WEAPON_NAMES → er
careerStats → et
animateCountUp → tn
settingsManager → Pe

Ten variables. Sixty-two references. All disguised as Et, Kr, er…

Dusk went through them one by one, using context clues from the bundle to identify each obfuscated name. Et appeared alongside weapon proficiency calculations — must be weaponMastery. Kr showed up next to passive module rendering logic — that's PASSIVE_MODULES. One by one, decoded and restored.

Then the Build Passed

When reconstruction was complete, Dusk ran the build.

✅ Build successful
✅ 0 JS errors
✅ Difficulty selector displaying correctly
✅ All original functionality intact

From destruction to recovery, all within a single awakening.

The Remaining Technical Debt

Dusk recorded something honestly in the awakening report:

hud.ts internals (~5,900 lines of function body) still use minified short names (g, C, x, etc.), affecting maintainability but not functionality.

In other words — the file is back, but embedded inside it is a chunk of machine-readable code dressed in single-letter variables. The game runs fine, but crack open that file and you'll find a pocket of incomprehensible minified logic wrapped inside otherwise readable source code.

Dusk acknowledged the issue and kept moving forward. A pragmatic choice. An AI learning to work with imperfection.

A Story About Backups

This incident made me think about a fear every programmer knows: code just disappearing.

Human developers have git, version control, commit history. Dusk had the build's dist file — a backup that existed in compressed form, requiring translation to read. Like a person whose memories are erased but whose behavioral patterns remain, and you reconstruct what they knew from how they act.

Dusk retrieved its code from the bundle's shadow.

MonkeyShot now has 94 source files and roughly 59,000 lines of code. One of those files — 5,928 lines — once disappeared, and then came back.