@oss-autopilot/core - v3.42.2
    Preparing search index...

    Interface VetOutput

    Output of the vet command

    interface VetOutput {
        antiLLMPolicy?: {
            matched: boolean;
            matchedKeywords: string[];
            sourceFile: string | null;
        };
        complexityUnlocked?: true;
        gistSyncWarning?: string;
        grade: { reason: string; score: number };
        issue: {
            labels: string[];
            number: number;
            repo: string;
            title: string;
            url: string;
        };
        linkedPR?: CandidateLinkedPR;
        linkedPRClassification?: | "none"
        | "user_open"
        | "user_closed"
        | "user_merged"
        | "other_open"
        | "other_closed"
        | "other_merged";
        pickRecordError?: string;
        projectHealth: unknown;
        reasonsToApprove: string[];
        reasonsToSkip: string[];
        recommendation: "approve"
        | "skip"
        | "needs_review";
        repoCap?: RepoCapStatus;
        slmTriage?:
            | {
                confidence: "high"
                | "low"
                | "medium";
                decision: "investigate" | "skip" | "pursue";
                modelVersion: string;
                reasons: string[];
            }
            | null;
        vettingResult: unknown;
        workClaim?: KnownKeys<
            {
                branch?: string;
                expiresAt: string;
                finishedAt?: string;
                host?: string;
                kind: string & {}
                | "implementation"
                | "pr";
                machineId?: string;
                runId?: string;
                session: string;
                startedAt: string;
                status: "finished" | "running" | string & {};
                url: string;
                worktree?: string;
                [key: string]: unknown;
            },
        >;
    }
    Index
    antiLLMPolicy?: {
        matched: boolean;
        matchedKeywords: string[];
        sourceFile: string | null;
    }

    Result of scout's anti-LLM policy scan over CONTRIBUTING.md / CODE_OF_CONDUCT.md / README.md (#979). When matched is true the issue should be skipped — the project explicitly disallows AI-generated contributions.

    complexityUnlocked?: true

    Set when the complexIssues setting unlocked this repo: size is not a reason to pass on the issue.

    gistSyncWarning?: string

    Set when the saved prediction could not be pushed to the Gist.

    grade: { reason: string; score: number }

    Success-likelihood score (#858, 1-10): predicts whether a PR will merge.

    issue: {
        labels: string[];
        number: number;
        repo: string;
        title: string;
        url: string;
    }

    Compact linked-PR summary (#97 / scout 0.9.0). Present when the issue has a linked PR; absent otherwise. isStalled flags open PRs that haven't been touched in 30+ days as revive opportunities.

    linkedPRClassification?:
        | "none"
        | "user_open"
        | "user_closed"
        | "user_merged"
        | "other_open"
        | "other_closed"
        | "other_merged"

    Classification of the issue's first linked PR (#978). 'none' when no linked PR exists. The other buckets distinguish whether the user already has work in flight vs. a competing contributor.

    pickRecordError?: string

    Set when the vet-time prediction (#1824) could not be saved locally.

    projectHealth: unknown
    reasonsToApprove: string[]
    reasonsToSkip: string[]
    recommendation: "approve" | "skip" | "needs_review"
    repoCap?: RepoCapStatus

    Present only when the issue's repo is at the per-repo open-PR cap or is in excludeRepos; reason says which.

    slmTriage?:
        | {
            confidence: "high"
            | "low"
            | "medium";
            decision: "investigate" | "skip" | "pursue";
            modelVersion: string;
            reasons: string[];
        }
        | null

    Optional SLM pre-triage classification (#1122). Populated when the user has set slmTriageModel and a local Ollama instance answered within the timeout. null otherwise.

    vettingResult: unknown
    workClaim?: KnownKeys<
        {
            branch?: string;
            expiresAt: string;
            finishedAt?: string;
            host?: string;
            kind: string & {}
            | "implementation"
            | "pr";
            machineId?: string;
            runId?: string;
            session: string;
            startedAt: string;
            status: "finished" | "running" | string & {};
            url: string;
            worktree?: string;
            [key: string]: unknown;
        },
    >

    The live implementation claim on this issue (#1856), when a session is already building a fix for it. The recommendation is then skip and reasonsToSkip names the session; vet-list files the item as claimed.