Move trial authorization out of MVP scope

Resolve the requirements-vs-architecture conflict found in the Phase 5
review. License v1 is frozen at nine fields with no expiry field
(perpetual is a bool; update/rebind policy are opaque labels), so it
cannot express a trial period. The implementation and architecture docs
correctly recorded that boundary, but 02-requirements still listed trial
as a P0 capability and an MVP acceptance criterion.

Decision: trial moves to V1.1.

- 02-requirements: drop trial from the user role and P0 feature list;
  acceptance now reads 'authorization state consistent between box and
  sub-apps'; add a V1.1 trial row naming the protocol prerequisite; add
  a scope row stating perpetual:false is display-only and never expires,
  and supports_trial does not grant local trial.
- 00-ai-start-here: remove trial from 'MVP does', add it to 'MVP does
  not' with the protocol reason.
- 04-architecture: development order step 5 no longer lists trial/rebind
  as MVP work.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/04-architecture.md

@@ -212,7 +212,7 @@ T-403 的盒子自更新由独立、无 Gio 的 `SoftBoxUpdater.exe` 完成。
 2. 最高风险原型:签名清单验签与缓存回退、ZIP 安全解压、staging/backup 原子切换。
 3. 核心用户流程:清单 → 列表/搜索 → 下载队列 → 安装 → 启动。
 4. 更新与自更新:子软件更新、SoftBoxUpdater、健康检查与回滚。
-5. 授权:机器指纹、许可证验证、试用/换绑/导入。
+5. 授权:机器指纹、许可证验证、离线导入与撤销状态(试用/换绑不在 MVP,见 `02-requirements.md`)。
 6. Win7 加固与发布:API 降级、真机矩阵、双通道发布流水线。
 
 ## 八、架构纪律