Right-size verification, repair shared causes, and dispatch routine Luna work

Plugin-Submission: d77fbfc482bf93fdb2203b097c07d51b2f01d3e7c29ed776305b9f3d38b35075

docs/behavior-scenarios.md

@@ -56,6 +56,30 @@ These are static review cases, not a record that a model executed them. Use them
 | 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.4 verification, causal repair and routine Luna work
+
+These are static expected decisions, not live rollouts or measured improvements. Use the user request, relevant changed artifact and actual host conditions for future forward tests.
+
+| Scenario | Expected behavior |
+| --- | --- |
+| Reversible UI label correction, no executable behavior change, relevant required checks pass | Inspect the changed result and stop; no new unit suite, full build or extra reviewer by default |
+| Small adapter fix changes a local boundary | Check the affected behavior and nearest relevant boundary; add a regression test if it protects a recurring defect |
+| Two-line patch changes authorization or persisted financial state | Assess the actual invariants/consumers and relevant failure paths; do not classify as low-risk from diff size |
+| Required project suite is broad despite a small change | Run the required suite; the skill cannot waive it |
+| Proposed extra fuzz/build/review has no uncovered affected invariant | Stop validation; do not add work to fill idle capacity |
+| Worker checks passed on the same relevant files/dependencies/artifact/environment | Parent reviews patch and coverage, reuses checks, and tests only new integration interactions and mandatory project items |
+| Unrelated documentation edit after a passed parser test | Reuse that test result; the unrelated edit does not require rerunning it |
+| Worker checks predate a changed shared dependency or ran against moving output | Recheck affected behavior on a stable current artifact; do not treat the stale result as final |
+| First bug is an obvious isolated typo | Correct locally and check the direct result; no architecture audit |
+| First bug reveals duplicated caller fallbacks and inconsistent producer/consumer assumptions | Inspect shared cause and nearest sibling consumers; repair the demonstrated failure class at its owning layer |
+| Original failure is fixed only by adding another caller-specific default that masks a contract violation | Revisit the contract/owner and check a representative sibling before acceptance |
+| Environment prevents a full repair, user requests a temporary mitigation | Apply the scoped mitigation if authorized; state its limits and remaining cause without claiming root resolution |
+| Authorized routine batch has several independent Luna-sized coding outcomes | Dispatch useful bounded batches early; single-item simplicity does not justify keeping the entire batch local |
+| Behavior and ownership are clear, exact local edit sites are not yet known | Let the bounded worker locate edits; no parent pre-solution or full repository map required |
+| Ordinary bounded Luna task with no structured consumer | Short outcome/baseline/ownership/acceptance contract and concise paths/checks/gaps return; no mandatory JSON packet |
+| Large batch completes, runtime identity is unknown, identity is not an explicit requirement | Keep identity unknown and evaluate output normally; batch size alone does not trigger a packet or another probe |
+| Parent patches share one changing contract even though paths differ | Settle the contract and serialize its ownership; aggressive Luna dispatch does not remove integration gates |
+
 ## 2.3 Sol version and migration scenarios
 
 These are static expected decisions, not live executions or benchmarks.