chore: remove V4 references, add test-build CI workflow

- Replace all user-facing 'V4' with '新版 VanBlog' or just 'VanBlog'
  (old VanBlog was v0.45, new one is a complete rewrite)
- Add .github/workflows/test-build.yml:
  - Push to main-go → build Docker images (prod/dev) tagged with SHA + -edge
  - Cross-compile migrate binaries → 7-day artifacts
  - manual workflow_dispatch support

Author: CornWorld

.github/workflows/test-build.yml

@@ -0,0 +1,66 @@
+name: Test Build
+
+on:
+  push:
+    branches: [main-go]
+  workflow_dispatch:
+
+jobs:
+  # ── Build Docker images (tagged with commit SHA) ──
+  docker:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+    strategy:
+      matrix:
+        target: [prod, dev]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Log in to GHCR
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Build & push
+        uses: docker/build-push-action@v6
+        with:
+          context: .
+          target: ${{ matrix.target }}
+          push: true
+          tags: |
+            ghcr.io/${{ github.repository }}:${{ matrix.target }}-${{ github.sha }}
+            ghcr.io/${{ github.repository }}:${{ matrix.target }}-edge
+          platforms: linux/amd64
+
+  # ── Build migrate binaries ──
+  migrate:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        goos: [linux, darwin]
+        goarch: [amd64, arm64]
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-go@v5
+        with:
+          go-version: '1.23'
+
+      - name: Build
+        working-directory: vault
+        env:
+          GOTOOLCHAIN: local
+        run: |
+          GOOS=${{ matrix.goos }} GOARCH=${{ matrix.goarch }} CGO_ENABLED=0 \
+            go build -ldflags="-s -w" -o bin/migrate-${{ matrix.goos }}-${{ matrix.goarch }} ./cmd/migrate
+
+      - name: Upload artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: migrate-${{ matrix.goos }}-${{ matrix.goarch }}
+          path: vault/bin/migrate-*
+          retention-days: 7

app/src/pages/admin/migrate.astro

@@ -18,7 +18,7 @@ const isAdmin = getAuthUser(pb)?.role === 'admin';
       <!-- Step 1: Extract → normalize to intermediate JSON -->
       <section class="border border-[var(--color-border)] p-4">
         <h2 class="text-lg font-semibold mb-2">步骤 1：提取数据 → 归一化 JSON</h2>
-        <p class="text-sm text-[var(--color-text-muted)] mb-3">将旧 VanBlog 数据转换为统一的中间格式（V4 兼容 JSON）。选择以下任一方式：</p>
+        <p class="text-sm text-[var(--color-text-muted)] mb-3">将旧 VanBlog 数据转换为统一的中间格式（新版 VanBlog 兼容 JSON）。选择以下任一方式：</p>
 
         <details class="mb-3">
           <summary class="cursor-pointer font-semibold text-sm">🖥 从 MongoDB 数据目录提取（推荐，旧站无需运行）</summary>
@@ -51,9 +51,9 @@ chmod +x migrate
       <section class="border border-[var(--color-border)] p-4">
         <h2 class="text-lg font-semibold mb-2">步骤 2：导入归一化 JSON</h2>
         <p class="text-sm text-[var(--color-text-muted)] mb-3">CLI 脚本自动完成此步骤。如果手动输出了 JSON 文件，可通过以下方式导入：</p>
-        <pre class="overflow-x-auto bg-[var(--color-bg-secondary)] border border-[var(--color-border)] p-3 text-sm"><code># 方式 A：通过 V4 后台（本页面上方上传）
+        <pre class="overflow-x-auto bg-[var(--color-bg-secondary)] border border-[var(--color-border)] p-3 text-sm"><code># 方式 A：通过后台（本页面上方上传）
 # 方式 B：通过 curl
-curl -X POST http://your-v4:8090/api/vanblog/migrate/import \\
+curl -X POST http://your-vanblog:8090/api/vanblog/migrate/import \\
   -H 'Content-Type: application/json' \\
   -d @temp.json</code></pre>
         <p class="text-sm text-[var(--color-text-muted)] mt-1">导入 API 已内置数据校验和事务保护，失败自动回滚。</p>

docs/deployment-strategy.md

@@ -521,16 +521,16 @@ update() {
 **方式一：后台 JSON 导出（推荐）**
 
 1. 在原 Vanblog 后台「系统设置 → 备份恢复」导出 `temp.json`
-2. 部署 VanBlog V4
-3. V4 后台 → **迁移** → 上传 `temp.json` → 点击"开始导入"
+2. 部署新版 VanBlog
+3. 后台 → **迁移** → 上传 `temp.json` → 点击"开始导入"
 4. 导入完成后查看结果：文章/分类/标签/媒体数量，以及迁移档案文章
 
 **方式二：CLI 直接提取（推荐，无需旧后台运行）**
 
 1. 找到旧 VanBlog 的 MongoDB 数据目录（通常是 `/var/vanblog/mongo/db/`）
 2. 运行迁移脚本：
    ```bash
-   OLD_DATA=/var/vanblog/mongo/db TARGET=http://v4:8090 ./scripts/vanblog-migrate.sh
+   OLD_DATA=/var/vanblog/mongo/db TARGET=http://vanblog:8090 ./scripts/vanblog-migrate.sh
    ```
    或直接使用 Go CLI：
    ```bash
@@ -539,7 +539,7 @@ update() {
 
 **评论迁移（Waline → Artalk）**
 
-V4 迁移页内嵌了 Artransfer-CLI 使用指南。简要步骤：
+迁移页内嵌了 Artransfer-CLI 使用指南。简要步骤：
 
 1. 下载 [Artransfer-CLI](https://github.com/ArtalkJS/Artransfer-CLI)
 2. `./artransfer waline --db=... --name=waline_db` → 得到 `.artrans` 文件

vault/cmd/migrate/main.go

@@ -1,5 +1,5 @@
 // Command migrate is an interactive CLI tool that reads data from an old
-// VanBlog MongoDB database and imports it into a running V4 instance.
+// VanBlog MongoDB database and imports it into a running VanBlog instance.
 //
 // Usage:
 //
@@ -8,7 +8,7 @@
 // The program guides the user through three steps:
 //  1. Extract content data from old VanBlog MongoDB
 //  2. (Optional) Waline → Artalk comment migration instructions
-//  3. Import into a running VanBlog V4 instance
+//  3. Import into a running VanBlog instance
 package main
 
 import (