@mmerterden/multi-agent-pipeline 20.22.0 → 20.23.1

package/CHANGELOG.md

@@ -16,6 +16,44 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ## [Unreleased]
 
+## [20.23.1] - 2026-10-13
+
+### Fixed
+
+- `/multi-agent:analysis-jira` finds a site's sub-task types on Jira Data Center 9, which answers only the per-project `createmeta/{project}/issuetypes`; sub-tasks were created under the generic `Sub-task` name there. `issueTree.subtaskIssueType` may now map each role to the site's type (`{"develop": "Development Task", "test": "Test Task"}`, `"*"` for any other role), a site with several sub-task types and no setting is named in the run's output, and the preview shows the type each role gets.
+- The code graph reads Swift imports behind an attribute (`@testable import`, `@_exported import`, `@preconcurrency import`, `@_spi(...) import`).
+- Python type parameters (`class Box[T](Base):`) keep their bases, and a TypeScript base built by a call (`extends mixin(Base)`) adds no edge to the function.
+- A diff hunk that only inserts or only deletes lines is given to the declaration spanning both lines around it, at any context size; at `-U0` it was given to the line before it.
+
+## [20.23.0] - 2026-10-13
+
+### Added
+
+- **Operational reporting reaches teammates on work machines.** When no GitHub account on the machine can prove access, setup and update ask once for the person's GitHub username and `usage-register.mjs --login <name>` registers it as declared; the server issues the token only to a collaborator (the repository owner registers with a proof), under a machine label with a random suffix, and marks its records `claimed`. Later runs re-register a declared name without asking. A declared name is used only when the machine proves no account: it never replaces a proven registration, a later proof replaces it, it is compared case-insensitively, it is never used for `/multi-agent:feedback`, it is not written on a dry run or (outside feedback) an opted-out machine, a refused name is forgotten so setup asks again, and a claim that failed otherwise is not resent for a day.
+- The installer starts `usage-report.mjs --lifecycle` right after writing the version stamps, so every install and update reaches the panel when it happens (`MULTI_AGENT_SKIP_USAGE_REPORT=1` turns it off).
+- `graph-confirm.mjs` merges a `graph-affected` answer with `code_references` results: each direct dependent is `confirmed`, `name-only` or `unchecked`, and `lspOnly` names files the server found that the graph missed. Only a ready semantic index confirms or demotes.
+- **`inherits` edges in the code graph** (schema 1.2.0): subtype to superclass, protocol or interface, read from Swift and Kotlin `:` lists, Swift extensions, Python bases and TypeScript `extends` / `implements`. `graph-affected "<Protocol>" --kind inherits --depth 1` lists its conformers.
+
+### Changed
+
+- A Story's description puts each section in a coloured wiki panel, its heading first: the user story `#d4d39e`, the acceptance criteria `#d4a19e`, every other section `#9eb6d4`. `/multi-agent:create-jira` and the stories `/multi-agent:analysis-jira` plans both write it; Task and Bug keep plain sections.
+- The code graph is on by default (`prefs.global.codeGraph.enabled: true`): it costs seconds and no API calls, never fails a run, and without it the diff mapping, `dependents_reached` and `inherits` answers never run. Set it to `false` and no graph is built or refreshed.
+- `knowledge.md` lists the stores a run fills without a model, how each reaches Phase 1, and why the prose files carry no generated copy of them.
+
+### Fixed
+
+- The code graph never points production code at a type a test file declares; a test fake named after a framework type (`protocol View`) made every view in an app depend on it.
+- A root-level `Tests/` directory (the SwiftPM layout) counts as test code in the code graph and in `test-gap-scan`.
+- An attribute whose arguments run over several lines (`@available(iOS 16,` / `macOS 13, *)`, `@Test(arguments: [Item.init(a: 1),`) belongs to the declaration below it.
+- `symbol-existence-gate`, `test-strength`, `valven-port` and `valven-split` read git path lists NUL-separated, so files with non-ASCII names are checked under their real paths; valven pathspecs are literal.
+- `learnings-ledger from-triage` exits 2 when it distills nothing, so a repeat `capture-flush` reports `ok-nothing-new` for the ledger.
+- `product-context.mjs learn` and `decline` write the preferences file under the shared file lock, leave a file that does not parse untouched, and write through a symlink.
+- A diff header whose quoted path is followed by a tab maps to the right file in `graph-affected --diff` and in `symbol-existence-gate`.
+- `graph-affected --diff <base>..<head>` reads the diff on the side the graph was built at (its head or its base) whatever the working tree holds.
+- `graph-build` keeps git's stderr off the terminal.
+- `capture-flush.sh --json` keeps stdout to the JSON answer; its progress lines go to stderr.
+- A preferences file that is a dangling symlink, or a chain of them, is written through to its target instead of replacing the link.
+
 ## [20.22.0] - 2026-10-13
 
 ### Added

package/docs/adr/0010-own-code-graph.md

@@ -51,8 +51,9 @@ The engine is `pipeline/scripts/_code-graph.mjs`, with per-stack rules in
 `pipeline/scripts/code-graph-rules/<stack>.json`, five entry points
 (`graph-build`, `graph-query`, `graph-affected`, `graph-report`,
 `validate-code-graph`), a schema at `pipeline/schemas/code-graph.schema.json`,
-and the `/multi-agent:graph` command. It is off by default behind
-`prefs.global.codeGraph.enabled`.
+and the `/multi-agent:graph` command. It sits behind
+`prefs.global.codeGraph.enabled`, off when this was decided and on by default
+since ADR 0017's change-impact work made Phase 3 depend on it.
 
 ## What we deliberately gave up
 

package/docs/facts.json

@@ -1,7 +1,7 @@
 {
   "$comment": "Generated by pipeline/scripts/gen-facts.mjs. Do not hand-edit: the site reads this, and a number edited here instead of at its source is the drift this file removes.",
-  "generatedAt": "2026-10-12",
-  "version": "20.22.0",
+  "generatedAt": "2026-10-13",
+  "version": "20.23.1",
   "phaseSchema": 2,
   "phases": [
     {
@@ -62,5 +62,5 @@
     "ui": 1
   },
   "pluginSkillCount": 252,
-  "toolkitVersion": "3.22.1"
+  "toolkitVersion": "3.22.2"
 }

package/docs/features.md

@@ -58,11 +58,11 @@ The install is not only useful while `/multi-agent` is running. `rules/outside-t
 
 Uninstall preserves the whole layer - tokens, the reader that opens them, the mapping that names them, the MCP registration. It is 1.5 kB of always-loaded text; the detail lives in a ref that loads on demand, and a gate keeps both under a ceiling because every byte there is paid by every session.
 
-### Code Graph (`/multi-agent:graph`, opt-in)
+### Code Graph (`/multi-agent:graph`)
 
 A deterministic, LLM-free map of what a repo declares and what refers to what, extracted by regex over comment-stripped source into `~/.claude/knowledge/<project>/code-graph.json`. Four stacks build today (Swift, Kotlin/Java, TypeScript/JavaScript, Python); each is one rules file, and the engine is the same for all of them. Zero runtime dependencies, zero API cost, read-only on the repo.
 
-Phase 1 queries it to hand Explore a ranked starting file set instead of a full scan, and Phase 5 rebuilds it after the branch changed code - a rebuild is seconds, so staleness is a `baseCommit` comparison rather than a date heuristic. Off by default behind `prefs.global.codeGraph.enabled`; with it off the pipeline behaves exactly as before.
+Phase 1 queries it to hand Explore a ranked starting file set instead of a full scan, and Phase 5 rebuilds it after the branch changed code - a rebuild is seconds, so staleness is a `baseCommit` comparison rather than a date heuristic. On by default behind `prefs.global.codeGraph.enabled`; with it off no graph is built or refreshed.
 
 `GRAPH_REPORT.md` also ends with **Symbols nothing else references**: symbols no other file in the repo names, split from the ones referenced only by their own tests. Candidates, never verdicts - the extractor is regex, not a parser, so the four classes that could not carry a reference edge either way (a kind outside the stack's `referenceKinds`, a name declared twice, a nested declaration, a test file) are counted and excluded rather than listed, and nothing gates on the result.
 

package/install/_usage-lifecycle.mjs

@@ -0,0 +1,44 @@
+/**
+ * Report the version just installed, without waiting for it.
+ *
+ * `usage-report.mjs --lifecycle` compares the version stamps the installer just
+ * wrote with `usageLog.reportedVersion` and sends one install or update record
+ * when they differ. It does nothing unless operational reporting is on and a
+ * token resolves, and it never fails. Starting it from the installer puts an
+ * install or update on the panel when it happens, including a version that is
+ * replaced before the machine's next pipeline run.
+ *
+ * `MULTI_AGENT_SKIP_USAGE_REPORT=1` starts nothing.
+ *
+ * @module install/_usage-lifecycle
+ */
+
+import { spawn } from "node:child_process";
+import { existsSync } from "node:fs";
+import { join } from "node:path";
+
+const HOSTS = [".claude", ".copilot", ".codex"];
+
+/**
+ * @param {{home: string, packageRoot?: string, env?: NodeJS.ProcessEnv, spawnImpl?: typeof spawn}} opts
+ * @returns {string|null} the script started, or null
+ */
+export function startLifecycleReport({ home, packageRoot, env = process.env, spawnImpl = spawn }) {
+  if (env.MULTI_AGENT_SKIP_USAGE_REPORT === "1") return null;
+  const candidates = [
+    ...HOSTS.map((h) => join(home, h, "scripts", "usage-report.mjs")),
+    ...(packageRoot ? [join(packageRoot, "pipeline", "scripts", "usage-report.mjs")] : []),
+  ];
+  const script = candidates.find((p) => existsSync(p));
+  if (!script) return null;
+  try {
+    spawnImpl(process.execPath, [script, "--lifecycle"], {
+      detached: true,
+      stdio: "ignore",
+      env: { ...process.env, ...env, HOME: home },
+    }).unref();
+    return script;
+  } catch {
+    return null;
+  }
+}