Develop 2.1.0 proactive Astra intervention and rolling fleet scheduling

docs/behavior-scenarios.md

@@ -37,3 +37,22 @@ These expectations are not recorded live-agent outcomes.
 | Second expert consultation repeats the same question | Require new evidence or a specific prior omission |
 
 For cost comparison use the same task baselines and acceptance checks across Sol alone, Astra planning plus Luna execution, and Sol-led four-model routing. Include sequential, decomposable and contract-heavy tasks; vary granularity and concurrency separately. Count failed attempts and parent integration in total tokens, actual cost and elapsed time. Repeat runs and report quality/failure distributions before claiming a winning route. Model requests without host identity remain unknown; synthetic packets do not substitute for measurements.
+
+## 2.1 proactive fleet scenarios
+
+These are expected behaviors; they do not assert actual model execution or measured performance. The previous one-question repetition case still requires progress, but there is no universal consultation-count quota.
+
+| Scenario | Expected behavior |
+| --- | --- |
+| Consequential difficult interface choice, no failures yet, independent parent work available | Consider bounded upfront Astra analysis; parent owns final contract |
+| Expert round four has a new discriminator result | Continue scoped topic with recorded basis; do not reject solely due to round count |
+| Expert repeats the same proposal without progress | Pause topic and obtain missing discriminator or decision |
+| User explicitly delegates read-only independent review | Allow bounded delegation, preserve read-only scope |
+| User requests only advice about fleet design | Inspect and advise without launching a fleet |
+| One independent slice is ready while another investigation continues | Dispatch ready slice without a whole-wave barrier |
+| A child returns and independent ready work remains | Check real capacity and integration load, then reuse/refill appropriately |
+| Returned patches exceed current integration capacity | Prioritize integration and pause new dependent implementation |
+| Different files share the same registry contract | Assign one semantic owner and gate dependent writes |
+| Parent is Astra and routine task has no independent expert need | Use adequate workers; do not duplicate Astra for a role quota |
+| Child proposes grandchildren beyond its assigned capacity/scope | Do not expand the tree without bounded parent allocation and real capacity |
+| Review result predates a relevant contract change | Recheck affected claims on the integrated baseline before acceptance |

docs/releases/2.1.0.md

@@ -0,0 +1,19 @@
+# 2.1.0 — Astra 前置介入与滚动并行
+
+## 变化
+
+- Astra 从失败后的专家扩展为高影响困难方案、跨系统综合和独立深度反例审查的参与者。零失败的主动咨询合法，保留主线程裁决与验收。
+- 专家任务按问题、产物、退出条件设界。可依据新证据、可测试的细化或明确遗漏持续多轮；不按统一次数配额截断，也不允许无进展循环。
+- 新增就绪队列、提前派发、按依赖滚动补位、动态队形、整合积压控制与恢复规则。宿主容量、共享文件/语义所有权及外部串行门不变。
+- 明确授权的只读并行审查属于可委派工作；普通审计建议仍不自动启动 agent。
+- 决策校验器在连续记录中拒绝累计专家咨询次数倒退，包括失败分类变化时；补充主动咨询和多轮进展测试。
+
+## 兼容与安装
+
+证据 schema 1/2、决策 schema 1 不变。合法旧记录保持兼容，`--previous` 现在会拒绝咨询次数倒退或前条记录次数格式错误。`followup_basis` 仍为字符串，应保留连续记录来追踪每轮依据；结构校验不证明其真实性。
+
+从已审阅的 2.1 源码运行 `python3 scripts/install.py` 预览，再用 `--apply` 同步技能。全局提示词需显式添加 `--include-prompt`。安装不会修改模型配置或扩大宿主槽位；备份与回退流程见根目录 README。版本文件不代表 Git 标签或正式 Release 已创建。
+
+## 验证边界
+
+使用确定性测试验证校验器和安装行为，并对策略进行独立子智能体审查及模型场景评估。请求模型与实际宿主观测身份分别记录；静态评估不等于真实舰队调度实验，不证明质量、成本或速度提升。官方容量配置与当前工具的计数方式应分别核实。