You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(echidnabot): consume typed VerifyOutcome + mode/smtStatus from echidna GraphQL (follow-up to echidna#180) #245
echidna#180 / echidna PR #188 added the three GraphQL operations (verifyProof, suggestTactics(prover/context/goalState), proverStatus) the echidnabot client expects, and also surfaced the typed REST /api/verify taxonomy through GraphQL:
new fields on VerifyProofResult: outcome: VerifyOutcome!, mode: String, smtStatus: String
This issue tracks the echidnabot-side work to consume the new typed fields. The current client (bots/echidnabot/src/dispatcher/echidna_client.rs) only deserializes status / message / proverOutput / durationMs / artifacts from GraphQL and the bare valid: bool from REST, dropping the typed taxonomy in both transports.
What to do
In bots/echidnabot/src/dispatcher/echidna_client.rs:
Extend VerifyProofData with optional outcome: Option<String> (or a typed enum mirroring the new server-side enum), mode: Option<String>, smt_status: Option<String>. Update the GraphQL query string in verify_proof_graphql to request the new fields.
Extend RestVerifyResponse identically — the REST handler has been emitting these fields since the 2026-04-17 typed-outcome work; the client currently silently discards them (seam-audit sub-finding in echidna#180).
Wire the typed outcome into ProofResult so downstream consumers can distinguish Timeout from Failed without re-parsing the message string. The existing parse_proof_status heuristic stays as a fallback for when outcome is None (older echidna servers).
Add a unit test that round-trips a VerifyOutcome::TIMEOUT and asserts it lands as ProofStatus::Timeout on the bot side.
GitHub does not auto-close cross-repo Closes references, per the estate memory entry [Cross-repo Closes keyword doesn't auto-fire]. This issue parks the follow-up that echidna PR #188 unblocks.
Activity