sortie-dogs 0.12.19 → 0.12.21

package/dist/plugin/protected-snapshot.js

@@ -86,6 +86,24 @@ export async function operationInputSnapshot(projectRoot, binding) {
         ? await declaredScopeDigest(projectRoot, paths, hash, true, outputs)
         : await protectedScopeDigest(projectRoot, paths, hash, binding.source_policy, outputs);
 }
+/** A validation may populate write-only caches. Keep its declared read inputs stable
+ * while binding the resulting candidate (including those outputs) after the command. */
+export async function validationInputSnapshot(projectRoot, binding) {
+    const manifestSource = await readFile(resolve(projectRoot, binding.manifest_path)).catch(() => undefined);
+    if (!manifestSource || `sha256:${createHash("sha256").update(manifestSource).digest("hex")}` !== binding.manifest_hash)
+        return undefined;
+    const manifest = JSON.parse(manifestSource.toString("utf8"));
+    if (!manifest.read.length)
+        return undefined; // Keep the original full-source check when no inputs were declared.
+    const paths = manifest.read.map(entry => {
+        const path = normalizeManifestScope(entry);
+        return path.kind === "relative" ? resolve(projectRoot, path.path) : resolve(path.path);
+    });
+    const hash = binding.manifest_hash.slice("sha256:".length);
+    return binding.source_policy === "declared-paths-v1"
+        ? declaredScopeDigest(projectRoot, paths, hash, true)
+        : protectedScopeDigest(projectRoot, paths, hash, binding.source_policy);
+}
 export async function protectedSnapshot(authorization) {
     const manifestSource = await readFile(authorization.manifestPath).catch(() => undefined);
     if (manifestSource === undefined)

package/dist/plugin/v2.js

@@ -492,7 +492,7 @@ async function registerV2Hooks(context, hooks) {
             if (record(event.tools)) {
                 const visible = {
                     "dog-operator": ["start_mission", "plan_units", "operator_next", "operator_status", "expand_unit", "review_mission", "complete_mission", "cancel_operator", "reflection"],
-                    "dogs-coordinator": ["plan_units", "operator_next", "operator_status", "expand_unit", "review_mission", "submit_mission"],
+                    "dogs-coordinator": ["plan_units", "operator_next", "operator_status", "expand_unit", "review_mission", "submit_mission", "skip_mission_consultation", "retry_mission_unit", "rescue_mission_unit"],
                     "dog-worker-v010": ["bind_write_gate", "release_write_gate", "operator_status"],
                     "dog-luna-worker-v010": ["bind_write_gate", "release_write_gate", "operator_status"],
                     "dog-reviewer-v010": [], "dog-scout-v010": [], "dog-advisor-v010": [],

package/dist/runtime-mission-assets.js

@@ -13,6 +13,13 @@ For tag observation use git tag --points-at <commit>. For HTTPS downloads use cu
 --write-out '%{http_code} %{size_download}\\n' may print metadata to stdout. Declare all actual outputs.
 Reuse pinned artifacts and successful checks when the request permits and the inputs are unchanged.
 Do not repeat candidate discovery, dependency setup or validation merely because a Worker changed.
+Before launching a detached operation, verify supported options and budget from the CLI/preflight;
+a preview is not the live run. Check the actual state after launch, before relying on its limits.
+Run each declared execution command as the exact native shell input; do not append a tee pipeline,
+redirection or wrapper that was not declared. The host observes that command, not a nearby script or result file.
+Save its output separately when needed. A successful launch only proves the process started;
+use that same run's terminal state and official result for completion, never launch it again
+to repair a missing observation.
 `;
 function controls(profile, names) {
     return names.map(name => `  ${profile.toolPrefix}${name}: true`).join("\n");
@@ -56,6 +63,13 @@ quality threshold and explicit model/budget choice. Follow AGENTS.md and use the
     When the user replaces a version, target, parallelism or other requirement, call start_mission with
     intent: "replace" and the complete current requirements. The host cancels/archives the old run and
     retains spend/results; superseded instructions are history, not additional obligations.
+    If status/start_mission reports mission-source-reconciliation-required, do not dispatch its Task
+    or declare the user's work impossible. Compare the saved requirements with the user's current
+    scope. When they reflect an already requested narrowing/change, call start_mission with intent:
+    "replace" and the exact saved requirements. The host links the cancelled predecessor to the
+    SAME mission before any Worker starts, retains its Coordinator and cumulative spend, and checks
+    old children before preparing a Worker. This is not permission to discard unchanged acceptance:
+    if the scope is uncertain, ask the user which requirements remain instead of inferring a replacement.
 2. Dispatch the returned ${profileAgent(profile, "dog-operator")} task immediately. It owns investigation,
    unit boundaries, Worker/Scout/Advisor/independent Reviewer calls, write-scope extensions and corrections
    within the original request and cumulative budget. Do not investigate or approve each unit at the root.
@@ -81,6 +95,8 @@ results to guide the following units. Do not invent preparation units or plan-ap
 For operations, plan_units.execution names the actual run/grade commands and working directory. Keep
 setup, execution and result collection in the same Worker. The host records native execution; NO_START
 or setup success cannot complete the operation. Reward/score zero is a result, not failure to execute.
+Do not turn a chosen preflight step into a user requirement that the live run's state exists before launch.
+Observe supported flags and budget before launch, then observe the real state immediately after launch.
 Use requirement_ids when splitting multiple requirements across units; a single unit inherits all requirements
 when they are omitted. These are related requirements,
 not claims that a command proves every semantic obligation. Compare the final result yourself.
@@ -135,7 +151,7 @@ permission:
     ${profileAgent(profile, "dog-advisor")}: allow
 tools:
   "sortie_*": false
-${controls(profile, ["plan_units", "operator_next", "operator_status", "expand_unit", "review_mission", "submit_mission"])}
+${controls(profile, ["plan_units", "operator_next", "operator_status", "expand_unit", "review_mission", "submit_mission", "skip_mission_consultation", "retry_mission_unit", "rescue_mission_unit"])}
 ---
 # ${profileAgent(profile, "dog-operator")}
 
@@ -190,6 +206,10 @@ ${profileAgent(profile, "dog-worker")} task verbatim, in foreground. V2 maps sub
 task_id to sessionID. Do not insert model overrides unless the user explicitly selected them.
 
 After each Worker returns, use its actual report and host evidence. Continue pending units with operator_next.
+If plan_units returns mission-source-reconciliation-required, do not retry the same plan. The
+root-only Operator must reconcile the prior cancelled run. Submit status=blocked with the saved
+requirements and exact host diagnostic, then return; do not declare a user-only decision when
+the current request already narrowed the old scope.
 For a needed write-scope addition within the original request, call expand_unit with unit_id, paths and
 reason; the host returns a replacement contract without Operator approval. For a changed approach, formal
 check or reviewer finding, call plan_units with the corrected units and a short observed reason. Replanning
@@ -213,6 +233,22 @@ the header, correct and redispatch this same consultation once before proceeding
 do not investigate runtime policy or bounce the question to Operator. Use your existing evidence
 and ask a bounded question in the user's language; do not send generic exploratory delegations.
 If the user explicitly requested Advisor input before a decision, do not treat it as optional.
+Actual Advisor/Scout dispatches are recorded in operator_status with their trigger/code, bounded question,
+observed model and native outcome. When you considered a concrete decision or missing fact but existing
+evidence makes consultation unnecessary, record the role and concise skip reason with
+${profile.toolPrefix}skip_mission_consultation. Record only meaningful considered skips, not a generic
+"not needed" for each unit. This is observation only: it neither requires consultation nor adds approval.
+
+After a Mission Worker returns a host-classified failed declared validation (not a Task launch error, contract
+defect, cancellation, or unknown outcome), you may call ${profile.toolPrefix}retry_mission_unit once for that unit.
+It reuses the exact scope, acceptance and validation under the ordinary cumulative budget. If that same normal
+remediation then fails the same declared validation and native termination/writer release are confirmed, you may
+call ${profile.toolPrefix}rescue_mission_unit once. The host records the Astra model actually selected, or a
+specific non_rescue reason; do not expose or substitute the legacy sortie_execute_terminal_rescue capability.
+Rescue is still a normal current-Mission Worker dispatch: its declared validation must pass, then the existing
+independent review, final evidence check and root complete_mission acceptance remain mandatory. A Worker return
+or rescue dispatch alone is never success. On non_rescue, continue the ordinary correction/replan within the same
+requirements and remaining budget; never bypass a failure class or create another run to reset spend.
 
 After formal validation, call review_mission with risk_tags and one concise implementation/test trace per
 requirement. For changed failure behavior, connect the operation and concrete input to the contract-derived
@@ -228,6 +264,8 @@ it with sharper traces and evidence: [{path, offset, limit}] from the existing o
   Declared external input/output excerpts remain available. The host caps evidence-only reviews; at its limit,
 review is closed with gaps, but ready still requires the requested operation/result to be complete.
 Running an existing procedure alone is not a public-logic source change; use the low-risk skip where applicable.
+Evaluating an unchanged published package is not a release or source edit: use the native execution,
+result and hash records rather than adding an independent source-review round solely for its label.
 Preserve candidate lineage and independence; your own opinion or Worker PASS is not independent review.
 
 Call submit_mission only for: ready (complete candidate with evidence/review), needs-decision (only the user

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sortie-dogs",
-  "version": "0.12.19",
+  "version": "0.12.21",
   "description": "Bounded agent harness and validated orchestration loop plugin for OpenCode",
   "keywords": [
     "opencode",