@oss-autopilot/core 1.11.0 → 1.12.1

package/dist/core/issue-eligibility.js

@@ -1,151 +0,0 @@
-/**
- * Issue Eligibility — checks whether an individual issue is claimable:
- * existing PR detection, claim-phrase scanning, user merge history,
- * and requirement clarity analysis.
- *
- * Extracted from issue-vetting.ts (#621) to isolate eligibility logic.
- */
-import { paginateAll } from './pagination.js';
-import { errorMessage } from './errors.js';
-import { warn } from './logger.js';
-import { getHttpCache } from './http-cache.js';
-import { getSearchBudgetTracker } from './search-budget.js';
-const MODULE = 'issue-eligibility';
-/** Phrases that indicate someone has already claimed an issue. */
-const CLAIM_PHRASES = [
-    "i'm working on this",
-    'i am working on this',
-    "i'll take this",
-    'i will take this',
-    'working on it',
-    "i'd like to work on",
-    'i would like to work on',
-    'can i work on',
-    'may i work on',
-    'assigned to me',
-    "i'm on it",
-    "i'll submit a pr",
-    'i will submit a pr',
-    'working on a fix',
-    'working on a pr',
-];
-/**
- * Check whether an open PR already exists for the given issue.
- * Uses the timeline API (REST) to detect cross-referenced PRs, avoiding
- * the Search API's strict 30 req/min rate limit.
- */
-export async function checkNoExistingPR(octokit, owner, repo, issueNumber) {
-    try {
-        // Use the timeline API (REST, not Search) to detect linked PRs.
-        // This avoids consuming GitHub Search API quota (30 req/min limit).
-        // Timeline captures formally linked PRs via cross-referenced events
-        // but may miss PRs that only mention the issue number without a formal
-        // link — an acceptable trade-off since most PRs use "Fixes #N" syntax.
-        const timeline = await paginateAll((page) => octokit.issues.listEventsForTimeline({
-            owner,
-            repo,
-            issue_number: issueNumber,
-            per_page: 100,
-            page,
-        }));
-        const linkedPRs = timeline.filter((event) => {
-            const e = event;
-            return e.event === 'cross-referenced' && e.source?.issue?.pull_request;
-        });
-        return { passed: linkedPRs.length === 0 };
-    }
-    catch (error) {
-        const errMsg = errorMessage(error);
-        warn(MODULE, `Failed to check for existing PRs on ${owner}/${repo}#${issueNumber}: ${errMsg}. Assuming no existing PR.`);
-        return { passed: true, inconclusive: true, reason: errMsg };
-    }
-}
-/** TTL for cached merged-PR counts per repo (15 minutes). */
-const MERGED_PR_CACHE_TTL_MS = 15 * 60 * 1000;
-/**
- * Check how many merged PRs the authenticated user has in a repo.
- * Uses GitHub Search API. Returns 0 on error (non-fatal).
- * Results are cached per-repo for 15 minutes to avoid redundant Search API
- * calls when multiple issues from the same repo are vetted.
- */
-export async function checkUserMergedPRsInRepo(octokit, owner, repo) {
-    const cache = getHttpCache();
-    const cacheKey = `merged-prs:${owner}/${repo}`;
-    // Manual cache check — do not use cachedTimeBased because we must NOT cache
-    // error-path fallback values (a transient failure returning 0 would poison the
-    // cache for 15 minutes, hiding that the user has merged PRs in the repo).
-    const cached = cache.getIfFresh(cacheKey, MERGED_PR_CACHE_TTL_MS);
-    if (cached != null && typeof cached === 'number') {
-        return cached;
-    }
-    try {
-        const tracker = getSearchBudgetTracker();
-        await tracker.waitForBudget();
-        try {
-            // Use @me to search as the authenticated user
-            const { data } = await octokit.search.issuesAndPullRequests({
-                q: `repo:${owner}/${repo} is:pr is:merged author:@me`,
-                per_page: 1, // We only need total_count
-            });
-            // Only cache successful results
-            cache.set(cacheKey, '', data.total_count);
-            return data.total_count;
-        }
-        finally {
-            // Always record the call — failed requests still consume GitHub rate limit points
-            tracker.recordCall();
-        }
-    }
-    catch (error) {
-        const errMsg = errorMessage(error);
-        warn(MODULE, `Could not check merged PRs in ${owner}/${repo}: ${errMsg}. Defaulting to 0.`);
-        return 0; // Not cached — next call will retry
-    }
-}
-/**
- * Check whether an issue has been claimed by another contributor
- * by scanning recent comments for claim phrases.
- */
-export async function checkNotClaimed(octokit, owner, repo, issueNumber, commentCount) {
-    if (commentCount === 0)
-        return { passed: true };
-    try {
-        // Paginate through all comments
-        const comments = await octokit.paginate(octokit.issues.listComments, {
-            owner,
-            repo,
-            issue_number: issueNumber,
-            per_page: 100,
-        }, (response) => response.data);
-        // Limit to last 100 comments to avoid excessive processing
-        const recentComments = comments.slice(-100);
-        for (const comment of recentComments) {
-            const body = (comment.body || '').toLowerCase();
-            if (CLAIM_PHRASES.some((phrase) => body.includes(phrase))) {
-                return { passed: false };
-            }
-        }
-        return { passed: true };
-    }
-    catch (error) {
-        const errMsg = errorMessage(error);
-        warn(MODULE, `Failed to check claim status on ${owner}/${repo}#${issueNumber}: ${errMsg}. Assuming not claimed.`);
-        return { passed: true, inconclusive: true, reason: errMsg };
-    }
-}
-/**
- * Analyze whether an issue body has clear, actionable requirements.
- * Returns true when at least two "clarity indicators" are present:
- * numbered/bulleted steps, code blocks, expected-behavior keywords, length > 200.
- */
-export function analyzeRequirements(body) {
-    if (!body || body.length < 50)
-        return false;
-    // Check for clear structure
-    const hasSteps = /\d\.|[-*]\s/.test(body);
-    const hasCodeBlock = /```/.test(body);
-    const hasExpectedBehavior = /expect|should|must|want/i.test(body);
-    // Must have at least two indicators of clarity
-    const indicators = [hasSteps, hasCodeBlock, hasExpectedBehavior, body.length > 200];
-    return indicators.filter(Boolean).length >= 2;
-}

package/dist/core/issue-filtering.d.ts

@@ -1,51 +0,0 @@
-/**
- * Issue Filtering — pure functions for filtering and spam detection on search results.
- *
- * Extracted from issue-discovery.ts (#356) to isolate filtering logic:
- * label farming detection, doc-only filtering, per-repo caps, templated title detection.
- */
-/** Minimal shape of a GitHub search result item (from octokit.search.issuesAndPullRequests) */
-export interface GitHubSearchItem {
-    html_url: string;
-    repository_url: string;
-    updated_at: string;
-    title?: string;
-    labels?: Array<{
-        name?: string;
-    } | string>;
-    [key: string]: unknown;
-}
-/** Labels that indicate documentation-only issues (#105). */
-export declare const DOC_ONLY_LABELS: Set<string>;
-/**
- * Check if an issue's labels are ALL documentation-related (#105).
- * Issues with mixed labels (e.g., "good first issue" + "documentation") pass through.
- * Issues with no labels are not considered doc-only.
- */
-export declare function isDocOnlyIssue(item: GitHubSearchItem): boolean;
-/** Known beginner-type label names used to detect label-farming repos (#97). */
-export declare const BEGINNER_LABELS: Set<string>;
-/** Check if a single issue has an excessive number of beginner labels (>= 5). */
-export declare function isLabelFarming(item: GitHubSearchItem): boolean;
-/** Detect mass-created issue titles like "Add Trivia Question 61" or "Create Entry #5". */
-export declare function hasTemplatedTitle(title: string): boolean;
-/**
- * Batch-analyze search items to detect label-farming repositories (#97).
- * Returns a Set of repo full names (owner/repo) that appear to be spam.
- *
- * A repo is flagged if:
- * - ANY single issue has >= 5 beginner labels (strong individual signal), OR
- * - It has >= 3 issues with templated titles (batch signal)
- */
-export declare function detectLabelFarmingRepos(items: GitHubSearchItem[]): Set<string>;
-/**
- * Apply per-repo cap to candidates (#105).
- * Keeps at most `maxPerRepo` issues from any single repo.
- * Maintains the existing sort order — first N from each repo are kept,
- * excess issues from over-represented repos are dropped.
- */
-export declare function applyPerRepoCap<T extends {
-    issue: {
-        repo: string;
-    };
-}>(candidates: T[], maxPerRepo: number): T[];

package/dist/core/issue-filtering.js

@@ -1,103 +0,0 @@
-/**
- * Issue Filtering — pure functions for filtering and spam detection on search results.
- *
- * Extracted from issue-discovery.ts (#356) to isolate filtering logic:
- * label farming detection, doc-only filtering, per-repo caps, templated title detection.
- */
-/** Labels that indicate documentation-only issues (#105). */
-export const DOC_ONLY_LABELS = new Set(['documentation', 'docs', 'typo', 'spelling']);
-/**
- * Check if an issue's labels are ALL documentation-related (#105).
- * Issues with mixed labels (e.g., "good first issue" + "documentation") pass through.
- * Issues with no labels are not considered doc-only.
- */
-export function isDocOnlyIssue(item) {
-    if (!item.labels || !Array.isArray(item.labels) || item.labels.length === 0)
-        return false;
-    const labelNames = item.labels.map((l) => (typeof l === 'string' ? l : l.name || '').toLowerCase());
-    // Filter out empty label names before checking
-    const nonEmptyLabels = labelNames.filter((n) => n.length > 0);
-    if (nonEmptyLabels.length === 0)
-        return false;
-    return nonEmptyLabels.every((n) => DOC_ONLY_LABELS.has(n));
-}
-/** Known beginner-type label names used to detect label-farming repos (#97). */
-export const BEGINNER_LABELS = new Set([
-    'good first issue',
-    'hacktoberfest',
-    'easy',
-    'up-for-grabs',
-    'first-timers-only',
-    'beginner-friendly',
-    'beginner',
-    'starter',
-    'newbie',
-    'low-hanging-fruit',
-    'community',
-]);
-/** Check if a single issue has an excessive number of beginner labels (>= 5). */
-export function isLabelFarming(item) {
-    if (!item.labels || !Array.isArray(item.labels))
-        return false;
-    const labelNames = item.labels.map((l) => (typeof l === 'string' ? l : l.name || '').toLowerCase());
-    const beginnerCount = labelNames.filter((n) => BEGINNER_LABELS.has(n)).length;
-    return beginnerCount >= 5;
-}
-/** Detect mass-created issue titles like "Add Trivia Question 61" or "Create Entry #5". */
-export function hasTemplatedTitle(title) {
-    if (!title)
-        return false;
-    // Matches "<anything> <category-noun> <number>" where category nouns are typical
-    // of mass-created templated issues. This avoids false positives on legitimate titles
-    // like "Add support for Python 3" or "Implement RFC 7231" which lack category nouns.
-    return /^.+\s+(question|fact|point|item|task|entry|post|challenge|exercise|example|problem|tip|recipe|snippet)\s+#?\d+$/i.test(title);
-}
-/**
- * Batch-analyze search items to detect label-farming repositories (#97).
- * Returns a Set of repo full names (owner/repo) that appear to be spam.
- *
- * A repo is flagged if:
- * - ANY single issue has >= 5 beginner labels (strong individual signal), OR
- * - It has >= 3 issues with templated titles (batch signal)
- */
-export function detectLabelFarmingRepos(items) {
-    const spamRepos = new Set();
-    const repoSpamCounts = new Map();
-    for (const item of items) {
-        const repoFullName = item.repository_url.split('/').slice(-2).join('/');
-        // Strong signal: single issue with 5+ beginner labels
-        if (isLabelFarming(item)) {
-            spamRepos.add(repoFullName);
-            continue;
-        }
-        // Weaker signal: templated title
-        if (item.title && hasTemplatedTitle(item.title)) {
-            repoSpamCounts.set(repoFullName, (repoSpamCounts.get(repoFullName) || 0) + 1);
-        }
-    }
-    // Flag repos with 3+ templated-title issues
-    for (const [repo, count] of repoSpamCounts) {
-        if (count >= 3) {
-            spamRepos.add(repo);
-        }
-    }
-    return spamRepos;
-}
-/**
- * Apply per-repo cap to candidates (#105).
- * Keeps at most `maxPerRepo` issues from any single repo.
- * Maintains the existing sort order — first N from each repo are kept,
- * excess issues from over-represented repos are dropped.
- */
-export function applyPerRepoCap(candidates, maxPerRepo) {
-    const repoCounts = new Map();
-    const kept = [];
-    for (const c of candidates) {
-        const count = repoCounts.get(c.issue.repo) || 0;
-        if (count < maxPerRepo) {
-            kept.push(c);
-            repoCounts.set(c.issue.repo, count + 1);
-        }
-    }
-    return kept;
-}

package/dist/core/issue-scoring.d.ts

@@ -1,43 +0,0 @@
-/**
- * Issue Scoring — pure functions for computing viability scores and quality bonuses.
- *
- * Extracted from issue-discovery.ts (#356) to isolate scoring logic.
- */
-/**
- * Calculate a quality bonus based on repo star and fork counts (#98).
- * Stars: <50 → 0, 50-499 → +3, 500-4999 → +5, 5000+ → +8
- * Forks: 50+ → +2, 500+ → +4
- * Natural max is 12 (8 stars + 4 forks).
- */
-export declare function calculateRepoQualityBonus(stargazersCount: number, forksCount: number): number;
-export interface ViabilityScoreParams {
-    repoScore: number | null;
-    hasExistingPR: boolean;
-    isClaimed: boolean;
-    clearRequirements: boolean;
-    hasContributionGuidelines: boolean;
-    issueUpdatedAt: string;
-    closedWithoutMergeCount: number;
-    mergedPRCount: number;
-    orgHasMergedPRs: boolean;
-    repoQualityBonus?: number;
-    /** True when the repo matches one of the user's preferred project categories. */
-    matchesPreferredCategory?: boolean;
-}
-/**
- * Calculate viability score for an issue (0-100 scale)
- * Scoring:
- * - Base: 50 points
- * - +repoScore*2 (up to +20 for score of 10)
- * - +repoQualityBonus (up to +12 for established repos, from star/fork counts) (#98)
- * - +15 for merged PR in this repo (direct proven relationship) (#99)
- * - +15 for clear requirements (clarity)
- * - +15 for freshness (recently updated)
- * - +10 for contribution guidelines
- * - +5 for org affinity (merged PRs in same org)
- * - +5 for category preference (matches user's project categories)
- * - -30 if existing PR
- * - -20 if claimed
- * - -15 if closed-without-merge history with no merges
- */
-export declare function calculateViabilityScore(params: ViabilityScoreParams): number;

package/dist/core/issue-scoring.js

@@ -1,97 +0,0 @@
-/**
- * Issue Scoring — pure functions for computing viability scores and quality bonuses.
- *
- * Extracted from issue-discovery.ts (#356) to isolate scoring logic.
- */
-import { daysBetween } from './utils.js';
-/**
- * Calculate a quality bonus based on repo star and fork counts (#98).
- * Stars: <50 → 0, 50-499 → +3, 500-4999 → +5, 5000+ → +8
- * Forks: 50+ → +2, 500+ → +4
- * Natural max is 12 (8 stars + 4 forks).
- */
-export function calculateRepoQualityBonus(stargazersCount, forksCount) {
-    let bonus = 0;
-    // Star tiers
-    if (stargazersCount >= 5000)
-        bonus += 8;
-    else if (stargazersCount >= 500)
-        bonus += 5;
-    else if (stargazersCount >= 50)
-        bonus += 3;
-    // Fork tiers
-    if (forksCount >= 500)
-        bonus += 4;
-    else if (forksCount >= 50)
-        bonus += 2;
-    return bonus;
-}
-/**
- * Calculate viability score for an issue (0-100 scale)
- * Scoring:
- * - Base: 50 points
- * - +repoScore*2 (up to +20 for score of 10)
- * - +repoQualityBonus (up to +12 for established repos, from star/fork counts) (#98)
- * - +15 for merged PR in this repo (direct proven relationship) (#99)
- * - +15 for clear requirements (clarity)
- * - +15 for freshness (recently updated)
- * - +10 for contribution guidelines
- * - +5 for org affinity (merged PRs in same org)
- * - +5 for category preference (matches user's project categories)
- * - -30 if existing PR
- * - -20 if claimed
- * - -15 if closed-without-merge history with no merges
- */
-export function calculateViabilityScore(params) {
-    let score = 50; // Base score
-    // Add repo score contribution (up to +20)
-    if (params.repoScore !== null) {
-        score += params.repoScore * 2;
-    }
-    // Repo quality bonus from star/fork counts (#98, up to +12)
-    score += params.repoQualityBonus ?? 0;
-    // Merged PR bonus (+15) — direct proven relationship with this repo (#99)
-    if (params.mergedPRCount > 0) {
-        score += 15;
-    }
-    // Clarity bonus (+15)
-    if (params.clearRequirements) {
-        score += 15;
-    }
-    // Freshness bonus (+15 for issues updated within last 14 days)
-    const updatedAt = new Date(params.issueUpdatedAt);
-    const daysSinceUpdate = daysBetween(updatedAt);
-    if (daysSinceUpdate <= 14) {
-        score += 15;
-    }
-    else if (daysSinceUpdate <= 30) {
-        // Partial bonus for 15-30 days
-        score += Math.round(15 * (1 - (daysSinceUpdate - 14) / 16));
-    }
-    // Contribution guidelines bonus (+10)
-    if (params.hasContributionGuidelines) {
-        score += 10;
-    }
-    // Org affinity bonus (+5) — user has merged PRs in another repo under same org
-    if (params.orgHasMergedPRs) {
-        score += 5;
-    }
-    // Category preference bonus (+5) — repo matches user's preferred project categories
-    if (params.matchesPreferredCategory) {
-        score += 5;
-    }
-    // Penalty for existing PR (-30)
-    if (params.hasExistingPR) {
-        score -= 30;
-    }
-    // Penalty for claimed issue (-20)
-    if (params.isClaimed) {
-        score -= 20;
-    }
-    // Penalty for closed-without-merge history with no successful merges (-15)
-    if (params.closedWithoutMergeCount > 0 && params.mergedPRCount === 0) {
-        score -= 15;
-    }
-    // Clamp to 0-100
-    return Math.max(0, Math.min(100, score));
-}

package/dist/core/issue-vetting.d.ts

@@ -1,33 +0,0 @@
-/**
- * Issue Vetting — orchestrates individual issue checks and computes
- * recommendation + viability score.
- *
- * Delegates to focused modules (#621):
- * - issue-eligibility.ts — PR existence, claim detection, requirements analysis
- * - repo-health.ts       — project health, contribution guidelines
- */
-import { Octokit } from '@octokit/rest';
-import { type SearchPriority, type IssueCandidate } from './types.js';
-import { getStateManager } from './state.js';
-export declare class IssueVetter {
-    private octokit;
-    private stateManager;
-    constructor(octokit: Octokit, stateManager: ReturnType<typeof getStateManager>);
-    /**
-     * Vet a specific issue — runs all checks and computes recommendation + viability score.
-     * Results are cached for 15 minutes to avoid redundant API calls on repeated searches.
-     */
-    vetIssue(issueUrl: string): Promise<IssueCandidate>;
-    /**
-     * Vet multiple issues in parallel with concurrency limit
-     */
-    vetIssuesParallel(urls: string[], maxResults: number, priority?: SearchPriority): Promise<{
-        candidates: IssueCandidate[];
-        allFailed: boolean;
-        rateLimitHit: boolean;
-    }>;
-    /**
-     * Get the repo score from state, or return null if not evaluated
-     */
-    private getRepoScore;
-}