@mmerterden/multi-agent-pipeline 20.33.0 → 20.35.0

package/pipeline/office/toolkit.json

@@ -1,3 +1,3 @@
 {
-  "toolkitVersion": "3.26.0"
+  "toolkitVersion": "3.27.0"
 }

package/pipeline/rules/response-shape.md

@@ -1,18 +1,17 @@
 ## Reply shape
 
-For replies in a conversation. Reports, PR, Jira and Confluence bodies keep
+For conversation replies. Reports, PR, Jira and Confluence bodies keep
 their own templates; the humanizer governs their wording.
 
 - First line: the answer or the next action. No preamble, no recap of the ask.
 - Steps: numbered, one action each. Items: at most five shown, the rest named
   as a count. That limit shapes the display only; never drop a finding, a
-  failure or a verification note to fit it.
-- Errors: the cause, then the fix. Finished work: what changed, how it was
-  checked.
+  failure or a verification note to fit it, and never shorten away a negation,
+  a number, a unit or a path.
+- Errors: cause, then fix. Finished work: what changed, how it was checked.
 - Tangents wait for the end, as one line.
-- Last line: what happens next, or what the user has to decide. No closing
-  pleasantries.
+- Last line: the next step or the user's decision. No closing pleasantries.
 - An explanation asked for runs as long as it needs; a destructive step is
   confirmed first; real ambiguity gets one question.
 
-Detail and examples: `$HOME/.claude/multi-agent-refs/response-shape.md`.
+Detail: `$HOME/.claude/multi-agent-refs/response-shape.md`.

package/pipeline/schemas/agent-state.schema.json

@@ -1268,6 +1268,20 @@
               "minimum": 0,
               "maximum": 3
             },
+            "trackerStatus": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": ["status", "at"],
+              "description": "Phase 2 Step 1: the issue's move to In Progress (Jira) / In Develop (Projects V2), re-read after the write. verified = the re-read showed it; declined = the user refused the write; not-tracked = the run has no board to move; failed = the write or its re-read did not land. write-state.mjs refuses to leave Phase 2 in an attended run with a tracked issue unless this is verified, declined or not-tracked.",
+              "properties": {
+                "status": {
+                  "type": "string",
+                  "enum": ["verified", "declined", "not-tracked", "failed"]
+                },
+                "observed": { "type": "string", "description": "The status the re-read returned." },
+                "at": { "type": "string", "format": "date-time" }
+              }
+            },
             "subStep": {
               "type": "string",
               "description": "Sub-step checkpoint for long phases (2, 5) so resume re-does only the unfinished tail instead of the whole phase. Short token, e.g. 'red'|'green'|'build'|'pr-opened'|'confluence-synced'. See operations.md 'Sub-step checkpoints'."
@@ -1408,6 +1422,24 @@
             "type": "string",
             "enum": ["fix", "accept", "escalate"]
           },
+          "rulings": {
+            "type": "array",
+            "description": "Written by rework-rulings.mjs when the rework cap is reached: one ruling per accepted finding still open. escalate stops the run for the user; parked carries the finding into Phase 4 Step 0b and the PR follow-ups.",
+            "items": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": ["ruling", "reason"],
+              "properties": {
+                "fingerprint": { "type": ["string", "null"] },
+                "file": { "type": ["string", "null"] },
+                "line": { "type": ["integer", "null"] },
+                "severity": { "type": ["string", "null"] },
+                "ruling": { "enum": ["escalate", "parked"] },
+                "reason": { "type": "string" },
+                "issue": { "type": "string" }
+              }
+            }
+          },
           "reworkEscalation": {
             "type": "object",
             "additionalProperties": false,
@@ -1891,6 +1923,10 @@
             "minimum": 0,
             "description": "v2.1.0+ push-must-succeed retry counter. Increments per rebase-retry."
           },
+          "pushStatus": {
+            "enum": ["pushed", "rebase-pushed", "skipped", "paused"],
+            "description": "Phase 4 push outcome for this repo. A commit counts as delivered once this is pushed, rebase-pushed or skipped (left to the user and reported in Phase 5), or the repo has a pr; run-completion.mjs refuses complete otherwise."
+          },
           "buildStatus": {
             "description": "Latest Phase 3 build outcome for this repo. A string in early phases ('pending'/'green'/'passed'/'failed') or null before any attempt; once Phase 3 runs a build it becomes a {ok, attempts, lastError} object (see phase-2-dev.md). run-metrics.mjs reads both the string and object forms.",
             "anyOf": [

package/pipeline/schemas/phases.json

@@ -42,25 +42,25 @@
       "id": 3,
       "name": "Review",
       "doc": "phase-3-review.md",
-      "maxTokens": 17200,
+      "maxTokens": 17260,
       "was": [4, 5]
     },
     {
       "id": 4,
       "name": "Commit",
       "doc": "phase-4-commit.md",
-      "maxTokens": 6600,
+      "maxTokens": 6650,
       "was": [6]
     },
     {
       "id": 5,
       "name": "Report",
       "doc": "phase-5-report.md",
-      "maxTokens": 5700,
+      "maxTokens": 5710,
       "was": [7]
     }
   ],
-  "totalMaxTokens": 63550,
+  "totalMaxTokens": 63710,
   "modes": {
     "full": {
       "phases": [0, 1, 2, 3, 4, 5],

package/pipeline/schemas/plan-critique.schema.json

@@ -47,8 +47,15 @@
         "properties": {
           "id": { "type": "string", "pattern": "^OBJ-[0-9]{2,3}$" },
           "lens": {
-            "enum": ["scope", "feasibility", "security", "alternative"],
-            "description": "scope: the plan does more or less than the analysis asks. feasibility: a step cannot work as planned. security: a step opens a hole. alternative: a cheaper plan reaches the same result."
+            "enum": [
+              "scope",
+              "feasibility",
+              "security",
+              "alternative",
+              "unstated-input",
+              "underspecified"
+            ],
+            "description": "scope: the plan does more or less than the analysis asks. feasibility: a step cannot work as planned. security: a step opens a hole. alternative: a cheaper plan reaches the same result. unstated-input: an input the spec implies (empty, boundary, expired, concurrent) that no task's tests exercise. underspecified: a decision the plan leaves to the task's implementer that the analysis or the user should make."
           },
           "claim": {
             "type": "string",

package/pipeline/schemas/planning-output.schema.json

@@ -1,9 +1,9 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://github.com/mmerterden/multi-agent-pipeline/pipeline/schemas/planning-output.schema.json",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "title": "Multi-Agent Pipeline  -  Phase 1 planning output",
-  "description": "Contract for Phase 2 task decomposition. Consumed by Phase 3 TDD cycles  -  each task becomes one red→green→refactor iteration.",
+  "description": "Contract for the Phase 1 task decomposition. Consumed by the Phase 2 TDD cycles  -  each task becomes one red→green→refactor iteration. 1.1.0 adds the plan-level reviewFocus[] and globalConstraints[].",
   "type": "object",
   "additionalProperties": false,
   "required": ["tasks", "approved"],
@@ -71,6 +71,24 @@
             "items": { "type": "string", "minLength": 1 },
             "description": "Interfaces or symbols this task calls or relies on without changing them. Paired against other tasks' produces and removes."
           },
+          "design": {
+            "type": "object",
+            "additionalProperties": false,
+            "required": ["component", "mapping"],
+            "description": "The design source of a UI task. validate-planning.mjs --spec checks the component against the analysis Section 6 (Component Inventory) rows.",
+            "properties": {
+              "component": {
+                "type": "string",
+                "minLength": 1,
+                "description": "The component name exactly as its Section 6 row names it."
+              },
+              "mapping": {
+                "type": "string",
+                "enum": ["code-connect", "new", "best-fit"],
+                "description": "code-connect = the Code Connect mapped component, used verbatim; new = a Section 6 row marked not existing; best-fit = no mapping, pending design review (needs a Risk row; Phase 3 gates it review_blocking)."
+              }
+            }
+          },
           "complexity": {
             "type": "object",
             "additionalProperties": false,
@@ -100,6 +118,29 @@
         }
       }
     },
+    "reviewFocus": {
+      "type": "array",
+      "maxItems": 5,
+      "description": "Inputs or failure modes the spec implies but no task's tests exercise, each given to the task that owns the code so a test covers it. validate-planning.mjs fails an owner id that is not a task.",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["input", "ownerTaskId"],
+        "properties": {
+          "input": {
+            "type": "string",
+            "minLength": 4,
+            "description": "The input or failure mode, concretely (an empty list, a token that expired mid-request)."
+          },
+          "ownerTaskId": { "type": "string", "pattern": "^T[0-9]+$" }
+        }
+      }
+    },
+    "globalConstraints": {
+      "type": "array",
+      "items": { "type": "string", "minLength": 1 },
+      "description": "Project-wide values every task must respect, copied verbatim (a minimum OS version, a naming rule, a module boundary), because each task's implementer sees only its own task."
+    },
     "approved": {
       "type": "boolean",
       "description": "User approved the plan (true) or changes requested (false → loop with feedback)."

package/pipeline/schemas/pr-reach.schema.json

@@ -0,0 +1,55 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://github.com/mmerterden/multi-agent-pipeline/pipeline/schemas/pr-reach.schema.json",
+  "title": "Pull request reach",
+  "description": "What GET /v1/prs/reach returns (`work-items.mjs reach`): for each open GitHub pull request (at most 20), how many files in the repository's own code graph depend on what it changes, widest first. Changed paths serve only as keys into the local graph and are never returned. A pull request that cannot be measured carries reach null and its reason.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["contractVersion", "depth", "items"],
+  "properties": {
+    "contractVersion": {
+      "type": "string",
+      "pattern": "^1\\.[0-9]+\\.[0-9]+$",
+      "x-sensitivity": "none"
+    },
+    "depth": {
+      "type": "integer",
+      "minimum": 1,
+      "description": "Reverse-dependency depth the count was taken at."
+    },
+    "items": {
+      "type": "array",
+      "maxItems": 20,
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["source", "repo", "number", "project", "reach"],
+        "properties": {
+          "source": { "enum": ["github", "bitbucket"] },
+          "repo": { "type": "string" },
+          "number": { "type": "integer" },
+          "project": {
+            "type": ["string", "null"],
+            "description": "The knowledge-folder project whose graph answered, or null."
+          },
+          "changed": {
+            "type": "integer",
+            "minimum": 0,
+            "description": "Files the pull request changes."
+          },
+          "inGraph": {
+            "type": "integer",
+            "minimum": 0,
+            "description": "Of those, files the graph knows."
+          },
+          "reach": {
+            "type": ["integer", "null"],
+            "minimum": 0,
+            "description": "Files that depend on the changed ones, within depth. Null when not measured."
+          },
+          "reason": { "type": "string", "description": "Why reach is null." }
+        }
+      }
+    }
+  }
+}

package/pipeline/schemas/prefs.schema.json

@@ -311,7 +311,7 @@
         },
         "office": {
           "type": "object",
-          "description": "The office panel (/multi-agent:office-on). page overrides the installed panel page; toolkitVersion pins an @latest toolkit registration for the panel's tool calls; remote is read only to report that a separately installed remote layer is present, and no remote code ships with the pipeline.",
+          "description": "The office panel (/multi-agent:office-on). page overrides the installed panel page; toolkitVersion pins an @latest toolkit registration for the panel's tool calls; remote configures the office remote layer (features/office-remote-protocol.md), which stays off until office-pair pairs a phone.",
           "additionalProperties": false,
           "properties": {
             "page": {
@@ -324,7 +324,13 @@
             },
             "remote": {
               "type": "object",
-              "description": "Configuration owned by a separately installed remote layer; the pipeline only checks that it exists."
+              "description": "The office remote layer. relayUrl is the origin office-pair registers pairings with and the phone page is served from.",
+              "properties": {
+                "relayUrl": {
+                  "type": "string",
+                  "pattern": "^https://[^/?#@]+$"
+                }
+              }
             }
           }
         },
@@ -906,7 +912,7 @@
           "type": "string",
           "enum": ["en", "tr"],
           "default": "en",
-          "description": "Language used for the assistant's NON-INTERACTIVE explanations, status updates, error messages, and pipeline-generated reports rendered to the user (e.g. `/multi-agent:help` body, `/multi-agent:status` table headers, summary blocks at the end of a run). Independent of `promptLanguage` so a user can have Turkish pickers but English summaries (or vice versa). External payloads (commits, PR/Jira/wiki) and skill-picker / confirmation / error UI exposed by the CLI host stay English regardless of this setting. Set via `/multi-agent:language output <en|tr>` or answered on first run by `/multi-agent:setup`."
+          "description": "Language used for the assistant's NON-INTERACTIVE explanations, status updates, error messages, and pipeline-generated reports rendered to the user (e.g. `/multi-agent:help` body, `/multi-agent:status` table headers, summary blocks at the end of a run). Independent of `promptLanguage` so a user can have Turkish pickers but English summaries (or vice versa). PR, Jira, issue and wiki bodies follow it too; commits, branch names, agent prompts and the CLI host's own picker and error UI stay English. Set via `/multi-agent:language output <en|tr>` or answered on first run by `/multi-agent:setup`."
         },
         "progressVerbosity": {
           "type": "string",
@@ -1891,6 +1897,29 @@
             "enabled": false
           }
         },
+        "memory": {
+          "type": "object",
+          "additionalProperties": false,
+          "description": "Limits on the per-repo memory stores under ~/.claude/memory/multi-agent/<repo-slug>/.",
+          "properties": {
+            "excludeProjects": {
+              "type": "array",
+              "items": { "type": "string", "minLength": 1 },
+              "description": "Repo slugs whose learnings ledger, triage corpus and debt list are never written. Reads still work on what is already there."
+            }
+          }
+        },
+        "fileContext": {
+          "type": "object",
+          "additionalProperties": false,
+          "description": "After a Read, hand the model what the repo's memory says about that file: ledger facts whose scope covers it, its latest review findings and its open known limits (debt-ledger.mjs), at most six lines, once per file per session, inside an <untrusted-data> block and after the secret scan. The hook is pipeline/scripts/file-context.sh, PostToolUse on Read (Claude Code). It never blocks.",
+          "properties": {
+            "enabled": {
+              "type": "boolean",
+              "description": "Absent = only inside a pipeline run bound to the session. true = in every session. false = never."
+            }
+          }
+        },
         "stopGuard": {
           "type": "object",
           "additionalProperties": false,
@@ -1915,17 +1944,17 @@
         "attendedCommitGate": {
           "type": "object",
           "additionalProperties": false,
-          "description": "What pre-commit-check.sh does with an attended `git commit` inside a pipeline run whose gate ledger holds no passing build and test verdict (evidence-gate/build, evidence-gate/test) for HEAD. evidence-gate.mjs records both in an attended run, marked attended. Read by gate-ledger.mjs `evidence`; a commit outside a run, or in a mode that commits nothing, is never checked. Unattended commits are held to the full ledger regardless of this setting.",
+          "description": "What pre-commit-check.sh does with an attended `git commit` inside a pipeline run whose gate ledger holds no passing build and test verdict (evidence-gate/build, evidence-gate/test) for HEAD, or, from Phase 4 on, no passing review-decision. evidence-gate.mjs records both in an attended run, marked attended. Read by gate-ledger.mjs `evidence`; a commit outside a run, or in a mode that commits nothing, is never checked. Unattended commits are held to the full ledger regardless of this setting.",
           "properties": {
             "mode": {
               "type": "string",
-              "enum": ["off", "warn", "block"],
-              "default": "warn",
-              "description": "warn = say so on stderr and let the commit through. block = refuse the commit (exit 2) until the evidence is recorded. off = no check."
+              "enum": ["off", "warn", "block", "auto"],
+              "default": "auto",
+              "description": "auto = block when the committing session is the one driving the run (its hostSessionId or launch sessionId), warn otherwise. warn = say so on stderr and let the commit through. block = refuse the commit (exit 2) until the evidence is recorded. off = no check."
             }
           },
           "default": {
-            "mode": "warn"
+            "mode": "auto"
           }
         },
         "mutationProbe": {

package/pipeline/schemas/reviewer-output.schema.json

@@ -1,9 +1,9 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://github.com/mmerterden/multi-agent-pipeline/pipeline/schemas/reviewer-output.schema.json",
-  "version": "1.5.0",
+  "version": "1.6.0",
   "title": "Multi-Agent Pipeline  -  Phase 3 reviewer output",
-  "description": "Contract for a single code-reviewer subagent's JSON output in Phase 4 Step 2. Every host dispatches 3 parallel reviewers; the middle slot is CLI-aware: Claude Code (Fable, Opus, Sonnet); Copilot CLI (Opus, GPT-5.4, Sonnet); Codex CLI dispatches 3 (gpt-5.6 at xhigh, gpt-5.4, gpt-5.6 at medium). Every reviewer must return an object matching this shape before Opus triage merges them. v1.1.0 adds the rule-ID conformance checklist: when the orchestrator supplies a ${CRITERIA} block (Phase 3 Step 1.78), the reviewer must return one conformance row per selected rule ID. Findings alone cannot answer 'was this applied completely' - a reviewer that opened nothing returns the same empty findings array as one that checked everything. v1.2.0 adds the optional per-finding fingerprint (Phase 3 Step 2.1): the stable id a finding keeps across review rounds. v1.4.0 adds the optional per-finding `security` envelope (OWASP + CWE + CVSS + evidence + remediation): the security-auditor emits reviewer-output objects whose findings carry it, so a blocking security finding merges at Step 3.0 and blocks Phase 4 like any reviewer blocker. General reviewers omit it. Its shape mirrors security-finding.schema.json, kept in step by smoke-security-schema-parity.sh. v1.5.0 adds the optional per-finding `quote`, `preExisting` and `baselineEvidence` (see triage-output.schema.json).",
+  "description": "Contract for a single code-reviewer subagent's JSON output in Phase 4 Step 2. Every host dispatches 3 parallel reviewers; the middle slot is CLI-aware: Claude Code (Fable, Opus, Sonnet); Copilot CLI (Opus, GPT-5.4, Sonnet); Codex CLI dispatches 3 (gpt-5.6 at xhigh, gpt-5.4, gpt-5.6 at medium). Every reviewer must return an object matching this shape before Opus triage merges them. v1.1.0 adds the rule-ID conformance checklist: when the orchestrator supplies a ${CRITERIA} block (Phase 3 Step 1.78), the reviewer must return one conformance row per selected rule ID. Findings alone cannot answer 'was this applied completely' - a reviewer that opened nothing returns the same empty findings array as one that checked everything. v1.2.0 adds the optional per-finding fingerprint (Phase 3 Step 2.1): the stable id a finding keeps across review rounds. v1.4.0 adds the optional per-finding `security` envelope (OWASP + CWE + CVSS + evidence + remediation): the security-auditor emits reviewer-output objects whose findings carry it, so a blocking security finding merges at Step 3.0 and blocks Phase 4 like any reviewer blocker. General reviewers omit it. Its shape mirrors security-finding.schema.json, kept in step by smoke-security-schema-parity.sh. v1.5.0 adds the optional per-finding `quote`, `preExisting` and `baselineEvidence` (see triage-output.schema.json). v1.6.0 adds the optional `cannotVerify[]`: requirements that live in code the diff does not touch, which triage must settle.",
   "type": "object",
   "additionalProperties": false,
   "required": ["findings", "approved"],
@@ -15,6 +15,24 @@
         "$ref": "#/$defs/finding"
       }
     },
+    "cannotVerify": {
+      "type": "array",
+      "description": "Requirements the reviewer could not verify from the diff because they live in unchanged code (a caller that must also change, a config read elsewhere). Triage settles each one; a reviewer never marks the change correct on the assumption.",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["requirement", "where", "why"],
+        "properties": {
+          "requirement": { "type": "string", "minLength": 4 },
+          "where": {
+            "type": "string",
+            "minLength": 1,
+            "description": "The unchanged file or symbol that holds it."
+          },
+          "why": { "type": "string", "minLength": 4, "description": "What the diff does not show." }
+        }
+      }
+    },
     "approved": {
       "type": "boolean",
       "description": "Reviewer's own verdict. MUST be false if any finding has severity=blocking, true otherwise. Triage may override."

package/pipeline/schemas/token-budget.json

@@ -13,14 +13,14 @@
       "max_tokens": 10650
     },
     "phase-3-review": {
-      "max_tokens": 17200
+      "max_tokens": 17260
     },
     "phase-4-commit": {
-      "max_tokens": 6600
+      "max_tokens": 6650
     },
     "phase-5-report": {
-      "max_tokens": 5700
+      "max_tokens": 5710
     }
   },
-  "total_max_tokens": 63550
+  "total_max_tokens": 63710
 }

package/pipeline/schemas/triage-output.schema.json

@@ -1,9 +1,9 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://github.com/mmerterden/multi-agent-pipeline/pipeline/schemas/triage-output.schema.json",
-  "version": "3.5.0",
+  "version": "3.6.0",
   "title": "Multi-Agent Pipeline  -  Phase 3 triage output",
-  "description": "Contract for the Opus triage agent's JSON output in Phase 4 Step 3. Triage consumes merged reviewer findings and splits them into accepted/deferred/rejected. Only `accepted` blocking/important items trigger Phase 3 rework. v3.1.0 adds the optional `consensus` block so triage can surface reviewer-agreement risk (false consensus among same-base-model reviewers) instead of silently merging. v3.2.0 adds the optional per-finding `verification` block written by Phase 3 Step 3.7 (verify-by-test): the empirical repro-test outcome for accepted blocking findings. v3.3.0 carries ruleId + criteriaSource through triage so a finding that cites a stable rule ID keeps that citation into Phase 4 and Phase 5, and the lesson loop can key durable learnings by rule. v3.4.0 adds the optional per-finding fingerprint (finding-fingerprint.mjs) so review-delta.mjs can tell still-present, resolved and new findings apart between rounds. v3.5.0 adds the optional per-finding `quote` (matched against the cited line by verify-citations.mjs) and `preExisting` + `baselineEvidence` on findings and on deferred/rejected items, so a pre-existing claim in an unattended run can be checked against the base commit.",
+  "description": "Contract for the Opus triage agent's JSON output in Phase 4 Step 3. Triage consumes merged reviewer findings and splits them into accepted/deferred/rejected. Only `accepted` blocking/important items trigger Phase 3 rework. v3.1.0 adds the optional `consensus` block so triage can surface reviewer-agreement risk (false consensus among same-base-model reviewers) instead of silently merging. v3.2.0 adds the optional per-finding `verification` block written by Phase 3 Step 3.7 (verify-by-test): the empirical repro-test outcome for accepted blocking findings. v3.3.0 carries ruleId + criteriaSource through triage so a finding that cites a stable rule ID keeps that citation into Phase 4 and Phase 5, and the lesson loop can key durable learnings by rule. v3.4.0 adds the optional per-finding fingerprint (finding-fingerprint.mjs) so review-delta.mjs can tell still-present, resolved and new findings apart between rounds. v3.5.0 adds the optional per-finding `quote` (matched against the cited line by verify-citations.mjs) and `preExisting` + `baselineEvidence` on findings and on deferred/rejected items, so a pre-existing claim in an unattended run can be checked against the base commit. v3.6.0 adds the optional `cannotVerify[]`: one settled row per requirement a reviewer could not verify from the diff.",
   "type": "object",
   "additionalProperties": false,
   "required": ["accepted", "deferred", "rejected", "approved"],
@@ -73,6 +73,24 @@
     },
     "consensus": {
       "$ref": "#/$defs/consensus"
+    },
+    "cannotVerify": {
+      "type": "array",
+      "description": "One row per reviewer cannotVerify requirement, settled before Phase 4: verified (checked in the unchanged code), finding (it is broken; the finding is in accepted or deferred) or out-of-scope. validate-triage.mjs --reviewers or --reviewers-dir fails a requirement with no row.",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["requirement", "resolution", "evidence"],
+        "properties": {
+          "requirement": { "type": "string", "minLength": 4 },
+          "resolution": { "enum": ["verified", "finding", "out-of-scope"] },
+          "evidence": {
+            "type": "string",
+            "minLength": 4,
+            "description": "verified: the file:line read. finding: the file:line of the accepted or deferred finding it became. out-of-scope: why. validate-triage.mjs checks the first two."
+          }
+        }
+      }
     }
   },
   "if": {
@@ -102,6 +120,11 @@
       "type": "string",
       "enum": ["blocking", "important", "suggestion"]
     },
+    "foundBy": {
+      "type": "string",
+      "pattern": "^(Source [A-Z]|security-auditor)$",
+      "description": "The anonymized source label triage judged the finding under, carried through verbatim. anonymize-findings.mjs --restore writes the reviewer family back from the label map after validation; validate-triage.mjs --anonymized refuses a verdict that names a reviewer itself."
+    },
     "reviewer": {
       "type": "string",
       "enum": ["fable", "opus", "sonnet", "gpt"],
@@ -214,6 +237,9 @@
         "reviewer": {
           "$ref": "#/$defs/reviewer"
         },
+        "foundBy": {
+          "$ref": "#/$defs/foundBy"
+        },
         "verification": {
           "$ref": "#/$defs/verification"
         },
@@ -254,7 +280,7 @@
         {
           "type": "object",
           "additionalProperties": false,
-          "required": ["severity", "file", "line", "issue", "reviewer", "fix"],
+          "required": ["severity", "file", "line", "issue", "fix"],
           "properties": {
             "severity": {
               "$ref": "#/$defs/severity"
@@ -274,6 +300,9 @@
             "reviewer": {
               "$ref": "#/$defs/reviewer"
             },
+            "foundBy": {
+              "$ref": "#/$defs/foundBy"
+            },
             "fix": {
               "type": "string",
               "minLength": 4,

package/pipeline/schemas/unattended-policy.json

@@ -135,6 +135,7 @@
     "credential-store.sh": ["get", "set", "delete"],
     "keychain.py": ["get", "set", "delete"],
     "gate-ledger.mjs": ["append"],
-    "phone-devices.mjs": ["add", "revoke", "launch"]
+    "phone-devices.mjs": ["add", "revoke", "launch"],
+    "office-pair.mjs": null
   }
 }