@teurons/vds 0.0.5 → 0.0.7

package/README.md

@@ -13,7 +13,7 @@ Copy this prompt into Claude Code, Codex or any coding agent, run from the root
 ```text
 Set up VDS in this project.
 
-1. Run `npx -y @teurons/vds init vds-workspace`. It creates the
+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.
    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
@@ -25,16 +25,38 @@ Set up VDS in this project.
    vds-workspace/VDS.md before changing it; run `vds index vds-workspace`
    first and `vds check vds-workspace` before finishing.
 5. Run `npx @teurons/vds check vds-workspace` and confirm it prints valid.
+   Then tell me to run `npx @teurons/vds run local` to open the studio, and
+   offer to connect yourself to its MCP at the address it prints.
 6. Tell me what you created and changed, file by file.
 ```
 
+## Upgrade with your AI agent
+
+Copy this prompt into your coding agent, run from the root of your project:
+
+```text
+Upgrade VDS in this project.
+
+1. Run `npx -y @teurons/vds@latest update`. It installs the newest vds,
+   migrates the workspace, refreshes VDS.md and prints the changelog for
+   every version it crossed.
+2. Do every agent step it printed, in order, oldest version first.
+3. Read vds-workspace/VDS.md again.
+4. Run `npx @teurons/vds check vds-workspace` and confirm it prints valid.
+5. Tell me which versions you crossed and which files changed.
+```
+
 ## Commands
 
 ```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 update [folder]  # install the newest vds, refresh VDS.md
+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 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 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
 ```
 
 `folder` defaults to the current folder, or to `vds-workspace` inside it when the current folder
@@ -45,7 +67,7 @@ is not a workspace itself. So from your project root, `vds check` checks `vds-wo
 ```text
 vds-workspace/
   VDS.md                      how agents and people work on this spec
-  .vds.json                   local settings: the port the local studio will use (coming soon)
+  .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
   scenarios/<RULE-ID>.feature Gherkin scenarios, one file per rule

package/dist/CHANGELOG.md

@@ -0,0 +1,114 @@
+# Changelog
+
+Every release of `@teurons/vds`, newest first.
+
+Each release has two parts:
+
+- **What changed**, written for people.
+- **Agent steps**, written for the AI agent that maintains a workspace.
+  They list what to do after upgrading to this version.
+  `vds update` prints both parts for every version between the one you had
+  and the one it installed.
+  "None" means there is nothing to do.
+
+## 0.0.7 (2026-11-02)
+
+### What changed
+
+- `vds evidence <report>` records a test run (JUnit XML or Vitest JSON) as evidence for the scenarios
+  whose ids appear in test names. The studio ticks the steps that have passing evidence.
+- Flows have versions. When a rule a flow depends on changes, the flow's version changes with it.
+  `vds built <flow>` marks a flow's current version built, with who and when. The studio shows a
+  compare view between versions, with the flows a rule change touched listed first.
+- `vds update` now prints the changelog for every version it crosses, with the agent steps marked,
+  and runs code migrations for any version that changes the workspace format, printing each file it
+  moves or rewrites. `vds changelog [--since x.y.z]` prints the changelog on demand. Releases are
+  versioned and their changelog entries are written with Changesets.
+
+### Agent steps
+
+- Name each test after its scenario id, for example `CLI-07-01 older version installed`.
+- After upgrading, run your test suite with a JUnit or Vitest JSON reporter and record it with `vds evidence <report-file>`.
+- Run `vds built <flow>` for each flow you have already built, so changes after this point show up as impact.
+- Run `npx -y @teurons/vds@latest update` and do every agent step it prints, oldest version first.
+
+## 0.0.6 (2026-11-03)
+
+### What changed
+
+- `vds run local` starts the studio on your machine, on the port in
+  `.vds.json`, or the next free port if that one is taken.
+- The studio shows the flows, each flow page, its steps and rules, and the
+  product-wide rules. It redraws within a second of a file changing, and it
+  shows the checker's problems on every page without stopping.
+- An MCP at `http://localhost:<port>/mcp` lets your AI app read and write the
+  workspace. The checker runs on every write and refuses a write that adds a
+  problem, naming each one.
+- Plain lines drop every "SHALL", including one after a comma.
+- `vds init` prints the command and the address for the studio.
+
+### Agent steps
+
+- Offer to connect yourself to the local MCP at the address `vds run local`
+  prints. Once connected, write through `vds_write` and `vds_delete` rather
+  than editing spec files directly, so the checker guards each change.
+
+## 0.0.5 (2026-11-03)
+
+### What changed
+
+- `vds check`, `vds index` and `vds update` with no folder named use the
+  current folder if it is a workspace, else its `vds-workspace` folder.
+
+### Agent steps
+
+- In the project's AGENTS.md or CLAUDE.md, `vds check vds-workspace` can
+  become `vds check` when run from the project root. Optional.
+
+## 0.0.4 (2026-11-03)
+
+### What changed
+
+- `vds update` installs the newest version and refreshes VDS.md.
+- VDS.md now starts with a line naming the version that wrote it.
+
+### Agent steps
+
+- Run `npx @teurons/vds@latest update` once. It adds the version line to
+  VDS.md. Read the new VDS.md afterwards.
+
+## 0.0.3 (2026-11-03)
+
+### What changed
+
+- Every release is published as `latest`, so a plain `npx @teurons/vds`
+  gets the newest version.
+- The README carries a set-up prompt for AI agents.
+
+### Agent steps
+
+None.
+
+## 0.0.2 (2026-11-03)
+
+### What changed
+
+- `vds init` starts a workspace: capabilities, flows and scenarios folders,
+  a VDS.md guide for agents, and a `.vds.json` holding the studio port. It
+  never overwrites an existing workspace.
+- The published package no longer carries paths from the build machine.
+
+### Agent steps
+
+None.
+
+## 0.0.1 (2026-11-02)
+
+### What changed
+
+- `vds check` checks every capability, flow and scenario in a folder.
+- `vds index` prints the workspace's index, one line per flow and rule.
+
+### Agent steps
+
+None.