docs(emergency-withdraw): update README for deployment, i18n, build setup

- New "Deployment" section — documents the GitHub Pages workflow
  (.github/workflows/deploy-emergency-withdraw.yml), the public/CNAME
  custom domain, and the one-time repo + DNS setup.
- New "Languages" section — English / 繁體中文 / 日本語, globe switcher,
  localStorage persistence, all bundled so it works offline.
- Development: fix the stale `cd v1/reference/emergency-withdraw` path to
  `cd emergency-withdraw`; prefer `npm ci` now that package-lock.json is
  committed.
- Usage Option A: emergency.optivaults.app is live — drop the "once
  published" qualifier.
- Trust model: refresh the SPA line-count note and mention i18n.

Author: optivaults-fi

README-zh-TW.md

@@ -41,7 +41,7 @@ OptiVaults V1 **刻意被設計成兩個可分離的層**:
 | `keeper/` | 🚧 Placeholder | V1 keeper 參考實作，在 keeper 驗證里程碑之後遷入。TypeScript、vitest 測試。 |
 | `frontend/` | ✅ 已發布 | React 19 + Vite 8 + TailwindCSS v4 SPA。CIP-30 錢包整合、**瀏覽器內 TX 建構（Lucid Evolution）**（無獨立 API server——原本的 `api/` 元件已併入 frontend client-side）、Blockfrost 直接 REST、vitest 測試。7 個頁面、EN / zh-TW / ja 三語 i18n。Operator-specific URL + Cloudflare Pages 部署腳本已在 `frontend/README.md` 為 forker 標註。 |
 | `withdraw-cli/` | ✅ 已發布 | Node CLI，用於 self-serve Withdraw（不依賴任何基礎設施）。 |
-| `emergency-withdraw/` | ✅ 已發布 | 靜態 HTML 的 self-serve 緊急提領工具——瀏覽器內運作、無 backend 依賴。 |
+| `emergency-withdraw/` | ✅ 已發布 | 靜態 HTML 的 self-serve 緊急提領工具——瀏覽器內運作、無 backend 依賴。English / zh-TW / ja 三語 i18n。 |
 
 剩餘元件會在驗證為 V1-ready 後分批遷入。
 

README.md

@@ -41,7 +41,7 @@ See the [OptiVaults whitepaper](https://github.com/OptiVaults/optivaults-protoco
 | `keeper/` | 🚧 Placeholder | V1 keeper reference implementation coming post keeper-verification milestone. TypeScript, vitest-tested. |
 | `frontend/` | ✅ Published | React 19 + Vite 8 + TailwindCSS v4 SPA. CIP-30 wallet integration, **in-browser TX building via Lucid Evolution** (no separate API server — the previous `api/` component has been folded into the frontend client-side), Blockfrost direct REST, vitest tests. 7 pages with EN / zh-TW / ja i18n. Operator-specific URLs + Cloudflare Pages deploy script flagged in `frontend/README.md` for forkers. |
 | `withdraw-cli/` | ✅ Published | Node CLI for self-serve Withdraw (no infrastructure dependency). |
-| `emergency-withdraw/` | ✅ Published | Static HTML self-serve emergency-withdraw tool — in-browser, no backend dependency. |
+| `emergency-withdraw/` | ✅ Published | Static HTML self-serve emergency-withdraw tool — in-browser, no backend dependency. English / zh-TW / ja i18n. |
 
 Remaining components will be added in batches as each is verified V1-ready against the on-chain contracts.
 

emergency-withdraw/README.md

@@ -20,7 +20,7 @@ V1 ships a different on-chain contract surface from V9.x / V10:
 |---|---|
 | Smart contract | OptiVaults V1 contract code on Cardano (open source, multiple rounds of internal audit, external Q2-Q3 2027 audit pending — Withdraw-Zero pattern + R55 compile-time Vault NFT anchor + V1 Layer 3 governance safety) |
 | Vault identity | One-shot Vault NFT minted at deploy ceremony — the validator script hashes physically encode the real NFT policy, and the page verifies the target vault UTXO holds that NFT before building the TX |
-| Withdrawal logic | This static React/Vite SPA (open source, ~700 lines logic + 700 lines UI) |
+| Withdrawal logic | This static React/Vite SPA — open source, ~700 lines of withdrawal logic in `lib/` plus the React UI (English / 繁體中文 / 日本語 i18n) |
 | Chain query | Blockfrost (your own API key) |
 | Deploy state | A `v1-deploy-state.json` ceremony file (operator-published, but you can swap it via `?config=<url>` query param) |
 | TX signing | Your CIP-30 wallet extension |
@@ -32,11 +32,15 @@ The page detects the network from the loaded ceremony JSON's `network` field, th
 
 V1 currently runs on **Preprod only** (release `v1-preprod-p23`). Mainnet deploy lands when V1 ceremony is performed.
 
+## Languages
+
+The UI ships in English, 繁體中文, and 日本語 — switch via the globe selector in the header. The choice is saved to `localStorage`, and on first visit it follows the browser language. All translations are bundled into the page (no network fetch), so they work in an offline-saved copy too.
+
 ## Usage
 
 ### Option A — online (operator-hosted)
 
-Visit the operator's URL (e.g. `https://emergency.optivaults.app` once published).
+Visit the operator's URL: <https://emergency.optivaults.app>.
 
 ### Option B — offline (recommended for worst-case)
 
@@ -80,15 +84,25 @@ Useful if you've forked the contract for your own instance and want to share an
 ## Development
 
 ```bash
-cd v1/reference/emergency-withdraw
-npm install
+cd emergency-withdraw
+npm ci           # reproducible install from package-lock.json (npm install also works)
 npm run dev      # vite dev server on :5173
 npm run build    # outputs dist/ (Buffer polyfill auto-injected post-build)
 npm run preview  # serve dist/ locally
 ```
 
 The build outputs a multi-file dist (HTML + JS chunks + WASM). For true single-file offline mode, run the build then drag `dist/index.html` into a browser; modern browsers inline assets automatically when saving "Webpage HTML Only".
 
+## Deployment
+
+The page is a static SPA, so any static host works. The OptiVaults-operated instance is published to GitHub Pages straight from this repo:
+
+- [`.github/workflows/deploy-emergency-withdraw.yml`](../.github/workflows/deploy-emergency-withdraw.yml) builds the SPA on every push to `v1` that touches `emergency-withdraw/`, then publishes `dist/` via `actions/deploy-pages`.
+- `public/CNAME` carries the custom domain `emergency.optivaults.app`. The site is served from the domain root, so Vite's default `base` (`/`) is left unchanged.
+- One-time repo setup: **Settings → Pages → Source → "GitHub Actions"**, plus a DNS `CNAME` record `emergency` → `optivaults.github.io`.
+
+Forking your own instance: repoint `public/CNAME` at your domain, or delete it and serve from the `*.github.io` project URL (set Vite `base` to match the sub-path), or drop the built `dist/` on any other static host.
+
 ## License
 
 Apache License 2.0 (permissive open-source, OSI-approved).