@execuro-sw-ecosystem/sw-ecosystem-agentic-harness 0.1.3 → 0.1.4

package/CHANGELOG.md

@@ -7,6 +7,19 @@ release.
 
 ## [Unreleased]
 
+## [0.1.4] - 2026-09-17
+
+### Added
+
+- **`sw-setup` gained a twelfth readiness row, "Package updates".** It checks
+  whether the harness, the Specs Editor and the Tender Discovery Tool are at
+  their target versions (the harness at npm's latest, each editor at its own
+  `extra_components[].version` pin, never npm's latest) via three
+  `npm view` lookups, each with a 10-second timeout — a failed or timed-out
+  lookup reports "could not check" rather than failing the row. Folds into
+  step 3's single question; never blocks readiness. The KB MCP keeps its
+  existing row (registered as `@latest`, nothing to update).
+
 ## [0.1.3] - 2026-09-17
 
 ### Changed

package/content/AGENTS.md

@@ -16,7 +16,7 @@ procedure, and the detail lives in `reference/*.md` files beside its
 | `sw-discover-tender` | Analyse a client tender (RFP, RFI or RFQ) for a Shopware 6 project into one markdown sidecar, <source basename>-analysis.md. |
 | `sw-document-feature` | Document one Shopware project feature into the LLM-wiki under docs/project-wiki/ — one feature page per surface (administration/ and/or storefront/), the "why" row in the domain index, ADR pages only promoted from the WIP ADR files sw-design-solution extracted into specs/ once they are accepted and built (with an organised table of contents) or provided by the user (never invented). |
 | `sw-implement-feature` | Implement a feature from its technical spec (specs/NNNN-slug-spec.md, written by sw-design-solution) following TDD — tests first per acceptance criterion, then the implementation, fixing until every relevant test passes (including that AC's own acceptance/e2e test, run immediately, not deferred), running Shopware's own shopware-cli fixers/static-analysis per AC to conform to Shopware's coding standards as code is written rather than after the fact. |
-| `sw-setup` | Print one environment-readiness table for the project's development/test setup — vendor/, Node, the editor CLIs, shopware-cli, the KB MCP, the acceptance-test project, Playwright browsers, its .env, per-plugin test scaffolding, the project wiki and `.gitignore`, plus the installer CLI's own configuration/drift status. |
+| `sw-setup` | Print one environment-readiness table for the project's development/test setup — vendor/, Node, the editor CLIs, shopware-cli, the KB MCP, the acceptance-test project, Playwright browsers, its .env, per-plugin test scaffolding, the project wiki, `.gitignore` and whether the SW AH npm packages are current, plus the installer CLI's own configuration/drift status. |
 | `sw-verify-feature` | Verify a feature implementation against its technical spec (specs/NNNN-slug-spec.md) by running three independent verifiers in parallel — AC test coverage/health, architecture/guideline compliance, and code quality/static analysis — then cross-checking their verdicts into one final per-AC pass/not pass/partly report. |
 | `sw-verify-feature-ac-tests` | Verify that a feature's acceptance criteria are backed by tests that actually exist, actually pass, and actually test what their name/comment/PHPDoc claims. |
 | `sw-verify-feature-architecture` | Verify that a feature's implementation matches the architectural decisions its spec made, and complies with Shopware's own Core conventions plus any written Project guidelines this repo defines. |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@execuro-sw-ecosystem/sw-ecosystem-agentic-harness",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Shopware 6 agentic harness: sw-* skills and sub-agents, plus an installer that writes them into Claude Code, Codex, GitHub Copilot and Cursor.",
   "license": "MIT",
   "author": "Execuro UG (haftungsbeschränkt)",

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "sw-ecosystem-agentic-harness",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Shopware 6 agentic harness: sw-* skills and sub-agents for requirements, specs, implementation, verification and documentation, with an installer CLI that writes them into Claude Code, Codex, GitHub Copilot and Cursor. The knowledge-base MCP and the editor tools are separate npm packages.",
   "author": {
     "name": "Execuro UG (haftungsbeschränkt)",

package/skills/sw-setup/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sw-setup
-description: Print one environment-readiness table for the project's development/test setup — vendor/, Node, the editor CLIs, shopware-cli, the KB MCP, the acceptance-test project, Playwright browsers, its .env, per-plugin test scaffolding, the project wiki and `.gitignore`, plus the installer CLI's own configuration/drift status. Stops when every row is ticked. When rows are missing, asks one yes/no question and delegates the fix to the installer CLI. Use when asked to set up the project, check if the environment is ready, or bootstrap the tests. Never designs, implements or verifies a feature itself — that's sw-design-solution, sw-implement-feature and sw-verify-feature, which call this skill first. Never writes a host configuration file itself — that's the installer CLI.
+description: Print one environment-readiness table for the project's development/test setup — vendor/, Node, the editor CLIs, shopware-cli, the KB MCP, the acceptance-test project, Playwright browsers, its .env, per-plugin test scaffolding, the project wiki, `.gitignore` and whether the SW AH npm packages are current, plus the installer CLI's own configuration/drift status. Stops when every row is ticked. When rows are missing, asks one yes/no question and delegates the fix to the installer CLI. Use when asked to set up the project, check if the environment is ready, or bootstrap the tests. Never designs, implements or verifies a feature itself — that's sw-design-solution, sw-implement-feature and sw-verify-feature, which call this skill first. Never writes a host configuration file itself — that's the installer CLI.
 when_to_use: Trigger phrases — "set up the project", "is the environment ready", "bootstrap the tests", "sw-setup".
 allowed-tools: Read Glob Grep AskUserQuestion Skill Bash mcp__ShopwareDevKnowledgeBase__kb_status Bash(npx -y @execuro-sw-ecosystem/sw-ecosystem-agentic-harness@latest *)
 ---
@@ -47,8 +47,9 @@ It prints one JSON object (`ok`, `next_step`, `help`, and its own
 `hosts[]`/`drift[]` configuration state). Alongside it, run every
 environment row's check from `reference/rows.md` in this skill's directory —
 read-only, seconds each: file/directory existence, one version command, one
-`kb_status` call. Never write, never install, never ask a question in this
-step.
+`kb_status` call, three `npm view` registry lookups (Package updates row) —
+the one part of step 1 that touches the network, so it is the slow part.
+Never write, never install, never ask a question in this step.
 
 Print one checkbox list, one line per row — the environment rows first, then
 one line per configuration item the CLI's `hosts[]`/`drift[]` reports:
@@ -65,6 +66,7 @@ one line per configuration item the CLI's `hosts[]`/`drift[]` reports:
 - [ ] ATS env — tests/acceptance/.env missing
 - [x] Plugin tests — AhCheckout: phpunit + jest ok
 - [ ] Project wiki — docs/project-wiki/ missing
+- [ ] Package updates — harness 0.1.0 → 0.1.3, Specs Editor not installed
 - [ ] Installer config — .mcp.json entry: drift (from CLI status)
 ```
 
@@ -91,8 +93,10 @@ npx -y @execuro-sw-ecosystem/sw-ecosystem-agentic-harness@latest plan
 
 List the concrete steps in plain words: environment-row fixes in order
 (vendor/ → Visual editors → KB MCP → Acceptance-test project →
-Playwright browsers → ATS env → Plugin tests → Project wiki), then the CLI's
-planned configuration changes last. Skip any row already ticked.
+Playwright browsers → ATS env → Plugin tests → Project wiki → Package
+updates), then the CLI's planned configuration changes last — Package
+updates comes immediately before those, since updating the harness is what
+may change them. Skip any row already ticked.
 
 Ask exactly one question: "Do this and that?" with the steps spelled out in
 plain words (no command dump). Ask the user with a structured question tool
@@ -138,7 +142,7 @@ line:
 
 ## Reference files
 
-`reference/rows.md` in this skill's directory — the eleven environment rows:
+`reference/rows.md` in this skill's directory — the twelve environment rows:
 check command(s), what "ticked" means, the fix steps verbatim from the
 guideline, and which skills the row blocks. Host configuration state (what
 gets installed into `.mcp.json`, permissions, `.gitignore`) is not in this

package/skills/sw-setup/reference/rows.md

@@ -1,6 +1,6 @@
 # Readiness rows
 
-Eleven environment rows. Each: check (read-only), what "ticked" means, the fix
+Twelve environment rows. Each: check (read-only), what "ticked" means, the fix
 (only run on approval, in this order), and which skills the row blocks when
 unticked. Host configuration files (`.mcp.json` entries, `.gitignore` lines,
 permission grants) are not rows here — the installer CLI owns them and
@@ -218,3 +218,42 @@ So this row never blocks readiness. It asks.
   project, verify-ac-tests screenshots). Idempotent — safe to re-run.
 - **Blocks:** nothing directly; unticked means the next `git status` will
   show generated/secret files as untracked.
+
+## 12. Package updates (optional)
+
+The KB MCP is excluded — it is registered as `@latest` and re-resolves on
+every host launch, so there is nothing to update (see row 5). This row covers
+only the three versioned packages: the harness itself, the Specs Editor and
+the Tender Discovery Tool.
+
+This row never blocks readiness. It folds into step 3's single question.
+
+- **Check:** three `npm view <pkg> version` calls, each with a 10-second
+  timeout — `npm view @execuro-sw-ecosystem/sw-ecosystem-agentic-harness
+  version`, `npm view @execuro-sw-ecosystem/sw-specs-editor version`,
+  `npm view @execuro-sw-ecosystem/sw-tender-discovery-tool version`. Installed
+  versions come from three different places: the harness's from
+  `installed_version` in the `status` JSON the skill already ran in step 1
+  (from the lock file); the Specs Editor's from `version` in
+  `node_modules/@execuro-sw-ecosystem/sw-specs-editor/package.json`; the
+  Tender Discovery Tool's the same way, in its own `node_modules` path. A
+  failed or timed-out `npm view` call reports "could not check" for that
+  package only — never an unticked row, never an error, never a blocked run.
+  No network is a normal condition, not a fault.
+- **Ticked:** all three packages at their target version — the harness at
+  npm's latest, each editor at the pin its own `status` output names
+  (`extra_components[].version`), not at npm's latest.
+- **Unticked:** one line per stale package, `installed → available` — e.g.
+  `harness 0.1.1 → 0.1.3`, `Specs Editor 0.1.0 → 0.1.0 (pinned)` when current.
+  An editor whose npm latest is ahead of the pin is a harness-release lag,
+  not a missing update: report it, but do not offer to install that newer
+  version — only a newer harness can raise the pin.
+- **Fix:** update the harness first — a newer harness may carry newer pins:
+  `npx -y @execuro-sw-ecosystem/sw-ecosystem-agentic-harness@latest install`.
+  That command rewrites the installed `sw-setup` skill itself, so the newer
+  skill takes effect on the next run — which step 3 already causes by
+  re-running step 1. Re-read the new `status` output, then for each stale
+  editor run the same `npm i -D <package>@<version>` shape row 3's Fix uses,
+  with `<package>` and `<version>` taken from that editor's own
+  `extra_components[]` entry in the re-read `status`.
+- **Blocks:** nothing. Out of date is not broken.