yadflow 3.9.3 → 3.10.0

package/skills/yad-docs/templates/app/package.json

@@ -13,16 +13,16 @@
     "framer-motion": "^12.34.4",
     "react": "^19.2.0",
     "react-dom": "^19.2.0",
-    "react-router-dom": "^7.13.1",
+    "react-router-dom": "^7.18.1",
     "zustand": "^5.0.11"
   },
   "devDependencies": {
     "@eslint/js": "^9.39.1",
-    "@tailwindcss/vite": "^4.2.1",
+    "@tailwindcss/vite": "^4.3.2",
     "@types/node": "^24.10.1",
     "@types/react": "^19.2.7",
     "@types/react-dom": "^19.2.3",
-    "@vitejs/plugin-react": "^5.1.1",
+    "@vitejs/plugin-react": "^5.2.0",
     "eslint": "^9.39.1",
     "eslint-plugin-react-hooks": "^7.0.1",
     "eslint-plugin-react-refresh": "^0.4.24",
@@ -30,6 +30,6 @@
     "tailwindcss": "^4.2.1",
     "typescript": "~5.9.3",
     "typescript-eslint": "^8.48.0",
-    "vite": "^7.3.1"
+    "vite": "^8.1.3"
   }
 }

package/skills/yad-epic/SKILL.md

@@ -156,6 +156,12 @@ Notes:
   and an empty comments ledger `{project-root}/epics/EP-<slug>/.sdlc/comments.json`, each containing
   `[]`, and the `reviews/` directory. (`comments.json` is the machine-readable counterpart to the
   `reviews/*--comments.md` markdown — `yad-review-gate` appends to it on every `comment`.)
+- **No UI?** Seed the chain **as-is** (always include the two `ui-design` steps). If this epic has no
+  user-facing surface (a backend/API service, data pipeline, infra), the `ui-design` step is optional
+  and can be marked N/A now with `yad skip EP-<slug> ui-design --reason "<why>"` — it stays visible,
+  short-circuits its gate, and advances straight to `stories` when architecture is approved. It is
+  reversible with `--undo` until the stories review opens. Don't hand-edit the seed to drop the steps;
+  the skip is the single, auditable mechanism (see `references/state-schema.md` → "ui-design is optional").
 
 ### Step 5b — Advance the authoring step — analysis-ran only
 *(Only when analysis ran — `state.json` already exists from `yad-analysis`.)*

package/skills/yad-epic/references/state-schema.md

@@ -37,6 +37,32 @@ existing `state.json` and does **not** re-seed.
 `analysis-review`, `ui-design-review`, and `test-cases-review` carry no `risk_tags` (base rule:
 owner + 1 reviewer).
 
+### `ui-design` is optional (skippable)
+
+The `ui-design` step (and its `ui-design-review` gate) is **optional** for an epic with no
+user-facing surface — a backend/API service, a data pipeline, infra work. Unlike `analysis` (which is
+optional by being **omitted** from the chain at seed time), `ui-design` is **always seeded** and then
+**marked N/A in place** so the skip stays visible and auditable. The single mechanism is
+`yad skip EP-<slug> ui-design --reason "<why>"` (reverse with `--undo`), usable at epic-authoring time
+or any point **up to authoring the `ui-design` step** — the skip is refused once its review gate has
+opened (the UI work is committed by then) or once `stories` has started. `--undo` is allowed until the
+`stories` review opens.
+
+A skipped step gets four extra fields and is pre-marked `done`:
+
+| Field | Values | Meaning |
+|-------|--------|---------|
+| `skipped` | `true` | This step is N/A for this epic; pre-marked `done`, short-circuited by `gatePredicate` (`rule: "skipped"`) so no review is required. |
+| `skipReason` | string | Why it was skipped (e.g. "backend-only service, no UI"). |
+| `skippedBy` | login/name or `null` | Who marked it N/A (best-effort, from the roster/git identity). |
+| `skippedAt` | `YYYY-MM-DD` or `null` | When it was marked N/A. |
+
+Both the `ui-design` **and** `ui-design-review` entries carry these fields. `advanceState` steps over
+any `skipped` step, so approving `architecture-review` on a UI-less epic lands directly on `stories`;
+`preconditionsMet` treats the pre-`done` steps as satisfied. `unskipStep` (via `yad skip … --undo`)
+strips the fields and restores the chain, refused once `stories-review` has opened. Only `ui-design` is
+skippable today (engine `SKIPPABLE_STEPS`).
+
 ### `test-cases` is a parallel, non-blocking track
 
 `test-cases` (and its `test-cases-review` gate) sit in `steps[]` after `stories-review`, but they are a

package/skills/yad-status/SKILL.md

@@ -46,6 +46,13 @@ Print, in this order:
    passes and runs alongside the build half, so when `currentStep` is `ready-for-build` the `test-cases`
    step may still be `in_progress`/`in_review` — show its status, and note "parallel" so it is clear it
    does not gate the build. Always render exactly the steps present in `steps[]`.
+   - **Skipped (N/A) steps:** the optional `ui-design` step may be marked N/A for an epic with no
+     user-facing surface. **Both** the `ui-design` author step **and** its `ui-design-review` gate stay
+     in `steps[]`, each carrying `skipped: true`, `status: "done"`, and a `skipReason`. Render **each**
+     as `<id> — SKIPPED (N/A: <skipReason>)` (with `skippedBy`/`skippedAt` if present) instead of the
+     plain status, so the deliberate skip and its reason are visible and the gate does not appear to
+     vanish. The chain then reads `… architecture-review → ui-design (N/A) → ui-design-review (N/A) →
+     stories → …`; the review gate never needs approvals.
 3. **Active gate** — for the `currentStep` (if it is a `review+approve` step), compute and show:
    - the reviewer rule in force — **base** (`owner + 1 reviewer`), **escalated** (list the required
      domains), or **per-repo** for `stories-review` (list each repo needing sign-off),

package/skills/yad-stories/SKILL.md

@@ -45,6 +45,11 @@ Read `epic.md` (scope, acceptance signals, `repos`), `architecture.md` (componen
 `contract.md` (the shared surface stories must honour), and `ui-design.md` (screens/flows). Stories
 must collectively satisfy the epic's acceptance signals and stay within the contract surface.
 
+- **UI-optional-safe:** `ui-design.md` may be absent — the `ui-design` step is optional and can be
+  marked N/A for an epic with no user-facing surface (state.json shows it `skipped`). When there is no
+  UI design, proceed without UI screens; the epic's acceptance signals + contract remain the source of
+  truth for the stories.
+
 ### Step 2b — Load existing-code context (make the brain code-aware)
 Read the registry `{project-root}/.sdlc/repos.json` (`config.yaml` `code_context`). For **each repo in
 `epic.repos`**, load the code-map `{project-root}/.sdlc/code-context/<repo>/code-map.md` so each story's

package/skills/yad-test-cases/SKILL.md

@@ -60,6 +60,10 @@ Read `epic.md` (user-level acceptance signals, scope), `architecture.md` (flows,
 **all** approved `stories/EP-<slug>-S0N.md`. Each story's **acceptance criteria are the source of truth**
 for the cases — the test cases must collectively verify every story's criteria.
 
+- **UI-optional-safe:** `ui-design.md` may be absent — the `ui-design` step is optional and can be
+  marked N/A for a UI-less epic (state.json shows it `skipped`). When there is no UI design, there are
+  simply no screens to exercise; the stories' acceptance criteria remain the source of truth.
+
 ### Step 2b — Load existing-code context (make the brain code-aware)
 Read the registry `{project-root}/.sdlc/repos.json` (`config.yaml` `code_context`). For **each repo in
 `epic.repos`**, load the code-map `{project-root}/.sdlc/code-context/<repo>/code-map.md` so the

package/skills/yad-ui/SKILL.md

@@ -42,6 +42,19 @@ it passes.
 This passes when `ui-design` is the next runnable step per the state sequence — every prior step
 (through the architecture review) is `done` and `ui-design` is not already `done`.
 
+**This step is OPTIONAL.** If the epic has no user-facing surface (a backend/API service, a data
+pipeline, infra work), it does not need a UI design. Two signals to watch for:
+
+- **Already skipped:** if `ui-design.status` is `done` with `skipped: true` in `state.json` (the
+  `--check` above will report `ui-design is already done`), the step was marked N/A — **STOP**, there
+  is nothing to author; point the user at `yad next EP-<slug>` (the next step is `stories`).
+- **Should be skipped:** if you reach this step and the epic clearly produces no screens, do **not**
+  invent a hollow UI artifact. Offer to mark it N/A instead:
+  `yad skip EP-<slug> ui-design --reason "<why, e.g. backend-only service>"`. That pre-marks both the
+  `ui-design` and `ui-design-review` steps `done` (recorded reason + actor), short-circuits the review
+  gate, and advances to `stories`. It is reversible with `yad skip EP-<slug> ui-design --undo` until the
+  stories review opens. See `../yad-epic/references/state-schema.md` → "ui-design is optional".
+
 ### Step 1b — Open the authoring branch
 Open the UI authoring branch `ui-design/EP-<slug>` per the shared procedure
 (`../yad-epic/references/state-schema.md` → "Authoring branches"): git-safe (skip with a note