cadet-agent 0.33.0 → 0.33.1

package/README.md

@@ -168,6 +168,10 @@ Hard gates are enforced at every phase transition. The agent reads `.cadet/state
 | review → validation | `codeReviewCompleted`, `securityReviewPassed`, `acceptanceCriteriaValidated` |
 | validation → closed | `designArtifactSyncConfirmed` |
 
+**`closed` is end-of-epic, not per-story.** `validation → closed` is taken only when no stories remain (`NEXT_STORY → no → CLOSED` above). When an epic still has stories, the next story re-enters from `validation → implementation` (`NEXT_STORY → yes → IMPL`). Do not close a story individually: `closed` is terminal, and there is no transition out of it.
+
+The full set of legal transitions is the three gated rows above **plus** the ungated forward edges (classification, planning progression, `story-breakdown → implementation`, and the `validation → implementation` next-story loop). Any transition outside that set is rejected with a named reason.
+
 ### Harness
 
 Gates are backed by **evidence**, not assertion. Each claimed gate must have a fresh, non-superseded evidence record bound to the current work item, input tree hash, and acceptance criteria. The harness also bounds context, tokens, tool calls, retries, wall-clock time, cost, and archive sizes — and those bounds are enforced, not advisory.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cadet-agent",
-  "version": "0.33.0",
+  "version": "0.33.1",
   "description": "Cross-IDE agent framework for Unity/C# game-development — one-command install",
   "type": "module",
   "bin": {

package/src/harness/state.mjs

@@ -718,8 +718,15 @@ const UNGATED_FORWARD_EDGES = Object.freeze([
   ['architectureComplete', 'story-breakdown'],
   ['spikes', 'story-breakdown'],
   ['story-breakdown', 'implementation'],
-  // Re-entering work for a new story/epic from a review/vallidation outcome.
-  ['story-breakdown', 'story-breakdown'],
+  // Next-story loop. The workflow is
+  //   VALIDATE -->|"gate: designArtifactSyncConfirmed"| NEXT_STORY
+  //   NEXT_STORY -->|"yes"| IMPL
+  //   NEXT_STORY -->|"no"| CLOSED
+  // so the next story in an epic re-enters implementation from `validation`.
+  // `closed` stays terminal — it means the epic/plan is finished
+  // (Resume: "All work is complete for the current epic(s)") — and is
+  // deliberately NOT an escape hatch for starting the next story.
+  ['validation', 'implementation'],
 ]);
 
 /** Is `from → to` one of the declared ungated forward edges? */