yadflow 3.7.0 → 3.7.1

package/CHANGELOG.md

@@ -1,13 +1,9 @@
-# [3.7.0](https://github.com/abdelrahmannasr/yadflow/compare/v3.6.1...v3.7.0) (2026-07-04)
+## [3.7.1](https://github.com/abdelrahmannasr/yadflow/compare/v3.7.0...v3.7.1) (2026-07-04)
 
 
-### Features
+### Bug Fixes
 
-* **cli:** add shared hub-commit default-branch guard helpers ([44290f6](https://github.com/abdelrahmannasr/yadflow/commit/44290f6109c806f077609fec352904efe801f830))
-* **cli:** add yad checkpoint to commit machine-written back-half state ([c09089c](https://github.com/abdelrahmannasr/yadflow/commit/c09089c698884ad39fc8cf66a7e28d8d44321668))
-* **cli:** add yad tidy up to fold finished ledger shards ([59727f3](https://github.com/abdelrahmannasr/yadflow/commit/59727f32a7b5e3274c8fd96b8b39134b3acf6705))
-* **cli:** shard-then-fold storage for the back-half ledgers ([6182598](https://github.com/abdelrahmannasr/yadflow/commit/618259847e3dbdee5f00bce4fa2a5d64df0364a3))
-* **cli:** wire yad checkpoint and yad tidy up into the CLI ([fe4770d](https://github.com/abdelrahmannasr/yadflow/commit/fe4770de87ebec394c3a29c78077a0baf7a924cc))
+* **ledger:** sanitize shard-name components against path traversal ([5d85286](https://github.com/abdelrahmannasr/yadflow/commit/5d85286591cc9e6c78e449551c82d87683accba5))
 
 # [2.2.0](https://github.com/abdelrahmannasr/yadflow/compare/v2.1.0...v2.2.0) (2026-06-14)
 

package/cli/ledger.mjs

@@ -18,8 +18,15 @@ import { epicFiles } from './manifest.mjs';
 // story ids already contain hyphens; the filename is just a unique handle (the entry inside carries
 // the fields), so no parsing-back is needed. A trust entry needs `uid` to stay unique across re-runs
 // of the same (story, repo, step); a ship is unique by (story, task, repo) already.
-export const trustShardName = (e) => `${e.story}-${e.repo}-${e.step}-${e.uid}.json`;
-export const buildShardName = (e) => `${e.story}-${e.task}-${e.repo}.json`;
+//
+// Each component is sanitized to a filename-safe charset FIRST: a `/`, `..`, or other separator in an
+// id would otherwise be a real path element under `path.join(dir, name)` + `writeJSON`, letting a
+// malformed shard escape the shard dir (and then vanish from `readShardDir`). Anything outside
+// [A-Za-z0-9_-] collapses to `_` (dots dropped too, so `.`/`..` can never form); an empty component
+// becomes `_` so a segment is never blank.
+const safe = (c) => String(c ?? '').replace(/[^A-Za-z0-9_-]/g, '_') || '_';
+export const trustShardName = (e) => `${safe(e.story)}-${safe(e.repo)}-${safe(e.step)}-${safe(e.uid)}.json`;
+export const buildShardName = (e) => `${safe(e.story)}-${safe(e.task)}-${safe(e.repo)}.json`;
 
 // Read every shard object under `dir` (each file = ONE entry object). Sorted for determinism; a
 // corrupt/non-object shard is skipped (these ledgers are advisory evidence, never fatal).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yadflow",
-  "version": "3.7.0",
+  "version": "3.7.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/yad-implement/SKILL.md

@@ -123,7 +123,8 @@ finalize a `tasks` trust entry, anchored to what the human/dev actually did with
 - the task list is discarded / regenerated → `rejected`.
 Write the entry to its own shard `epics/<epic>/.sdlc/trust-log/<story>-<repo>-tasks-<uid>.json` (a fresh
 `uid` per run, so concurrent writers never conflict; readers union the folded `trust-log.json` + the
-loose shards). Schema: `../yad-epic/references/state-schema.md`. `tasks` stays `human_approve` until its slice clears
+loose shards, skipping any shard whose full `(story, repo, step, uid)` already appears folded — a
+half-applied `yad tidy up` — so entries are never double-counted). Schema: `../yad-epic/references/state-schema.md`. `tasks` stays `human_approve` until its slice clears
 the threshold — this only *gathers* evidence. (The `implement` step's own verdict is finalized later,
 at the engineer review in `yad-engineer-review`: merged as authored → `approved-unchanged`; edited first →
 `approved-with-edits`; scope/contract/checks halt → `rejected`.)