/**
 * Change significance briefing (change: add-change-significance-briefing) —
 * "a lot changed since I last looked; what actually matters?"
 *
 * Every other change-oriented tool OpenLore has is about YOUR OWN pending diff
 * (`blast_radius`, `change_impact_certificate`). This one answers the reviewer /
 * catch-up / onboarding question instead: given a base ref, what changed since it
 * and which of those changes is structurally load-bearing — ranked by labels the
 * analyzer already produces, never by a hidden weighted score.
 *
 * The pipeline is pure reuse:
 *   1. `getChangedFiles` (drift/git-diff) → the files changed since the base ref.
 *   2. `seedsFromFiles` (test-impact) → the changed production symbols (file-level
 *      granularity, the same primitive `select_tests`/`report_coverage_gaps` use).
 *   3. `computeLandmarkSignals` → each symbol's hub/orchestrator/chokepoint labels.
 *   4. `analyzeChangeCoupling` → per-file churn + how much history exists.
 *   5. `labelChangeSignificance` (analyzer/change-significance) → one tier per symbol.
 *   6. `handleSelectTests` → the tests to run for the whole change set.
 *
 * Honest by construction: file-level granularity is disclosed; the surprising-change
 * label is withheld when history is too shallow; truncation always carries a receipt
 * (omitted count + lowest tier reached) and never drops a higher tier for a lower
 * one. The cursor is the base ref, never wall-clock time.
 */
export interface BriefingSinceInput {
    directory: string;
    /**
     * The cursor: a git ref to brief changes SINCE (the last-reviewed commit, a PR
     * base, "where I was when I left"). Default "auto" → resolve main → master →
     * HEAD~1 → empty tree. Never wall-clock time.
     */
    baseRef?: string;
    /** Region scope — only brief changes whose file path contains this substring. */
    filePattern?: string;
    /** Bound on briefed symbols, highest-tier-first (default 50, capped 200). */
    maxResults?: number;
}
/**
 * Produce a ranked, labeled catch-up briefing of what changed since a base ref.
 * Read-only, deterministic, offline. Returns `unknown` (additive-by-cast),
 * conclusion-shaped (a ranked tier list + receipts), never a diff or a graph.
 */
export declare function handleBriefingSince(input: BriefingSinceInput): Promise<unknown>;
//# sourceMappingURL=briefing-since.d.ts.map