@tacuchi/agent-workflow-cli 22.0.1 → 22.2.0

package/skills/w/context/MANIFEST.json

@@ -32,6 +32,8 @@
     "quick.deliverable-is-analysis": "what the task produces is an analysis or a design, so its criterion is a rubric a person ratifies",
     "spec.functional-ambiguity": "a functional ambiguity with two readings that would change what gets built is blocking this spec",
     "spec.solution-space-unexplored": "a trigger of the ideation gate fires: the spec settled on its first idea and the alternatives would change the outcome",
+    "spec.escalation-adopted": "this refine consumed the escalation package an execution handed over, instead of re-deriving its diagnosis",
+    "spec.escalation-absent": "no escalation package reached this refine, so it starts from the spec alone",
     "spec.independent-outcomes": "the prompt holds outcomes each worth delivering on its own",
     "spec.enumerated-features": "the prompt enumerates distinct features explicitly",
     "spec.distinct-moments": "the parts are requested for different moments or in a stated order",
@@ -50,6 +52,14 @@
     "plan.entry-gap-structural": "phases, contracts or journey are missing, or temporary behavior leaves its boundary undeclared",
     "plan.deviation-structural": "the change that appeared while implementing touches a contract, the participating components, the phase order or the simulation boundary",
     "plan.deviation-functional": "the change that appeared while implementing touches the expected result, the scope, a business rule or an acceptance criterion",
+    "plan.deviation-composable": "the change keeps the functional lineage and can be reconciled forward as a durable decision note instead of returning to a refine",
+    "plan.deviation-escalation": "what was found does not compose against this lineage and belongs to a spec of its own",
+    "plan.closure-lineage": "the divergence stays inside the same functional lineage: it amends how the promise is met, not who promised it",
+    "plan.closure-intent": "the intent behind the divergence is settled, so nothing further has to be elicited before deciding",
+    "plan.closure-impact": "the transitive impact can be enumerated: every consumer the decision reaches is nameable",
+    "plan.closure-recoverable": "the result can be sealed and recovered: an identical retry gives the same outcome and a failure leaves nothing half-written",
+    "plan.escalation-adopted": "this refine consumed the escalation package an execution handed over, instead of re-deriving its diagnosis",
+    "plan.escalation-absent": "no escalation package reached this refine, so it starts from the document alone",
     "chassis.context-pressure": "a fresh reader would need the CHECKPOINT to continue this run",
     "plan.tasks-to-mark": "at least one task of the batch finished its local work and its checkbox is still open",
     "plan.plan-closable": "every phase of the plan will be validated once this batch closes, so the plan can be sealed done",

package/skills/w/loops/plan-exec-loop/LOOP.md

@@ -139,22 +139,47 @@ reconciliation** in `CHECKPOINT`, never reported as published.
 
 ## Deviation gate
 
-Execution resolves **detail**, never **redesign**. This gate lives **only** in this loop — the chassis does not carry it.
+Execution resolves **detail**, never **redesign** — and between those two there is a third thing: a
+divergence that keeps the functional lineage and can be reconciled **forward**.
+This gate lives **only** in this loop — the chassis does not carry it. It has **four** exits, and the
+run stops at it: declaring a deviation no longer carries on to the commit by itself.
 
-- **Local decision — `plan-exec` continues.** A class or method name; a local helper; internal code layout; imports; a choice between equivalent APIs already allowed; a fix needed to compile; a minor refactor that does not move the journey; one extra focused test for a risk found while implementing. Recorded in `DECISION` only when it is not obvious.
+- **Local decision — `plan-exec` continues.** A class or method name; a local helper; internal code layout; imports; a choice between equivalent APIs already allowed; a fix needed to compile; a minor refactor that does not move the journey; one extra focused test for a risk found while implementing. Declares **no signal** — the gate is not raised — and is recorded in `DECISION` only when it is not obvious.
+- **Composable decision — a note is registered and execution continues.** The change amends how the promise is met without changing who promised it. It is the only exit that writes a **decision note**, and it is available **only** when all four closures hold (below). The spec and the plan stay byte-exact.
 - **Structural deviation — stop and return to `plan-refine`.** Stop when the change touches: an input or output; an observable state; a relevant endpoint or public contract; the set of participating components or repositories; the phase order; the simulation boundary; the integration strategy; a material dependency; the main persistence mechanism; a phase already `validada`; the evidence needed to demonstrate the result. A decision that substantially expands or shrinks the work counts too.
 - **Functional change — return to `spec-refine`.** Stop when the change touches: the expected result; the functional scope; a business rule; an acceptance criterion; the actor or consumer; or a product decision.
 
-On either return path: `CHECKPOINT` records the state reached and the trigger, the phase keeps the state it really has (`en ejecución` or `bloqueada`, never `validada`), the working tree is left committed or acknowledged (Delta 2), and the human is told through a structured-choice which command to run. Resuming later over the corrected plan is a normal `create_or_resume`.
-
-| Finding | `plan-exec` | `plan-refine` | `spec-refine` |
-|---|---|---|---|
-| Rename a helper · internal implementation · test for a local risk | continues | — | — |
-| Change the public DTO | stops | yes | yes, if behavior changes |
-| Add a participating repository | stops | yes | — |
-| Move the simulation to another boundary | stops | yes | — |
-| Change the phase order | stops | yes | — |
-| Add a functional rule · change an acceptance criterion | stops | — | yes |
+**Eligibility is closure, never size.** The composable exit opens only when the four close: the
+divergence stays in the **same functional lineage**; its **intent is settled**, so nothing further has
+to be elicited; its **transitive impact can be enumerated**, every consumer nameable; and its
+**result can be sealed and recovered**, so an identical retry gives the same outcome and a failure
+leaves nothing half-written. Counts — of criteria, phases or repositories — are reported and decide
+nothing: a divergence touching one criterion that closes three of the four is not composable, and one
+touching nine that closes all four is.
+
+> **Which exit the run takes is the person's, and which are offered is not this document's call:** the deterministic steps below are decided by the CLI (`aw flow advance`), not by this document. Recognizing the divergence and closing its eligibility are judgment; counting the closures and raising the choice are a rule.
+
+On any exit that leaves the phase: `CHECKPOINT` records the state reached and the trigger, the phase
+keeps the state it really has (`en ejecución` or `bloqueada`, never `validada`), and the working tree
+is left committed or acknowledged (Delta 2). On the two return paths and on an escalation, the
+**escalation package** travels with it — diagnosis, decisions already taken, evidence gathered and the
+return point — and the destination **declares that it consumed it**, so returning never costs redoing
+the analysis execution had already done. Resuming later over the corrected plan is a normal
+`create_or_resume`.
+
+**More than one divergence may appear in a run, and every one is kept.** A later recognition never
+erases an earlier one.
+
+| Finding | `plan-exec` | note | `plan-refine` | `spec-refine` |
+|---|---|---|---|---|
+| Rename a helper · internal implementation · test for a local risk | continues | — | — | — |
+| Same promise, different route, four closures held | continues | yes | — | — |
+| Change the public DTO | stops | — | yes | yes, if behavior changes |
+| Add a participating repository | stops | — | yes | — |
+| Move the simulation to another boundary | stops | — | yes | — |
+| Change the phase order | stops | — | yes | — |
+| Add a functional rule · change an acceptance criterion | stops | — | — | yes |
+| Does not compose against this lineage at all | stops | — | — | a spec of its own |
 
 ## Delta 2 — Git policy: **safe branch + proposed commits**