Devblog action: fix git pretty-format escape, backfill posts
Root cause: the format string used JS "\u001f" escapes but git's
Root cause: the format string used JS “\u001f” escapes but git’s —pretty=format: doesn’t interpret those as control characters — it emits the literal text “\u001f”. Script then split on the actual 0x1F byte and never matched, so every run silently produced zero posts even when there were new commits in the range.
Fix: use git’s %x1f / %x1e hex escape tokens in the format string so git emits the real 0x1F / 0x1E bytes that the Node-side split expects.
Also backfills the 20+ devblog posts that should have been auto- generated from yesterday’s big 15-commit push (audio, VFX, combat mechanics, meta-progression, etc.) so the site and game news panel catch up.
Commit 03375d3 by astafford8488.