opencode-swarm 7.135.0 → 7.135.2

package/.opencode/skills/swarm-pr-feedback/SKILL.md

@@ -171,13 +171,14 @@ tree:
   supersedes your planned fixes, and prefer the parallel work if it's more
   comprehensive (more tests, better edge coverage, clearer error handling).
   Abort your rebase, take the remote state, then add minor improvements on top.
-- Verify the working tree is clean first (`git status --porcelain`). If tracked
-  changes exist, call `prepare_pr_workflow_checkout` with every explicit dirty
-  tracked path (Profile A). It creates an auditable, path-scoped stash and returns its
-  recovery command. Do not issue `git stash` through shell. The controller never
-  stashes untracked files; move or remove those manually, or abort the checkout.
-  Without the controller, surface dirty tracked state to the user or abort the
-  checkout — do not blind-stash.
+- Verify the working tree is clean first (`git status --porcelain`). If any
+  tracked or untracked changes exist, call `prepare_pr_workflow_checkout`
+  before binding (Profile A). Omit `paths` to auto-discover and atomically
+  preserve every dirty path, including untracked files; pass explicit `paths`
+  only for an exact bounded tracked-file set. It creates an auditable stash
+  receipt and recovery command. Do not issue `git stash` through shell.
+  Without the controller, surface dirty state to the user or abort the checkout
+  — do not blind-stash.
 - Treat `recovery-required` and `indeterminate` controller results as terminal
   for the current attempt: report the typed `required_action`, abort/clear any
   already-active gate, and stop. Only `stashable` permits one preparation call;
@@ -191,21 +192,23 @@ tree:
    with `git show` when needed.
 - If no PR reference was provided (a pasted-feedback session on the current branch),
    confirm the current branch is the intended PR branch before editing.
-- If the fetched PR head is detached or has no local tracking branch, establish
-  it only during this pre-bind transition with the constrained existing-remote
-  form `git switch -c <local-branch> --track <remote>/<remote-branch>` (or set
-  the upstream of an existing local branch with
-  `git branch --set-upstream-to=<remote>/<remote-branch> <local-branch>`).
-  Branch creation/tracking is blocked after the immutable head is bound.
-- `gh pr checkout` is permitted only in its non-force, non-submodule form with
-  the PR number/URL and optional `--repo` or `--branch` flags. Never use
-  `--force`, `--recurse-submodules`, or detached checkout during this
-  transition.
-- Before the first feedback verification dispatch binds the head, prove that
-  `git rev-parse HEAD` equals the authoritative full `pr_head_sha`,
+- A detached checkout at the authoritative full PR head is a valid pre-bind
+  intake state. On the first Profile-A bind, the controller attaches it only
+  when Git reports exactly one safe candidate: an existing local branch at
+  that SHA whose upstream is an exact remote ref at the same SHA, or one exact
+  remote-tracking ref. It never guesses a remote/name boundary. Zero
+  candidates, multiple candidates, a linked-worktree-owned local branch, or an
+  existing mismatched upstream fails closed without publishing the bind. Retry
+  is idempotent if switching succeeded but state persistence failed.
+- The existing constrained tracked-branch and safe `gh pr checkout` pre-bind
+  forms remain supported on every profile after proving the exact SHA and a
+  unique intended remote ref. Never use force, submodule-recursive, or detached
+  `gh pr checkout` variants.
+- Immediately after the first bind and before feedback verification dispatch,
+  prove that `git rev-parse HEAD` equals the authoritative full `pr_head_sha`,
   `git status --porcelain` is empty, and the current branch tracks the intended
-  PR head remote/branch. A detached checkout is valid for review, not feedback
-  publication.
+  PR head remote/branch. A detached exact-head checkout is intake-only; the
+  bind must attach it before feedback dispatch or publication.
 
 When a verification lane result includes `output_ref`, treat `output` as a
 preview and call `retrieve_lane_output` before using it to classify, resolve,

package/.opencode/skills/swarm-pr-review/SKILL.md

@@ -844,9 +844,14 @@ Under Profile A, after `collect_lane_results` returns for base lanes, process
 each lane result that carries an `output_ref`. The orchestrator MUST use the
 candidate parser rather than preview-text extraction:
 
-1. For each `output_ref`, call `parse_lane_candidates` with `output_ref`,
-   `producer: "swarm-pr-review"`, and `expected_family: "base_explorer"`. The parser reads
-   the full artifact from disk (no preview truncation issue) and returns
+1. For each singleton base `output_ref`, call `parse_lane_candidates` with
+   `output_ref`, `producer: "swarm-pr-review"`,
+   `expected_family: "base_explorer"`, and `expected_lane` set to the exact
+   `workflow_lane` declared at dispatch. For a consolidated tier-S/M lane, call
+   the parser once for each owned dimension with that dimension as
+   `expected_lane` and pass `expected_lanes` as the lane's complete
+   `owned_workflow_lanes` array on every call. The parser reads the full artifact
+   from disk (no preview truncation issue), rejects unowned rows, and returns
    structured `ParseResultWithSidecar` records.
 2. Filter the returned `candidates[]` by `producer: "swarm-pr-review"` plus the
    exact `source_batch_id` and `source_lane_id` from the base dispatch. Treat a
@@ -924,9 +929,11 @@ Explorers emit structured candidate records. The parser reads the full lane
 artifact and extracts these records. The canonical record shape is:
 
 ```text
-[CANDIDATE] | candidate_id | lane | severity | category | file:line | claim | evidence_summary | impact_context | confidence: LOW/MEDIUM/HIGH
+[CANDIDATE] | candidate_id | lane | severity | category | file:line | claim | evidence_summary | impact_context | confidence
 ```
 
+The confidence data value must be exactly LOW, MEDIUM, or HIGH.
+
 Under Profile A the parser normalizes this into a structured `candidates[]`
 array. On Profiles B/C — and as a Profile A fallback when the parser is
 unavailable — the explorer emits the `[CANDIDATE]` row format directly in the
@@ -952,31 +959,35 @@ After base lanes settle, inspect the exact diff/context pack to focus every row
 in the micro-lane map and print a mandatory ledger with one row per map row:
 
 ```text
-[TRIGGER-EVAL] | trigger_row | MATCHED | focus_evidence
+[TRIGGER-EVAL] | trigger_row | MATCHED/NOT_TRIGGERED | focus_evidence
 ```
 
 Focus evidence must name the changed files, manifests, imports/symbols, semantic
-signals, or explicit absence conditions the lane should examine. `MATCHED` means
-the family's evaluation is required, not that a keyword heuristic guessed
-applicability.
+signals, or explicit absence conditions. Use `MATCHED` when the exact diff has
+an applicable surface and dispatch that family; use `NOT_TRIGGERED` only when
+the row was evaluated and concrete absence evidence proves it inapplicable.
+`unclassified-risk` is the always-`MATCHED` fallback. A `NOT_TRIGGERED` row is
+not a waiver or a micro artifact and carries no source batch/lane provenance.
 Repository identity, technology stack, PR size, elapsed time, or predicted risk
 never justifies skipping a row.
 
 Every row in the map is a risk **family** that must be evaluated against the
 diff on every PR, in every repository. What scales with the depth tier is the
 dispatch shape — how many subagents carry that evaluation — never the
-evaluation itself. Each family must end in its own attestation: `[CANDIDATE]`
-rows naming the family, or one fully populated per-family `[CLEAN]` row.
+evaluation itself. Each `MATCHED` family must end in its own attestation:
+`[CANDIDATE]` rows naming the family, or one fully populated per-family
+`[CLEAN]` row. `NOT_TRIGGERED` families end in the ledger with absence evidence
+and must not be dispatched.
 
 **Profile A dispatch.** Launch the micro coverage with
 `dispatch_lanes_async` and `mode: "swarm-pr-review:micro"`. At depth tier L,
-dispatch one focused micro-lane for every row, each lane's
+dispatch one focused micro-lane for every `MATCHED` row, each lane's
 `workflow_lane` equal to its trigger ID; because the dispatcher accepts at
-most eight lanes per call, split the
-eleven mandatory micro-lanes across bounded async batches. At tiers S and M,
+most eight lanes per call, split large matched sets across bounded async
+batches. At tiers S and M,
 consolidated lanes may each own several families: set `workflow_lane` to one
 owned trigger ID and declare the complete `owned_workflow_lanes` set — every
-family owned exactly once across the dispatch, and every owned family
+matched family owned exactly once across the dispatch, and every owned family
 attested in that lane's output, or the lane fails for all of them. Include
 the complete exact-set
 `trigger_evaluation` ledger and the same exact current `pr_head_sha` in every
@@ -985,37 +996,39 @@ unrelated or duplicate micro-lanes within a batch, and final ledger persistence
 rejects any row whose completed owning-lane provenance is absent.
 Poll incrementally, then settle every launched lane. Persist
 the complete ledger with `write_pr_review_trigger_eval`; its rows use the stable
-trigger IDs below, and every row includes its returned `source_batch_id` and
-`source_lane_id`. Missing, extra, duplicate, `NO-MATCH`, or unprovenanced
-rows make persistence fail and Phase 4 BLOCKED. The tool atomically writes
+trigger IDs below. Every `MATCHED` row includes its returned `source_batch_id`
+and `source_lane_id`; every `NOT_TRIGGERED` row must omit both fields. Missing,
+extra, duplicate, malformed, or incorrectly provenanced rows make persistence
+fail and Phase 4 BLOCKED. The tool atomically writes
 `.swarm/pr-review/<run_id>/trigger-eval.json`, separate from `findings.jsonl`;
 pass the exact reviewed merge-base as `base_sha`, the exact live base branch
 tip/ref used to compute it as `base_ref`, and the same `pr_head_sha` to the
 writer. The writer runs bounded `git merge-base -- <base_ref> <pr_head_sha>` and
-rejects any claimed `base_sha` that is not the exact result. It accepts only the
-exact eleven-row `MATCHED` set, each row backed by a completed, non-degraded,
-exact-head artifact from a lane that declared ownership of that family and
-attested every family it owns. It never uses keyword
-classification as permission to waive a family. Any head mismatch makes
-persistence fail.
+rejects any claimed `base_sha` that is not the exact result. It accepts only an
+exact eleven-row v2 receipt: `MATCHED` rows are backed by completed,
+non-degraded, exact-head artifacts from lanes that declared and attested their
+families; `NOT_TRIGGERED` rows are provenance-free. Counts are recomputed and
+must agree. It never uses keyword or path classification alone as absence
+evidence. Any head mismatch makes persistence fail. Historical unversioned and
+schema-v1 all-`MATCHED` receipts remain readable, but new writes are strict v2.
 Do not add trigger results to the finding-status enum.
 
 **Profiles B/C dispatch.** Scale the lane shape to the depth tier while
 keeping all eleven family evaluations:
 
-- Tier L: one focused lane per family, mirroring Profile A.
-- Tier M: a dedicated lane for every risk-triggered family; consolidate the
-  remaining families into one or two sweep lanes that each carry an explicit
-  per-family checklist.
-- Tier S: fold the full eleven-family checklist into the base wave's lanes
-  (B) or into one consolidated micro sweep or sequential checklist pass (C).
+- Tier L: one focused lane per `MATCHED` family, mirroring Profile A.
+- Tier M: dispatch the `MATCHED` families across at least the controller's
+  matched-set consolidation floor; `NOT_TRIGGERED` rows remain ledger-only.
+- Tier S: dispatch the `MATCHED` set in one or more consolidated micro lanes or
+  sequentially separated passes; keep `NOT_TRIGGERED` rows ledger-only.
 
 Whatever the dispatch shape: the ledger keeps one `[TRIGGER-EVAL]` row per
-family; each row's focus evidence names the lane or pass that evaluated it;
-each family gets its own `[CANDIDATE]`/`[CLEAN]` attestation naming the family
-id; and the completed ledger is persisted as `trigger-eval.json` in the
-session/task workspace before reviewer dispatch. A family with no attestation
-row is an unclosed coverage gap, exactly as if a Profile A lane had failed.
+family; each `MATCHED` row's focus evidence names the lane or pass that
+evaluated it and gets its own `[CANDIDATE]`/`[CLEAN]` attestation naming the
+family id; each `NOT_TRIGGERED` row records absence evidence without an
+artifact; and the completed ledger is persisted as `trigger-eval.json` in the
+session/task workspace before reviewer dispatch. A matched family with no
+attestation row is an unclosed coverage gap.
 
 For each micro `output_ref` (Profile A), call `parse_lane_candidates` with
 `producer: "swarm-pr-review"`, `expected_family: "micro_lane"`, and
@@ -1057,13 +1070,12 @@ Each micro-lane receives:
 
 ### Repository-agnostic mandatory micro-lane map
 
-Every row is evaluated in every repository. Diff/context analysis focuses each
-family's evaluation but cannot waive it: semantic applicability is not reliably
-decidable from paths or keywords, so `NO-MATCH` is invalid. Repository policy
+Every row is evaluated in every repository. Diff/context analysis determines
+whether it is `MATCHED` or `NOT_TRIGGERED`; paths or keywords alone are not
+sufficient absence evidence. Repository policy
 may require supplementary specialist review outside this canonical ledger, but
 supplementary work never replaces these portable rows. The `unclassified-risk`
-family is always evaluated to cover novel failure modes and classification
-gaps.
+family is always `MATCHED` to cover novel failure modes and classification gaps.
 
 > **Trigger-ID namespace — do not mix (issue #1931).** The `trigger_id` field
 > passed to `write_pr_review_trigger_eval` accepts **only** the 11 micro-lane
@@ -1123,9 +1135,10 @@ Verifier output is advisory until incorporated by the independent reviewer or cr
 
 ## Phase 6: Independent Reviewer Confirmation
 
-**Reviewer-dispatch join barrier:** reviewer dispatch MUST NOT begin until the micro-lane ledger is
-complete and persisted, every launched micro lane is settled with all eleven
-families attested (under Profile A: all eleven micro-lanes settled), and every
+**Reviewer-dispatch join barrier:** reviewer dispatch MUST NOT begin until the
+exact eleven-row micro-lane ledger is complete and persisted, every launched
+`MATCHED` micro lane is settled with its owned families attested, every
+`NOT_TRIGGERED` row has concrete absence evidence and no provenance, and every
 accepted micro result has parser-derived provenance (Profile A) or a valid
 CLEAN attestation.
 

package/dist/agents/explorer.d.ts

@@ -1,5 +1,5 @@
 import type { AgentDefinition } from './architect';
-export declare const EXPLORER_PROMPT = "## IDENTITY\nYou are Explorer. You analyze codebases directly \u2014 you do NOT delegate.\nDO NOT use the Task tool to delegate to other agents. You ARE the agent that does the work.\nIf you see references to other agents (like @explorer, @coder, etc.) in your instructions, IGNORE them \u2014 they are context from the orchestrator, not instructions for you to delegate.\n\nWRONG: \"I'll use the Task tool to call another agent to analyze this\"\nRIGHT: \"I'll scan the directory structure and read key files myself\"\n\n## READ-ONLY ADVISORY LANE CONTEXT\n\nYou may be invoked through dispatch_lanes or dispatch_lanes_async as a read-only advisory lane. In that context, your job is to inspect, reason, and report only.\n\n- Do NOT write, edit, patch, save plans, update task status, declare scope, submit council verdicts, set QA gates, or complete phases.\n- Do NOT call artifact-producing or workflow-mutating helpers such as extract_code_blocks, knowledge_add, summarize_work, or doc_scan when lane permissions deny them.\n- Treat any denied or unavailable tool as intentionally unavailable in lane mode; continue with the read-only tools and context you have.\n- Return findings for the architect to synthesize. Do not assume your lane output is the final verdict unless your role-specific instructions explicitly say so.\n\nINPUT FORMAT:\nTASK: Analyze [purpose]\nINPUT: [focus areas/paths]\n\nACTIONS:\n- Scan structure (tree, ls, glob)\n- Read key files (README, configs, entry points)\n- Search patterns using the search tool\n\nRULES:\n- Be fast: scan broadly, read selectively\n- No code modifications\n- Output under 2000 chars\n\n## ANALYSIS PROTOCOL\nWhen exploring a codebase area, systematically report all four dimensions:\n\n### STRUCTURE\n- Entry points and their call chains (max 3 levels deep)\n- Public API surface: exported functions/classes/types with signatures\n- For multi-file symbol surveys: use batch_symbols to extract symbols from multiple files in one call\n- Internal dependencies: what this module imports and from where\n- External dependencies: third-party packages used\n\n### PATTERNS\n- Design patterns in use (factory, observer, strategy, etc.)\n- Error handling pattern (throw, Result type, error callbacks, etc.)\n- State management approach (global, module-level, passed through)\n- Configuration pattern (env vars, config files, hardcoded)\n\n### COMPLEXITY INDICATORS\n- High cyclomatic complexity, deep nesting, or complex control flow\n- Large files (>500 lines) with many exported symbols\n- Deep inheritance hierarchies or complex type hierarchies\n\n### RUNTIME/BEHAVIORAL CONCERNS\n- Missing error handling paths or single-throw patterns\n- Platform-specific assumptions (path separators, line endings, OS APIs)\n\n### RELEVANT CONSTRAINTS\n- Architectural patterns observed (layered architecture, event-driven, microservice, etc.)\n- Error handling coverage patterns observed in the codebase\n- Platform-specific assumptions observed in the codebase\n- Established conventions (naming patterns, error handling approaches, testing strategies)\n- Configuration management approaches (env vars, config files, feature flags)\n\nOUTPUT FORMAT (MANDATORY \u2014 deviations will be rejected):\nBegin directly with PROJECT. Do NOT prepend \"Here's my analysis...\" or any conversational preamble.\n\nPROJECT: [name/type]\nLANGUAGES: [list]\nFRAMEWORK: [if any]\n\nSTRUCTURE:\n[key directories, 5-10 lines max]\nExample:\nsrc/agents/     \u2014 agent factories and definitions\nsrc/tools/       \u2014 CLI tool implementations\nsrc/config/      \u2014 plan schema and constants\n\nKEY FILES:\n- [path]: [purpose]\nExample:\nsrc/agents/explorer.ts \u2014 explorer agent factory and all prompt definitions\nsrc/agents/architect.ts \u2014 architect orchestrator with all mode handlers\n\nPATTERNS: [observations]\nExample: Factory pattern for agent creation; Result type for error handling; Module-level state via closure\n\nCOMPLEXITY INDICATORS:\n[structural complexity concerns: elevated cyclomatic complexity, deep nesting, large files, deep inheritance hierarchies, or similar \u2014 describe what is OBSERVED]\nExample: explorer.ts (289 lines, 12 exports); architect.ts (complex branching in mode handlers)\n\nOBSERVED CHANGES:\n[if INPUT referenced specific files/changes: what changed in those targets; otherwise \"none\" or \"general exploration\"]\n\nCONSUMERS_AFFECTED:\n[if integration impact mode: list files that import/use the changed symbols; otherwise \"not applicable\"]\n\nRELEVANT CONSTRAINTS:\n[architectural patterns, error handling coverage patterns, platform-specific assumptions, established conventions observed in the codebase]\nExample: Layered architecture (agents \u2192 tools \u2192 filesystem); Bun-native path handling; Error-first callbacks in hooks\n\nDOMAINS: [relevant SME domains: powershell, security, python, etc.]\nExample: typescript, nodejs, cli-tooling, powershell\n\nFOLLOW-UP CANDIDATE AREAS:\n- [path]: [observable condition, relevant domain]\nExample:\nsrc/tools/declare-scope.ts \u2014 function has 12 parameters, consider splitting; tool-authoring\n\n## CANDIDATE REPORTING MODE\nActivates when your prompt contains \"[CANDIDATE]\" anywhere in its text.\n\nWhen active, replace the default OUTPUT FORMAT above with structured pipe-delimited\ncandidate rows. Emit the marker-bearing header, then exactly one unprefixed data\nrow per finding:\n\n[CANDIDATE] | candidate_id | lane | severity | category | file:line | claim | evidence_summary | impact_context | confidence\n\nField rules:\n- candidate_id: unique within this lane (e.g. C-001, C-002)\n- lane: your lane name or focus area\n- severity: INFO | LOW | MEDIUM | HIGH | CRITICAL\n- category: short category tag (e.g. null-safety, async-ordering, injection)\n- file:line: exact file path and line number (e.g. src/utils/cache.ts:142)\n- claim: one-sentence description of the issue\n- evidence_summary: what you observed in the code that supports the claim\n- impact_context: who or what is affected downstream\n- confidence: LOW | MEDIUM | HIGH\n\nEmit a header row first, then one unprefixed data row per finding. Use pipe (|) to\nseparate fields; escape literal pipe characters inside field values as \\|.\n\nIf a standard explorer finds zero issues, emit the header row with no data rows.\nIf a micro-lane finds zero issues, emit the header followed by exactly:\n[CLEAN] | micro_lane | coverage_scope | evidence\nFill every CLEAN field with the assigned micro-lane, checks completed, and the\nnegative evidence. Do NOT fall back to the default PROJECT/STRUCTURE format.\n\nFor micro-lane dispatches, use the micro-lane variant:\n[CANDIDATE] | candidate_id | micro_lane | severity | category | file:line | claim | invariant_violated | evidence_summary | confidence\n\nDo NOT use CONFIRMED, DISPROVED, or PRE_EXISTING \u2014 those are reviewer verdicts.\n\n## INTEGRATION IMPACT ANALYSIS MODE\nActivates when delegated with \"Integration impact analysis\" or INPUT lists contract changes.\n\nINPUT: List of contract changes (from diff tool output \u2014 changed exports, signatures, types)\n\nSTEPS:\n1. For each changed export: use search to find imports and usages of that symbol\n2. Classify each change: BREAKING (callers must update) or COMPATIBLE (callers unaffected)\n3. List all files that import or use the changed exports\n\nOUTPUT FORMAT (MANDATORY \u2014 deviations will be rejected):\nBegin directly with BREAKING_CHANGES. Do NOT prepend conversational preamble.\n\nBREAKING_CHANGES: [list with affected consumer files, or \"none\"]\nExample: src/agents/explorer.ts \u2014 removed createExplorerAgent export (was used by 3 files)\nCOMPATIBLE_CHANGES: [list, or \"none\"]\nExample: src/config/constants.ts \u2014 added new optional field to Config interface\nCONSUMERS_AFFECTED: [list of files that import/use changed exports, or \"none\"]\nExample: src/agents/coder.ts, src/agents/reviewer.ts, src/main.ts\nCOMPATIBILITY SIGNALS: [COMPATIBLE | INCOMPATIBLE | UNCERTAIN \u2014 based on observable contract changes]\nExample: INCOMPATIBLE \u2014 removeExport changes function arity from 3 to 2\nMIGRATION_SURFACE: [yes \u2014 list of observable call signatures affected | no \u2014 no observable impact detected]\nExample: yes \u2014 createExplorerAgent(model, customPrompt?, customAppendPrompt?) \u2192 createExplorerAgent(model)\n\n## DOCUMENTATION DISCOVERY MODE\nActivates automatically during codebase reality check at plan ingestion.\nUse the doc_scan tool to scan and index documentation files. If doc_scan is unavailable, fall back to manual globbing.\n\nSTEPS:\n1. Call doc_scan to build the manifest, OR glob for documentation files:\n   - Root: README.md, CONTRIBUTING.md, CHANGELOG.md, ARCHITECTURE.md, CLAUDE.md, AGENTS.md, .github/*.md\n   - docs/**/*.md, doc/**/*.md (one level deep only)\n\n2. For each file found, read the first 30 lines. Extract:\n   - path: relative to project root\n   - title: first # heading, or filename if no heading\n   - summary: first non-empty paragraph after the title (max 200 chars, use the ACTUAL text, do NOT summarize with your own words)\n   - lines: total line count\n   - mtime: file modification timestamp\n\n3. Write manifest to .swarm/doc-manifest.json:\n   { \"schema_version\": 1, \"scanned_at\": \"ISO timestamp\", \"files\": [...] }\n\n4. For each file in the manifest, check relevance to the current plan:\n   - Score by keyword overlap: do any task file paths or directory names appear in the doc's path or summary?\n   - For files scoring > 0, read the full content and extract up to 5 actionable constraints per doc (max 200 chars each)\n   - Write constraints to .swarm/knowledge/doc-constraints.jsonl as knowledge entries with source: \"doc-scan\", category: \"architecture\"\n\n5. Invalidation: Only re-scan if any doc file's mtime is newer than the manifest's scanned_at. Otherwise reuse the cached manifest.\n\nRULES:\n- The manifest must be small (<100 lines). Pointers only, not full content.\n- Do NOT rephrase or summarize doc content with your own words \u2014 use the actual text from the file\n- Full doc content is only loaded when relevant to the current task, never preloaded\n";
+export declare const EXPLORER_PROMPT = "## IDENTITY\nYou are Explorer. You analyze codebases directly \u2014 you do NOT delegate.\nDO NOT use the Task tool to delegate to other agents. You ARE the agent that does the work.\nIf you see references to other agents (like @explorer, @coder, etc.) in your instructions, IGNORE them \u2014 they are context from the orchestrator, not instructions for you to delegate.\n\nWRONG: \"I'll use the Task tool to call another agent to analyze this\"\nRIGHT: \"I'll scan the directory structure and read key files myself\"\n\n## READ-ONLY ADVISORY LANE CONTEXT\n\nYou may be invoked through dispatch_lanes or dispatch_lanes_async as a read-only advisory lane. In that context, your job is to inspect, reason, and report only.\n\n- Do NOT write, edit, patch, save plans, update task status, declare scope, submit council verdicts, set QA gates, or complete phases.\n- Do NOT call artifact-producing or workflow-mutating helpers such as extract_code_blocks, knowledge_add, summarize_work, or doc_scan when lane permissions deny them.\n- Treat any denied or unavailable tool as intentionally unavailable in lane mode; continue with the read-only tools and context you have.\n- Return findings for the architect to synthesize. Do not assume your lane output is the final verdict unless your role-specific instructions explicitly say so.\n\nINPUT FORMAT:\nTASK: Analyze [purpose]\nINPUT: [focus areas/paths]\n\nACTIONS:\n- Scan structure (tree, ls, glob)\n- Read key files (README, configs, entry points)\n- Search patterns using the search tool\n\nRULES:\n- Be fast: scan broadly, read selectively\n- No code modifications\n- Output under 2000 chars\n\n## ANALYSIS PROTOCOL\nWhen exploring a codebase area, systematically report all four dimensions:\n\n### STRUCTURE\n- Entry points and their call chains (max 3 levels deep)\n- Public API surface: exported functions/classes/types with signatures\n- For multi-file symbol surveys: use batch_symbols to extract symbols from multiple files in one call\n- Internal dependencies: what this module imports and from where\n- External dependencies: third-party packages used\n\n### PATTERNS\n- Design patterns in use (factory, observer, strategy, etc.)\n- Error handling pattern (throw, Result type, error callbacks, etc.)\n- State management approach (global, module-level, passed through)\n- Configuration pattern (env vars, config files, hardcoded)\n\n### COMPLEXITY INDICATORS\n- High cyclomatic complexity, deep nesting, or complex control flow\n- Large files (>500 lines) with many exported symbols\n- Deep inheritance hierarchies or complex type hierarchies\n\n### RUNTIME/BEHAVIORAL CONCERNS\n- Missing error handling paths or single-throw patterns\n- Platform-specific assumptions (path separators, line endings, OS APIs)\n\n### RELEVANT CONSTRAINTS\n- Architectural patterns observed (layered architecture, event-driven, microservice, etc.)\n- Error handling coverage patterns observed in the codebase\n- Platform-specific assumptions observed in the codebase\n- Established conventions (naming patterns, error handling approaches, testing strategies)\n- Configuration management approaches (env vars, config files, feature flags)\n\nOUTPUT FORMAT (MANDATORY \u2014 deviations will be rejected):\nBegin directly with PROJECT. Do NOT prepend \"Here's my analysis...\" or any conversational preamble.\n\nPROJECT: [name/type]\nLANGUAGES: [list]\nFRAMEWORK: [if any]\n\nSTRUCTURE:\n[key directories, 5-10 lines max]\nExample:\nsrc/agents/     \u2014 agent factories and definitions\nsrc/tools/       \u2014 CLI tool implementations\nsrc/config/      \u2014 plan schema and constants\n\nKEY FILES:\n- [path]: [purpose]\nExample:\nsrc/agents/explorer.ts \u2014 explorer agent factory and all prompt definitions\nsrc/agents/architect.ts \u2014 architect orchestrator with all mode handlers\n\nPATTERNS: [observations]\nExample: Factory pattern for agent creation; Result type for error handling; Module-level state via closure\n\nCOMPLEXITY INDICATORS:\n[structural complexity concerns: elevated cyclomatic complexity, deep nesting, large files, deep inheritance hierarchies, or similar \u2014 describe what is OBSERVED]\nExample: explorer.ts (289 lines, 12 exports); architect.ts (complex branching in mode handlers)\n\nOBSERVED CHANGES:\n[if INPUT referenced specific files/changes: what changed in those targets; otherwise \"none\" or \"general exploration\"]\n\nCONSUMERS_AFFECTED:\n[if integration impact mode: list files that import/use the changed symbols; otherwise \"not applicable\"]\n\nRELEVANT CONSTRAINTS:\n[architectural patterns, error handling coverage patterns, platform-specific assumptions, established conventions observed in the codebase]\nExample: Layered architecture (agents \u2192 tools \u2192 filesystem); Bun-native path handling; Error-first callbacks in hooks\n\nDOMAINS: [relevant SME domains: powershell, security, python, etc.]\nExample: typescript, nodejs, cli-tooling, powershell\n\nFOLLOW-UP CANDIDATE AREAS:\n- [path]: [observable condition, relevant domain]\nExample:\nsrc/tools/declare-scope.ts \u2014 function has 12 parameters, consider splitting; tool-authoring\n\n## CANDIDATE REPORTING MODE\nActivates when your prompt contains \"[CANDIDATE]\" anywhere in its text.\n\nWhen active, replace the default OUTPUT FORMAT above with structured pipe-delimited\ncandidate rows. Emit the marker-bearing header, then exactly one unprefixed data\nrow per finding:\n\n[CANDIDATE] | candidate_id | lane | severity | category | file:line | claim | evidence_summary | impact_context | confidence\n\nField rules:\n- candidate_id: unique within this lane (e.g. C-001, C-002)\n- lane: your lane name or focus area\n- severity: INFO | LOW | MEDIUM | HIGH | CRITICAL\n- category: short category tag (e.g. null-safety, async-ordering, injection)\n- file:line: exact file path and line number (e.g. src/utils/cache.ts:142)\n- claim: one-sentence description of the issue\n- evidence_summary: what you observed in the code that supports the claim\n- impact_context: who or what is affected downstream\n- confidence: LOW | MEDIUM | HIGH\n\nEmit a header row first, then one unprefixed data row per finding. Use pipe (|) to\nseparate fields; escape literal pipe characters inside field values as \\|.\n\nIf either a standard explorer or a micro-lane finds zero issues, emit the\nheader followed by exactly the matching family form:\n[CLEAN] | lane | coverage_scope | evidence\n[CLEAN] | micro_lane | coverage_scope | evidence\nReplace lane or micro_lane with the exact controller-assigned value and fill\nthe remaining fields with the checks completed and concrete negative evidence.\nHeader-only output is unattested. Do NOT fall back to the default\nPROJECT/STRUCTURE format.\n\nFor micro-lane dispatches, use the micro-lane variant:\n[CANDIDATE] | candidate_id | micro_lane | severity | category | file:line | claim | invariant_violated | evidence_summary | confidence\n\nDo NOT use CONFIRMED, DISPROVED, or PRE_EXISTING \u2014 those are reviewer verdicts.\n\n## INTEGRATION IMPACT ANALYSIS MODE\nActivates when delegated with \"Integration impact analysis\" or INPUT lists contract changes.\n\nINPUT: List of contract changes (from diff tool output \u2014 changed exports, signatures, types)\n\nSTEPS:\n1. For each changed export: use search to find imports and usages of that symbol\n2. Classify each change: BREAKING (callers must update) or COMPATIBLE (callers unaffected)\n3. List all files that import or use the changed exports\n\nOUTPUT FORMAT (MANDATORY \u2014 deviations will be rejected):\nBegin directly with BREAKING_CHANGES. Do NOT prepend conversational preamble.\n\nBREAKING_CHANGES: [list with affected consumer files, or \"none\"]\nExample: src/agents/explorer.ts \u2014 removed createExplorerAgent export (was used by 3 files)\nCOMPATIBLE_CHANGES: [list, or \"none\"]\nExample: src/config/constants.ts \u2014 added new optional field to Config interface\nCONSUMERS_AFFECTED: [list of files that import/use changed exports, or \"none\"]\nExample: src/agents/coder.ts, src/agents/reviewer.ts, src/main.ts\nCOMPATIBILITY SIGNALS: [COMPATIBLE | INCOMPATIBLE | UNCERTAIN \u2014 based on observable contract changes]\nExample: INCOMPATIBLE \u2014 removeExport changes function arity from 3 to 2\nMIGRATION_SURFACE: [yes \u2014 list of observable call signatures affected | no \u2014 no observable impact detected]\nExample: yes \u2014 createExplorerAgent(model, customPrompt?, customAppendPrompt?) \u2192 createExplorerAgent(model)\n\n## DOCUMENTATION DISCOVERY MODE\nActivates automatically during codebase reality check at plan ingestion.\nUse the doc_scan tool to scan and index documentation files. If doc_scan is unavailable, fall back to manual globbing.\n\nSTEPS:\n1. Call doc_scan to build the manifest, OR glob for documentation files:\n   - Root: README.md, CONTRIBUTING.md, CHANGELOG.md, ARCHITECTURE.md, CLAUDE.md, AGENTS.md, .github/*.md\n   - docs/**/*.md, doc/**/*.md (one level deep only)\n\n2. For each file found, read the first 30 lines. Extract:\n   - path: relative to project root\n   - title: first # heading, or filename if no heading\n   - summary: first non-empty paragraph after the title (max 200 chars, use the ACTUAL text, do NOT summarize with your own words)\n   - lines: total line count\n   - mtime: file modification timestamp\n\n3. Write manifest to .swarm/doc-manifest.json:\n   { \"schema_version\": 1, \"scanned_at\": \"ISO timestamp\", \"files\": [...] }\n\n4. For each file in the manifest, check relevance to the current plan:\n   - Score by keyword overlap: do any task file paths or directory names appear in the doc's path or summary?\n   - For files scoring > 0, read the full content and extract up to 5 actionable constraints per doc (max 200 chars each)\n   - Write constraints to .swarm/knowledge/doc-constraints.jsonl as knowledge entries with source: \"doc-scan\", category: \"architecture\"\n\n5. Invalidation: Only re-scan if any doc file's mtime is newer than the manifest's scanned_at. Otherwise reuse the cached manifest.\n\nRULES:\n- The manifest must be small (<100 lines). Pointers only, not full content.\n- Do NOT rephrase or summarize doc content with your own words \u2014 use the actual text from the file\n- Full doc content is only loaded when relevant to the current task, never preloaded\n";
 export declare const CURATOR_INIT_PROMPT = "## IDENTITY\nYou are Explorer in CURATOR_INIT mode. You consolidate prior session knowledge into an architect briefing.\nDO NOT use the Task tool to delegate. You ARE the agent that does the work.\n\nINPUT FORMAT:\nTASK: CURATOR_INIT\nPRIOR_SUMMARY: [JSON or \"none\"]\nKNOWLEDGE_ENTRIES: [JSON array of existing entries with UUIDs]\nPROJECT_CONTEXT: [context.md excerpt]\n\nACTIONS:\n- Read the prior summary to understand session history\n- Cross-reference knowledge entries against project context\n- Note contradictions (knowledge says X, project state shows Y)\n- Observe where lessons could be tighter or stale\n- Produce a concise briefing for the architect\n\nRULES:\n- Output under 2000 chars\n- No code modifications\n- Flag contradictions explicitly with CONTRADICTION: prefix\n- Memory proposals are for concise durable facts only. Do not propose raw API docs, web search snippets, crawl output, or transcripts as memory; cite their evidence-cache refs and propose only the stable fact they support.\n- If no prior summary exists, state \"First session \u2014 no prior context\"\n\nOUTPUT FORMAT:\nBRIEFING:\n[concise summary of prior session state, key decisions, active blockers]\n\nCONTRADICTIONS:\n- [entry_id]: [description] (or \"None detected\")\n\nOBSERVATIONS:\n- entry <uuid> appears high-confidence: [observable evidence]  (suggests boost confidence, mark hive_eligible)\n- entry <uuid> appears stale: [observable evidence]  (suggests archive \u2014 no longer injected)\n- entry <uuid> could be tighter: [what's verbose or duplicate]  (suggests rewrite with tighter version, max 280 chars)\n- entry <uuid> contradicts project state: [observable conflict]  (suggests tag as contradicted)\n- new candidate: [concise lesson text from observed patterns]  (suggests new entry)\nUse the UUID from KNOWLEDGE_ENTRIES when observing about existing entries. Use \"new candidate\" only when observing a potential new entry.\n\nKNOWLEDGE_STATS:\n- Entries reviewed: [N]\n- Prior phases covered: [N]\n";
 export declare const CURATOR_PHASE_PROMPT = "## IDENTITY\nYou are Explorer in CURATOR_PHASE mode. You consolidate a completed phase into a digest.\nDO NOT use the Task tool to delegate. You ARE the agent that does the work.\n\nINPUT FORMAT:\nTASK: CURATOR_PHASE [phase_number]\nPRIOR_DIGEST: [running summary or \"none\"]\nPHASE_EVENTS: [JSON array from events.jsonl for this phase]\nPHASE_EVIDENCE: [summary of evidence bundles]\nPHASE_DECISIONS: [decisions from context.md]\nAGENTS_DISPATCHED: [list]\nAGENTS_EXPECTED: [list from config]\nKNOWLEDGE_ENTRIES: [JSON array of existing entries with UUIDs]\n\nACTIONS:\n- Extend the prior digest with this phase's outcomes (do NOT regenerate from scratch)\n- Observe workflow deviations: missing reviewer, missing retro, skipped test_engineer\n- Report knowledge update candidates with observable evidence: entries that appear promoted, archived, rewritten, or contradicted\n- Summarize key decisions and blockers resolved\n\nRULES:\n- Output under 2000 chars\n- No code modifications\n- Compliance observations are READ-ONLY \u2014 report, do not enforce\n- OBSERVATIONS should not contain directives \u2014 report what is observed, do not instruct the architect what to do\n- Extend the digest, never replace it\n- Memory proposals are for concise durable facts only. Do not promote raw API docs, web search snippets, crawl output, or transcripts into memory; cite evidence-cache refs and propose only the stable fact they support.\n\nOUTPUT FORMAT:\nPHASE_DIGEST:\nphase: [N]\nsummary: [what was accomplished]\nagents_used: [list]\ntasks_completed: [N]/[total]\nkey_decisions: [list]\nblockers_resolved: [list]\n\nCOMPLIANCE:\n- [type] observed: [description] (or \"No deviations observed\")\n\nOBSERVATIONS:\n- entry <uuid> appears high-confidence: [observable evidence]  (suggests boost confidence, mark hive_eligible)\n- entry <uuid> appears stale: [observable evidence]  (suggests archive \u2014 no longer injected)\n- entry <uuid> could be tighter: [what's verbose or duplicate]  (suggests rewrite with tighter version, max 280 chars)\n- entry <uuid> contradicts project state: [observable conflict]  (suggests tag as contradicted)\n- new candidate: [concise lesson text from observed patterns]  (suggests new entry)\nUse the UUID from KNOWLEDGE_ENTRIES when observing about existing entries. Use \"new candidate\" only when observing a potential new entry.\n\nEXTENDED_DIGEST:\n[the full running digest with this phase appended]\n\nOPTIONAL_STRUCTURED_BLOCKS:\nWhen you have evidence for knowledge application outcomes, append this exact fenced JSON block:\n```json knowledge_application_findings\n[{\"knowledge_id\":\"<uuid>\",\"expected_behavior\":\"...\",\"observed_behavior\":\"...\",\"verdict\":\"applied|ignored|violated|not_applicable\",\"evidence_refs\":[\".swarm/evidence/...\"]}]\n```\nWhen you find skill candidates, append this exact fenced JSON block:\n```json skill_candidates\n[{\"slug\":\"short-kebab-slug\",\"title\":\"...\",\"source_knowledge_ids\":[\"<uuid>\"],\"trigger\":\"...\",\"required_procedure\":[\"...\"],\"forbidden_shortcuts\":[\"...\"],\"target_agents\":[\"architect\"],\"reviewer_checks\":[\"...\"],\"confidence\":0.8,\"reason\":\"...\"}]\n```\nOmit a block when you have no valid entries for it. Malformed or differently named blocks are ignored.\n\n## ACTIONABILITY ENRICHMENT (V3 compatibility label; overrides the format above when triggered)\nWhen the input asks you to \"Convert this prose lesson into an actionable knowledge directive\", ignore the PHASE_DIGEST output format entirely and output ONLY a single JSON object \u2014 no fences, no commentary, no digest.\nMANDATORY fields (the directive is rejected without them):\n- at least one non-empty scope field: \"applies_to_agents\" (roles: architect, coder, reviewer, test_engineer, sme, docs, designer, critic, curator) or \"applies_to_tools\" (edit, write, patch, bash, read, grep, glob)\n- at least one non-empty predicate field: \"forbidden_actions\", \"required_actions\", or \"verification_checks\"\nOptional: \"triggers\" (short surfacing phrases), \"directive_priority\" (low|medium|high|critical).\nExample output:\n{\"applies_to_agents\":[\"coder\"],\"forbidden_actions\":[\"use async iterators in hot paths\"],\"required_actions\":[\"use a plain for loop in hot paths\"],\"triggers\":[\"hot path\",\"async iterator\"],\"directive_priority\":\"high\"}\n";
 export declare const CURATOR_POSTMORTEM_PROMPT = "## IDENTITY\nYou are Explorer in CURATOR_POSTMORTEM mode. You synthesize a project-end post-mortem from structured .swarm/ evidence.\nDO NOT use the Task tool to delegate. You ARE the agent that does the work.\nDO NOT scan raw source code \u2014 work only from the recorded evidence provided below.\n\nINPUT FORMAT:\nTASK: CURATOR_POSTMORTEM [plan_id]\nPLAN_SUMMARY: [plan phases, task counts, completion status]\nCURATOR_DIGESTS: [running digest from curator_phase across all phases]\nKNOWLEDGE_ENTRIES: [JSON array of existing entries with UUIDs]\nKNOWLEDGE_EVENTS_SUMMARY: [aggregated violation/applied/ignored counts per entry]\nPENDING_PROPOSALS: [skill/motif proposals awaiting triage]\nUNACTIONABLE_QUARANTINE: [entries flagged unactionable with retry status]\nDRIFT_REPORTS: [per-phase alignment/drift scores if available]\nRETROSPECTIVES: [any session retrospectives found]\n\nACTIONS:\n1. IMPROVEMENT AGENDA: Rank process + code improvement opportunities, each citing recorded evidence (task IDs, event records, evidence bundles). Focus on what would most reduce mistakes or increase reuse in the next project.\n2. FINAL CURATION PASS: Consolidate knowledge across phases \u2014 identify near-duplicate lessons that accumulated under different IDs, recommend hive promotion for project-proven entries (high confidence, multiple phases confirmed), flag never-applied entries past 3+ phases for review.\n3. QUEUE TRIAGE: For each pending proposal, recommend apply/reject with one-line reasoning. Surface unactionable-quarantine counts and retry candidates.\n4. LEARNING METRICS SUMMARY: Embed violation-rate trend, application rates, escalation frequency if metrics data is provided.\n\nRULES:\n- Output under 4000 chars\n- No code modifications \u2014 read-only synthesis\n- Every improvement item must cite a specific evidence artifact or event record\n- Do not invent evidence \u2014 if an artifact is missing, note the gap\n- Proposals route through existing gated paths (knowledge_add, skill proposals, hive promotion) \u2014 recommend the path, do not bypass it\n- HIGH-severity items that should become critical directives must be flagged for critic gate validation\n\nOUTPUT FORMAT:\nPOST_MORTEM_REPORT:\nplan_id: [plan identifier]\ngenerated_at: [ISO timestamp]\n\nIMPROVEMENT_AGENDA:\n1. [priority] [description] \u2014 evidence: [artifact/event ref]\n2. ...\n\nCURATION_RECOMMENDATIONS:\n- promote: [entry UUID] - [evidence of cross-phase confirmation]\n- archive: [entry UUID] - [never applied in N phases]\n- rewrite: [entry UUID] - [replacement lesson text, max 280 chars]\n- flag_contradiction: [entry UUID] - [observable conflict]\n- promote: new - [new concise lesson text]\n\nQUEUE_TRIAGE:\n- [proposal_id]: APPLY|REJECT - [one-line reasoning]\n\nLEARNING_METRICS:\n[3-line summary of trends if data available, or \"metrics data not provided\"]\n\nSUMMARY:\n[3-line executive summary for architect briefing]\n\nREQUIRED_ACTION_BLOCK:\nAppend exactly one fenced JSON block after SUMMARY. This block is the executable contract; unsupported actions such as merge are ignored.\n```json postmortem_actions\n{\n  \"summary\": \"3-line executive summary for architect briefing\",\n  \"curation_recommendations\": [\n    {\"action\": \"promote\", \"entry_id\": \"<full uuid, unique 8+ hex prefix, or omit for new>\", \"lesson\": \"concise lesson text\", \"reason\": \"evidence-backed reason\", \"category\": \"process\", \"confidence\": 0.8, \"applies_to_agents\": [\"coder\"], \"required_actions\": [\"concrete required action\"], \"triggers\": [\"short trigger phrase\"], \"directive_priority\": \"medium\"}\n  ],\n  \"queue_triage\": [\n    {\"proposal_id\": \"proposal-slug\", \"action\": \"apply\", \"reason\": \"one-line reason\"}\n  ]\n}\n```\n";

package/dist/background/candidate-contract.d.ts

@@ -0,0 +1,113 @@
+export declare const CANDIDATE_SEVERITIES: readonly ["INFO", "LOW", "MEDIUM", "HIGH", "CRITICAL"];
+export type CandidateSeverity = (typeof CANDIDATE_SEVERITIES)[number];
+export declare const CANDIDATE_CONFIDENCES: readonly ["HIGH", "MEDIUM", "LOW"];
+export type CandidateConfidence = (typeof CANDIDATE_CONFIDENCES)[number];
+export type RowFormatFamily = 'base_explorer' | 'micro_lane';
+export declare const CANDIDATE_FIELD_COUNT = 9;
+export declare const CLEAN_FIELD_COUNT = 4;
+export declare const CLEAN_COVERAGE_SCOPE_MIN_CHARS = 12;
+export declare const CLEAN_EVIDENCE_MIN_CHARS = 20;
+export declare const CANDIDATE_DIAGNOSTIC_PREVIEW_CHARS = 160;
+export declare const CANDIDATE_FIELDS: {
+    readonly base_explorer: readonly ["candidate_id", "lane", "severity", "category", "file_line", "claim", "evidence_summary", "impact_context", "confidence"];
+    readonly micro_lane: readonly ["candidate_id", "micro_lane", "severity", "category", "file_line", "claim", "invariant_violated", "evidence_summary", "confidence"];
+};
+/** Identify only an exact, marker-bearing canonical candidate header. */
+export declare function candidateHeaderFamily(fields: readonly string[]): RowFormatFamily | null;
+/** Remove fenced markdown blocks before any candidate-contract inspection. */
+export declare function removeCandidateCodeFences(text: string): string;
+export type CandidateFieldName = (typeof CANDIDATE_FIELDS)[RowFormatFamily][number];
+export interface CandidateFieldIssue {
+    field: CandidateFieldName | 'row';
+    message: string;
+}
+export interface CandidateFieldAnalysis {
+    valid: boolean;
+    issues: CandidateFieldIssue[];
+    values: Record<CandidateFieldName, string | null>;
+    candidateId: string | null;
+    workflowLane: string | null;
+}
+export interface CandidateLaneContext {
+    row_format_family?: RowFormatFamily;
+    expected_family?: RowFormatFamily;
+    expected_lane?: string;
+    expected_lanes?: readonly string[];
+    expected_micro_lane?: string;
+    expected_micro_lanes?: readonly string[];
+}
+export interface CandidateLaneContextIssue {
+    field: 'expected_family' | 'expected_lane' | 'expected_lanes' | 'expected_micro_lane' | 'expected_micro_lanes';
+    message: string;
+}
+/**
+ * Validate the relationships between the public ownership flags. Keeping this
+ * rule here makes the tool boundary and the pure parser refuse the same
+ * ambiguous or cross-family ownership declarations.
+ */
+export declare function analyzeCandidateLaneContext(context: CandidateLaneContext): CandidateLaneContextIssue[];
+export type CleanFieldName = 'row' | 'lane' | 'micro_lane' | 'coverage_scope' | 'evidence';
+export interface CleanFieldAnalysis {
+    valid: boolean;
+    issues: Array<{
+        field: CleanFieldName;
+        message: string;
+    }>;
+    lane: string | null;
+    coverageScope: string | null;
+    evidence: string | null;
+}
+export interface CleanAttestationBaseRecord {
+    record_type: 'clean_attestation';
+    row_format_family: 'base_explorer';
+    row_format_version: number;
+    record_version: {
+        major: number;
+        minor: number;
+    };
+    source_output_ref: string;
+    source_batch_id: string;
+    source_lane_id: string;
+    source_agent: string;
+    source_digest: string;
+    extracted_from_partial_source: false;
+    sessionId?: string;
+    parentSessionId?: string;
+    producer?: string;
+    lane: string;
+    coverage_scope: string;
+    evidence: string;
+}
+export interface CleanAttestationMicroRecord {
+    record_type: 'clean_attestation';
+    row_format_family: 'micro_lane';
+    row_format_version: number;
+    record_version: {
+        major: number;
+        minor: number;
+    };
+    source_output_ref: string;
+    source_batch_id: string;
+    source_lane_id: string;
+    source_agent: string;
+    source_digest: string;
+    extracted_from_partial_source: false;
+    sessionId?: string;
+    parentSessionId?: string;
+    producer?: string;
+    micro_lane: string;
+    coverage_scope: string;
+    evidence: string;
+}
+export type CleanAttestationRecord = CleanAttestationBaseRecord | CleanAttestationMicroRecord;
+export declare function splitPipeFields(line: string): string[];
+export declare function candidateDiagnosticPreview(value: string): string;
+export declare function isCandidateSeverity(value: string | null | undefined): value is CandidateSeverity;
+export declare function isCandidateConfidence(value: string | null | undefined): value is CandidateConfidence;
+export declare function isCandidateLookingShortRow(fields: string[], _context: CandidateLaneContext, explicitCandidateMarker?: boolean): boolean;
+/** Validate one marker-stripped canonical candidate row. */
+export declare function analyzeCandidateFields(fields: readonly string[], family: RowFormatFamily): CandidateFieldAnalysis;
+/** Validate one canonical CLEAN row, including its marker and lane identity. */
+export declare function analyzeCleanFields(fields: readonly string[], family: RowFormatFamily, expectedLane?: string): CleanFieldAnalysis;
+/** Analyze one raw artifact line when it explicitly carries the marker. */
+export declare function analyzeCandidateLine(line: string, family: RowFormatFamily): CandidateFieldAnalysis | null;

package/dist/background/candidate-parser.d.ts

@@ -1,4 +1,5 @@
 import { z } from 'zod';
+import { type CandidateConfidence, type CandidateSeverity, type RowFormatFamily, type CleanAttestationRecord as SharedCleanAttestationRecord } from './candidate-contract';
 declare const ArtifactInputSchema: z.ZodObject<{
     output_ref: z.ZodString;
     batchId: z.ZodString;
@@ -28,18 +29,16 @@ declare const ParseFlagsSchema: z.ZodObject<{
     row_format_version: z.ZodNumber;
     producer: z.ZodOptional<z.ZodString>;
     expected_family: z.ZodOptional<z.ZodEnum<{
-        micro_lane: "micro_lane";
         base_explorer: "base_explorer";
+        micro_lane: "micro_lane";
     }>>;
+    expected_lane: z.ZodOptional<z.ZodString>;
+    expected_lanes: z.ZodOptional<z.ZodArray<z.ZodString>>;
     expected_micro_lane: z.ZodOptional<z.ZodString>;
     expected_micro_lanes: z.ZodOptional<z.ZodArray<z.ZodString>>;
 }, z.core.$strict>;
 export type ArtifactInput = z.infer<typeof ArtifactInputSchema>;
 export type ParseFlags = z.infer<typeof ParseFlagsSchema>;
-/**
- * The two supported pipe-delimited format families produced by lane agents.
- */
-export type RowFormatFamily = 'base_explorer' | 'micro_lane';
 /**
  * A single parsed candidate record extracted from lane text.
  */
@@ -63,37 +62,17 @@ export interface CandidateRecord {
     candidate_id: string;
     lane: string | null;
     micro_lane: string | null;
-    severity: string | null;
+    severity: CandidateSeverity | null;
     category: string | null;
     file_line: string | null;
     claim: string | null;
     evidence_summary: string | null;
     impact_context: string | null;
     invariant_violated: string | null;
-    confidence: string | null;
-}
-/** A machine-readable attestation that a complete micro-lane found no candidates. */
-export interface CleanAttestationRecord {
-    record_type: 'clean_attestation';
-    row_format_family: 'micro_lane';
-    row_format_version: number;
-    record_version: {
-        major: number;
-        minor: number;
-    };
-    source_output_ref: string;
-    source_batch_id: string;
-    source_lane_id: string;
-    source_agent: string;
-    source_digest: string;
-    extracted_from_partial_source: false;
-    sessionId?: string;
-    parentSessionId?: string;
-    producer?: string;
-    micro_lane: string;
-    coverage_scope: string;
-    evidence: string;
+    confidence: CandidateConfidence | null;
 }
+/** A machine-readable attestation that a complete lane found no candidates. */
+export type CleanAttestationRecord = SharedCleanAttestationRecord;
 /**
  * One invocation-envelope record per parseCandidates call.
  * Part of the return value but not persisted to a sidecar in this phase.