@fro.bot/systematic 3.25.0 → 3.25.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -212,7 +212,7 @@
212
212
  }
213
213
  },
214
214
  "findings": {
215
- "maxItems": 32,
215
+ "maxItems": 2048,
216
216
  "type": "array",
217
217
  "items": {
218
218
  "type": "object",
@@ -350,7 +350,7 @@
350
350
  },
351
351
  "input_finding_ids": {
352
352
  "minItems": 1,
353
- "maxItems": 32,
353
+ "maxItems": 2048,
354
354
  "type": "array",
355
355
  "items": {
356
356
  "type": "string",
@@ -412,7 +412,7 @@
412
412
  }
413
413
  },
414
414
  "declined_merges": {
415
- "maxItems": 32,
415
+ "maxItems": 2048,
416
416
  "type": "array",
417
417
  "items": {
418
418
  "type": "object",
@@ -434,7 +434,7 @@
434
434
  },
435
435
  "input_finding_ids": {
436
436
  "minItems": 2,
437
- "maxItems": 32,
437
+ "maxItems": 2048,
438
438
  "type": "array",
439
439
  "items": {
440
440
  "type": "string",
@@ -517,7 +517,7 @@
517
517
  "additionalProperties": false
518
518
  },
519
519
  "applied_fixes": {
520
- "maxItems": 32,
520
+ "maxItems": 2048,
521
521
  "type": "array",
522
522
  "items": {
523
523
  "type": "string",
@@ -527,7 +527,7 @@
527
527
  }
528
528
  },
529
529
  "residual_actionable_work": {
530
- "maxItems": 32,
530
+ "maxItems": 2048,
531
531
  "type": "array",
532
532
  "items": {
533
533
  "type": "string",
@@ -537,7 +537,7 @@
537
537
  }
538
538
  },
539
539
  "advisory_outputs": {
540
- "maxItems": 32,
540
+ "maxItems": 2048,
541
541
  "type": "array",
542
542
  "items": {
543
543
  "type": "string",
@@ -557,10 +557,10 @@
557
557
  "validators": {
558
558
  "type": "integer",
559
559
  "minimum": 0,
560
- "maximum": 64
560
+ "maximum": 2048
561
561
  },
562
562
  "residual_risks": {
563
- "maxItems": 64,
563
+ "maxItems": 4096,
564
564
  "type": "array",
565
565
  "items": {
566
566
  "type": "string",
@@ -570,7 +570,7 @@
570
570
  }
571
571
  },
572
572
  "testing_gaps": {
573
- "maxItems": 64,
573
+ "maxItems": 4096,
574
574
  "type": "array",
575
575
  "items": {
576
576
  "type": "string",
@@ -590,7 +590,7 @@
590
590
  }
591
591
  },
592
592
  "validator_failures": {
593
- "maxItems": 64,
593
+ "maxItems": 2048,
594
594
  "type": "array",
595
595
  "items": {
596
596
  "type": "string",
@@ -600,7 +600,7 @@
600
600
  }
601
601
  },
602
602
  "intent_uncertainty": {
603
- "maxItems": 64,
603
+ "maxItems": 67584,
604
604
  "type": "array",
605
605
  "items": {
606
606
  "type": "string",
@@ -17,16 +17,17 @@ Your sole job is to answer three questions about one specific finding and return
17
17
  Return ONLY valid JSON matching this schema. No prose, no markdown, no explanation outside the JSON object.
18
18
 
19
19
  {
20
- "validated": <boolean>,
21
- "reason": "<one sentence explaining why the finding is validated or not>"
20
+ "outcome": "true" | "false" | "failed" | "unavailable",
21
+ "reason": "<one sentence; omit when outcome is true>"
22
22
  }
23
23
 
24
24
  Rules:
25
25
  - You are a leaf validator inside an already-running review workflow. Do not invoke systematic skills or agents. Perform your analysis directly and return the JSON verdict only.
26
26
  - You are operationally read-only. You may use non-mutating inspection tools (file reads, glob, grep, git log, git diff, git show, git blame, gh pr view) to examine the code. Do not edit project files, change branches, commit, push, create PRs, or otherwise mutate the checkout or repository state.
27
- - Answer the three validation questions below. Set `validated: true` only when all three answers are YES. Set `validated: false` when any answer is NO.
28
- - The `reason` field must be one sentence. State the specific code evidence that drove your verdict (file name, function name, or line reference when relevant). Do not repeat the finding title verbatim.
29
- - Be conservative: when evidence is ambiguous, prefer `validated: true` (keep the finding in the actioned set). A false negative that lets a real bug through is worse than a false positive that the human reviewer can dismiss.
27
+ - Answer the three validation questions below. Set `outcome: "true"` only when all three answers are YES. Set `outcome: "false"` when any answer is NO.
28
+ - A `false` verdict needs a `reason` of one sentence. State the specific code evidence that drove your verdict (file name, function name, or line reference when relevant). Do not repeat the finding title verbatim. A `true` verdict carries no reason.
29
+ - Return `failed` with a reason when your analysis could not be completed, and `unavailable` with a reason when the code or tools you need could not be reached. Never guess a verdict to avoid either.
30
+ - Be conservative: when evidence is ambiguous, prefer `outcome: "true"` (keep the finding in the actioned set). A false negative that lets a real bug through is worse than a false positive that the human reviewer can dismiss.
30
31
  - Do not validate based on general coding principles alone. Ground your verdict in the actual code as written in this diff and the surrounding context.
31
32
  </output-contract>
32
33
 
@@ -42,8 +43,8 @@ Answer each question YES or NO based on the code evidence you find.
42
43
  3. **Is the issue already handled elsewhere?**
43
44
  Check whether the problem is already mitigated by a guard, middleware, framework behavior, type constraint, or other mechanism not visible at the cited line. A finding is not valid if the issue is fully handled at a higher or lower layer that the reviewer missed.
44
45
 
45
- Set `validated: true` only when: the issue is real (Q1 YES), introduced by this diff or newly relevant (Q2 YES), and not already handled elsewhere (Q3 YES).
46
- Set `validated: false` when any question is NO, and state which question failed and why in `reason`.
46
+ Set `outcome: "true"` only when: the issue is real (Q1 YES), introduced by this diff or newly relevant (Q2 YES), and not already handled elsewhere (Q3 YES).
47
+ Set `outcome: "false"` when any question is NO, and state which question failed and why in `reason`.
47
48
  </validation-questions>
48
49
 
49
50
  <finding>
@@ -89,8 +90,8 @@ Diff:
89
90
 
90
91
  ## Dispatch Notes
91
92
 
92
- - Dispatch one validator subagent per gated finding **in parallel** to keep latency bounded.
93
+ - Dispatch one validator subagent per gated finding. Run them in bounded batches, sized to what the harness handles reliably: the validators of a batch run in parallel, and a batch finishes before the next starts.
93
94
  - Pass the full diff and file list so the validator can inspect surrounding context, not just the cited line.
94
- - The validator returns `{validated, reason}`. Attach both fields to the finding before Stage 6.
95
- - **Never drop a finding based on the validator verdict.** A finding with `validated: false` moves to the "Filtered (not validated)" presentation group in Stage 6. It is never removed from the report.
96
- - If a validator subagent fails or times out, treat the finding as `validated: true` (conservative fallback — keep it in the actioned set) and note the validator failure in the Coverage section.
95
+ - The validator returns `{outcome, reason?}`. Record it as that finding's lifecycle result, keyed by `finding_id`, and carry it into `finalize` as `validator_lifecycle_results`.
96
+ - **Never drop a finding based on the validator verdict.** A finding with `outcome: "false"` moves to the "Filtered (not validated)" presentation group in Stage 6. It is never removed from the report.
97
+ - If a validator subagent fails, times out, or returns nothing, record `failed` or `unavailable` with a reason. The finding stays actionable and unvalidated, and `finalize` records a lifecycle failure that marks the run degraded. Report that validator in the Coverage section. Do not treat the finding as validated.