/**
 * Manifest validators — runtime JSON Schema check for v1 provider manifests.
 *
 * The schemas live under `schemas/{category}/provider.schema.json` and are
 * the authoritative contract for what a v1 manifest may contain. Daemon
 * code that loads a manifest at install or boot time runs it through
 * `validateCliProviderManifest()` first; failures are reported back to
 * the caller with structured paths so manifest authors can locate the
 * offending field without guessing.
 *
 * Validation lives in the SDK layer (not in provider-loader) so dashboards,
 * registry workers, and the provider publish flow can all reuse the
 * same code path and produce identical error messages.
 */
export interface ManifestValidationIssue {
    /** JSON Pointer-style path into the manifest. Empty string for the root. */
    path: string;
    /** Schema-keyword that failed. */
    keyword: string;
    /** Human-readable explanation. */
    message: string;
    /** Allowed values when the failure is an `enum` / `const` / `additionalProperties`. */
    allowed?: unknown;
}
export interface ManifestValidationResult {
    ok: boolean;
    issues: ManifestValidationIssue[];
}
/**
 * Validate a CLI provider.v1.json manifest. Returns `{ ok: true, issues: [] }`
 * on success and `{ ok: false, issues: [...] }` on failure with each issue
 * pointing at the offending field. Never throws — manifest parse errors
 * should be caught by the caller before this is called.
 */
export declare function validateCliProviderManifest(manifest: unknown): ManifestValidationResult;
/**
 * Render a list of validation issues as a single multi-line string,
 * suitable for log lines or daemon command error fields.
 */
export declare function formatManifestValidationIssues(issues: ManifestValidationIssue[]): string;
