docs: fix status page tier availability and add page limits

Status page is not Pro-only: all plans get public status pages
(Free/Standard: 1, Pro: 5), internal pages are Pro-only (up to 20).
Verified against fc-statuspage/logic/page/page.go constants.

- Split "Status page" into "Public/Internal status page" in feature matrix
- Add page count limits to resource limits table
- Fix version tips on statuspage docs pages

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: ysyneu

en/on-call/statuspage/statuspage.mdx

@@ -3,7 +3,7 @@ title: "Status Page"
 description: "Achieve efficient internal and external communication during incidents through a unified service status dashboard"
 ---
 
-<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+<Tip>**Plan requirement**: All plans can create public status pages (Free and Standard: up to 1, Pro: up to 5). Internal status pages are available on the Pro plan only (up to 20). [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
 
 Service interruptions are inevitable, but communication efficiency can be systematically improved.
 

en/platform/pricing.mdx

@@ -52,7 +52,8 @@ Each License corresponds to one account member. Only members with a License can
 | **Intelligent alert grouping** | ❌ | ❌ | ✅ |
 | **External incident creation** | ❌ | ❌ | ✅ |
 | **Post-mortem** | ❌ | ❌ | ✅ |
-| **Status page** | ❌ | ❌ | ✅ |
+| **Public status page** | ✅ | ✅ | ✅ |
+| **Internal status page** | ❌ | ❌ | ✅ |
 | **AI incident summary** | ❌ | ❌ | ✅ |
 | **War room** | ❌ | ❌ | ✅ |
 | **Ticketing integration** (Jira, ServiceNow) | ❌ | ❌ | ✅ |
@@ -67,6 +68,8 @@ For detailed feature comparison, also visit: [Pricing Page](https://flashcat.clo
 | Maximum schedules | 1 | Unlimited | Unlimited |
 | Maximum channels | 1 | Unlimited | Unlimited |
 | Daily alert limit | 100 | Unlimited | Unlimited |
+| Public status pages | 1 | 1 | 5 |
+| Internal status pages | Not available | Not available | 20 |
 | Data retention | 30 days | 180 days | 360 days |
 | Audit logs | Not available | 10 days | 30 days |
 

zh/on-call/statuspage/statuspage.mdx

@@ -4,7 +4,7 @@ description: "通过统一的服务状态看板，实现故障期间的高效内
 keywords: ["状态页", "服务状态", "可用性", "故障通报", "外部沟通"]
 ---
 
-<Tip>**版本要求**：此功能需要 On-call 专业版及以上订阅。[了解更多](https://flashcat.cloud/flashduty/price/)</Tip>
+<Tip>**版本要求**：所有版本均可创建公开状态页（免费版和标准版最多 1 个，专业版最多 5 个）。内部状态页仅在专业版中提供（最多 20 个）。[了解更多](https://flashcat.cloud/flashduty/price/)</Tip>
 
 服务中断不可避免，但沟通效率可以系统性提升。
 

zh/platform/pricing.mdx

@@ -52,7 +52,8 @@ On-call 采用 **License 订阅制**收费，按活跃用户数量计费。
 | **智能告警分组** | ❌ | ❌ | ✅ |
 | **外部创建故障** | ❌ | ❌ | ✅ |
 | **故障复盘** | ❌ | ❌ | ✅ |
-| **状态页** | ❌ | ❌ | ✅ |
+| **公开状态页** | ✅ | ✅ | ✅ |
+| **内部状态页** | ❌ | ❌ | ✅ |
 | **AI 故障摘要** | ❌ | ❌ | ✅ |
 | **作战室** | ❌ | ❌ | ✅ |
 | **工单集成**（Jira、ServiceNow） | ❌ | ❌ | ✅ |
@@ -67,6 +68,8 @@ On-call 采用 **License 订阅制**收费，按活跃用户数量计费。
 | 最大值班表数 | 1 | 不限 | 不限 |
 | 最大协作空间数 | 1 | 不限 | 不限 |
 | 每日告警上限 | 100 条 | 不限 | 不限 |
+| 公开状态页 | 1 个 | 1 个 | 5 个 |
+| 内部状态页 | 不支持 | 不支持 | 20 个 |
 | 数据保留时长 | 30 天 | 180 天 | 360 天 |
 | 审计日志 | 不支持 | 10 天 | 30 天 |