From d71cf752094254fa197ca153c4b6d231e2fc58d5 Mon Sep 17 00:00:00 2001 From: Alex Clarke Date: Wed, 9 Sep 2026 17:39:56 -0600 Subject: [PATCH] fix: Fixed the bad formatting in the finding-verifier agent --- assets/agents/finding-verifier/graph.yaml | 25 ++++++++--------------- 1 file changed, 9 insertions(+), 16 deletions(-) diff --git a/assets/agents/finding-verifier/graph.yaml b/assets/agents/finding-verifier/graph.yaml index 8a114aa..472fe48 100644 --- a/assets/agents/finding-verifier/graph.yaml +++ b/assets/agents/finding-verifier/graph.yaml @@ -129,6 +129,15 @@ nodes: - `UNVERIFIABLE` — you could not establish it either way (claim depends on runtime behavior, external systems, or code you cannot locate with confidence). Explain why in `note`. Doubt lands here, never in FALSE. + + Output format — respond with ONLY this JSON object, no prose before or + after it: + {"id": "", + "verdict": "VERIFIED" | "FALSE" | "UNVERIFIABLE", + "evidence": "", + "note": ""} prompt: | Repository: {{project_dir}} @@ -141,22 +150,6 @@ nodes: max_iterations: 8 max_attempts: 2 temperature: 0.1 - output_schema: - type: object - properties: - id: - type: string - description: The finding's id, echoed back verbatim. - verdict: - type: string - enum: [VERIFIED, FALSE, UNVERIFIABLE] - evidence: - type: string - description: Verbatim quoted line(s) with path:line. Required for VERIFIED and FALSE; empty for UNVERIFIABLE. - note: - type: string - description: One line — for FALSE the disproof in words, for UNVERIFIABLE why it could not be established. Empty otherwise. - required: [id, verdict, evidence, note] done: id: done