@execuro-sw-ecosystem/sw-ecosystem-agentic-harness 0.1.7 → 0.1.9

package/lib/hosts.mjs

@@ -10,17 +10,17 @@
 import { homedir } from 'node:os';
 import { join } from 'node:path';
 import {
-  agents, agentsMd, claudeSettings, mcpServers, LOCK_DIR, PKG_ROOT, skills,
+  agents, agentsMd, claudeSettings, lockDir, lockNeedsGitignore, mcpServers, PKG_ROOT, skills,
 } from './content.mjs';
 import { abs, isDir, isWritable, walk } from './fsx.mjs';
 import { renderTomlTable, tomlTableExists, findFence } from './merge.mjs';
 import { readTextMaybe } from './fsx.mjs';
-import { EXTRA_COMPONENTS } from './extra-components.mjs';
 
 export const AGENTS = ['claude-code', 'codex', 'copilot', 'cursor'];
 
-/** Where each host reads its skills from — the base every skill-copy and
- * extra-component skill-copy action is rooted at. */
+/** Where each host reads its skills from — the base every skill copy is
+ * rooted at, and the directory `sw-setup` hands to an editor package's own
+ * `install-skill --target`. */
 export const SKILL_DIR = {
   'claude-code': '.claude/skills',
   codex: '.agents/skills',
@@ -103,21 +103,6 @@ function skillActions(host, targetBase) {
   return out;
 }
 
-/**
- * One `skill-copy` action per optional extra component. The `skill:`
- * segment (not `file:`) keeps these ids from colliding, or deduping,
- * against a shipped `file-copy` action at the same path.
- */
-function extraComponentActions(host, targetBase) {
-  return EXTRA_COMPONENTS.map((c) => {
-    const target = `${targetBase}/${c.id}/SKILL.md`;
-    return {
-      id: `${host}:skill:${target}`, host, kind: 'skill-copy',
-      component: c.id, package: `${c.pkg}@${c.version}`, target,
-    };
-  });
-}
-
 function agentActions(host, targetBase, pick, ext) {
   return agents().map((agent) => {
     const target = `${targetBase}/${agent.name}${ext}`;
@@ -147,11 +132,17 @@ function agentsMdAction(host) {
   };
 }
 
-/** The lock file describes one machine's install, so it is gitignored. */
-function gitignoreAction(host) {
+/**
+ * The lock describes one machine's install, so it must not be tracked. Under
+ * `var/` the `shopware/core` Flex recipe already ignores it (`/var/*`), so
+ * there is nothing to write and we do not touch the user's `.gitignore` at
+ * all. Only the fallback location needs the managed line.
+ */
+function gitignoreAction(host, ctx) {
+  if (!lockNeedsGitignore(ctx.root)) return null;
   return {
     id: 'shared:text:.gitignore#lock', host, kind: 'text-fence',
-    target: '.gitignore', block: 'lock', syntax: 'gitignore', body: `${LOCK_DIR}/`,
+    target: '.gitignore', block: 'lock', syntax: 'gitignore', body: `${lockDir(ctx.root)}/`,
   };
 }
 
@@ -159,7 +150,6 @@ function planClaude(ctx) {
   const host = 'claude-code';
   const out = [
     ...skillActions(host, SKILL_DIR[host]),
-    ...(ctx.extraComponents === false ? [] : extraComponentActions(host, SKILL_DIR[host])),
     ...agentActions(host, '.claude/agents', 'claude', '.md'),
     ...mcpJsonActions(host, '.mcp.json', 'mcpServers', ctx),
   ];
@@ -176,8 +166,8 @@ function planClaude(ctx) {
       target: '.claude/settings.json', pointer: setting.pointer, op: 'set', value: setting.value,
     });
   }
-  out.push(gitignoreAction(host));
-  return out;
+  out.push(gitignoreAction(host, ctx));
+  return out.filter(Boolean);
 }
 
 function planCodex(ctx) {
@@ -185,7 +175,6 @@ function planCodex(ctx) {
   const out = [
     // Codex discovers skills from `.agents/skills`, never `.claude/skills`.
     ...skillActions(host, SKILL_DIR[host]),
-    ...(ctx.extraComponents === false ? [] : extraComponentActions(host, SKILL_DIR[host])),
     ...agentActions(host, '.codex/agents', 'codex', '.toml'),
   ];
 
@@ -222,15 +211,14 @@ function planCodex(ctx) {
     },
   });
 
-  out.push(agentsMdAction(host), gitignoreAction(host));
-  return out;
+  out.push(agentsMdAction(host), gitignoreAction(host, ctx));
+  return out.filter(Boolean);
 }
 
 function planCopilot(ctx) {
   const host = 'copilot';
   const out = [
     ...skillActions(host, SKILL_DIR[host]),
-    ...(ctx.extraComponents === false ? [] : extraComponentActions(host, SKILL_DIR[host])),
     ...agentActions(host, '.github/agents', 'copilot', '.agent.md'),
     // Copilot CLI reads `.mcp.json`; VS Code reads `.vscode/mcp.json` under the
     // incompatible `servers` key. Both, or the two surfaces disagree.
@@ -239,9 +227,9 @@ function planCopilot(ctx) {
       ...a, id: a.id.replace('shared:', 'copilot:'),
     })),
     agentsMdAction(host),
-    gitignoreAction(host),
+    gitignoreAction(host, ctx),
   ];
-  return out;
+  return out.filter(Boolean);
 }
 
 function planCursor(ctx) {
@@ -257,12 +245,26 @@ function planCursor(ctx) {
     || (isDir(abs(ctx.root, '.claude/skills')) && isDir(abs(ctx.root, '.claude/agents')));
   if (!claudeTrees) {
     out.push(...skillActions(host, SKILL_DIR[host]));
-    if (ctx.extraComponents !== false) out.push(...extraComponentActions(host, SKILL_DIR[host]));
     out.push(...agentActions(host, '.cursor/agents', 'claude', '.md'));
   }
   out.push(...mcpJsonActions(host, '.cursor/mcp.json', 'mcpServers', ctx));
-  out.push(agentsMdAction(host), gitignoreAction(host));
-  return out;
+  out.push(agentsMdAction(host), gitignoreAction(host, ctx));
+  return out.filter(Boolean);
+}
+
+/**
+ * The skills directory a host actually reads, for `status` to report — the
+ * one `sw-setup` passes to an editor package's `install-skill --target`.
+ * Cursor is the exception: when the Claude trees are present it reads those,
+ * so naming `.cursor/skills` would put an editor skill where Cursor never
+ * looks.
+ */
+export function skillsDir(id, ctx) {
+  if (id === 'cursor'
+    && isDir(abs(ctx.root, '.claude/skills')) && isDir(abs(ctx.root, '.claude/agents'))) {
+    return SKILL_DIR['claude-code'];
+  }
+  return SKILL_DIR[id];
 }
 
 /** What is already installed for a host, for `status`. */

package/lib/lock.mjs

@@ -1,4 +1,6 @@
-// The lock file: `.sw-ai-sdk/harness.lock.json` in the host repository.
+// The lock file: `var/sw-ai-sdk/harness.lock.json` in the host repository, or
+// `.sw-ai-sdk/harness.lock.json` in a root that has no `var/` (see
+// `lockDir()` in content.mjs).
 //
 // This is the ownership record. JSON config files have no comments, so nothing
 // in `.mcp.json` can tell us who wrote an entry — the lock does, by content
@@ -6,15 +8,29 @@
 // removal is always narrower than addition, and which rules the user declined
 // so we never ask twice.
 //
-// It is gitignored by default: it describes one machine's install, not the
-// project.
+// It is never tracked: it describes one machine's install, not the project.
+// Under `var/` the Shopware recipe already ignores it; in the fallback
+// location the installer writes the managed `.gitignore` line itself.
+//
+// A lock left at the old `.sw-ai-sdk/` path is read and rewritten to the new
+// one on the next write, so an existing install never looks fresh.
 
-import { LOCK_FILE, SUPPORTED_CONTENT, CONTENT_VERSION, PKG_NAME, PKG_VERSION } from './content.mjs';
-import { abs, readTextMaybe, writeAtomic } from './fsx.mjs';
+import {
+  LOCK_FILE, SUPPORTED_CONTENT, CONTENT_VERSION, PKG_NAME, PKG_VERSION, lockFile,
+} from './content.mjs';
+import {
+  abs, ensureDir, exists, readTextMaybe, removeDirIfEmpty, removeFile, writeAtomic,
+} from './fsx.mjs';
+import { dirname } from 'node:path';
 
 export class LockVersionError extends Error {}
 
 export function lockPath(root) {
+  return abs(root, lockFile(root));
+}
+
+/** The pre-`var/` location, kept only so an existing install can be migrated. */
+export function legacyLockPath(root) {
   return abs(root, LOCK_FILE);
 }
 
@@ -41,19 +57,26 @@ export function empty(scope) {
 
 /** Read the lock, or null when absent. Throws on a layout we cannot undo. */
 export function read(root, scope) {
-  const found = readTextMaybe(lockPath(root));
+  // The new location first; a lock still at the old one is read here and
+  // rewritten by `write()`.
+  let where = lockFile(root);
+  let found = readTextMaybe(lockPath(root));
+  if (found === null) {
+    found = readTextMaybe(legacyLockPath(root));
+    where = LOCK_FILE;
+  }
   if (found === null) return null;
   let lock;
   try {
     lock = JSON.parse(found.text);
   } catch {
     throw new LockVersionError(
-      `${LOCK_FILE} is not valid JSON. Move it aside and re-run apply to rebuild it.`,
+      `${where} is not valid JSON. Move it aside and re-run apply to rebuild it.`,
     );
   }
   if (!SUPPORTED_CONTENT.includes(lock.content_version)) {
     throw new LockVersionError(
-      `${LOCK_FILE} records content_version ${lock.content_version}, which this ` +
+      `${where} records content_version ${lock.content_version}, which this ` +
         `version of ${PKG_NAME} (${PKG_VERSION}) does not understand.`,
     );
   }
@@ -68,7 +91,16 @@ export function read(root, scope) {
 export function write(root, lock) {
   const next = { ...lock, updated_at: new Date().toISOString() };
   if (!next.installed_at) next.installed_at = next.updated_at;
-  writeAtomic(lockPath(root), `${JSON.stringify(next, null, 2)}\n`);
+  const target = lockPath(root);
+  ensureDir(dirname(target));
+  writeAtomic(target, `${JSON.stringify(next, null, 2)}\n`);
+  // Migration: one lock, at one path. Writing the new one and leaving the old
+  // would make an older CLI, or our own `read()`, resurrect a stale record.
+  const legacy = legacyLockPath(root);
+  if (legacy !== target && exists(legacy)) {
+    removeFile(legacy);
+    removeDirIfEmpty(dirname(legacy));
+  }
   return next;
 }
 

package/lib/render.mjs

@@ -197,8 +197,9 @@ function renderApply(body, opts, t) {
   const s = body.summary ?? {};
   const changed = (s.created ?? 0) + (s.updated ?? 0);
   const problems = issues(body);
+  const migrated = body.migrated ?? [];
 
-  if (changed === 0 && problems.length === 0) {
+  if (changed === 0 && problems.length === 0 && migrated.length === 0) {
     // ONE line. Nothing changed means nothing to restart and nothing to read.
     return `${t.green('✓')} Shopware agentic harness: already up to date — nothing to change.\n`;
   }
@@ -207,13 +208,18 @@ function renderApply(body, opts, t) {
   const changedIds = groups.map((g) => g.id).filter((id) => id !== SHARED);
   const verb = (s.updated ?? 0) === 0 ? 'Installed' : 'Updated';
   const lines = [];
-  lines.push(changed
-    ? `${t.green('✓')} ${verb} the Shopware agentic harness.`
-    : `${t.yellow('!')} Nothing was written — see below.`);
+  if (changed) lines.push(`${t.green('✓')} ${verb} the Shopware agentic harness.`);
+  else if (problems.length) lines.push(`${t.yellow('!')} Nothing was written — see below.`);
+  // Only tidy-up ran: the install itself was already current.
+  else lines.push(`${t.green('✓')} Shopware agentic harness: already up to date.`);
   if (groups.length) {
     lines.push('');
     lines.push(...groupLines(groups, opts, t));
   }
+  if (migrated.length) {
+    lines.push('');
+    for (const m of migrated) lines.push(`  ${t.dim('·')} ${m.target}: ${m.detail}`);
+  }
   if (problems.length) {
     lines.push('');
     lines.push(...issueLines(problems, t));
@@ -292,11 +298,6 @@ function renderStatus(body, opts, t) {
     lines.push(...issueLines(problems, t));
   }
 
-  const missing = (body.extra_components ?? []).filter((c) => !c.available && c.install);
-  if (missing.length) {
-    lines.push('');
-    lines.push(`  ${t.dim('Optional add-ons not installed:')} ${missing.map((c) => c.install).join(', ')}`);
-  }
   return `${lines.join('\n')}\n`;
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@execuro-sw-ecosystem/sw-ecosystem-agentic-harness",
-  "version": "0.1.7",
+  "version": "0.1.9",
   "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.7",
+  "version": "0.1.9",
   "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-design-requirements/SKILL.md

@@ -3,7 +3,7 @@ name: sw-design-requirements
 description: Turn a briefing — chat text or a file, covering one or more features — into a lean, business-only PRD stored as specs/NNNN-slug.md. Runs an interactive clarification loop for the requirement gaps and inconsistencies that actually change the requirements, then scores a weighted confidence %. Use when asked to write, draft, refine, continue, or score a PRD / requirements doc / feature brief for this Shopware project. Never writes a tech spec or answers architecture questions — that's sw-design-solution.
 when_to_use: Trigger phrases — "write a PRD", "draft requirements", "turn this brief into a PRD", "continue PRD 0003", "is this PRD ready for specification", "raise the confidence on this PRD", "requirements for <feature>".
 argument-hint: '[file-path | briefing text | specs/NNNN-slug.md to continue] [--editor]'
-allowed-tools: Read Write Edit Glob Grep AskUserQuestion Agent Skill Bash(ls *) Bash(mkdir -p specs) Bash(npx -y @execuro-sw-ecosystem/sw-specs-editor@0.1.0 *) mcp__ShopwareDevKnowledgeBase__list_docs mcp__ShopwareDevKnowledgeBase__grep_docs mcp__ShopwareDevKnowledgeBase__read_doc mcp__ShopwareDevKnowledgeBase__kb_status
+allowed-tools: Read Write Edit Glob Grep AskUserQuestion Agent Skill Bash(ls *) Bash(mkdir -p specs) Bash(npx -y @execuro-sw-ecosystem/sw-specs-editor@latest *) mcp__ShopwareDevKnowledgeBase__list_docs mcp__ShopwareDevKnowledgeBase__grep_docs mcp__ShopwareDevKnowledgeBase__read_doc mcp__ShopwareDevKnowledgeBase__kb_status
 
 ---
 

package/skills/sw-design-requirements/reference/editor-gate.md

@@ -2,7 +2,7 @@
 
 Runs before the `--editor` hand-off (step 0). The Specs Editor is an **optional** add-on: it is not part of this plugin, and a host that never installed it is a supported, normal setup. `sw-setup` offers to install it.
 
-What is checked is the **skill**, `sw-specs-editor`, because that is what `sw-setup` installs and what the hand-off calls. The skill brings the CLI with it — it invokes `npx -y @execuro-sw-ecosystem/sw-specs-editor@0.1.0`, which fetches the package on first use.
+What is checked is the **skill**, `sw-specs-editor`, because that is what `sw-setup` installs and what the hand-off calls. The skill brings the CLI with it — it invokes `npx -y @execuro-sw-ecosystem/sw-specs-editor@latest`, which fetches the package on first use.
 
 Check: is the `sw-specs-editor` skill available in this session?
 

package/skills/sw-design-requirements/reference/editor-mode.md

@@ -8,8 +8,8 @@ Invoked as `<path> --editor-session <url> --batch <batch.json>` — one note bat
 - **Full pass on request only.** A review request ("check the whole PRD", "reconcile") runs the full flow: step 2, §11 gap review, missing options/marks/notes filled. Otherwise touched questions get options.
 - **Scoped agent runs.** Spawn `sw-product-manager`/`sw-shopware-architect` only when a note touches feasibility, §10, or a §11 block changes (one brief per run); else edit, anchor, log alone.
 - **Preserve on every write:** status tags on item ids (`- **FR-3** [done] …`, also `AC-n`/`BR-n`), the `Diagram:` line, the §11 question blocks and ticks. Rewrite in place; never regenerate.
-- **Diagrams.** Domain diagram: `specs/NNNN-slug.domain.graph.json` (business concepts only). Write/update, run `npx -y @execuro-sw-ecosystem/sw-specs-editor@0.1.0 diagram specs/NNNN-slug.domain.graph.json specs/NNNN-slug.domain.excalidraw`, ensure §4 carries `Diagram: specs/NNNN-slug.domain.excalidraw`; never write `.excalidraw` directly, first request only.
-- **Progress.** Before each step, before/after each spawn: `npx -y @execuro-sw-ecosystem/sw-specs-editor@0.1.0 emit progress "<step>" --batch <id> --doc prd`.
+- **Diagrams.** Domain diagram: `specs/NNNN-slug.domain.graph.json` (business concepts only). Write/update, run `npx -y @execuro-sw-ecosystem/sw-specs-editor@latest diagram specs/NNNN-slug.domain.graph.json specs/NNNN-slug.domain.excalidraw`, ensure §4 carries `Diagram: specs/NNNN-slug.domain.excalidraw`; never write `.excalidraw` directly, first request only.
+- **Progress.** Before each step, before/after each spawn: `npx -y @execuro-sw-ecosystem/sw-specs-editor@latest emit progress "<step>" --batch <id> --doc prd`.
 - **Report:** changed blocks, answers (Q ids → anchor), top remaining gap or `none`, confidence %, status, `Agents: <list or none>`.
 
 Graph shape (`bin/cli.mjs diagram` input): `{ "title", "direction": "LR", "groups": [{id,label}], "nodes": [{id,label,type: entity|actor|service|external|event|store, group?, note?}], "edges": [{from,to,label?}] }`.

package/skills/sw-design-solution/SKILL.md

@@ -3,7 +3,7 @@ name: sw-design-solution
 description: Turn a PRD (specs/NNNN-slug.md) into a technical spec at specs/NNNN-slug-spec.md. Applies TDD — every acceptance criterion gets an implementation plan and e2e coverage, with Shopware toolchain (shopware-cli/PHPStan/ESLint/Stylelint) conventions baked into decisions up front. Runs a clarification loop for the gaps that change the implementation plan, and on the user's say-so extracts project-wide architecture/stack decisions into ADR files (specs/NNNN-slug-adr-<topic>.md) that gate readiness while proposed. Pre-checks vendor/ and the KB before it starts. Use when asked to write, draft, refine, or continue a tech spec / implementation plan. Never edits the source PRD or answers business/requirements questions — that's sw-design-requirements.
 when_to_use: Trigger phrases — "write the tech spec for PRD 0007", "create an implementation plan for this PRD", "draft the spec", "continue spec 0007", "is this spec ready for implementation".
 argument-hint: '[specs/NNNN-slug.md | specs/NNNN-slug-spec.md] [--editor]'
-allowed-tools: Read Write Edit Glob Grep AskUserQuestion Agent Skill Bash(ls *) Bash(npx -y @execuro-sw-ecosystem/sw-specs-editor@0.1.0 *) WebSearch WebFetch mcp__ShopwareDevKnowledgeBase__list_docs mcp__ShopwareDevKnowledgeBase__grep_docs mcp__ShopwareDevKnowledgeBase__read_doc mcp__ShopwareDevKnowledgeBase__kb_status
+allowed-tools: Read Write Edit Glob Grep AskUserQuestion Agent Skill Bash(ls *) Bash(npx -y @execuro-sw-ecosystem/sw-specs-editor@latest *) WebSearch WebFetch mcp__ShopwareDevKnowledgeBase__list_docs mcp__ShopwareDevKnowledgeBase__grep_docs mcp__ShopwareDevKnowledgeBase__read_doc mcp__ShopwareDevKnowledgeBase__kb_status
 ---
 
 # sw-design-solution

package/skills/sw-design-solution/reference/editor-mode.md

@@ -9,8 +9,8 @@ Same procedure/boundary/verification/ADR rules, plus:
 - **Batch input.** Ticks first — a ticked question with no note is still an answer. `answer`/`[x]` tick → anchor, append Decision Log, delete block (`[adr]` sub-step 3, `[gate]` sub-step 5). `comment`/`free` → this run's briefing (block-bound `path`/`line`–`endLine`/`md`/`quote`/`hash`; verify `md` matches, fall back to `quote`; `selection` → rework only that text). `diagram` → update the graph file. *What*/*why* notes belong to the PRD. First write migrates a pre-template spec; blocks get missing options only when touched.
 - **Scoped runs.** Re-spawn architect only for an overturned/new decision, QA only for a changed test plan, `sw-product-manager` only for feasibility — together still one message; else edit/verify/anchor/log alone, name agents.
 - **Preserve:** status tags (`- **AC-2** [partly] (FR-3)`, `- **Decision:** [done] …`), `Diagram:` line, §6 blocks/ticks — rewrite in place, never regenerate.
-- **Diagrams.** `specs/NNNN-slug-spec.architecture.graph.json`; run `npx -y @execuro-sw-ecosystem/sw-specs-editor@0.1.0 diagram specs/NNNN-slug-spec.architecture.graph.json specs/NNNN-slug-spec.architecture.excalidraw`, keep §2's `Diagram:` line — never write it directly.
-- **Progress.** `npx -y @execuro-sw-ecosystem/sw-specs-editor@0.1.0 emit --since <step-0.5 start> progress "<step>" --batch <id> --doc spec` before/after each step/spawn; `--since` prefixes `+m:ss`.
+- **Diagrams.** `specs/NNNN-slug-spec.architecture.graph.json`; run `npx -y @execuro-sw-ecosystem/sw-specs-editor@latest diagram specs/NNNN-slug-spec.architecture.graph.json specs/NNNN-slug-spec.architecture.excalidraw`, keep §2's `Diagram:` line — never write it directly.
+- **Progress.** `npx -y @execuro-sw-ecosystem/sw-specs-editor@latest emit --since <step-0.5 start> progress "<step>" --batch <id> --doc spec` before/after each step/spawn; `--since` prefixes `+m:ss`.
 - **Report:** changed blocks; answers (Q ids → anchor); first unmet §7 criterion or `none`; status/confidence/`Open ADRs`; `Agents: <list or none>`; `Timing:`.
 
 Graph shape: `{ title, direction: "LR", groups: [{id,label}], nodes: [{id,label,type: entity|actor|service|external|event|store,group?,note?}], edges: [{from,to,label?}] }`.

package/skills/sw-discover-tender/SKILL.md

@@ -3,7 +3,7 @@ name: sw-discover-tender
 description: Analyse a client tender (RFP, RFI or RFQ) for a Shopware 6 project into one markdown sidecar, <source basename>-analysis.md. Every requirement row gets a class against the installed Shopware version (stock / config / plugin / custom), a three-point person-day estimate, one line of mechanism and proposed scope-lock assumptions the partner accepts by ticking checkboxes — in the file or on the Tender Discovery Tool page (`--editor`); the next run reconciles the ticks, dissolves answered questions and re-estimates. At Ready to submit it exports one CSV per client table with compliance, comment and effort filled in the client's columns. Scope and PD only — never costs, prices, licence fees or budgets. Never designs the solution — that's sw-design-solution.
 when_to_use: Trigger phrases — "scope this RFP", "analyse the tender", "answer the RFI", "discover RFP 0001", "continue RFP 0001", "reconcile RFP 0001", "export the response for RFP 0001", "is RFP 0001 ready to submit", "open RFP 0001 in the browser", "open the tender tool", "sw-discover-tender specs/rfp-0001-x-analysis.md --editor".
 argument-hint: '[tender file or folder of exports (.xlsx|.md|.txt|.csv|.pdf) | specs/rfp-NNNN-slug-analysis.md to continue] [--editor] [--batch <n|all>] [--export]'
-allowed-tools: Read Write Edit Glob Grep Agent AskUserQuestion Bash(ls *) Bash(mkdir -p specs) Bash(mkdir -p specs/.rfp *) Bash(shasum -a 256 *) Bash(npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@0.1.0 *) Bash(open *) Bash(xdg-open *) Bash(tail *) Bash(grep *) Bash(printf *) mcp__ShopwareDevKnowledgeBase__list_docs mcp__ShopwareDevKnowledgeBase__grep_docs mcp__ShopwareDevKnowledgeBase__read_doc mcp__ShopwareDevKnowledgeBase__kb_status
+allowed-tools: Read Write Edit Glob Grep Agent AskUserQuestion Bash(ls *) Bash(mkdir -p specs) Bash(mkdir -p specs/.rfp *) Bash(shasum -a 256 *) Bash(npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@latest *) Bash(open *) Bash(xdg-open *) Bash(tail *) Bash(grep *) Bash(printf *) mcp__ShopwareDevKnowledgeBase__list_docs mcp__ShopwareDevKnowledgeBase__grep_docs mcp__ShopwareDevKnowledgeBase__read_doc mcp__ShopwareDevKnowledgeBase__kb_status
 ---
 
 # sw-discover-tender
@@ -24,7 +24,7 @@ One markdown sidecar per tender, `<source basename>-analysis.md`: class, three-p
 | Argument | Behaviour |
 | --- | --- |
 | `.md` / `.txt` / `.csv` / `.pdf`, or a folder of such exports | New tender: extract, analyse, write `<basename>-analysis.md` next to the source |
-| `.xlsx` | Import first, per `reference/procedure.md` step 1 ".xlsx import": `npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@0.1.0 import` proposes a mapping (install gate: `reference/editor-session.md` §0), confirmed via `--editor` or a one-line yes/no, before the normalised source and the analysis are set. A refusal (encrypted, `.xls`, `.xlsb`) is relayed verbatim and the run stops |
+| `.xlsx` | Import first, per `reference/procedure.md` step 1 ".xlsx import": `npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@latest import` proposes a mapping (install gate: `reference/editor-session.md` §0), confirmed via `--editor` or a one-line yes/no, before the normalised source and the analysis are set. A refusal (encrypted, `.xls`, `.xlsb`) is relayed verbatim and the run stops |
 | `.docx` | Stop. One line: export every requirement table as CSV UTF-8 (or paste it as markdown tables, header row kept) and rerun with that file or folder |
 | `*-analysis.md` | Continue: reconcile, advance, rewrite in place |
 | `--export`, or "export the response for RFP NNNN" | Continue, then run step 9 if the gate holds |

package/skills/sw-discover-tender/reference/editor-session.md

@@ -5,7 +5,7 @@ The Tender Discovery Tool: a local live page for one analysis document. The skil
 **The protocol is not in this file.** Run
 
 ```
-npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@0.1.0 guide
+npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@latest guide
 ```
 
 and follow it: it is the single source for the xlsx import, start, the batch kinds, poll, emit, redelivery and close, and every command ends with a `next_step:` line. An installed copy of any of that goes stale against a newer CLI. This file adds only what `guide` cannot know — the install gate, the row-batch setting, which opening batch to post, the subagent brief, the follow-up queueing grammar and the close report.
@@ -58,7 +58,7 @@ Invoke it with the Skill tool: skill "sw-discover-tender", args "<analysis path>
 Append the session's row-batch setting to the args when it is not the default: <--batch n | --batch all>.
 If the Skill tool is not available to you, read the SKILL.md of the `sw-discover-tender` skill and follow it exactly, including its "Editor mode" section.
 Rules: never ask the user a question with a structured question tool (Claude Code: `AskUserQuestion`; Codex: `request_user_input`); every gap becomes a §5 block with options; emit progress with
-  npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@0.1.0 emit progress "<step>" --batch <id>
+  npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@latest emit progress "<step>" --batch <id>
   before each procedure step and before/after each agent wave; never change a [x] or [-] except by reconciling it; keep every [ ] line whose
   Evidence / risk or Risk to says "partner"; frozen accepted/rejected lines stay byte-identical; never edit the client's file.
 Context — last chat entries (newest last):
@@ -111,5 +111,5 @@ Invoked by the editor session (`reference/editor-session.md` in this skill's dir
 - **Notes.** `comment` notes carry `block`, `blockKind`, `path` (section breadcrumb), `line`–`endLine`, `md` (the block's source line), `quote`, `hash` and sometimes `selection` (the exact text the user highlighted). Open the file at that range under that path, confirm the text matches `md`, fall back to searching for `quote` when lines shifted. By `blockKind`: `req` → the note questions the class, mechanism or estimate: re-spawn the architect for that row only and rewrite the `req` line; `assume` / `global` → rewrite the statement as a new `[ ]` line (a frozen line is never edited; a proposed line may be replaced in place), or adjust `PD saved` when the note is about the figure; `clarify` → the decision text; `question` → reword or re-option the block (keep its id); `section` / `paragraph` / `row` → that text. `free` notes and `chat` are the briefing for the run. No PD figure ever comes from the page: a note asking for a different number is an architect question, not a hand edit.
 - **A note on a row still `queued` or `analysing`** is not an immediate re-spawn: carry it into that row's own estimate batch and answer it there.
 - **Preserve on every write.** Frozen `accepted <date>` / `rejected <date>` lines byte-identical; every `[x]` / `[-]` untouched except by reconciling it; partner-proposed `[ ]` lines; `X-n` exclusions the page added; §1.1, §1.2, §8, §9 and the nine section headings; the frontmatter block. Rewrite lines in place, never regenerate from the template. Every write must leave the document parseable — the page re-renders on each one.
-- **Progress.** `npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@0.1.0 emit progress "<step>" --batch <id>` before each procedure step and before and after each spawn wave; the page shows it. Row status carries the rest: `queued` → `analysing` → `estimated`.
+- **Progress.** `npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@latest emit progress "<step>" --batch <id>` before each procedure step and before and after each spawn wave; the page shows it. Row status carries the rest: `queued` → `analysing` → `estimated`.
 - **Report.** The 8-line report of step 8 with its `next:` line (plus the 3 export lines); the editor posts it to the page. Never paste the document into the report.

package/skills/sw-discover-tender/reference/procedure.md

@@ -14,7 +14,7 @@
 
 `ls specs`. Keep `rfp-NNNN-` from the input name; else `NNNN` = highest existing + 1, zero-padded, slug = kebab-case `<client>-<project>`. An xlsx is imported and its mapping confirmed first (below). `shasum -a 256` every source file into frontmatter `source`; for an xlsx, the workbook, `import-map.json` and every CSV. Continue mode: keep path, number and slug; never renumber, never a second file for the same tender.
 
-**.xlsx import.** Install gate first, per `reference/editor-session.md` §0: the `sw-tender-discovery-tool` skill must be installed; missing → stop, do not import. `npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@0.1.0 import --source <file>` reads the workbook (hidden and `_` sheets never leave it) and proposes a mapping — which tabs are requirement tables, where each header sits, what each column means, which tokens the dropdowns allow. **With `--editor`** the user confirms it on the steering screen. **Without it**, print the proposed table the command listed, ask the user in one line whether it is right, and on a yes run `npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@0.1.0 import --source <file> --map --accept-proposed`; if a tab or a column is wrong, say so and rerun with `--editor`. Either way the confirmed `import-map.json` and the normalised `<source dir>/<basename>/<pos>-<sheet-slug>.csv` are then the source, and the analysis lands next to the workbook. A refusal (encrypted, `.xls`, `.xlsb`) is relayed verbatim and the run stops.
+**.xlsx import.** Install gate first, per `reference/editor-session.md` §0: the `sw-tender-discovery-tool` skill must be installed; missing → stop, do not import. `npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@latest import --source <file>` reads the workbook (hidden and `_` sheets never leave it) and proposes a mapping — which tabs are requirement tables, where each header sits, what each column means, which tokens the dropdowns allow. **With `--editor`** the user confirms it on the steering screen. **Without it**, print the proposed table the command listed, ask the user in one line whether it is right, and on a yes run `npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@latest import --source <file> --map --accept-proposed`; if a tab or a column is wrong, say so and rerun with `--editor`. Either way the confirmed `import-map.json` and the normalised `<source dir>/<basename>/<pos>-<sheet-slug>.csv` are then the source, and the analysis lands next to the workbook. A refusal (encrypted, `.xls`, `.xlsb`) is relayed verbatim and the run stops.
 
 ### 2. Reconcile — first step of every continue run, before any spawn
 
@@ -93,6 +93,6 @@ When the gate below holds, one more line: "Generate the response CSV?" Then end.
 - **Assemble and check, delegated**: one `sw-tender-editor` per client table, all in one message, cap 10, brief `§ASSEMBLE`. Each concatenates its cluster CSVs behind the client's header row into `<source basename>-response-<n>-<table-slug>.csv` (`<n>` and slug from the Source map) and runs the file checks: row count and id sequence equal the source table; header equals the client's; every compliance value in the allowed list; every effort cell a number, or empty with the blocked comment; no `A-`, `CQ-`, `Q-`, `RC-`, `.a`, `.c`, `PD saved`, `EUR`, `€`; no proposed or rejected assumption text; constant column count. Any failure → the agent deletes the file and returns the failing check. The orchestrator never reads the CSVs.
 - **Check the sums** itself, from the returned per-table effort sums: they must equal §2 per priority. Mismatch → delete the files, report the check.
 - **Write back.** Frontmatter `export: {date, files, source_sha256, stale: false}`; one `C-n`: `Response exported: <files> files, <rows> rows, Must <n> PD`.
-- **Workbook copy.** After every response CSV passes its checks, run `npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@0.1.0 export --xlsx --source <file>`: it writes `<source basename>-response.xlsx`, a copy of the client's own workbook with compliance, comment and effort filled in from those CSVs, styles and dropdowns intact. The client's original is never written. Only for an xlsx tender with a confirmed mapping; a CSV/markdown tender stops at the CSVs.
+- **Workbook copy.** After every response CSV passes its checks, run `npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@latest export --xlsx --source <file>`: it writes `<source basename>-response.xlsx`, a copy of the client's own workbook with compliance, comment and effort filled in from those CSVs, styles and dropdowns intact. The client's original is never written. Only for an xlsx tender with a confirmed mapping; a CSV/markdown tender stops at the CSVs.
 - **Report** three lines: files with row counts · Must / Should / Could as exported · checks passed or the failing check.
 - Same analysis and same source give byte-identical files.

package/skills/sw-setup/SKILL.md

@@ -2,7 +2,7 @@
 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, `.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 coding agent's 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 *)
+allowed-tools: Read Glob Grep AskUserQuestion Skill Bash mcp__ShopwareDevKnowledgeBase__kb_status Bash(npx -y @execuro-sw-ecosystem/sw-ecosystem-agentic-harness@latest *) Bash(npx -y @execuro-sw-ecosystem/sw-specs-editor@latest *) Bash(npx -y @execuro-sw-ecosystem/sw-tender-discovery-tool@latest *)
 ---
 
 # sw-setup
@@ -49,8 +49,8 @@ prints a human summary, not the object below. It prints one JSON object
 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, three `npm view` registry lookups (Package updates row) —
-the one part of step 1 that touches the network, so it is the slow part.
+`kb_status` call, one `npm view` registry lookup (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
@@ -60,7 +60,7 @@ one line per configuration item the CLI's `agents[]`/`drift[]` reports:
 - [x] vendor/ — shopware/core 6.7.13.0
 - [ ] vendor/ — vendor/bin/phpunit missing (tree built --no-dev)
 - [ ] Node — 18.x (need >= 20)
-- [-] Visual editors (optional) — Specs Editor not installed, Tender tool not installed
+- [-] Visual editors (optional) — Specs Editor installed, Tender tool declined
 - [x] shopware-cli — 0.16.10
 - [x] KB MCP — platform: implemented
 - [ ] Acceptance-test project — tests/acceptance/ missing
@@ -68,7 +68,7 @@ one line per configuration item the CLI's `agents[]`/`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
+- [ ] Package updates — harness 0.1.0 → 0.1.3
 - [ ] Installer config — .mcp.json entry: drift (from CLI status)
 ```