Struct EditValidation 

pub struct EditValidation {
    pub status: String,
    pub introduced_errors: Vec<DiagnosticError>,
    pub resolved_errors: Vec<DiagnosticError>,
    pub validation_confidence: Option<String>,
    pub recovery_action: Option<String>,
}

The result of LSP validation for an edit operation.

Fields

status: String

"passed", "failed", "skipped", or "uncertain".

• "passed": validation ran and detected no new errors
• "failed": validation ran and detected new errors
• "skipped": validation was not performed (no LSP available)
• "uncertain": validation ran but results are unreliable (LSP warmup)

introduced_errors: Vec<DiagnosticError>

Errors introduced by the edit.

resolved_errors: Vec<DiagnosticError>

Errors resolved by the edit.

validation_confidence: Option<String>

IW-2: Confidence in the validation result.

• "high": LSP pull diagnostics used (definitive result).
• "medium": LSP push diagnostics used (may miss errors during indexing).
• "low": Both pre/post diagnostic sets were empty (could be clean or LSP not ready).
• "none": Validation was skipped entirely.

Agents should use this to decide whether to re-validate or proceed: "high" → trust the result; "low"/"none" → consider calling lsp_health first.

recovery_action: Option<String>

MT-4: Actionable recovery instruction for the agent.

Present when validation was skipped or degraded due to an LSP error. Tells the agent what to do next to recover or validate externally.

Examples:

• "Call lsp_health to check server status"
• "LSP request timed out. Call lsp_health(action='restart')."
• "No LSP configured. Install a language server or run cargo check externally."

Implementations

impl EditValidation

pub fn skipped() -> Self

Return a skipped validation result (no LSP available).

pub fn skipped_with_recovery(recovery_action: Option<String>) -> Self

Return a skipped validation result enriched with a recovery hint.

Use this instead of skipped() whenever an LspError is the cause — pass lsp_error.recovery_hint() as the recovery_action argument. This is the MT-4 telemetry path.

pub fn uncertain() -> Self

Return an uncertain validation result (LSP ran but results are unreliable).

Use when both pre- and post-edit diagnostics are empty, which could mean either (a) the code is genuinely clean, or (b) the LSP hasn’t finished indexing. Agents should treat “uncertain” as “possibly correct but unverified”.

Trait Implementations

impl Clone for EditValidation

fn clone(&self) -> EditValidation

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for EditValidation

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl JsonSchema for EditValidation

fn schema_name() -> Cow<'static, str>

The name of the generated JSON Schema.

fn schema_id() -> Cow<'static, str>

Returns a string that uniquely identifies the schema produced by this type.

fn json_schema(generator: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn inline_schema() -> bool

Whether JSON Schemas generated for this type should be included directly in parent schemas, rather than being re-used where possible using the $ref keyword.

impl Serialize for EditValidation

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.