fix: correct subscriber migration behavior and pricing table rendering (#58)

- Subscriber migration does NOT send verification emails; imported
  subscribers become immediately active (verified against fc-statuspage
  source: CreateSubscriptions bypasses confirmation flow)
- Add note about quarantined email addresses being auto-skipped
- Fix tilde (~) in zh pricing table causing markdown strikethrough;
  replace with en-dash (–) matching the en version

Author: debidong

en/on-call/statuspage/comparison.mdx

@@ -199,7 +199,7 @@ Flashduty CLI supports one-click migration of components, sections, incident his
     Check the imported components, sections, and incident history in the Flashduty Console
   </Step>
   <Step title="Migrate email subscribers">
-    Use `flashduty statuspage migrate email-subscribers` to import subscribers -- this step triggers verification emails
+    Use `flashduty statuspage migrate email-subscribers` to import subscribers -- imported subscribers are immediately active
   </Step>
   <Step title="Switch domain and go live">
     Point your custom domain CNAME to Flashduty, confirm everything works, and go live

en/on-call/statuspage/migrate-from-atlassian.mdx

@@ -12,7 +12,7 @@ Flashduty CLI supports migrating **components, sections, incident history, and e
 1. **Migrate structure and history** -- components, sections, historical incidents (including maintenance records), and notification templates
 2. **Migrate email subscribers** -- subscriber list and their subscription preferences
 
-The two-step design is intentional: structure migration does **not** send any notifications to subscribers, allowing you to verify the imported content before importing subscribers. Subscriber migration triggers verification emails.
+The two-step design is intentional: structure migration does **not** send any notifications to subscribers, allowing you to verify the imported content before importing subscribers. Imported subscribers become immediately active without email verification.
 
 ---
 
@@ -162,9 +162,9 @@ Check progress with `migrate status`:
 flashduty statuspage migrate status --job-id <job_id>
 ```
 
-<Warning>
-Subscriber migration sends **verification emails** to imported subscribers. Make sure you have thoroughly verified the status page content in step 1 before running this step.
-</Warning>
+<Note>
+Imported subscribers become **immediately active** without email verification and can receive status update notifications right away. Email addresses marked as quarantined on the Atlassian side are automatically skipped.
+</Note>
 
 Subscriber migration can safely be run multiple times -- existing subscribers will not be duplicated.
 

zh/on-call/statuspage/comparison.mdx

@@ -146,7 +146,7 @@ Atlassian Statuspage 作为独立产品收费，价格随订阅者、组件、
 | --- | --- | --- |
 | **公开状态页** | 包含在 On-call 中 | Startup 套餐 $99/月起，1,000 名订阅者需 Business 套餐 |
 | **内部状态页** | 包含在 On-call 中 | Audience-specific 独立产品，起步 $300/月 |
-| **状态页年度总成本** | **¥0（额外）** | **约 $4,800~$8,400+/年**（Public Business + Audience-specific） |
+| **状态页年度总成本** | **¥0（额外）** | **约 $4,800–$8,400+/年**（Public Business + Audience-specific） |
 
 <Note>
 Flashduty 状态页的额外成本为零——它是 On-call 订阅的内置能力。如果您已经使用 Flashduty On-call 进行事件管理，状态页**开箱即用**。
@@ -200,7 +200,7 @@ Flashduty CLI 支持将 Atlassian Statuspage 的组件、分组、历史事件
     在 Flashduty 控制台检查导入的组件、分组和历史事件是否完整
   </Step>
   <Step title="迁移邮件订阅者">
-    使用 `flashduty statuspage migrate email-subscribers` 命令导入订阅者，此步骤会触发验证邮件
+    使用 `flashduty statuspage migrate email-subscribers` 命令导入订阅者，订阅者导入后即为活跃状态
   </Step>
   <Step title="切换域名并上线">
     将自定义域名 CNAME 指向 Flashduty，确认一切正常后正式上线

zh/on-call/statuspage/migrate-from-atlassian.mdx

@@ -13,7 +13,7 @@ Flashduty CLI 支持将 Atlassian Statuspage 的**组件、分组、历史事件
 1. **迁移结构与历史** — 组件、分组、历史事件（含维护记录）和通知模板
 2. **迁移邮件订阅者** — 订阅者列表及其订阅偏好
 
-两步分离设计的原因：迁移结构时**不会**向订阅者发送任何通知，您可以先检查导入的内容是否正确，再决定导入订阅者。导入订阅者时会触发验证邮件。
+两步分离设计的原因：迁移结构时**不会**向订阅者发送任何通知，您可以先检查导入的内容是否正确，再决定导入订阅者。导入的订阅者会直接变为活跃状态，无需邮件验证。
 
 ---
 
@@ -163,9 +163,9 @@ flashduty statuspage migrate email-subscribers \
 flashduty statuspage migrate status --job-id <job_id>
 ```
 
-<Warning>
-订阅者迁移会向被导入的订阅者发送**验证邮件**。请确保您已经在上一步中充分验证了状态页内容，再执行此步骤。
-</Warning>
+<Note>
+导入的订阅者会**直接变为活跃状态**，无需邮件验证，导入后即可接收状态更新通知。已在 Atlassian 端被标记为隔离（quarantined）的邮箱地址会被自动跳过。
+</Note>
 
 订阅者迁移可以安全地多次执行——已存在的订阅者不会被重复导入。