@execuro-sw-ecosystem/sw-ecosystem-agentic-harness 0.1.12 → 0.1.13

package/CHANGELOG.md

@@ -7,6 +7,19 @@ release.
 
 ## [Unreleased]
 
+## [0.1.13] - 2026-10-21
+
+### Changed
+
+- **The installer sets up only the coding agents a project targets.** The
+  target agents are anchored in `sw-ecosystem-agentic-harness.json`, next to
+  the lock file, by `agents --agent <a>` or by the first `install` with
+  `--agent` or the picker. Marker directories such as a bare `.vscode/` only
+  produce candidates and never make an agent a target. Once anchored,
+  `status` judges only those agents (the others report `not-targeted`),
+  `apply --yes` runs without `--agent`, and `uninstall` prunes what it removes
+  from the targets. `sw-setup` and its rows reflect the new `agents` command.
+
 ## [0.1.12] - 2026-09-25
 
 ### Changed

package/README.md

@@ -56,7 +56,8 @@ stops with one line saying so.
 | Command | What it does |
 | --- | --- |
 | `install` | installs into the resolved coding agent(s) (see Flags below); the same as `apply --yes` |
-| `status` | read-only; what is installed, what drifted, and each agent's `skills_dir` |
+| `agents` | shows, or with `--agent` anchors, the coding agents this project targets |
+| `status` | read-only; the target agents, what is installed, what drifted, and each agent's `skills_dir` |
 | `plan` | the exact changes, written as a diff; writes nothing |
 | `apply --yes` | performs them |
 | `uninstall --yes` | removes what the lock file records |
@@ -68,12 +69,21 @@ directory), `--yes` (required by `apply` and `uninstall` — `install` implies
 it), `--json` and `--verbose` (see Output below).
 
 `install`/`apply` resolve which coding agent(s) to write into, in order:
-`--agent` if given; else the agents a lock file already records (a re-run
-needs no question); else, with a terminal attached, an interactive picker;
-else exit 2 with the four `install --agent <a>` commands as `help` — it never
-guesses and never hangs. `status` and `uninstall` are unaffected by this and
-keep covering every agent by default; `plan` writes nothing, so with no
-`--agent` and no lock it previews all four and says so.
+`--agent` if given; else the anchored target agents; else the agents a lock
+file already records (a re-run needs no question); else, with a terminal
+attached, an interactive picker; else exit 2 with the four
+`install --agent <a>` commands as `help` — it never guesses and never hangs.
+`plan` writes nothing, so with none of these it previews all four and says so.
+
+The anchored target agents live in `sw-ecosystem-agentic-harness.json`, next
+to the lock file (`var/sw-ai-sdk/`, else `.sw-ai-sdk/`). Marker directories
+such as a bare `.vscode/` only produce `candidates`; they never make an agent
+a target. `agents --agent <a>` (repeatable) anchors exactly those agents and
+writes nothing else; the first `install` with `--agent` or the picker anchors
+its choice too. Once anchored, `status` judges only those agents (the others
+report `not-targeted`) and `apply --yes` runs without `--agent`. `uninstall`
+keeps covering every agent by default and prunes what it removes from the
+targets.
 
 ### Output
 
@@ -109,7 +119,7 @@ row is ticked.
 
 `apply` refuses without `--yes`. Neither `apply` nor `install` prompts for
 consent — typing the verb, or passing `--yes`, is the consent — but with no
-`--agent`, no existing lock and no terminal (Codex's question tool does not
+`--agent`, no anchored targets, no existing lock and no terminal (Codex's question tool does not
 block outside Plan mode, and CI has no terminal either), it exits 2 rather
 than guess. Add `--agent claude-code` (repeatable) to install into one agent,
 and `--scope user` to install into your home directory instead of this

package/bin/cli.mjs

@@ -23,6 +23,7 @@ const COMMANDS = {
   apply: async () => (await import('../lib/commands.mjs')).apply,
   install: async () => (await import('../lib/commands.mjs')).install,
   uninstall: async () => (await import('../lib/commands.mjs')).uninstall,
+  agents: async () => (await import('../lib/commands.mjs')).agentsCommand,
   guide: async () => (await import('../lib/guide.mjs')).main,
 };
 
@@ -33,6 +34,8 @@ const USAGE = `usage: sw-ecosystem-agentic-harness <command> [options]
   plan       [--agent <a>] [--scope project|user] [--root <path>]
   apply      --yes [--agent <a>] [--scope project|user] [--root <path>]
   uninstall  --yes [--agent <a>] [--scope project|user] [--root <path>]
+  agents     [--agent <a> ...] [--scope project|user] [--root <path>]
+             show, or with --agent anchor, the project's target agents
   guide      print the install protocol
 
   install is apply --yes under a friendlier name: the whole install in one
@@ -41,10 +44,13 @@ const USAGE = `usage: sw-ecosystem-agentic-harness <command> [options]
 
   <a> is one of: claude-code, codex, copilot, cursor. Repeat --agent to select
   several. install/apply resolve which agent(s) to use, in order: --agent if
-  given; else the agents already recorded in the lock file, if one exists;
-  else, with a terminal attached, an interactive picker; else exit 2 with
-  the four "... install --agent <a>" commands as help. status and uninstall
-  keep covering every agent by default.
+  given; else the anchored target agents (\`agents --agent <a>\`, stored next
+  to the lock file); else the agents already recorded in the lock file, if
+  one exists; else, with a terminal attached, an interactive picker; else
+  exit 2 with the four "... install --agent <a>" commands as help. An
+  explicit choice is anchored on the first install. status reports only the
+  anchored agents when there are any; uninstall keeps covering every agent
+  by default and prunes the agents it removes from the anchored targets.
 
   --scope defaults to project: nothing is written under your home directory
   unless you ask for it. --root defaults to the current directory.

package/lib/commands.mjs

@@ -17,6 +17,7 @@ import * as lockfile from './lock.mjs';
 import { dedupe, execute, isWritableState, preview, pruneDirs, revert } from './actions.mjs';
 import { removeDirIfEmpty, removeFile } from './fsx.mjs';
 import { askAgents } from './prompt.mjs';
+import * as settings from './settings.mjs';
 import { RESTART } from './render.mjs';
 
 const RUN = 'sw-ecosystem-agentic-harness';
@@ -86,33 +87,40 @@ export function buildContext(argv, command) {
 /**
  * The agent-resolution chain every write command shares:
  *   1. `--agent` given → use exactly those. No question.
- *   2. else a lock already records agents → reuse them. This is an update;
- *      the choice was already made. No question. A lock written before the
- *      rename records them under `hosts`; lib/lock.mjs reads either.
- *   3. else a TTY is attached (apply/install only) → ask, via lib/prompt.mjs.
- *   4. else → UsageError, exit 2, `help` lists the four runnable commands.
+ *   2. else agents are anchored (lib/settings.mjs) → use them. The choice was
+ *      already made. No question.
+ *   3. else a lock already records agents → reuse them. A legacy install; a
+ *      lock written before the rename records them under `hosts`, which
+ *      lib/lock.mjs reads either way.
+ *   4. else a TTY is attached (apply/install only) → ask, via lib/prompt.mjs.
+ *   5. else → UsageError, exit 2, `help` lists the four runnable commands.
  *
- * `status` and `uninstall` keep their old, ungated default of every agent —
- * reporting and removal are not consent points. `plan` writes nothing, so it
- * never reaches step 3: steps 1-2, then it previews all four and says so.
+ * `source` says which step answered; apply anchors the answer of 1 and 4.
+ * `status` takes steps 1-2, then every agent; `uninstall` takes step 1, then
+ * every agent — reporting and removal are not consent points. `plan` writes
+ * nothing, so it never reaches step 4: steps 1-3, then it previews all four.
  *
  * Call after `loadLock(ctx)` so `ctx.lock` is populated for step 2.
  */
 async function resolveAgents(ctx, command) {
-  if (ctx.agents.length) return { agents: [...new Set(ctx.agents)], chosen: true };
-  if (command === 'status' || command === 'uninstall') return { agents: [...AGENTS], chosen: true };
+  if (ctx.agents.length) return { agents: [...new Set(ctx.agents)], chosen: true, source: 'flag' };
+  if (command === 'uninstall') return { agents: [...AGENTS], chosen: true, source: 'all' };
+
+  const anchored = settings.read(ctx.root)?.agents ?? [];
+  if (anchored.length) return { agents: anchored, chosen: true, source: 'settings' };
+  if (command === 'status') return { agents: [...AGENTS], chosen: true, source: 'all' };
 
   const recorded = ctx.lock?.agents ? Object.keys(ctx.lock.agents) : [];
-  if (recorded.length) return { agents: recorded, chosen: true };
+  if (recorded.length) return { agents: recorded, chosen: true, source: 'lock' };
 
-  if (command === 'plan') return { agents: [...AGENTS], chosen: false };
+  if (command === 'plan') return { agents: [...AGENTS], chosen: false, source: 'all' };
 
   if (process.stdin.isTTY) {
     const chosen = await askAgents(AGENTS);
-    if (chosen) return { agents: chosen, chosen: true };
+    if (chosen) return { agents: chosen, chosen: true, source: 'picker' };
   }
   throw new UsageError(
-    'no --agent given, this repository has no recorded install, and there is no terminal to ask which coding agent(s) to use',
+    'no --agent given, no anchored target agents, this repository has no recorded install, and there is no terminal to ask which coding agent(s) to use',
     AGENTS.map((a) => `${RUN} ${command} --agent ${a}`),
   );
 }
@@ -162,6 +170,39 @@ function publicAction(a) {
   return rest;
 }
 
+/** The anchored targets as every result reports them. */
+function targetsOf(root, anchored) {
+  return {
+    agents: anchored?.agents ?? [],
+    source: anchored ? 'settings' : 'none',
+    settings_file: settings.settingsFile(root),
+  };
+}
+
+// ------------------------------------------------------------------ agents
+
+/**
+ * Read or anchor the target agents. Detection only yields `candidates`; the
+ * write touches the settings file and nothing else.
+ */
+export async function agentsCommand(argv) {
+  const ctx = buildContext(argv, 'agents');
+  const candidates = (await detectAll(ctx)).filter((d) => d.detected).map((d) => d.id);
+  let anchored = settings.read(ctx.root);
+  if (ctx.agents.length) {
+    const same = ctx.agents.length === candidates.length && ctx.agents.every((a) => candidates.includes(a));
+    anchored = settings.write(ctx.root, ctx.agents, same ? 'detected' : 'chosen');
+  }
+  return out.ok('agents', head(ctx, {
+    next_step: anchored
+      ? `Target agents: ${anchored.agents.join(', ')}. Run \`${RUN} status\` to check them.`
+      : `Nothing is anchored — run \`${RUN} agents --agent <id>\` (candidates: ${candidates.join(', ') || 'none'}).`,
+    help: [`${RUN} status`, ...AGENTS.map((a) => `${RUN} agents --agent ${a}`)],
+    targets: targetsOf(ctx.root, anchored),
+    candidates,
+  }));
+}
+
 // ------------------------------------------------------------------ status
 
 export async function status(argv) {
@@ -176,7 +217,11 @@ export async function status(argv) {
     }
     throw e;
   }
-  ({ agents: ctx.agents } = await resolveAgents(ctx, 'status'));
+  const resolved = await resolveAgents(ctx, 'status');
+  ctx.agents = resolved.agents;
+  // Untargeted only means something once a choice exists (`--agent` or anchored).
+  const narrowed = resolved.source === 'flag' || resolved.source === 'settings';
+  const anchored = settings.read(ctx.root);
 
   const detections = await detectAll(ctx);
   const { actions, errors } = previewAll(ctx);
@@ -184,8 +229,10 @@ export async function status(argv) {
 
   const agentStates = detections.map((d) => {
     const mine = actions.filter((a) => a.host === d.id || a.host === 'shared');
+    const targeted = !narrowed || ctx.agents.includes(d.id);
     let state = 'absent';
-    if (d.detected) {
+    if (!targeted) state = 'not-targeted';
+    else if (d.detected) {
       const pending = mine.filter((a) => isWritableState(a.state));
       const bad = mine.filter((a) => a.state === 'conflict' || a.state === 'drift');
       if (bad.length) state = bad.some((a) => a.state === 'conflict') ? 'conflict' : 'drift';
@@ -193,7 +240,7 @@ export async function status(argv) {
       else state = lock?.agents?.[d.id] ? 'drift' : 'not-installed';
     }
     return {
-      id: d.id, detected: d.detected, marker: d.marker, writable: d.writable,
+      id: d.id, detected: d.detected, targeted, marker: d.marker, writable: d.writable,
       skills_dir: skillsDir(d.id, ctx),
       installed: installedCounts(d.id, ctx), state, notes: d.notes,
     };
@@ -209,15 +256,22 @@ export async function status(argv) {
   const pending = actions.filter((a) => isWritableState(a.state)).length;
   const worst = ['conflict', 'drift', 'not-installed', 'ok', 'absent']
     .find((s) => agentStates.some((a) => a.state === s)) ?? 'absent';
+  const candidates = detections.filter((d) => d.detected).map((d) => d.id);
 
   let next = pending
     ? `Run \`${RUN} plan\` to see the ${pending} change(s) needed, then \`${RUN} apply --yes\`.`
     : `Nothing to do — the harness is installed and up to date. Run \`${RUN} plan\` any time to re-check.`;
+  if (!anchored) {
+    next = `No target agents are anchored yet — run \`${RUN} agents --agent <id>\` (candidates: ${candidates.join(', ') || 'none'}). ${next}`;
+  }
 
   return out.ok('status', head(ctx, {
     installed_version: lock?.version ?? null,
     state: worst,
     next_step: next,
+    targets: targetsOf(ctx.root, anchored),
+    candidates,
+    lock_file: lockFile(ctx.root),
     help: [`${RUN} plan`, `${RUN} apply --yes`, `${RUN} guide`],
     inventory: { skills: skills().length, agents: agents().length },
     agents: agentStates, drift,
@@ -281,7 +335,8 @@ export async function apply(argv, label = 'apply') {
     }
     throw e;
   }
-  ({ agents: ctx.agents } = await resolveAgents(ctx, label));
+  const resolved = await resolveAgents(ctx, label);
+  ctx.agents = resolved.agents;
 
   // An apply we cannot record is an apply we cannot undo. Refuse up front
   // rather than leave the user with files and no way back.
@@ -359,6 +414,11 @@ export async function apply(argv, label = 'apply') {
     lock = { ...lock, agents: { ...lock.agents, [agent]: { installed_at: new Date().toISOString(), version: PKG_VERSION } } };
   }
   lockfile.write(ctx.root, lock);
+  settings.migrate(ctx.root);
+  // The first explicit choice becomes the project's target agents.
+  if ((resolved.source === 'flag' && !settings.read(ctx.root)) || resolved.source === 'picker') {
+    settings.write(ctx.root, ctx.agents, 'chosen');
+  }
 
   const summary = {
     created: results.filter((r) => r.state === 'created').length,
@@ -411,6 +471,7 @@ export async function uninstall(argv) {
   ({ agents: ctx.agents } = await resolveAgents(ctx, 'uninstall'));
 
   if (!lock) {
+    settings.prune(ctx.root, ctx.agents);
     // No record means no evidence of what we own. Guessing here would delete
     // someone else's files, so it does nothing and says so.
     return out.ok('uninstall', head(ctx, {
@@ -447,6 +508,7 @@ export async function uninstall(argv) {
 
   const prunedDirs = pruneDirs(lock.dirs ?? [], ctx);
   const failed = errors.length;
+  if (!failed) settings.prune(ctx.root, [...selected]);
 
   if (failed === 0 && survivors.length === 0 && selected.size === AGENTS.length) {
     // Everything we recorded is gone; the lock has nothing left to describe.

package/lib/guide.mjs

@@ -21,26 +21,34 @@ registers the MCP servers and permission rules they depend on.
    The whole install in one command. It never prompts for consent — typing
    the verb is the consent — but it does still need to know **which** coding
    agent(s) to write into, resolved in order: \`--agent\`, if given; else the
-   agents a lock file already records, if this is a re-run; else, with a real
+   anchored target agents (step 2); else the agents a lock file already
+   records, if this is a re-run; else, with a real
    terminal attached, an interactive picker; else it exits 2 with the four
    \`${RUN} install --agent <a>\` commands as \`help\` rather than guess or
    hang — Codex's question tool does not block outside Plan mode, and CI has
    no terminal, so a skill invoking this must always pass \`--agent\`.
 
-2. \`${RUN} status\`
-   Read-only, optional. Reports which agents are present, what is already
+2. \`${RUN} agents [--agent <a> ...]\`
+   Reads, or with \`--agent\` anchors, the coding agents this project
+   targets, in \`sw-ecosystem-agentic-harness.json\` next to the lock file.
+   Marker directories only produce \`candidates\`; an explicit first
+   \`--agent\` choice on \`install\` is anchored too. Once anchored, \`status\`
+   judges only those agents and \`install\` needs no \`--agent\`.
+
+3. \`${RUN} status\`
+   Read-only, optional. Reports the target agents, what is already
    installed, and anything that has drifted since it was installed. Always safe.
 
-3. \`${RUN} plan\`
+4. \`${RUN} plan\`
    Prints the exact set of changes and writes nothing. Every entry says what it
    would do and why. Show this to the user before applying.
 
-4. \`${RUN} apply --yes\`
+5. \`${RUN} apply --yes\`
    The scriptable name for the same write \`install\` performs — use it for
    re-runs and repairs. It refuses without \`--yes\`, and resolves which
    agent(s) to touch the same way \`install\` does (see step 1).
 
-5. \`${RUN} uninstall --yes\`
+6. \`${RUN} uninstall --yes\`
    Removes what the lock file records and reverts the managed config blocks.
 
 ## Flags

package/lib/settings.mjs

@@ -0,0 +1,77 @@
+// The anchored target agents: `sw-ecosystem-agentic-harness.json`, next to the lock (see
+// `lockDir()` in content.mjs).
+//
+// The lock records what was *installed*; this records what the project
+// *targets*. Marker directories only ever produce candidates — a stray empty
+// `.vscode/` must not make Copilot a target — so every command that has to
+// pick agents reads this file first. Only the CLI writes it, per checkout: it
+// lives in the ignored state directory, so each machine anchors once.
+
+import { dirname } from 'node:path';
+import { LOCK_DIR, lockDir } from './content.mjs';
+import {
+  abs, ensureDir, exists, readTextMaybe, removeDirIfEmpty, removeFile, writeAtomic,
+} from './fsx.mjs';
+import { AGENTS } from './hosts.mjs';
+
+const NAME = 'sw-ecosystem-agentic-harness.json';
+
+export function settingsFile(root) {
+  return `${lockDir(root)}/${NAME}`;
+}
+
+/** The pre-`var/` location; read only so an anchored project survives the move. */
+function legacyPath(root) {
+  return abs(root, `${LOCK_DIR}/${NAME}`);
+}
+
+/** The anchored agents, or null when nothing is anchored (or the file is unusable). */
+export function read(root) {
+  const found = readTextMaybe(abs(root, settingsFile(root))) ?? readTextMaybe(legacyPath(root));
+  if (found === null) return null;
+  let parsed;
+  try { parsed = JSON.parse(found.text); } catch { return null; }
+  const agents = (Array.isArray(parsed?.agents) ? parsed.agents : []).filter((a) => AGENTS.includes(a));
+  return agents.length ? { ...parsed, agents: [...new Set(agents)] } : null;
+}
+
+export function write(root, agents, source) {
+  const settings = {
+    schema: 1, agents: [...new Set(agents)], anchored_at: new Date().toISOString(), source,
+  };
+  const target = abs(root, settingsFile(root));
+  ensureDir(dirname(target));
+  writeAtomic(target, `${JSON.stringify(settings, null, 2)}\n`);
+  dropLegacy(root, target);
+  return settings;
+}
+
+function dropLegacy(root, target) {
+  const legacy = legacyPath(root);
+  if (legacy !== target && exists(legacy)) {
+    removeFile(legacy);
+    removeDirIfEmpty(dirname(legacy));
+  }
+}
+
+/** Move a settings file left at the old path to the current one. */
+export function migrate(root) {
+  const current = read(root);
+  if (current && legacyPath(root) !== abs(root, settingsFile(root)) && exists(legacyPath(root))) write(root, current.agents, current.source ?? 'chosen');
+}
+
+/** Drop agents from the targets; the file goes when none are left. */
+export function prune(root, removed) {
+  const current = read(root);
+  if (!current) return;
+  const left = current.agents.filter((a) => !removed.includes(a));
+  if (left.length === current.agents.length) return;
+  if (left.length) {
+    write(root, left, current.source ?? 'chosen');
+    return;
+  }
+  const target = abs(root, settingsFile(root));
+  removeFile(target);
+  removeDirIfEmpty(dirname(target));
+  dropLegacy(root, target);
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@execuro-sw-ecosystem/sw-ecosystem-agentic-harness",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "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.12",
+  "version": "0.1.13",
   "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

@@ -50,10 +50,9 @@ npx -y @execuro-sw-ecosystem/sw-ecosystem-agentic-harness@latest status --json
 
 `--json` is mandatory for every call this skill makes: without it the CLI
 prints a human summary, not the object below. It prints one JSON object
-(`ok`, `next_step`, `help`, and its own `agents[]`/`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
+(`ok`, `next_step`, `help`, `targets`, `agents[]`, `drift[]`). First settle
+the target agents (`reference/rows.md`, Target agents); alongside, run every
+environment row's check from `reference/rows.md` — read-only, seconds each: file/directory existence, one version command, one
 `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.
@@ -74,7 +73,8 @@ one line per configuration item the CLI's `agents[]`/`drift[]` reports:
 - [x] Plugin tests — AhCheckout: phpunit + jest ok
 - [ ] Project wiki — docs/project-wiki/ missing
 - [ ] Package updates — harness 0.1.0 → 0.1.3
-- [ ] Installer config — .mcp.json entry: drift (from CLI status)
+- [x] Target agents — claude-code (anchored)
+- [ ] Installer config — .mcp.json entry: drift
 ```
 
 Per-plugin rows print one line per directory under `custom/plugins/`, e.g.
@@ -87,8 +87,7 @@ Print one closing line: `Environment ready.` Stop. No question.
 ### 3. Missing rows
 
 For a missing environment row, research only what it needs: the guideline
-sections `reference/rows.md` cites for that row
-(`shopware-project-qa-guidelines.md` §3.3–§3.7, §6.1), `compose.yaml` for the
+sections `reference/rows.md` cites for that row, `compose.yaml` for the
 service name, `custom/plugins/*` names for per-plugin rows.
 
 For a missing/drifted configuration row, do not research or plan the fix

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

@@ -11,16 +11,25 @@ Every installer-CLI call this skill makes passes `--json`. Without it the CLI
 prints a short human summary instead of the object these rows read — that
 summary is for the person typing the command, never for a skill parsing it.
 
-When that `status --json` call reports no install at all (no lock file, so no
-recorded agents), the installer CLI's `apply --yes`/`install` has no `--agent`
-to reuse and, run from this skill, no terminal to ask on — it would exit 2.
-Do not pass a guessed `--agent`. Report this to the user instead: the first
-install must be run by them directly in a terminal, e.g.
-`npx -y @execuro-sw-ecosystem/sw-ecosystem-agentic-harness@latest install`,
-which then either takes their `--agent` or prompts them interactively. Re-run
-this skill's `status` check afterwards — every later `apply --yes --json`
-reuses the agents that first run recorded, and this skill can call it
-directly again. Expect `agents[]` in every output this skill reads.
+## Target agents
+
+Every row below is judged against the **anchored target agents** only, never
+against marker directories: a stray `.vscode/` makes Copilot a candidate, not a
+target. Read `targets` and `candidates` from the step-1 `status --json`.
+
+- `targets.source` is `settings`: use `targets.agents`. Ask nothing.
+- `none` and exactly one candidate: anchor it with
+  `npx -y @execuro-sw-ecosystem/sw-ecosystem-agentic-harness@latest agents --agent <id> --json`
+  and say so in one line. This is the one write allowed before the question.
+- `none` and zero or several candidates: ask one multi-select question listing
+  the four agents (`claude-code`, `codex`, `copilot`, `cursor`), detected ones
+  marked, then anchor the answer the same way (one `--agent` per pick). Ask
+  with the structured question tool as in `SKILL.md` step 3.
+- A later change of mind goes through the same `agents --agent …` call.
+
+Re-run `status --json` after anchoring and read `agents[]` from that. An agent
+whose `state` is `not-targeted` is never printed or acted on. Print
+`- [x] Target agents — <ids> (anchored)` as the first configuration line.
 
 ## 1. vendor/
 
@@ -69,7 +78,7 @@ So this row never blocks readiness, and it never probes. It asks.
 
 - **Check:** read `agents[]` from the `status --json` output step 1 already
   ran. Each entry carries `id` and `skills_dir` — the directory that agent
-  actually reads skills from. For each agent whose `state` is not `absent`,
+  actually reads skills from. For each target agent (`targeted` is true),
   list `<skills_dir>/sw-specs-editor/` and
   `<skills_dir>/sw-tender-discovery-tool/`: a `SKILL.md` there means that
   editor is installed for that agent. That directory read is the whole check —
@@ -78,12 +87,12 @@ So this row never blocks readiness, and it never probes. It asks.
   state, not something to go looking for. Also read
   `sw-setup-editors.json` from the installer's own state directory if it
   exists — this skill's note of what the user has already declined
-  (`{"sw-specs-editor": "declined"}`). That directory is whatever `lock_file`
-  in the step-1 `status --json` output names, minus the file name — normally
+  (`{"sw-specs-editor": "declined"}`). That directory is the one
+  `settings_file` in `targets` names, minus the file name — normally
   `var/sw-ai-sdk/`, which a Shopware project already ignores. Read the path;
   never hard-code it.
 - **Ticked:** `[x]` when the editor's `SKILL.md` is present in every
-  non-`absent` agent's `skills_dir`; `[-]` when the note records a decline, or
+  target agent's `skills_dir`; `[-]` when the note records a decline, or
   when it is installed for some agents but not all (say which). `[ ]` only for
   an editor that is neither installed nor declined — and even then it does not
   hold the table open: report it as optional and move on.
@@ -97,7 +106,7 @@ So this row never blocks readiness, and it never probes. It asks.
     `--editor` and the `.xlsx` import on `sw-discover-tender`. Install?"
 
   On yes, for each accepted editor, run its own installer once per
-  non-`absent` agent, passing that agent's `skills_dir` from `status --json`:
+  target agent, passing that agent's `skills_dir` from `status --json`:
 
   ```
   npx -y @execuro-sw-ecosystem/sw-specs-editor@latest install-skill --target <skills_dir>
@@ -130,7 +139,7 @@ So this row never blocks readiness, and it never probes. It asks.
   <skills_dir>` and re-run the removal" — and carry on with the other agents
   and the other editor.
 - **On no:** write the decline to `sw-setup-editors.json` in the directory
-  `lock_file` names (create the file, and that directory, if absent; it is
+  `targets.settings_file` names (create the file, and that directory, if absent; it is
   never tracked) and do not
   offer that editor again on any later run. The user asking for it by name is
   the only thing that re-opens it — then delete its key and install. `--editor`
@@ -305,7 +314,8 @@ This row never blocks readiness. It folds into step 3's single question.
   npx -y @execuro-sw-ecosystem/sw-ecosystem-agentic-harness@latest install
   ```
 
-  That command rewrites the installed `sw-setup` skill itself, so the newer
+  That command reuses the anchored target agents and 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. For the editors, see row 3: re-running their `install-skill` line is
   their update.