import type { SeverityCounts, ValidationIssue } from '@vibe-agent-toolkit/agent-schema';
import type { EvidenceRecord } from '../evidence/index.js';
export interface ValidationResult {
    path: string;
    type: 'agent-skill' | 'vat-agent' | 'claude-plugin' | 'marketplace' | 'registry' | 'unknown';
    /**
     * The worst ACTIONABLE severity among {@link ValidationResult.issues}.
     *
     * Three values for a four-valued question, so it cannot express the
     * distribution — read {@link ValidationResult.issueCounts} for that. In
     * particular an info-only result is `success`, which is only honest because
     * the counts sit beside it.
     */
    status: 'success' | 'warning' | 'error';
    summary: string;
    issues: ValidationIssue[];
    /**
     * Issue counts by resolved severity. REQUIRED, deliberately: this repo had five
     * "issues → status" collapses and three different answers for an info-only set,
     * every one of which resolved the ambiguous case to the reassuring one. Making
     * the counts required means a new producer cannot omit the distribution — the
     * compiler asks for it rather than a reviewer having to notice it is missing.
     * Build it with `countBySeverity(issues)`.
     */
    issueCounts: SeverityCounts;
    metadata?: {
        name?: string;
        description?: string;
        version?: string;
        lineCount?: number;
        referenceFiles?: number;
    };
    /** Raw evidence records collected during validation. Rendered in --verbose. */
    evidence?: EvidenceRecord[];
    /** Validation results for transitively linked markdown files */
    linkedFiles?: LinkedFileValidationResult[];
}
/**
 * Validation result for a single linked markdown file (not SKILL.md)
 */
export interface LinkedFileValidationResult {
    /** Absolute path to the linked file */
    path: string;
    /** Line count of the file */
    lineCount: number;
    /** Number of links found in this file */
    linksFound: number;
    /** Number of links successfully validated */
    linksValidated: number;
    /** Issues found in this file */
    issues: ValidationIssue[];
}
export interface ValidateOptions {
    /** Path to SKILL.md file */
    skillPath: string;
    /** Root directory (for resolving relative links) */
    rootDir?: string;
    /**
     * Root that every emitted `ValidationIssue.location` is expressed relative
     * to — the ANCHOR base, not a validation-policy boundary. A batching caller
     * (`vat audit`, which spans many governing configs in one run) MUST pass its
     * invocation scan root here: otherwise each skill answers "relative to what?"
     * with its own nearest-ancestor config root and one report mixes coordinate
     * systems, letting two distinct files carry an identical `location`.
     *
     * Defaults to the same `findProjectRoot(dirname(skillPath)) ?? skill dir`
     * fallback `validateSkillForPackaging` uses, so a single-skill caller — where
     * scan root and project root coincide — needs no ceremony.
     */
    locationRoot?: string;
    /** Treat as VAT-generated skill (stricter validation) */
    isVATGenerated?: boolean;
    /** Check for files in skill directory that aren't referenced in markdown content */
    checkUnreferencedFiles?: boolean;
}
/**
 * Discriminated union representing different resource formats that can be validated
 */
export type ResourceFormat = {
    type: 'claude-plugin';
    path: string;
} | {
    type: 'marketplace';
    path: string;
} | {
    type: 'installed-plugins-registry';
    path: string;
    filename: string;
} | {
    type: 'known-marketplaces-registry';
    path: string;
    filename: string;
} | {
    type: 'unknown';
    path: string;
    reason?: string;
};
/**
 * One recognized manifest surface at a directory's root layer.
 *
 * Unlike {@link ResourceFormat} — which is the single-answer API used by
 * `detectResourceFormat()` — `Surface` is emitted by `enumerateSurfaces()`
 * which returns *every* manifest found in the same directory. A directory can
 * contain multiple surfaces: e.g., a skill-claude-plugin has both `agent-skill`
 * (root SKILL.md) and `claude-plugin` (.claude-plugin/plugin.json) surfaces.
 *
 * The `path` field points to the file to hand the validator: the SKILL.md path
 * for skills, the directory path for plugin/marketplace (those validators resolve
 * `<dir>/.claude-plugin/<manifest>.json` themselves).
 */
export type Surface = {
    type: 'agent-skill';
    path: string;
} | {
    type: 'claude-plugin';
    path: string;
} | {
    type: 'marketplace';
    path: string;
};
//# sourceMappingURL=types.d.ts.map