@teurons/vds 0.0.8 → 0.0.9

package/README.md

@@ -3,7 +3,7 @@
 The `vds` command. It starts, checks and indexes a VDS workspace on your machine.
 
 VDS keeps a product's spec as files: capabilities that hold rules written in EARS,
-scenarios in Gherkin, and flows that point at those rules in order.
+scenarios in Gherkin, and journeys that point at those rules in order.
 This package is an early alpha.
 
 ## Set it up with your AI agent
@@ -14,7 +14,7 @@ Copy this prompt into Claude Code, Codex or any coding agent, run from the root
 Set up VDS in this project.
 
 1. Run `npx -y @teurons/vds@latest init vds-workspace`. It creates the
-   capabilities, flows and scenarios folders, a VDS.md guide and a .vds.json.
+   capabilities, journeys and scenarios folders, a VDS.md guide and a .vds.json.
    If it says a workspace already exists, stop and tell me what it found.
 2. Add `"vds": "vds"` to package.json scripts and @teurons/vds to
    devDependencies if this project uses npm, pnpm or yarn. Otherwise skip this.
@@ -51,25 +51,40 @@ Upgrade VDS in this project.
 ```sh
 npx @teurons/vds init [folder]       # start a workspace (never overwrites one)
 npx @teurons/vds check [folder]      # print every problem; exit 1 if any
-npx @teurons/vds index [folder]      # print the index: every flow and rule, one line each
+npx @teurons/vds index [folder]      # print the index: every journey and rule, one line each
 npx @teurons/vds run local [folder]  # the studio on localhost, with an MCP for your AI app at /mcp
-npx @teurons/vds built <flow> [folder]       # mark a flow's current version built, with who and when
-npx @teurons/vds evidence <report> [folder]  # record a test run (JUnit XML or Vitest JSON) as evidence
+npx @teurons/vds built <journey> [folder]    # mark a journey's current version built, with who and when
+npx @teurons/vds evidence <report> [folder]  # record a test run (JUnit XML or Vitest/Jest JSON) as evidence
 npx @teurons/vds changelog [--since x.y.z]   # print the changelog, or only the versions after x.y.z
 npx @teurons/vds update [folder]     # install the newest vds, migrate the workspace, refresh VDS.md, print what changed
+npx @teurons/vds --help              # the same list; --version prints the installed version
 ```
 
 `folder` defaults to the current folder, or to `vds-workspace` inside it when the current folder
 is not a workspace itself. So from your project root, `vds check` checks `vds-workspace`.
 
+`check` and `index` stop with a message when the folder is missing or holds no workspace.
+`index` prints the index and, on stderr, how many files it could not read.
+
+### Where `vds init` puts the workspace
+
+- `vds init <folder>` makes the workspace in that folder.
+- `vds init` with no folder uses the current folder when it is empty, and `vds-workspace` inside it
+  when the folder already has files (a project root).
+- `vds init` refuses, and changes nothing, when the folder already holds a workspace, an old
+  `flows/` folder (run `vds update` for that) or, with no folder named, a `vds-workspace` folder.
+
+`vds evidence` writes nothing and exits 1 when the file is neither a JUnit XML nor a Vitest/Jest
+JSON report, or has no tests in it.
+
 ## A workspace
 
 ```text
 vds-workspace/
-  VDS.md                      how agents and people work on this spec
+  VDS.md                      how agents and people work on this spec, with every file format
   .vds.json                   local settings: the port the local studio uses
   capabilities/<CODE>.yaml    rules, each one EARS statement with an id like ONB-01
-  flows/<id>.yaml             versioned flows whose steps point at rule ids
+  journeys/<id>.yaml          versioned journeys whose states point at rule ids
   scenarios/<RULE-ID>.feature Gherkin scenarios, one file per rule
 ```
 

package/dist/CHANGELOG.md

@@ -11,6 +11,35 @@ Each release has two parts:
   and the one it installed.
   "None" means there is nothing to do.
 
+## 0.0.9 (2026-11-03)
+
+### What changed
+
+- Checker, versions and compare fixes:
+  
+  - vds check refuses a scenario file that is not Gherkin (no Feature line or no Scenario), a scenario file for a rule the workspace does not have, a scenario whose @REQ tag differs from its file name, and a capability file whose code differs from its file name.
+  - vds built (and vds_mark_built) now records a fingerprint of every rule the journey uses. A rule edited later on disk, in an editor or by git pull, shows the journey as changed in the studio and the index, naming the rules, even when nobody bumped the version. Older built records behave as before.
+  - The studio compare view marks the steps that use a rule changed since the build as "rule changed", with the rule's plain line. A compare with versions that do not exist says which versions exist instead of showing a not-found page.
+  - The index line for a journey says built, not built, or changed with the rule ids; a journey that uses no rules says "uses no rules".
+  - Changing a journey file keeps its own style: untouched lines stay as written, and new built and changes blocks are written in block style.
+- Command-line and guide fixes:
+  
+  - VDS.md now holds the full file formats for capabilities, journeys and scenarios with one checked example of each, and says how to write: through the local MCP (vds_write, vds_delete) when vds run local is running, or by editing files and running vds check. The MCP instructions list the formats too.
+  - vds check and vds index on a folder that is missing or holds no workspace now fail with a message that names the folder and suggests vds init.
+  - vds init without a folder uses the current folder when it is empty and vds-workspace when the folder has files; it refuses when vds-workspace already exists, and when the folder has an old flows folder it says to run vds update. It lists what it created and the next steps.
+  - vds evidence refuses a file that is not a JUnit XML or Vitest/Jest JSON report, or has no tests, and writes nothing. Evidence file names use local time.
+  - vds index says on stderr how many files could not be read.
+  - vds --help, help, -h, --version and -v work; an unknown command prints the usage on stderr and exits 2.
+  - vds built with no journey prints its usage; vds changelog --since a version that is not out says nothing is newer; vds update offline says it could not reach npm and names the registry.
+  - The README says journeys everywhere and lists every command.
+- internal: the tools run over a store, so the hosted app can share them
+
+### Agent steps
+
+- Run vds check: it now refuses scenario files that are not Gherkin, scenarios for rules that do not exist, and capability files whose code differs from the file name. Fix what it lists.
+- Run vds built <journey> again for journeys you have built, so later rule edits show as changes.
+- Read VDS.md again: it now has the full file formats.
+
 ## 0.0.8 (2026-11-03)
 
 ### What changed