yadflow 3.16.3 → 3.17.1

package/skills/yad-implement/SKILL.md

@@ -23,9 +23,9 @@ declares; it does not redesign, does not widen the contract, and does not pick u
 - The work happens **inside the code repo** (a separate git repo) at
   `{project-root}/demo-repos/<repo>/` (`config.yaml` `build.code_repos_root`). Use absolute paths.
 - **Branch name:** `feat/<story-id>-<task-id>-<short-slug>` (e.g.
-  `feat/EP-istifta-inquiries-S01-T01-create-inquiry`). Branched off the code repo's default branch.
+  `feat/EP-checkout-S01-T01-create-order`). Branched off the code repo's default branch.
 - **Commit message:** a conventional subject, body describing the change, and a **required `Task:`
-  trailer** (e.g. `Task: EP-istifta-inquiries-S01-T01`) in the trailer block. Add `Contract-Change: yes`
+  trailer** (e.g. `Task: EP-checkout-S01-T01`) in the trailer block. Add `Contract-Change: yes`
   **only** if the diff touches the locked contract surface (see Step 5), and a per-commit
   `Co-Authored-By:` for any AI tool that helped author the diff (the human author owns the commit;
   trailer order `Task:` → `Contract-Change:` → `Co-Authored-By:`). The skill installs a `.gitmessage`
@@ -84,7 +84,7 @@ boundary breach). The same applies to the Step 5 contract-surface stop (`contrac
 ### Step 5 — Contract-surface check (local pre-flight for Step C)
 Determine whether the diff touches the **locked contract surface** (the API/event/data-model shapes in
 `epics/<epic>/contract.md`'s `CONTRACT-SURFACE` block). Normal implementation **consumes** the
-contract (e.g. implementing `POST /inquiries` to the agreed shape) — that is **not** a contract change.
+contract (e.g. implementing `POST /orders` to the agreed shape) — that is **not** a contract change.
 A contract change means the diff alters the agreed cross-repo shape itself.
 
 - If the diff does **not** change the surface: proceed; no `Contract-Change` trailer.

package/skills/yad-implement/references/implement-conventions.md

@@ -10,11 +10,11 @@ diff back to its task, story, and contract.
 feat/<story-id>-<task-id>-<short-slug>
 ```
 
-- `<story-id>` — the permanent story ID, e.g. `EP-istifta-inquiries-S01`.
+- `<story-id>` — the permanent story ID, e.g. `EP-checkout-S01`.
 - `<task-id>` — the atomic task ID from `tasks.md`, e.g. `T01`.
-- `<short-slug>` — 2–4 hyphenated words naming the change, e.g. `create-inquiry`.
+- `<short-slug>` — 2–4 hyphenated words naming the change, e.g. `create-order`.
 
-Example: `feat/EP-istifta-inquiries-S01-T01-create-inquiry`. Branched off the code repo's default
+Example: `feat/EP-checkout-S01-T01-create-order`. Branched off the code repo's default
 branch. One task = one branch; never reuse a branch for a different task, never fork a second branch
 for the same task.
 
@@ -33,9 +33,9 @@ Task: <story-id>-<task-id>
 - The **`<type>` is lowercase** (`feat`, `fix`, `docs`, `refactor`, `test`, `perf`, `build`, `ci`,
   `chore`, `revert`) and the **`<subject>` starts lowercase**, is **imperative**, and has **no trailing
   period** — Conventional Commits (see `CONTRIBUTING.md` and `config.yaml` `build.commit_subject_style`).
-  Proper nouns/acronyms keep their case (`fix: refresh OAuth token`). e.g. `feat: add POST /inquiries
-  create path`, not `feat: Add POST /inquiries create path.`
-- The **`Task:` trailer is required** (`Task: EP-istifta-inquiries-S01-T01`) — the anchor the spec-link
+  Proper nouns/acronyms keep their case (`fix: refresh OAuth token`). e.g. `feat: add POST /orders
+  create path`, not `feat: Add POST /orders create path.`
+- The **`Task:` trailer is required** (`Task: EP-checkout-S01-T01`) — the anchor the spec-link
   check (§C) and the PR (§D) read to connect the diff to its spec and story. It need not be the *last*
   line: the spec-link gate finds it with git's native trailer parser
   (`%(trailers:key=Task)`), which is order-independent. All trailers must sit in **one contiguous block**
@@ -85,7 +85,7 @@ The **locked contract surface** is the cross-repo agreement in `epics/<epic>/con
 `CONTRACT-SURFACE` block, hash-locked at `.sdlc/contract-lock.json`). Distinguish:
 
 - **Consuming the contract** (normal) — implementing an endpoint/event/entity to the shape the contract
-  already agreed (e.g. building `POST /inquiries` to its agreed request/response). **Not** a contract
+  already agreed (e.g. building `POST /orders` to its agreed request/response). **Not** a contract
   change; no trailer.
 - **Changing the contract** (exceptional) — altering the agreed shape itself (new field crossing repos,
   changed status enum, new shared endpoint). This is **not** an implementation decision. Stop, go back

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

@@ -188,7 +188,9 @@ PR only — against the `review/<epic>/<artifact>` branch, which must already ex
 records this skill describes. The skill's
 job is the human half: presenting the artifact, helping the owner address comments, and narrating the
 gate. Local `yad gate sync` is advisory in bridge mode (reads the platform, prints status, writes
-nothing); a human must never commit gate-state files (the `ledger-guard` check rejects it). The single
+nothing); a human must never commit gate-state files (the `ledger-guard` check rejects it, and the
+`hooks/ledger-guard.sh` harness hook refuses an agent the edit up front, naming `yad gate open`
+instead — see `yad-checks`). The single
 exception is an epic's **seed** — no CI path can create a ledger, so a brand-new epic's `.sdlc/` rides
 its **first** review PR/MR, cut from the authoring branch (creation, not mutation, #162).
 

package/skills/yad-spec/SKILL.md

@@ -25,7 +25,7 @@ is the same graceful-degradation pattern `yad-ui` uses for Impeccable.
 - **Code repos are separate git repos**, one `.git` each, under `{project-root}/demo-repos/<repo>/`
   (`config.yaml` `build.code_repos_root`). All Spec Kit outputs land **inside the code repo**, never
   in the product repo.
-- `{feature-id}` is the **story ID** (e.g. `EP-istifta-inquiries-S01`) — **pinned**, never Spec Kit's
+- `{feature-id}` is the **story ID** (e.g. `EP-checkout-S01`) — **pinned**, never Spec Kit's
   numbered auto-slug (which is unstable and severs the permanent story link). The spec folder is
   `specs/<story-id>/`.
 - Spec Kit output layout (RESEARCH-NOTES §2): `specs/<feature-id>/spec.md` (+ `research.md`,

package/skills/yad-spec/references/spec-handoff.md

@@ -48,11 +48,11 @@ comes from the story's acceptance criteria and the **locked contract surface**
   contract endpoints/entities the story touches.
 - **`research.md`** — list the decisions and any unknowns; if the story is unambiguous, say so. Note
   where the contract already settles a question (e.g. status is server-owned).
-- **`data-model.md`** — the entities/fields **this repo** implements. Shared entities (e.g. `Inquiry`,
-  `InquiryStatus`) are **quoted from the contract** and marked as contract-owned; repo-private fields
+- **`data-model.md`** — the entities/fields **this repo** implements. Shared entities (e.g. `Order`,
+  `OrderStatus`) are **quoted from the contract** and marked as contract-owned; repo-private fields
   are marked as local.
 - **`contracts/`** — the slice of the API/event surface this repo implements, **quoted from the locked
-  `contract.md`** (e.g. `POST /inquiries` request/response). Add a one-line note that this is a quote of
+  `contract.md`** (e.g. `POST /orders` request/response). Add a one-line note that this is a quote of
   the locked surface, not a new definition.
 - **`plan.md`** — the technical approach for this repo at story altitude (components, sequence,
   test approach). No new cross-repo surface.

package/skills/yad-status/SKILL.md

@@ -38,7 +38,7 @@ Print, in this order:
 1. **Header:** render the kind noun from `epic.md` frontmatter `kind` — **Change request** (`change`),
    **Defect** (`defect`), **Hotfix** (`hotfix`), or **Epic** (`feature`, and the default when `kind` is
    absent) — followed by `epicId`, then `status` from `epic.md` frontmatter, `currentStep`, and `repos`
-   (the touched domains). Example: `Defect EP-istifta-queue-filter — draft @ stories`. A bug is a defect
+   (the touched domains). Example: `Defect EP-checkout-queue-filter — draft @ stories`. A bug is a defect
    (`kind: defect`) — there is no separate noun. This is presentation only; the artifact is still an epic.
 2. **Steps table** — for every front step in `steps[]` order (10, or 12 when the optional analysis step
    was run): `id`, `type`, `status`, `assistance`, `automation`, `locked`, and `risk_tags`. Mark the

package/skills/yad-stories/SKILL.md

@@ -18,7 +18,7 @@ There is **no `sm` agent** (Phase 0 Deviation 1): the `pm` lens breaks down the
 
 - `{project-root}` resolves from the project working directory.
 - Stories live under `{project-root}/epics/EP-<slug>/stories/` (build plan §6).
-- Story files are named `EP-<slug>-S0N.md` (zero-padded, e.g. `EP-istifta-inquiries-S01.md`).
+- Story files are named `EP-<slug>-S0N.md` (zero-padded, e.g. `EP-checkout-S01.md`).
 - Speak in the configured `communication_language`; write documents in `document_output_language`.
 
 ## On Activation

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

@@ -152,7 +152,7 @@ When Step 3b generated or linked automation, write the machine-readable case→t
   "direction": "generated | linked",
   "tests": [
     { "case": "TC-01", "story": "EP-<slug>-S01", "repo": "backend", "level": "e2e",
-      "path": "tests/inquiry.spec.ts", "url": "<repo url to the test>" }
+      "path": "tests/order.spec.ts", "url": "<repo url to the test>" }
   ],
   "source": "playwright-mcp"
 }

package/skills/yad-test-cases/references/test-cases-schema.md

@@ -45,7 +45,7 @@ Written by `yad-test-cases` Step 4b. Absent when the step ran artifacts-only (`t
   "direction": "generated | linked",
   "tests": [
     { "case": "TC-01", "story": "EP-<slug>-S01", "repo": "backend", "level": "e2e",
-      "path": "tests/inquiry.spec.ts", "url": "<repo url to the test>" }
+      "path": "tests/order.spec.ts", "url": "<repo url to the test>" }
   ],
   "source": "playwright-mcp"
 }

package/skills/yad-ui/SKILL.md

@@ -160,7 +160,7 @@ When Step 3b generated or linked a design, write the machine-readable screen→f
   "generatedAt": "<YYYY-MM-DD>",
   "direction": "generated | linked",
   "screens": [
-    { "name": "Submit Inquiry", "platform": "mobile",
+    { "name": "Checkout", "platform": "mobile",
       "nodeId": "123:45", "url": "https://www.figma.com/file/<key>/?node-id=123-45" }
   ],
   "source": "figma-mcp"