Rewind dan Plan Mode Claude Code: Batalkan Perubahan Berisiko

 * Idempotent: a slug already in BLOG_POSTS_STATIC is skipped.
 *
 *   node scripts/merge-blog-staging.mjs [--dry-run]
 *
 * Design note — why this is plan-then-write rather than validate-then-write:
 * the previous version validated the staged CONTENT completely, then began
 * writing, and resolved each insertion anchor at write time. When a constant
 * moved module (REAL_IMAGE_SLUGS left blog-posts-static.ts), the third write
 * threw after messages/*.json and the post registry had already been updated —
 * a half-merged repo that a re-run would not fix, because by then the slug
 * existed in en.json and got skipped. Anchors are now resolved during
 * validation, so either every edit is possible or nothing is touched.

Skrip yang tidak perlu membatalkan apa pun karena memeriksa lebih dulu. Ia menyelesaikan setiap anchor sisipan saat validasi, sehingga semua edit mungkin dilakukan atau tidak ada yang disentuh. Skrip ini berjalan lewat Bash, jadi rewind tidak bisa memulihkannya; merencanakan sebelum menulis adalah cara skrip melindungi enam filenya.

**The half-merge.** The merge script validates everything, then writes. Anchor
resolution happens at _write_ time, so a moved constant threw mid-write after
`messages/*.json` and `BLOG_POSTS_STATIC` were already updated. Re-running does
not recover — the script skips slugs it finds in `en.json` and considers the job
done. Recovery:

```bash
git status --short          # see which of the six the aborted run reached
git checkout -- <those files>   # revert only those; keep your component
# fix the anchor, then re-run the merge
```

Your component and staging folder are untouched by a failed merge, so only the
generated writes need reverting.

Cadangan yang jujur. Ketika merge setengah selesai, pemulihan yang didokumentasikan adalah git status untuk melihat file mana yang dijangkau proses itu, lalu git checkout hanya pada file tersebut. Git, bukan checkpoint, adalah undo untuk perubahan yang dibuat oleh skrip.

**Always run `npx tsc --noEmit && npm run build` before pushing.** The build runs `assertBlogParity()` from `lib/blog-meta.ts` which fails if a blog post is registered in `BLOG_POSTS_STATIC` but missing from `BLOG_META` (or vice versa).

Verifikasi sebagai lapisan terakhir. Build menjalankan assertBlogParity(), yang gagal ketika sebuah post terdaftar di satu daftar tetapi tidak ada di daftar lain. Ia menangkap perubahan yang salah yang akan lolos dari plan mode maupun rewind.