yadflow 3.18.0 → 3.19.0-next.2

package/skills/yad-discovery/SKILL.md

@@ -10,12 +10,12 @@ requirement-gathering for the whole product — under the reserved `EP-discovery
 hand off to `yad-review-gate`. The output `roadmap.md` is the menu of features; each feature is later
 taken into the normal `yad-epic` flow, which reads the roadmap for project context.
 
-This is a **front state**: human-authored with AI assist and **never auto-advances**. It runs **once
+This is a **Shape step**: human-authored with AI assist and **never auto-advances**. It runs **once
 per project** and is **optional** — a team that already knows what to build can skip it and start at
 `yad-epic`. It supports **both greenfield and brownfield**, and produces a **competitor study in both**.
 
 This skill enforces the build plan's core rules: all state lives in files; IDs are engine-assigned
-(the reserved `EP-discovery`, never a typed feature slug); front steps are locked to `human_approve`.
+(the reserved `EP-discovery`, never a typed feature slug); Shape steps are locked to `human_approve`.
 
 ## Conventions
 
@@ -63,7 +63,7 @@ roadmap extends the real system rather than re-proposing it.
 Open the discovery authoring branch `discovery/EP-discovery` per the shared procedure
 (`../yad-epic/references/state-schema.md` → "Authoring branches"): git-safe (skip with a note if
 `{project-root}` is not a git work tree), check out the branch if it exists, else create it from the
-hub's default branch. Author and commit the discovery set on it. Distinct from the bridge's
+hub's default branch. Author and commit the discovery set on it. Distinct from the verified ledger's
 `review/EP-discovery/discovery` branch.
 
 ### Step 4 — Write the discovery set
@@ -113,7 +113,7 @@ Notes:
 - Also create an empty approvals ledger `.sdlc/approvals.json` and comments ledger
   `.sdlc/comments.json`, each containing `[]`, and the `reviews/` directory.
 - Commit the seed on the `discovery/EP-discovery` branch, and cut `review/EP-discovery/discovery` from
-  it so the **first** review PR/MR carries the ledger to the default branch. In bridge mode
+  it so the **first** review PR/MR carries the ledger to the default branch. In verified mode
   `ledger-guard` exempts a new epic's ledger (creation, not mutation, #162); every later change to it
   is CI's. See `../yad-epic/references/state-schema.md`, "Authoring branches".
 
@@ -121,11 +121,11 @@ Notes:
 Report: the path to the discovery set, and that the next action is **review** via `yad-review-gate`
 (base rule: owner + 1 reviewer) on the virtual artifact `discovery/`. **Never mark discovery-review
 approved here** — only real reviewers do that through the gate. When the discovery gate passes, the
-state moves to the `discovery-done` sentinel (not `ready-for-build` — discovery has no build half); the
+state moves to the `discovery-done` sentinel (not `ready-for-build` — discovery has no Build); the
 roadmap is now the input that each `yad-epic` reads (its "Step 2c — read the roadmap"). When the hub
 has a platform, the gate opens a review PR on the hub (via `yad-hub-bridge`) and
 `yad-review-gate action: sync` pulls platform approvals/comments into the ledger; otherwise the review
-is recorded file-only.
+is recorded local.
 
 ## Reference
 - Discovery artifact templates + the 2-step state shape: `references/discovery-schema.md`.

package/skills/yad-discovery/references/discovery-schema.md

@@ -29,7 +29,7 @@ object and the 2-step chain.
   `yad gate open` / `yad gate sync` warn with the missing filenames. Write all six (in greenfield,
   `current-state.md` is a short clean-slate note) before handing off to the gate.
 - On approval the gate sets `currentStep: "discovery-done"` (a terminal sentinel — discovery has **no**
-  build half, so it never becomes `ready-for-build`).
+  Build, so it never becomes `ready-for-build`).
 - The discovery files (relative to the epic dir) the gate commits on the review branch and re-hashes at
   merge are: `market-research.md`, `competitor-analysis.md`, `current-state.md`, `feasibility.md`,
   `requirements.md`, `roadmap.md` (the `DISCOVERY_FILES` list).

package/skills/yad-docs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: yad-docs
-description: 'Generates the per-epic interactive documentation site — a vendored React/Vite/Tailwind SPA with an animated flow canvas and role-based stakeholder doc pages — from the epic''s approved artifacts (epic, architecture, the locked contract, UI design, stories, code-context, test cases). Themes it from the design tokens, wires the docs.json base path, and drives `yad docs build/deploy` to publish to Pages (or build-only when no target). This is an OUTPUT ENRICHMENT, never a gated front state: it never mutates state.json steps, approvals, or the contract lock. Use when the user says "generate the docs site", "build the interactive docs", or "deploy the epic docs".'
+description: 'Generates the per-epic interactive documentation site — a vendored React/Vite/Tailwind SPA with an animated flow canvas and role-based stakeholder doc pages — from the epic''s approved artifacts (epic, architecture, the locked contract, UI design, stories, code-context, test cases). Themes it from the design tokens, wires the docs.json base path, and drives `yad docs build/deploy` to publish to Pages (or build-only when no target). This is an OUTPUT ENRICHMENT, never a gated Shape step: it never mutates state.json steps, approvals, or the contract lock. Use when the user says "generate the docs site", "build the interactive docs", or "deploy the epic docs".'
 ---
 
 # SDLC — Author the Interactive Docs Site (per-epic, output enrichment)
@@ -12,7 +12,7 @@ stakeholder doc pages** (each lens → a set of doc sections). The shell is gene
 generated entirely into `src/data/*.ts` and the theme into `src/index.css`.
 
 This is an **output enrichment**, exactly like `design-links.json` / `test-links.json` — **NOT a gated
-front state.** It **never** mutates `.sdlc/state.json` `steps[]`, `approvals.json`, or
+Shape step.** It **never** mutates `.sdlc/state.json` `steps[]`, `approvals.json`, or
 `contract-lock.json`, and it never adds a `state.json` step. It reads the *approved* shape and renders
 it; it never decides approval. When a docs target is connected (`yad-connect-docs` → `.sdlc/docs.json`)
 the site is built + deployed; when none is, it is npm-built to a local `dist/` (build-only).
@@ -152,7 +152,7 @@ the default-theme degrade), the **deploy URL** or "build-only", and the **stalen
 - The connected docs target + base-path resolution: `../yad-connect-docs/SKILL.md`.
 - The design tokens this themes from: `../yad-connect-design/SKILL.md`.
 - The code-context the data enriches: `../yad-connect-repos/SKILL.md`.
-- The authoring pattern (front-state author that writes link artifacts without gating):
+- The authoring pattern (Shape step author that writes link artifacts without gating):
   `../yad-ui/SKILL.md`.
 - State schema + the "Authoring branches" procedure: `../yad-epic/references/state-schema.md`.
 - The project overview site + the staleness/CI reconciler: `../yad-docs-overview/SKILL.md`,

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

@@ -11,7 +11,7 @@
         "framer-motion": "^12.34.4",
         "react": "^19.2.0",
         "react-dom": "^19.2.0",
-        "react-router-dom": "^7.18.1",
+        "react-router-dom": "^7.18.2",
         "zustand": "^5.0.11"
       },
       "devDependencies": {
@@ -505,29 +505,43 @@
       }
     },
     "node_modules/@humanfs/core": {
-      "version": "0.19.1",
-      "resolved": "https://registry.npmjs.org/@humanfs/core/-/core-0.19.1.tgz",
-      "integrity": "sha512-5DyQ4+1JEUzejeK1JGICcideyfUbGixgS9jNgex5nqkW+cY7WZhxBigmieN5Qnw9ZosSNVC9KQKyb+GUaGyKUA==",
+      "version": "0.19.2",
+      "resolved": "https://registry.npmjs.org/@humanfs/core/-/core-0.19.2.tgz",
+      "integrity": "sha512-UhXNm+CFMWcbChXywFwkmhqjs3PRCmcSa/hfBgLIb7oQ5HNb1wS0icWsGtSAUNgefHeI+eBrA8I1fxmbHsGdvA==",
       "dev": true,
       "license": "Apache-2.0",
+      "dependencies": {
+        "@humanfs/types": "^0.15.0"
+      },
       "engines": {
         "node": ">=18.18.0"
       }
     },
     "node_modules/@humanfs/node": {
-      "version": "0.16.7",
-      "resolved": "https://registry.npmjs.org/@humanfs/node/-/node-0.16.7.tgz",
-      "integrity": "sha512-/zUx+yOsIrG4Y43Eh2peDeKCxlRt/gET6aHfaKpuq267qXdYDFViVHfMaLyygZOnl0kGWxFIgsBy8QFuTLUXEQ==",
+      "version": "0.16.8",
+      "resolved": "https://registry.npmjs.org/@humanfs/node/-/node-0.16.8.tgz",
+      "integrity": "sha512-gE1eQNZ3R++kTzFUpdGlpmy8kDZD/MLyHqDwqjkVQI0JMdI1D51sy1H958PNXYkM2rAac7e5/CnIKZrHtPh3BQ==",
       "dev": true,
       "license": "Apache-2.0",
       "dependencies": {
-        "@humanfs/core": "^0.19.1",
+        "@humanfs/core": "^0.19.2",
+        "@humanfs/types": "^0.15.0",
         "@humanwhocodes/retry": "^0.4.0"
       },
       "engines": {
         "node": ">=18.18.0"
       }
     },
+    "node_modules/@humanfs/types": {
+      "version": "0.15.0",
+      "resolved": "https://registry.npmjs.org/@humanfs/types/-/types-0.15.0.tgz",
+      "integrity": "sha512-ZZ1w0aoQkwuUuC7Yf+7sdeaNfqQiiLcSRbfI08oAxqLtpXQr9AIVX7Ay7HLDuiLYAaFPu8oBYNq/QIi9URHJ3Q==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "engines": {
+        "node": ">=18.18.0"
+      }
+    },
     "node_modules/@humanwhocodes/module-importer": {
       "version": "1.0.1",
       "resolved": "https://registry.npmjs.org/@humanwhocodes/module-importer/-/module-importer-1.0.1.tgz",
@@ -1470,9 +1484,9 @@
       }
     },
     "node_modules/@typescript-eslint/typescript-estree/node_modules/brace-expansion": {
-      "version": "5.0.8",
-      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-5.0.8.tgz",
-      "integrity": "sha512-JZyDyq3D4AUifKTPOB7DELf6XsB3WdPuNxCtob1vFXPsSXhdAiHBWJ/tJ8HAc9aH84BK+5JFZLNkJKx3G9kzQg==",
+      "version": "5.0.9",
+      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-5.0.9.tgz",
+      "integrity": "sha512-ScQ4IuvIEF1TMlP7Zt+vjJ//9zlPb2SDcxWxM3bk8s6t6GGdJ7KO1dCcTidOPJKePW30LE/2cT7wCyPho9/Wxg==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
@@ -1658,9 +1672,9 @@
       "license": "MIT"
     },
     "node_modules/baseline-browser-mapping": {
-      "version": "2.10.42",
-      "resolved": "https://registry.npmjs.org/baseline-browser-mapping/-/baseline-browser-mapping-2.10.42.tgz",
-      "integrity": "sha512-c/jurFrDLyui7o1J86yLkRu4LMsTYcBohveus7/I2Hzdn9KIP2bdJPTue/lR1KH46enoPbD77GKeSYNdyPoD3Q==",
+      "version": "2.11.21",
+      "resolved": "https://registry.npmjs.org/baseline-browser-mapping/-/baseline-browser-mapping-2.11.21.tgz",
+      "integrity": "sha512-uh8vpY/1/YyFkunIDFH/12p7/7VdPKA1hejMVEbdkEaWnUz0Hesvx5EbiU6XxjyHZIOju+ZMbQJkRh+es3/spQ==",
       "dev": true,
       "license": "Apache-2.0",
       "bin": {
@@ -1671,9 +1685,9 @@
       }
     },
     "node_modules/brace-expansion": {
-      "version": "1.1.16",
-      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.16.tgz",
-      "integrity": "sha512-IDw48K2/2kRkg9LdJxurvq3lV3aBgq0REY89duEqFRthjlPdXHKMj7EnQOXVckxzgisinf3nHfrcE2FufFLXMw==",
+      "version": "1.1.18",
+      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.18.tgz",
+      "integrity": "sha512-Edep/X9fGqVNmzKBVsDYIOtD+z1tuezV70LBjdCst9Tqu76lsnvRiZ6oTic1n+/BIwX6QDGAO94PN4N2SADvtw==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
@@ -1682,9 +1696,9 @@
       }
     },
     "node_modules/browserslist": {
-      "version": "4.28.5",
-      "resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.28.5.tgz",
-      "integrity": "sha512-Cu2E6QejHWzuDMTkuwgpABFgDfZrXLQq5V13YOACZx4mFAG4IwGTbTfHPMr4WtxlHoXSM8FIuRwYYCz5XiabaQ==",
+      "version": "4.28.9",
+      "resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.28.9.tgz",
+      "integrity": "sha512-EWazOblFYUvlGZcfGhPUPmYh3nikUxBVb+y9MJun5f3hBi812X+8MSQTujLBtgK3cf51fJWbWfOjyeO954d+Eg==",
       "dev": true,
       "funding": [
         {
@@ -1702,11 +1716,11 @@
       ],
       "license": "MIT",
       "dependencies": {
-        "baseline-browser-mapping": "^2.10.42",
-        "caniuse-lite": "^1.0.30001800",
-        "electron-to-chromium": "^1.5.387",
-        "node-releases": "^2.0.50",
-        "update-browserslist-db": "^1.2.3"
+        "baseline-browser-mapping": "^2.11.20",
+        "caniuse-lite": "^1.0.30001810",
+        "electron-to-chromium": "^1.5.420",
+        "node-releases": "^2.0.54",
+        "update-browserslist-db": "^1.3.2"
       },
       "bin": {
         "browserslist": "cli.js"
@@ -1726,9 +1740,9 @@
       }
     },
     "node_modules/caniuse-lite": {
-      "version": "1.0.30001802",
-      "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001802.tgz",
-      "integrity": "sha512-vmv8ub2xwTNmljSKf82mtCk5JH7hC+YgzLj3P5zotvA0tPQ9016tdNNOG8WRca1IxOnhSsivB+J0z5FeE5LOUw==",
+      "version": "1.0.30001810",
+      "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001810.tgz",
+      "integrity": "sha512-TITQPUkaz+aVk5GL6NhOdwk1aEaNTSDPsGFWrTuhKGtjTF70jL/Oht2W4c6rXUe5fu7Ie19VIahAXHIIiWWNeg==",
       "dev": true,
       "funding": [
         {
@@ -1868,9 +1882,9 @@
       }
     },
     "node_modules/electron-to-chromium": {
-      "version": "1.5.388",
-      "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.388.tgz",
-      "integrity": "sha512-Pl/aJaqOOxYxda3vcx1IKSJimwYXHDkEnGn0F+kG2EE68dDtx2uCinaS+Vih8Z91B9t8CSAbiF/HKyWcnXjhzw==",
+      "version": "1.5.422",
+      "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.422.tgz",
+      "integrity": "sha512-UvA/32XqrLDdZSn7Jllo1AYNcWji/G0d5M0GTViE7KoGBiMunw3a34Sb2KO4ZZyrSEhqsxFoVhWWJshdyfKqJA==",
       "dev": true,
       "license": "ISC"
     },
@@ -2815,9 +2829,9 @@
       "license": "MIT"
     },
     "node_modules/nanoid": {
-      "version": "3.3.15",
-      "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.15.tgz",
-      "integrity": "sha512-y7Wygv/7mEOvxTuEQDB8StXdMRBWf1kR/tlhAzBRUFkB2jfcLOAxO/SHmOO2zgz1pVgK29/kyupn059/bCHdjA==",
+      "version": "3.3.18",
+      "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.18.tgz",
+      "integrity": "sha512-DTg4MJbGMWkfi6VZFdNt2/caMbQy4Ou+Op/hJQvGEWcnVfoA1QA+xzRKAzw9jD6+GVOOeYr/mIcuDSdug6F6+w==",
       "dev": true,
       "funding": [
         {
@@ -2841,9 +2855,9 @@
       "license": "MIT"
     },
     "node_modules/node-releases": {
-      "version": "2.0.50",
-      "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.50.tgz",
-      "integrity": "sha512-J6l92tKHX6w8Jy5nO1Vuc01NoIiRGi/d6qBKVxh+IQ8Cr3b6HbVNfKiF8ZpFKufTwpwxMmce2W3iQZ861ZRyTg==",
+      "version": "2.0.54",
+      "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.54.tgz",
+      "integrity": "sha512-YHs7BmmcsdAI5Ozuf8JZo6PT0mv2GIWC9vMfvUC3dp65M8hn7Ux8CPL+2oBI7juNuj9d0ndhTcznq2ODBps9cQ==",
       "dev": true,
       "license": "MIT",
       "engines": {
@@ -2954,9 +2968,9 @@
       }
     },
     "node_modules/postcss": {
-      "version": "8.5.16",
-      "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.16.tgz",
-      "integrity": "sha512-vuwillviilfKZsg0VGj5R/YwwcHx4SLsIOI/7K6mQkWx+l5cUHTjj5g0AasTBcyXsbfTgrwsUNmVUb5xVwyPwg==",
+      "version": "8.5.28",
+      "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.28.tgz",
+      "integrity": "sha512-RRuzqDtt5Y9h3quz5hWhK+TPnsmVs6WwSU6LkJMeY4HstUEDuYTG8UJSdawMRzmzAtV+KEoG8N3Qg2qLy5vM/A==",
       "dev": true,
       "funding": [
         {
@@ -2974,7 +2988,7 @@
       ],
       "license": "MIT",
       "dependencies": {
-        "nanoid": "^3.3.12",
+        "nanoid": "^3.3.18",
         "picocolors": "^1.1.1",
         "source-map-js": "^1.2.1"
       },
@@ -3034,9 +3048,9 @@
       }
     },
     "node_modules/react-router": {
-      "version": "7.18.1",
-      "resolved": "https://registry.npmjs.org/react-router/-/react-router-7.18.1.tgz",
-      "integrity": "sha512-GDLgg3i3uM0aeJO3Fm+TCS+sDQ7gu12T6x0qdTEzcwqEfleci7JwugVNIF3U//0FWKnJT7ptG+20B2jfDqnZAg==",
+      "version": "7.18.3",
+      "resolved": "https://registry.npmjs.org/react-router/-/react-router-7.18.3.tgz",
+      "integrity": "sha512-gyXgtdr5uACJ5b1Q4udzjVV+tb/rlHIMJKuJ0e89R4Kzgz47z/rgP0dIKxktqIEUhDHluGTPJJH/wRha7CyqsA==",
       "license": "MIT",
       "dependencies": {
         "cookie": "^1.0.1",
@@ -3056,12 +3070,12 @@
       }
     },
     "node_modules/react-router-dom": {
-      "version": "7.18.1",
-      "resolved": "https://registry.npmjs.org/react-router-dom/-/react-router-dom-7.18.1.tgz",
-      "integrity": "sha512-KaZh+X/6UtEp28x51AUYZDMg9NGoz2ja3dNHa+ta/tk40vCzKhQ/RypCWBMLbmDr6//E24Vv5uPsrqXFozdkAg==",
+      "version": "7.18.3",
+      "resolved": "https://registry.npmjs.org/react-router-dom/-/react-router-dom-7.18.3.tgz",
+      "integrity": "sha512-ytVbyBBM7vMfRCam25r0WMhSVSom909A8p+8m0/f1w853dz/xfFu6etAT2SEbVoSnI+ZoPRDqIsQXVT89gp7kg==",
       "license": "MIT",
       "dependencies": {
-        "react-router": "7.18.1"
+        "react-router": "7.18.3"
       },
       "engines": {
         "node": ">=20.0.0"
@@ -3319,9 +3333,9 @@
       "license": "MIT"
     },
     "node_modules/update-browserslist-db": {
-      "version": "1.2.3",
-      "resolved": "https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.2.3.tgz",
-      "integrity": "sha512-Js0m9cx+qOgDxo0eMiFGEueWztz+d4+M3rGlmKPT+T4IS/jP4ylw3Nwpu6cpTTP8R1MAC1kF4VbdLt3ARf209w==",
+      "version": "1.3.2",
+      "resolved": "https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.3.2.tgz",
+      "integrity": "sha512-UQ+MSxlhRm1bzjhU+DcuXfjFO1FzNtqhK5+9Yvlp90ItDLk5vT932A0rFu619nf7RVS+Y/VeaUW1jaRDqZ8VJw==",
       "dev": true,
       "funding": [
         {

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

@@ -13,7 +13,7 @@
     "framer-motion": "^12.34.4",
     "react": "^19.2.0",
     "react-dom": "^19.2.0",
-    "react-router-dom": "^7.18.1",
+    "react-router-dom": "^7.18.2",
     "zustand": "^5.0.11"
   },
   "devDependencies": {

package/skills/yad-docs-overview/SKILL.md

@@ -7,7 +7,7 @@ description: 'Generates the project-level SDLC-overview interactive site — the
 
 **Goal:** Render the **whole yadflow pipeline** — every stage from setup → ship — as an interactive site,
 reusing the same shell as the per-epic docs (`skills/yad-docs/templates/app/`). Where `yad-docs`
-animates one epic's flows, this animates the **workflow itself**: the front gates, the build half, the
+animates one epic's flows, this animates the **workflow itself**: the Shape gates, Build, the
 automation dial, the setup connectors. The hand-maintained overview report stays the **main
 documentation at the Pages root** (`<base>/`, served from `public/report.html` and `public/index.html`);
 this interactive SPA mounts under `<base>/app/` and is reached from the report — the report links
@@ -39,7 +39,7 @@ It only reads the pipeline definition and writes a project-level site. When a do
 There is no epic; the inputs are the workflow's own config + manifest (full mapping in
 `references/pipeline-model.md`):
 
-- `skills/sdlc/config.yaml` — the front/back steps, the **two dials** (assistance, automation),
+- `skills/sdlc/config.yaml` — the Shape/Build steps, the **two dials** (assistance, automation),
   defaults, the review-gate rule, the build conventions, the automation/trust thresholds.
 - `skills/sdlc/module-help.csv` — the **canonical skill manifest**: each skill's `phase`,
   `preceded-by` / `followed-by`, and `outputs`. This is the ordering source of truth.
@@ -56,7 +56,7 @@ git work tree). Generate and commit on it.
 Map the pipeline onto the same data structures `yad-docs` uses (concrete mapping in
 `references/pipeline-model.md`):
 
-- **Flow paths** = the **phases** — `Setup`, `Front-zero` (discovery), `Front half`, `Build half`, `Automation`, `Change management` (feature threads).
+- **Flow paths** = the **phases** — `Setup`, `Front-zero` (discovery), `Shape`, `Build`, `Automation`, `Change management` (feature threads).
 - **Flow steps** = the **skills/gates in order** (from `module-help.csv` `preceded-by`/`followed-by`),
   each step's `messages` = the skill's `outputs`, and `sideEffects` = the `.sdlc/` files it writes.
 - **System components** = the **durable state objects** — the product hub, each `.sdlc/*.json`

package/skills/yad-docs-overview/references/pipeline-model.md

@@ -10,7 +10,7 @@ ordering source of truth is `skills/sdlc/module-help.csv` (`phase`, `preceded-by
 
 | Shell primitive | Overview meaning |
 |-----------------|------------------|
-| `FlowPath` (`paths.ts`) | a **phase**: Setup, Front-zero (discovery), Front half, Build half, Automation, Change management (feature threads). |
+| `FlowPath` (`paths.ts`) | a **phase**: Setup, Front-zero (discovery), Shape, Build, Automation, Change management (feature threads). |
 | `FlowStep` (within a path) | a **skill or gate** in order; `messages` = its `outputs`; `sideEffects` = the `.sdlc/` files it writes; `status`/`bookingStatus` annotate gated vs. enrichment vs. earned. |
 | `SystemComponent` (`components.ts`) | a **durable state object** (the hub, each `.sdlc/*.json`, code repos, the design/testing/learning tools, the platform). |
 | `RoleConfig` (`roles.ts`) | a **lens** → its relevant sections + paths. |
@@ -35,7 +35,7 @@ and never gates.
 ### Path: Front-zero (`phase: 0-front`)
 The OPTIONAL once-per-project discovery phase, modelled as the reserved "epic zero" `EP-discovery`.
 Greenfield AND brownfield; a 2-step author→review chain whose review binds to the whole artifact set
-and terminates at `discovery-done` (no build half).
+and terminates at `discovery-done` (no Build).
 
 | Step (skill) | Gate | Outputs / sideEffects |
 |--------------|------|------------------------|
@@ -44,7 +44,13 @@ and terminates at `discovery-done` (no build half).
 `roadmap.md` is the menu of features each `yad-epic` reads (Step 2c) — reference-only, never
 auto-seeds epics.
 
-### Path: Front half (`phase: 1-front`)
+<!-- `1-front` and `3-build` are DATA — the `phase` column in skills/sdlc/module-help.csv, which
+     the overview build reads. The Shape/Build/Run rename deliberately left them alone: change-safety
+     rule 3 says a release may add but never rename, so a stored value moves in a major with a
+     migration, not in a wording sweep. The display names below are the new vocabulary; the ids are
+     the old one, on purpose. -->
+
+### Path: Shape (`phase: 1-front`)
 The gated authoring chain + the reusable review gate (10 steps, or 12 with the optional analysis).
 
 | Step (skill) | Gate | Outputs / sideEffects |
@@ -59,7 +65,7 @@ The gated authoring chain + the reusable review gate (10 steps, or 12 with the o
 | `yad-review-companion` | the fun/visible review layer (trailer/cards/chat + engagement) | `approvals.json` `engagement`, platform trailer/cards |
 | `yad-hub-bridge` | the platform PR/MR bridge | `hub-prs.json` |
 
-### Path: Build half (`phase: 3-build`)
+### Path: Build (`phase: 3-build`)
 Per-story, per-repo: `spec → tasks → implement → checks → engineer-review`, plus the commit/PR helpers.
 
 | Step (skill) | Outputs / sideEffects |
@@ -78,7 +84,7 @@ node classes from the diagram.
 
 | Step (skill) | Outputs / sideEffects |
 |--------------|------------------------|
-| `yad-run` | drives the back-half loop; `build-state/<story>.json`, `trust-log.json`, kill switch |
+| `yad-run` | drives the Build loop; `build-state/<story>.json`, `trust-log.json`, kill switch |
 | `yad-learn` | tutoring; `learning-records.json` (LOCAL-ONLY, gitignored) |
 | `yad-status` | read-only view (no writes) |
 | `yad-docs` / `yad-docs-overview` / `yad-docs-sync` | the docs sites + their `docs-build.json` manifests |
@@ -86,9 +92,9 @@ node classes from the diagram.
 ### Path: Change management — feature threads (`phase: 6-change`)
 The post-lock evolution layer. Once an epic is **sealed** (all stories shipped), behaviour can no longer
 be mutated in place — a change request becomes a **new epic threaded to its parent** (genesis → change →
-defect), inheriting unchanged front artifacts **by reference** and re-authoring only what changes, so
+defect), inheriting unchanged Shape artifacts **by reference** and re-authoring only what changes, so
 locked artifacts are never mutated and never go stale, only superseded. Three CI gates enforce the thread
-(`lineage-check`, `epic-open`, `reconcile-debt`). This path never gates the front chain; `yad-change` is
+(`lineage-check`, `epic-open`, `reconcile-debt`). This path never gates the Shape chain; `yad-change` is
 the intake, then it hands off to the normal authoring skills + the review gate.
 
 | Step (skill) | Outputs / sideEffects |
@@ -99,7 +105,7 @@ the intake, then it hands off to the normal authoring skills + the review gate.
 | `yad-reconcile` | advisory drift / orphan / debt sweep (read-only; mirrors `yad-docs-sync`) |
 
 CLI: `yad thread [<epic>]` prints a thread + its resolved current truth + open debt; `yad reconcile`
-runs the sweep. The three thread gates ride in the build-half `yad-checks` set above.
+runs the sweep. The three thread gates ride in the Build `yad-checks` set above.
 
 ## System components = the durable state objects
 
@@ -121,11 +127,11 @@ The eight yadflow lenses, each to its relevant phase sections + paths:
 
 | Lens | Relevant phases / sections |
 |------|----------------------------|
-| analyst | Setup intent, project discovery (front-zero), analysis step, front-half discovery |
-| pm | project discovery (market/feasibility/roadmap), epic, stories; the front gates |
+| analyst | Setup intent, project discovery (front-zero), analysis step, Shape discovery |
+| pm | project discovery (market/feasibility/roadmap), epic, stories; the Shape gates |
 | architect | architecture + the locked contract; escalation |
 | ux | UI design, design tool connection, the design system |
-| dev | build half: spec → implement, the per-repo loop |
+| dev | Build: spec → implement, the per-repo loop |
 | tester | test-cases (parallel track), the testing tool, checks |
 | reviewer | the review gate, comments, the hub bridge |
 | engineer | engineer review + ship, the merge gate, automation dial/trust |

package/skills/yad-engineer-review/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: yad-engineer-review
-description: 'Build-half Step E of the gated SDLC — AI review, engineer review, then merge. Wire an advisory AI first-pass (CodeRabbit) on the PR/MR; record the human engineer review with the same human_approve discipline as the front gates (owner + 1 reviewer, escalating to domain owners on high risk / contract / auth / payments — the Step D routing); and on merge, record the ship in the epic build-log and update the story state so the epic → story → task → PR chain is traceable. Never auto-advances — the human owns the merge. Use when the user says "record the engineer review", "merge this task", or "wire the AI review". (To commit + open the PR/MR, use yad-ship.)'
+description: 'Build Step E of the gated SDLC — AI review, engineer review, then merge. Wire an advisory AI first-pass (CodeRabbit) on the PR/MR; record the human engineer review with the same human_approve discipline as the Shape gates (owner + 1 reviewer, escalating to domain owners on high risk / contract / auth / payments — the Step D routing); and on merge, record the ship in the epic build-log and update the story state so the epic → story → task → PR chain is traceable. Never auto-advances — the human owns the merge. Use when the user says "record the engineer review", "merge this task", or "wire the AI review". (To commit + open the PR/MR, use yad-ship.)'
 ---
 
-# SDLC — Engineer Review & Merge (build-half Step E)
+# SDLC — Engineer Review & Merge (Build Step E)
 
 **Goal:** Take a task PR/MR that has passed the **check gates** (Step C) through two sets of eyes and
 out to production: an **AI first-pass** (advisory) and a **human engineer review** (the authority),
-then **ship** — merge, record the ship, and update the story state. This is the last build-half step
-(build plan §E). It is a **human gate**, the same `human_approve` discipline as the front states:
+then **ship** — merge, record the ship, and update the story state. This is the last Build step
+(build plan §E). It is a **human gate**, the same `human_approve` discipline as the Shape steps:
 **nothing auto-advances**; the engineer owns the merge.
 
 ## Conventions
@@ -66,7 +66,7 @@ approve); `yad review reconcile --epic <id> --repo <r> --pr <n>` stamps it onto
 platform (mutating the ship's shard where it lives, or its folded entry if already tidied). Soft by default (both count; a bare approve draws `yad review nudge`); only gates when
 `hub.review.requireEngagement: true`. The signal is gameable by design and sits **beside** the CI gates,
 never above them.
-Recording an approval does **not** ship — shipping is a separate, explicit step. Front-half discipline:
+Recording an approval does **not** ship — shipping is a separate, explicit step. Shape discipline:
 the gate talks only through files; refuse to treat AI review as a human approval.
 
 ### Step 3 — `ship` (merge + record + update state)
@@ -94,18 +94,18 @@ engineer-review rule is satisfied (Step 2). Then:
   a rejected one is `rejected`. This is the evidence that later earns a step its `machine_advance`
   (it never weakens the merge gate — the engineer still owns the merge).
 - **Commit the machine-written ledgers.** Run `yad checkpoint --push` from `{project-root}` to commit
-  the back-half ledgers just written (the `build-log/` shard, and the `trust-log/` shard /
+  the Build ledgers just written (the `build-log/` shard, and the `trust-log/` shard /
   `build-state/<story>.json` if the story ran through `yad-run`) as one `chore(hub): …` audit-trail
   commit — default branch only, staging the shard dirs (`yad tidy up` folds finished shards later),
-  never a front-half gate file. It is the back-half analogue of the front-half `yad gate` sync. The
+  never a Shape gate file. It is the Build analogue of the Shape `yad gate` sync. The
   same commit also **carries the story `status:` flip** you just wrote (`approved → in-build/shipped`,
   #112) — because that story now has a build-log ship, checkpoint stages `stories/<story>.md` alongside
   the ledgers, so the artifact never drifts from build-log and you never fall back to a raw git-to-main
   push. (The code-repo `tasks.md` is committed in its own repo as usual.)
 
 ### Step 4 — Stop
-Report what shipped and the story's state. Do not advance anything else; the front-half `state.json`
-stays as it was (`ready-for-build`). The build half is recorded in `build-log.json` + the story status.
+Report what shipped and the story's state. Do not advance anything else; the Shape `state.json`
+stays as it was (`ready-for-build`). Build is recorded in `build-log.json` + the story status.
 
 ## Hard rules (build plan §E, Cross-cutting)
 

package/skills/yad-engineer-review/references/ship-and-record.md

@@ -1,6 +1,6 @@
 # Ship — the build ledger and the story state
 
-Step E (`yad-engineer-review`) closes the build half: AI review (advisory) → engineer review (the human gate) →
+Step E (`yad-engineer-review`) closes Build: AI review (advisory) → engineer review (the human gate) →
 ship. Shipping records the merge and updates the story state so the whole chain is traceable.
 
 ## Two sets of eyes
@@ -59,16 +59,16 @@ without the `{ epic, ships }` wrapper):
 }
 ```
 
-This is the back-half analogue of the front half's `approvals.json` — files only, no hidden state, so a
+This is the Build analogue of Shape's `approvals.json` — files only, no hidden state, so a
 future service can drive ship by writing the same records. Like the trust log and build-state, it is a
-machine-written ledger committed by **`yad checkpoint`** (the back-half analogue of `yad gate` sync),
+machine-written ledger committed by **`yad checkpoint`** (the Build analogue of `yad gate` sync),
 not by hand: after recording the ship, `yad checkpoint --push` lands the new `build-log/` shard as a
-`chore(hub): …` audit-trail commit on the default branch (allowlist-scoped to the back-half ledgers,
-never a front-half gate file); `yad tidy up` folds finished shards into `build-log.json` later.
+`chore(hub): …` audit-trail commit on the default branch (allowlist-scoped to the Build ledgers,
+never a Shape gate file); `yad tidy up` folds finished shards into `build-log.json` later.
 
 ### Retroactive ship — a pre-tracking story (#142)
 
-A story that was merged and shipped **before** the back-half ledger existed has no build-log ship, so
+A story that was merged and shipped **before** the Build ledger existed has no build-log ship, so
 `yad checkpoint` can't carry its `status: shipped` flip (the flip is only carried when a ship backs it,
 #112) — leaving a raw `git push origin main` as the only way to land it, against the never-raw-git
 convention. To reconcile it through yad, record a **retroactive** ship, then checkpoint carries the flip
@@ -83,7 +83,7 @@ It writes ONE minimal ship shard marked `retroactive: true` (`task` defaults to
 the normal checkpoint so the story's already-made `status:` flip rides along in the **same** commit. It
 refuses when the story already has a ship **in that repo** (then it isn't pre-tracking there — use the
 normal flow). It does **not** author the story frontmatter — and to keep evidence and the flip atomic (the no-drift
-invariant), it **refuses** unless you have already set a back-half `status:` (`in-build` or `shipped`) in
+invariant), it **refuses** unless you have already set a Build `status:` (`in-build` or `shipped`) in
 `stories/<story>.md`, so a ship shard is never committed while the artifact still says `approved`.
 
 **Where the record lands — it is a shard, not an append to `build-log.json`.** Like every other ship, a
@@ -129,7 +129,7 @@ a bare approve draws a friendly `yad review nudge`); it only gates ship when
 `hub.review.requireEngagement: true`. `yad review reconcile --epic <id> --repo <r> --pr <n>` reads the
 code PR's approvals (with the engagement signal) and stamps them onto the matching ship record — writing
 back into the ship's shard where it lives (or its folded entry if the story was already tidied) — the
-back-half **bridge**, the analogue of `yad gate sync`. The signal is gameable by design ("visible, not
+Build **bridge**, the analogue of `yad gate sync`. The signal is gameable by design ("visible, not
 impossible"): it makes engineer-review quality visible, it does not prove a human read the diff. It sits
 **beside** the CI gates (build/test/lint/contract/verified-commits) — never above them; CI still
 decides machine safety, the merge is still the human act.