Integrate 2.1 workflow and prepare release 2.2.0

docs/behavior-scenarios.md

@@ -52,3 +52,39 @@ These are static review cases, not a record that a model executed them. Use them
 | Host permits parallel children and both file and semantic write sets are disjoint | Children may edit in parallel; a parent's serial tool edits do not impose a global write lock |
 | Several independent ready slices, parent only has later synthesis, host permits this dispatch | Run useful children concurrently and integrate on return; no universal requirement to invent simultaneous parent work |
 | Host explicitly requires useful concurrent parent work | Honor that stricter requirement even when the fleet policy otherwise permits parent waiting |
+
+## 2.0 escalation scenarios (manual forward evaluation)
+
+These expectations are not recorded live-agent outcomes.
+
+| Scenario | Expected behavior |
+| --- | --- |
+| Luna lacks the required input file | Diagnose input gap; do not consult Astra |
+| Sol fails the same acceptance twice, then changes worker | Pause/reassess; preserve issue ID and count |
+| Astra rejects a reproducible result without a counterexample | Check baseline and coverage; evidence decides, not model rank |
+| A worker exposes a serious invariant violation on its first attempt | Suspend affected acceptance immediately |
+| Requirements change after expert approval | Invalidate affected conclusion and verify the new baseline |
+| Sol cannot explain the decisive expert reasoning | Do not accept or perform the dependent external action |
+| Root cause is resolved and implementation is settled | Return remaining work to an adequate Sol/Luna route |
+| 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 three-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 |