v3.54.0 — Archive is now a browsable, editable mirror (no more .bin)

You were right: an archive full of data/<hash>.bin blobs is opaque — you can't see what got captured, and you can't edit it. Fixed.

What changed

• Every recorded response is now written under files/ at a real path that mirrors its URL, with a real extension — ui.shadcn.com/_next/static/chunks/….js, …/index.html, …/app.css, API JSON, fonts, images. No opaque blobs (0 .bin on a typical capture).
• It's editable. Change a text response (e.g. files/<host>/index.html) and re-run serve.mjs — the edit shows up, because the replay server reads files fresh on every request. index.json maps each request → its file.
• Static-asset filenames stay clean (per-deploy ?dpl=… cache-busters are dropped from the name); genuinely colliding paths fall back to _blobs/<hash>.

Archive vs Rebuild — which one to edit

The Archive reproduces behavior (the real site running offline); the mirror makes it inspectable and tweakable. But to actually develop a copy — clean React + Tailwind components with your own content — use the Rebuild (/uiforge:clone --react). Archive = behavior, Rebuild = editing. Both are documented in the command playbook now.

Verified end-to-end: a fresh ui.shadcn.com archive renders offline (Next.js boots, real content), and an edit to index.html is reflected on reload.