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.

docs/development.md

@@ -15,6 +15,10 @@ The bundled validator validates evidence structure only. It cannot authenticate
 
 Use Python 3.9+ and the standard library. The optional upstream skill-creator quick_validate.py requires PyYAML; if missing, report the missing dependency rather than substituting an unreported result.
 
+For this repository, run the checks required by AGENTS.md once on the final relevant baseline, including the available skill-creator validator. Unit tests already cover validator smoke behavior and installer safety; do not stack their equivalent standalone examples after a passing run. Instruction changes need a focused static review of representative decisions, not wording-matching unit tests. Installation comparison is for an installation task, not a requirement that a contributor's active global prompt equal the template.
+
+For tasks using the skill, select checks through [verification scope and causal repair](../skills/codex-subagent-router/references/engineering-workflow.md). Preserve required checks; reuse unaffected evidence and stop when the relevant outcome is supported. Static scenarios remain expectations until real authorized forward tests observe behavior. Do not claim this policy reduced elapsed time, cost or defects without measurements.
+
 ## Compatibility with other skills
 
 Do not automatically rewrite unrelated skills. Older orchestration skills may assume forked workspaces, a close tool, or a Sol-only parent. Resolve conflicting applicable instructions according to host precedence and identify the exact remaining gate. For a coordinated migration, explicitly include those files and their project-specific requirements.

docs/releases/2.4.0.md

@@ -0,0 +1,16 @@
+# 2.4.0 — 最小充分验证、因果修复与简单任务并行
+
+## 变化
+
+- 验证按实际影响分档，并明确停止条件。低风险改动默认检查差异与直接结果，局部行为改动检查受影响路径，共享合同或高影响改动覆盖相关消费者与集成；保留项目必需检查。可信 worker 结果按相关产物和环境复用，整合只补查新增交互，不默认叠加全量测试、额外审查或 JSON 证据包。
+- 排障在第一次实质问题出现时定位原因并简查同机制的相邻调用点。重复特判、兜底或生产者/消费者分歧触发合同、设计与流程调查，优先在原因所属层修复已证实的一类问题；明显局部错误仍局部处理，不要求普遍架构审计或无关重构。
+- 已获授权的多个简单编码批次属于正常 Luna 工作。有明确行为、基线与文件/语义所有权即可分派，由 worker 定位局部改动；不等完整仓库地图或主线程预先解完任务。按实际容量及时补位，普通合同和返回使用简短文字，验证只分配实际需要的检查。
+- 新增按需读取的工程工作流参考，并同步技能入口、可选全局提示词、舰队/升级参考、维护文档与静态行为场景。README 不再把单元测试已覆盖的校验器样例、self-test 或本机安装一致性列成每轮必做项。
+
+## 兼容与验证边界
+
+保留子智能体授权、真实宿主槽位、文件与语义所有权、主线程整合及外部操作边界。证据 schema、决策 schema、模型路由和安装备份行为不变。仓库内模板不会自动成为当前会话指令，安装技能不会开启并行能力。
+
+本轮静态场景描述预期决策，不是实时 agent 行为或性能测量。节省时间、成本与减少缺陷需通过后续已授权真实任务核实。
+
+更新个人全局规则应先备份并做定向合并；`--include-prompt --apply` 仍整体替换提示词，不用于合并个人规则。