@mmerterden/multi-agent-pipeline 20.34.0 → 20.35.0

package/CHANGELOG.md

@@ -16,6 +16,61 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ## [Unreleased]
 
+## [20.35.0] - 2026-10-27
+
+### Added
+
+- Office: each person wears their own sheet, recoloured at build time from the CC0 character sheets (`office-art/employees.json`), with a name, agent and model tier; clicking a person opens their card, and a Building window lists every room and who works there.
+- Office remote layer, first part: `features/office-remote-protocol.md` (the end-to-end layer, relay, pairing and passkey tiers around the existing signed phone routes) and `lib/office-remote.mjs`, the machine side of its cryptography: P-256 ECDH with HKDF into one AES-256-GCM key per direction, counter nonces that refuse replays, the pairing envelope keyed with the one-time secret, the comparison code, and the WebAuthn assertion check.
+- Office remote client: `office-remote-client.mjs` polls the relay, opens each frame with the paired device's key, applies the passkey tier (read session, low-risk window, per-request for launch), forwards only phone routes to the loopback server without an `Authorization` header and seals the reply; one audit line per frame without bodies or header values. `office-on` starts it only when a device is paired, `office-off` stops it.
+- Office pairing: `office-pair.mjs start | wait | confirm <code> | cancel` registers a pairing with the relay (only the SHA-256 of the machine's relay token leaves the machine), shows the QR code on the local screen through the dependency-free encoder in `lib/qr-code.mjs`, opens the phone's sealed pairing message with the one-time secret carried in the link fragment, and enrols the device with scopes `read,answer` only after the comparison code is typed back. `phone-devices.mjs revoke` also drops the device's remote keys; `office-status` reports remote access as off, configured or paired.
+
+- `answer-check.sh`, a PostToolUse hook on AskUserQuestion: a question the user submitted without a choice is named back to the model, so it is asked again instead of resolved to the Recommended option. Registered by `install` in every session; it only adds context.
+- `worktree-prepare-all.mjs` creates a multi-repo task's worktrees in one step and, when a repo fails, rolls back what it created: worktrees without `--force`, and a branch only when it created that branch and it still points at `origin/<base>`. Phase 0 uses it for multi-repo runs; `worktree-prepare.sh` reports `newBranch`.
+- `test-stability-gate.mjs` compares the repeated runs (`.pipeline/repeat-<k>.junit.xml`) of the new and changed tests: a test whose outcome differs across runs, a missing run or a test that failed every time is not GREEN.
+
+### Changed
+
+- agent-guard asks on a `git commit` from the session driving an attended run (where prompts are off it denies until `confirm-command.mjs` records the user's yes), and inside that run refuses a commit subject with no conventional type or over 72 characters, and a PR, issue or Jira body with a literal `\n` or an HTML entity outside code.
+- `prefs.global.attendedCommitGate.mode` defaults to `auto`: a commit by the session driving the run is refused without the run's build and test evidence, and from Phase 4 on without a passing `review-decision`, which attended runs now record. Other sessions are warned as before; `warn`, `block` and `off` still apply when set.
+- Triage judges anonymized findings end to end: the verdict carries each finding's `foundBy` label (or a gate `tag`) instead of a reviewer name, `validate-triage.mjs --anonymized` refuses a verdict that names a reviewer, and `anonymize-findings.mjs --restore` writes the reviewer family back from the label map after validation.
+- `scope-check-gate.mjs --rejected <triage> --rework-base <rev>` lists `rejectedTouched[]`: findings triage rejected whose lines a rework hunk changed. Phase 2 records the reviewed commit per review round with `rework-base.mjs record` (`.pipeline/rework-base-<N>`).
+- `validate-planning.mjs --spec` checks UI tasks against the analysis Section 6 inventory: a task touching a view file names its component in the new `design` field, and the name must be a Section 6 row.
+- `update-issue-progress.sh` exits 5 without editing the issue unless the account has commented on it since the run started with the template's `Ref: #N` footer: the comment and the Progress flags go together. `--comment-file` posts the comment first through the outbound gate; the unattended runner's issue update uses it with the PR link. Issue coordinates that are not an owner/repo and a number exit 6.
+- `write-state.mjs` refuses to leave Phase 2 of an attended run with a tracked issue unless `phases["2"].trackerStatus` is `verified`, `declined` or `not-tracked`. A run already in Phase 2 when this lands records the status once before it moves on.
+- `task-mirror.sh` records a phase tile's id as its `tasklist_id` and notes a tile created after a higher-numbered phase's tile.
+- `write-state.mjs` refuses to leave Phase 1 of an attended full run without `phases["1"].planApprovedAt`, and refuses to change a `sessionId` already set (exit 6, nothing written). Autopilot, background launches and analysis mode are not asked for a plan approval.
+- A run cannot complete while a repo's commit has no recorded push: `projects[].pushStatus` must be `pushed`, `rebase-pushed` or `skipped`, or the repo has a pull request. `pushStatus` is declared in the state schema.
+- agent-guard: a closing keyword in a `gh pr create/edit --title` or in a commit message asks first; AI attribution in a gh pull request or issue title, body, body file or comment is blocked; `vercel` with `--token` is refused; `purge.sh`, `prune-logs.sh --yes` and `run-kill.mjs apply` ask first; a stored secret read with nothing capturing or consuming its output is refused.
+- `pre-commit-check.sh` refuses signing material and keystores (`.p12`, `.p8`, `.mobileprovision`, `.jks`, `.keystore` ...) and `Pods/`, `.build/`, `DerivedData/` paths by name, binaries included; `.DerivedData/` joins the clone-local exclude list.
+- `run-scope-guard` also registers on `Bash|WebFetch`: a Figma read over HTTP (figma.com, api.figma.com) after analysis is denied under the same phase rule, and a direct write to `agent-state.json` or `tracker-state.json` (Edit/Write, a redirect or `tee`) is denied in any session. The wrapper starts node only when the payload mentions Figma or a state file.
+- The test-integrity gate flags a test switched off (`XCTSkip`, `.skip(`, `xit(`, `@Disabled`, `@Ignore`, `@pytest.mark.skip`, `t.Skip(`, a `.disabled` trait) as a blocking `disabled-test` finding; a conditional skip is left alone.
+- `worktree-prepare.sh` refuses a worktree outside `<project>/.worktrees/` and a new branch outside `feature/`, `bugfix/`, `hotfix/`, `release/`; an existing branch, local or on origin, is re-entered as it is.
+- agent-guard asks before a POST or PUT to a Jira comment, a Confluence page or a Slack webhook, and refuses a Bitbucket pull request PUT whose body has no reviewers, fromRef or toRef (the PUT replaces the record and would wipe them).
+- agent-guard refuses a side effect from a read-only subagent (one whose definition denies it Write), identified by the hook's `agent_type`: run-state writes, git commit or push, write requests with curl-like clients, and gh pull request, issue and api writes. Reads stay open.
+- `run-scope-guard` denies `AskUserQuestion` from a bound autopilot run (it derives or records a halt) and `git add -A`, `--all` or `.` inside a bound run (files are staged by name); it now registers on `Bash|WebFetch|AskUserQuestion`.
+- `validate-planning.mjs --spec` refuses a raw pixel or point value in a task when the spec carries a Figma design; values are named by design token.
+- `gate-ledger.mjs append` pauses the run on the fourth consecutive failing `evidence-gate/build` or `evidence-gate/test` verdict (status `paused`, `haltReason <phase>:retry-cap`, exit 5): the three-attempt fix loop ends on a record.
+- A commit inside a live pipeline run is refused when its author (`--author`, `-c user.email=`, or the repository's config) is not the identity Phase 0 chose (`run-commit-check.mjs`, called from the commit hook; silent outside a bound run).
+- `phase-tracker.sh init` refuses to re-initialize a tracker that already holds phases; `--force` starts it over.
+- `phase0-exit-gate.mjs` fails below the published version floor, reading the answer Step 0.6 cached (`update-check.sh --cache-only`, any age, never the network).
+
+### Fixed
+
+- File locks (`json-file-lock.mjs`, `write-state.mjs`) read a lock's PID and its identity through one descriptor, and reclaim a dead holder's lock by moving it aside first. Read by path twice, a lock released and re-acquired in between looked like a dead holder's, and the live one was deleted, so two writers held it and one update was lost.
+
+### Added
+
+- Office: the pull request window ranks open pull requests by graph reach, the number of files that depend on what each one changes, read from that repository's own code graph. A repository with no graph says so instead of ranking. Served by a new local-only route `GET /v1/prs/reach` (`work-items.mjs reach`); contract 1.7.0 adds `pr-reach.schema.json`.
+
+### Changed
+
+- Every skill companion file over 100 lines (references, patterns, templates beside a `SKILL.md`) now opens with a generated table of contents, as the multi-agent-refs already did. `gen-ref-toc.mjs` covers `pipeline/skills/` and takes `--dir <skills-tree>` for the plugin marketplace; a file with fewer than three sections at its section depth lists the depth below as well.
+- Skill text that aged with the calendar no longer does: `app-store-review` drops "As of May 2026", and `google-play-compliance` points at its Rule 1 for the target API level instead of quoting a number in prose. `google-play-compliance` and `channels` name the MCP server and say when they apply.
+- `google-play-compliance` Rule 1 carries the current target API requirement: 36 for new apps and updates on phones and tablets from 31 Aug 2026 (extension to 1 Nov 2026), 35 on Wear OS and Automotive, 34 on TV and XR.
+- The bulk reader and Phase 3 triage write terse machine fields (a short phrase per `why` / `reason`), keeping every negation, number and path; the explorer already did.
+- `test/project.test.mjs` also holds optional, peer and bundled dependencies at zero and the development tooling to its recorded set.
+
 ## [20.34.0] - 2026-10-26
 
 ### Added
@@ -157,7 +212,6 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 - `prefs.global.readOnlyRepos[]`: checkouts that may not be edited, committed or pushed.
 - `/multi-agent:doctor` reports template hooks that are not registered or not executable and preferences that no registered hook enforces. The installer registers the run hooks itself, records them in `multi-agent-hook-manifest.json` after settings.json is written, and does not re-add a hook the user removed.
 
-
 ## [20.28.0] - 2026-10-24
 
 ### Added

package/README.md

@@ -504,6 +504,7 @@ The **secret scan** runs as a `PreToolUse` hook on Claude Code (hard-blocks a co
 | `run-stop-guard.sh` (no silent stop mid-run) | Stop | none: halts stay the phase's own write | none |
 | `task-mirror.sh` (native task list into the run tracker, so the office shows it) | PostToolUse `TaskCreate`/`TaskUpdate` | none: the phase calls `phase-tracker.sh task` itself | none: the phase calls `phase-tracker.sh task` itself |
 | `file-context.sh` (what the repo's memory says about a file, after it is read) | PostToolUse `Read` | none | none |
+| `answer-check.sh` (an AskUserQuestion submitted without a choice is asked again, not defaulted) | PostToolUse `AskUserQuestion` | none | none |
 | `edit-syntax-gate.sh` | PostToolUse file edits | PostToolUse `apply_patch` | none: Copilot discards postToolUse output |
 | `check-read-size.sh`, capture hooks | registered | none | none |
 

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-26",
-  "version": "20.34.0",
+  "generatedAt": "2026-10-27",
+  "version": "20.35.0",
   "phaseSchema": 2,
   "phases": [
     {