yadflow 3.17.0 → 3.17.1

package/CHANGELOG.md

@@ -1,3 +1,5 @@
+## [3.17.1](https://github.com/abdelrahmannasr/yadflow/compare/v3.17.0...v3.17.1) (2026-09-02)
+
 # [3.17.0](https://github.com/abdelrahmannasr/yadflow/compare/v3.16.3...v3.17.0) (2026-08-12)
 
 

package/cli/commit.mjs

@@ -38,7 +38,7 @@ export function buildCommitMessage({ type, subject, task, contractChange = false
   return parts.join('\n');
 }
 
-// feat/EP-istifta-inquiries-S01-T01-create-inquiry -> EP-istifta-inquiries-S01-T01
+// feat/EP-checkout-S01-T01-create-order -> EP-checkout-S01-T01
 export function taskFromBranch(branch = '') {
   const m = branch.match(/(.+-S\d+-T\d+)(?:-|$)/i);
   return m ? m[1].replace(/^[a-z]+\//i, '') : null;

package/cli/next.mjs

@@ -46,7 +46,7 @@ const actionFor = (root, id) => ({
   lineageKind: epicLineage(root, id).kind,
 });
 
-// EP-istifta-inquiries-S03 → S03 (the compact lane label for the roll-up). Falls back to the full id.
+// EP-checkout-S03 → S03 (the compact lane label for the roll-up). Falls back to the full id.
 const shortStory = (s) => (s && s.match(/S\d+$/i)?.[0]) || s || '(story)';
 
 // Every per-repo lane across the build, flattened with its story id attached.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yadflow",
-  "version": "3.17.0",
+  "version": "3.17.1",
   "description": "Yadflow — the gated, team, multi-repo SDLC: author → review → build with a PR-driven review gate and a zero-dependency `yad` CLI (setup, gate, commit, open-pr, ship, repo, thread, reconcile). A BMAD module + 38 yad-* skills.",
   "type": "module",
   "author": "AbdelRahman Nasr",

package/skills/sdlc/config.yaml

@@ -94,7 +94,7 @@ build:
   spec_layout: speckit          # follow Spec Kit's native spec/plan/tasks layout
   speckit_ceremony: [specify, clarify, plan, analyze, checklist, tasks]   # heavy run, once per story per repo
   # Step B (yad-implement) — the light per-task loop. One atomic task = one branch = one PR/MR.
-  branch_convention: "feat/<story-id>-<task-id>-<short-slug>"   # e.g. feat/EP-istifta-inquiries-S01-T01-create-inquiry
+  branch_convention: "feat/<story-id>-<task-id>-<short-slug>"   # e.g. feat/EP-checkout-S01-T01-create-order
   commit_task_trailer: "Task: <story-id>-<task-id>"             # final commit trailer; anchors the spec-link check (Step C)
   contract_change_trailer: "Contract-Change: yes"              # ONLY when the locked contract surface is touched (routes back to architecture gate)
   # Commit subject + PR/MR title style (Conventional Commits — see CONTRIBUTING.md). PRs are squash-merged,

package/skills/yad-analysis/SKILL.md

@@ -62,7 +62,7 @@ roadmap. **Optional & non-blocking:** if there is no discovery, or it has not ye
 
 ### Step 3 — Generate the Epic ID (engine-assigned, never by hand)
 Derive `EP-<slug>` where `slug` is **2–4 lowercase words joined by hyphens**, drawn from the idea
-(e.g. `EP-istifta-inquiries`). Lowercase except the fixed `EP` prefix. `EP-discovery` is **reserved**
+(e.g. `EP-checkout`). Lowercase except the fixed `EP` prefix. `EP-discovery` is **reserved**
 for the project front-zero — never use it for a feature. **The ID is assigned once and
 never renamed** — renaming breaks every downstream link (build plan §6b). Check
 `{project-root}/epics/` for collisions; if the slug exists, append a distinguishing word.

package/skills/yad-checks/references/check-gates.md

@@ -489,15 +489,15 @@ bash checks/commit-message.sh --profile code master
 # pr-title / pr-template validate the actual PR/MR metadata (in CI they come from the event payload).
 # By hand, pass the title, and a FILE holding the PR/MR description (the rendered/filled body, not the
 # template source):
-bash checks/pr-title.sh --profile code "feat: add the inquiry endpoint"
+bash checks/pr-title.sh --profile code "feat: add the order endpoint"
 # save the PR/MR description to a file first (e.g. `gh pr view <n> --json body -q .body > /tmp/pr-body.md`)
 bash checks/pr-template.sh --profile code /tmp/pr-body.md
 ```
 
-## Proven behavior (demo: `demo-repos/backend`, story EP-istifta-inquiries-S01)
+## Proven behavior (demo: `demo-repos/backend`, story EP-checkout-S01)
 
 - **Good PR** (task branch with a `Task:` trailer, no surface change, passing tests) → all three **PASS**.
 - **Bad PR A** (a code change committed with **no** `Task:` trailer) → spec-link **FAILS**.
-- **Bad PR B** (edits `specs/.../contracts/inquiries.md` to widen the surface, with a `Task:` trailer
+- **Bad PR B** (edits `specs/.../contracts/orders.md` to widen the surface, with a `Task:` trailer
   but **no** `Contract-Change`) → spec-link passes, contract-check **FAILS** and routes back to the
   architecture gate.

package/skills/yad-connect-learning/references/learning-registry.md

@@ -17,7 +17,7 @@ root, not under any `epics/EP-<slug>/.sdlc/`.
   "tool": "deeptutor",                               // deeptutor | <adapter id> | none (harness-native)
   "provider": "deeptutor-cli",                       // the concrete CLI: deeptutor-cli | null
   "version": "1.4.5",                                // CLI version reported at detect time; null if absent
-  "kb": "yadflow-istifta",                           // grounded knowledge-base name; null if not built
+  "kb": "yadflow-checkout",                           // grounded knowledge-base name; null if not built
   "kb_sources": ["epic.md", "architecture.md", "contract.md", "ui-design.md", "stories/", "code-context/*/code-map.md"],
   "auth": "user",                                    // ALWAYS the user's own DeepTutor config / LLM keys — never a token
   "connectedAt": "2026-06-14",                       // first connect (YYYY-MM-DD)

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

@@ -36,13 +36,13 @@ without the `{ epic, ships }` wrapper):
 
 ```json
 {
-  "epic": "EP-istifta-inquiries",
+  "epic": "EP-checkout",
   "ships": [
     {
-      "story": "EP-istifta-inquiries-S01",
+      "story": "EP-checkout-S01",
       "task": "T01",
       "repo": "backend",
-      "branch": "feat/EP-istifta-inquiries-S01-T01-create-inquiry",
+      "branch": "feat/EP-checkout-S01-T01-create-order",
       "pr": "<url|#|local>",
       "mergeCommit": "<sha>",
       "gates": ["spec-link", "contract-check", "build-test-lint"],

package/skills/yad-epic/SKILL.md

@@ -83,7 +83,7 @@ unchanged — do not consume an unapproved roadmap. After seeding the epic, the
 ### Step 3 — Generate the Epic ID (engine-assigned, never by hand) — analysis-skipped only
 *(Skip when analysis ran — the ID was already assigned by `yad-analysis`.)*
 Derive `EP-<slug>` where `slug` is **2–4 lowercase words joined by hyphens**, drawn from the idea
-(e.g. `EP-istifta-inquiries`). Lowercase except the fixed `EP` prefix. `EP-discovery` is **reserved**
+(e.g. `EP-checkout`). Lowercase except the fixed `EP` prefix. `EP-discovery` is **reserved**
 for the project front-zero — never use it for a feature. **The ID is assigned once and
 never renamed** — renaming breaks every downstream link (build plan §6b).
 Check `{project-root}/epics/` for collisions; if the slug exists, append a distinguishing word.

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

@@ -416,7 +416,7 @@ only re-authored steps run. The seeder sets `currentStep` to the first re-author
 ```json
 { "id": "architecture", "type": "author", "artifact": "architecture.md",
   "assistance": "review", "automation": "human_approve", "locked": true,
-  "status": "done", "inherited": true, "inheritedFrom": "EP-istifta-inquiries",
+  "status": "done", "inherited": true, "inheritedFrom": "EP-checkout",
   "boundHash": "sha256:…", "risk_tags": [] }
 ```
 
@@ -432,7 +432,7 @@ only re-authored steps run. The seeder sets `currentStep` to the first re-author
 
 ```json
 { "artifact": "architecture.md", "step": "architecture-review", "status": "inherited",
-  "from": "EP-istifta-inquiries", "boundHash": "sha256:…", "date": "<YYYY-MM-DD>" }
+  "from": "EP-checkout", "boundHash": "sha256:…", "date": "<YYYY-MM-DD>" }
 ```
 
 ## The pointer-lock — `contract-lock.json` in a change-epic
@@ -443,7 +443,7 @@ no `contract.md` in the child to edit, so the surface physically cannot drift.
 
 ```json
 { "artifact": "contract.md", "hash": "sha256:<parent hash, verbatim>", "lockedAt": "<date>",
-  "inheritedFrom": "EP-istifta-inquiries", "ref": "../../EP-istifta-inquiries/.sdlc/contract-lock.json" }
+  "inheritedFrom": "EP-checkout", "ref": "../../EP-checkout/.sdlc/contract-lock.json" }
 ```
 
 Omitting `architecture` from `inherits` (depth `contract-surface`) is what triggers a **real re-lock**:
@@ -455,9 +455,9 @@ architecture gate" with "open a contract-surface change-epic" — one mechanism,
 Intake + triage record, one per change/defect/hotfix epic (sibling of `approvals.json`).
 
 ```json
-{ "epicId": "EP-istifta-queue-filter", "thread": "EP-istifta-inquiries", "parent": "EP-istifta-inquiries",
+{ "epicId": "EP-checkout-queue-filter", "thread": "EP-checkout", "parent": "EP-checkout",
   "kind": "defect", "depth": "defect-fix", "intakeBy": "alice", "intakeDate": "<YYYY-MM-DD>",
-  "title": "Pending queue returns answered inquiries", "description": "…",
+  "title": "Pending queue returns fulfilled orders", "description": "…",
   "affectedArtifacts": ["stories", "test-cases"],
   "reauthors": ["stories", "test-cases"], "inherits": ["epic", "architecture", "contract", "ui-design"],
   "defect": { "origin": "production", "severity": "sev2", "escape_stage": "test-cases",
@@ -476,7 +476,7 @@ sharing `thread` and read each `change.json`; there is no duplicated thread regi
 Append-only ledger of hotfix ship-first debt (a hotfix shipped code before its front gates approved).
 
 ```json
-[ { "thread": "EP-istifta-inquiries", "epicId": "EP-istifta-hotfix-x", "openedDate": "<date>",
+[ { "thread": "EP-checkout", "epicId": "EP-checkout-hotfix-x", "openedDate": "<date>",
     "reason": "prod outage", "requires": ["artifacts-updated", "regression-test"],
     "status": "open", "paidDate": null, "paidBy": null,
     "evidence": { "artifacts": [], "regressionTest": "" } } ]

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-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"