fix: [AI-5975] distinguish infrastructure errors from validation findings in validate tool

Validation findings (e.g., "table not found") are semantic results, not
operational failures. Only `result.error` / `data.error` (infrastructure
errors) should set `success: false`. Validation findings still populate
`metadata.error` for telemetry but keep `success: true`.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: suryaiyer95

packages/opencode/src/altimate/tools/altimate-core-validate.ts

@@ -23,11 +23,14 @@ export const AltimateCoreValidateTool = Tool.define("altimate_core_validate", {
         schema_context: args.schema_context,
       })
       const data = (result.data ?? {}) as Record<string, any>
-      const error = result.error ?? data.error ?? extractValidationErrors(data)
-      const isRealFailure = !!error
+      // Infrastructure errors (dispatcher/handler failures) vs validation findings.
+      // "table not found" is a valid analysis result, not an operational failure.
+      const infraError = result.error ?? data.error
+      const findingsError = extractValidationErrors(data)
+      const error = infraError ?? findingsError
       return {
-        title: isRealFailure ? "Validate: ERROR" : `Validate: ${data.valid ? "VALID" : "INVALID"}`,
-        metadata: { success: !isRealFailure, valid: data.valid, ...(error && { error }) },
+        title: infraError ? "Validate: ERROR" : `Validate: ${data.valid ? "VALID" : "INVALID"}`,
+        metadata: { success: !infraError, valid: data.valid, ...(error && { error }) },
         output: formatValidate(data),
       }
     } catch (e) {