@hivelore/core 0.54.0 → 0.57.1

package/dist/index.d.ts

@@ -830,6 +830,26 @@ declare const HIVELORE_ATTRIBUTION = "\uD83D\uDEE1\uFE0F Generated by [Hivelore]
  * so the receipt is useful on day one, before any prevention has been recorded.
  */
 declare function renderPreventionReceiptShare(receipt: PreventionReceipt): string;
+/** Stable marker the CI job greps for to update its own comment instead of posting a new one. */
+declare const PREVENTION_RECEIPT_MARKER = "<!-- haive:prevention-receipt -->";
+interface PreventionCommentFinding {
+    code?: string;
+    message?: string;
+    memory_ids?: string[];
+    file?: string;
+    /** The exact source line that matched — what makes the receipt actionable rather than a tally. */
+    matched_line?: string;
+}
+/**
+ * Full PR-comment body: marker + what fired on THIS pull request + the rolling receipt.
+ *
+ * This used to be assembled by a multi-line `jq -nr` program embedded in the generated
+ * `hivelore-enforcement.yml`. Its literal newlines terminated the surrounding YAML scalar, so the
+ * workflow every user got from `hivelore init` did not parse and GitHub refused to run it at all
+ * ("This run likely failed because of a workflow file issue"). Rendering the body here means the
+ * generated YAML holds a plain command and never a program — the defect class cannot come back.
+ */
+declare function renderPreventionComment(receipt: PreventionReceipt, findings?: PreventionCommentFinding[]): string;
 /** Read all catch events (skips malformed lines). */
 declare function loadPreventionEvents(paths: HaivePaths): Promise<PreventionEvent[]>;
 interface PreventionTrend {
@@ -907,6 +927,238 @@ declare function projectContextRecentlyEmitted(paths: HaivePaths, hash: string,
 /** Record that this exact project-context body was just emitted. Best-effort. */
 declare function recordProjectContextEmission(paths: HaivePaths, hash: string, now?: number): Promise<void>;
 
+/** One full reminder per working day: long enough to stop nagging, short enough to still land. */
+declare const GATE_REMINDER_WINDOW_MS: number;
+/**
+ * Should this reminder be shown in full right now? True the first time in the window, and again
+ * once the window lapses. Recording is the caller's job (see {@link recordGateReminder}) so a
+ * reminder that was never actually rendered does not consume the window.
+ */
+declare function shouldExpandGateReminder(paths: HaivePaths, key: string, now?: number, windowMs?: number): Promise<boolean>;
+/** Record that the full reminder was just shown. Best-effort: telemetry never breaks a commit. */
+declare function recordGateReminder(paths: HaivePaths, key: string, now?: number): Promise<void>;
+
+/**
+ * The gate's decision layer — pure, and the only place that decides what refuses.
+ *
+ * ## Why this module exists
+ *
+ * This logic used to live inside `packages/cli/src/commands/enforce.ts`, a 3300-line file, as
+ * THREE separate downgrade passes applied one after another: one relaxing process gates for human
+ * commits, one making them advisory by default, one making them advisory again at commit stage.
+ * Each arrived with a different bug fix; none knew about the others. The verdict therefore depended
+ * on their execution order, which was never written down anywhere, and adding a fourth pass was the
+ * obvious way to fix the next report. That is how a gate becomes unpredictable.
+ *
+ * There is now ONE pass. Each finding's severity is decided once, from an explicit policy, with the
+ * reason recorded on the finding. It is a pure function: no filesystem, no git, no config loading —
+ * so "why was this push refused?" is answerable by reading one file and provable by a unit test that
+ * runs in a millisecond instead of an 88-second integration suite.
+ */
+/** Severity as reported by a gate check, before policy is applied. */
+type GateSeverity = "ok" | "info" | "warn" | "error";
+interface GateFinding {
+    severity: GateSeverity;
+    code: string;
+    message: string;
+    fix?: string;
+    impact?: number;
+    reason?: string;
+    affected_files?: string[];
+    memory_ids?: string[];
+    /** Project-relative file a deterministic finding fired on, when one is known. */
+    file?: string;
+    /** The exact source line that matched — what makes a refusal actionable. */
+    matched_line?: string;
+    /** Collapsed rendering for a repeated advisory; `message` always holds the full text. */
+    short_message?: string;
+}
+type GateStage = "local" | "pre-commit" | "pre-push" | "ci";
+/**
+ * PROCESS gates describe the AGENT WORKFLOW around a change — "was team knowledge consulted?",
+ * "was the session recapped?" — never the change itself.
+ */
+declare const PROCESS_GATE_CODES: Set<string>;
+/**
+ * CONTENT catches are deterministic statements about THIS diff: a documented lesson matched the code
+ * being committed. These are the findings the gate is entitled to refuse on.
+ */
+declare const CONTENT_CATCH_CODES: Set<string>;
+/** Setup/baseline gates — about the repo's knowledge layer being cold, not the change just made. */
+declare const SETUP_GATE_CODES: Set<string>;
+/**
+ * A named posture, so a team picks ONE thing instead of reasoning about how two dozen independent
+ * switches interact. Individual knobs still win when set explicitly — the posture only supplies the
+ * defaults for the three that decide whether anything refuses.
+ */
+type GatePosture = "advisory" | "balanced" | "strict";
+declare const DEFAULT_POSTURE: GatePosture;
+interface GatePolicyInput {
+    posture?: GatePosture;
+    mode?: "off" | "advisory" | "strict";
+    processGate?: "warn" | "block";
+    humanCommits?: "relaxed" | "strict";
+    scoreThreshold?: number;
+}
+interface GatePolicy {
+    posture: GatePosture;
+    mode: "off" | "advisory" | "strict";
+    processGate: "warn" | "block";
+    humanCommits: "relaxed" | "strict";
+    scoreThreshold: number;
+    /** Which fields the user pinned explicitly, so `doctor` can show posture vs. override. */
+    overrides: string[];
+}
+declare function resolveGatePolicy(input: GatePolicyInput | undefined): GatePolicy;
+/** One sentence describing what a posture actually does, for `doctor` and `--explain`. */
+declare function describePosture(policy: GatePolicy): string;
+interface GateVerdictInput {
+    findings: GateFinding[];
+    policy: GatePolicy;
+    stage: GateStage;
+    /** True when an agent harness was detected in the environment. */
+    isAgent: boolean;
+    /** Env signals that identified the agent, for the actor label. */
+    agentSignals?: string[];
+}
+interface BaselineHealth {
+    /**
+     * Health of the repo's KNOWLEDGE LAYER, 0–100. Deliberately not a verdict on the change: content
+     * catches are excluded, because a number that moves both when the repo is cold and when this
+     * particular diff repeated a lesson cannot be tracked over time — it never means one thing.
+     */
+    score: number;
+    threshold: number;
+    checks: {
+        total: number;
+        ok: number;
+        warn: number;
+        error: number;
+    };
+}
+interface GateVerdict {
+    findings: GateFinding[];
+    should_block: boolean;
+    actor: string;
+    baseline_health: BaselineHealth;
+    /** Content catches that refuse this change, one entry per memory (never the same lesson twice). */
+    refusals: GateFinding[];
+    /** Why process gates did or did not bind on this run. */
+    process_gate_reason: string;
+}
+/**
+ * Baseline health, computed from the repo's STANDING STATE only.
+ *
+ * Content catches are excluded on purpose. They are a verdict about one diff; folding them into a
+ * health percentage meant the number dropped because of a change under review and rose again when
+ * that change was fixed, while also encoding "the corpus is cold". One number, two meanings, and so
+ * no meaning at all — nobody could act on a trend in it.
+ */
+declare function computeBaselineHealth(findings: GateFinding[], threshold: number): BaselineHealth;
+/**
+ * Collapse content catches so one lesson is reported once.
+ *
+ * Two independent diff-scan layers exist — the anti-pattern matcher and the sensor runner — and they
+ * legitimately both fire on the same memory. Reported separately, a single lesson on a single line
+ * of code produced four lines of output (two in the headline, two in the findings list), at exactly
+ * the moment the reader's attention is most worth spending. Grouped by memory id, keeping the
+ * richest entry: the one that knows which line matched.
+ */
+declare function dedupeRefusals(findings: GateFinding[]): GateFinding[];
+/**
+ * Decide the whole verdict in one pass. Pure: same inputs, same answer, anywhere.
+ */
+declare function decideVerdict(input: GateVerdictInput): GateVerdict;
+/**
+ * The health finding, emitted only when it is worth reading: below target, and nothing else refused.
+ *
+ * When a documented lesson refuses a change, that lesson is the message. Appending "health 2% — top
+ * penalties: …" underneath buries the one line the developer needs.
+ */
+declare function buildBaselineHealthFinding(findings: GateFinding[], health: BaselineHealth, shouldBlock: boolean): GateFinding | null;
+
+/**
+ * How much does an anchor actually TELL US?
+ *
+ * A memory anchored to a file matched by the change is treated as `must_read` — the strongest
+ * ranking signal there is, ahead of anything semantic. That is right when the anchor is specific.
+ * It is wrong when the anchor is a file every commit touches.
+ *
+ * Measured on this repository (60 commits, 116 anchored memories):
+ *
+ *   - the MEDIAN memory claims relevance on 12 of 60 commits (20%)
+ *   - the p90 memory claims 36 of 60 (60%)
+ *   - the worst claim 37–42, and every one of them is anchored to a `package.json`
+ *
+ * A version bump touches `package.json`, so a lesson about cross-package dependency ranges declares
+ * itself `must_read` on every release commit. On a typical commit here, ~34 memories all claimed the
+ * top rank at once and the briefing had 8 slots: recall@8 was pinned near its arithmetic ceiling,
+ * and the slots went to whichever plausible memory sorted first rather than to the one that mattered.
+ * That is the mechanism behind a field report scoring briefing usefulness 30/100 while the eval
+ * harness reported 98% recall — the eval asks "given a query written to find memory X, does X
+ * surface?", which never exposes anchors competing with each other.
+ *
+ * The correction is the oldest one in information retrieval: weight a match by how rare it is.
+ * An anchor on a file touched by 3% of commits is strong evidence; the same match on a file touched
+ * by 60% of them is nearly none, and must be corroborated before it outranks everything else.
+ *
+ * Pure: churn is measured elsewhere (git), scored here.
+ */
+/** How many of the sampled commits touched each project-relative path. */
+type AnchorChurn = ReadonlyMap<string, number>;
+/**
+ * Anchors touched by more than this share of recent commits carry too little information to
+ * promote a memory on their own. 0.35 keeps genuinely component-scoped anchors (a module a third of
+ * the work touches is still a real signal) while demoting repo-wide files like `package.json`,
+ * lockfiles and CI config.
+ */
+declare const WEAK_ANCHOR_CHURN_RATIO = 0.35;
+/** Unknown churn must never penalise: a repo with no git history ranks exactly as it did before. */
+declare const DEFAULT_SPECIFICITY = 1;
+/**
+ * Specificity of the BEST anchor that matched, in 0..1.
+ *
+ * 1 = this path is barely ever touched, so matching it is strong evidence.
+ * 0 = every commit touches it, so matching it says nothing.
+ *
+ * The best (rarest) matching anchor wins: a memory anchored to both `package.json` and one precise
+ * file is precise when the precise file is what changed.
+ */
+declare function anchorSpecificity(matchedPaths: readonly string[], churn: AnchorChurn, totalCommits: number): number;
+/** True when this anchor is too common in this repo to promote a memory by itself. */
+declare function isWeakAnchor(specificity: number): boolean;
+declare function normalizeChurnPath(value: string): string;
+/**
+ * Roll per-file commit counts up to the anchor paths a memory actually declares, so a directory or
+ * glob anchor inherits the churn of everything under it. Without this, `packages/cli/` would look
+ * unknown (no commit touches a directory) and silently keep the strong default.
+ */
+declare function churnForAnchors(anchorPaths: readonly string[], fileChurn: AnchorChurn): AnchorChurn;
+interface AnchorAuditRow {
+    id: string;
+    /** Specificity of this memory's most discriminating anchor, 0..1. */
+    specificity: number;
+    /** The anchors that make it broad, with the share of commits touching each. */
+    broad: Array<{
+        path: string;
+        ratio: number;
+    }>;
+}
+/**
+ * Which memories claim relevance on nearly every change?
+ *
+ * A memory anchored only to high-churn files is not wrong — the lesson really is about that file —
+ * but it cannot help a briefing choose. It occupies a slot on every commit and displaces the lesson
+ * that is actually about the work in hand. Surfacing the list turns an invisible ranking problem
+ * into a corpus-hygiene task with an obvious fix: add the precise path the lesson is really about.
+ *
+ * Pure. Sorted worst-first so a report can take the head.
+ */
+declare function auditAnchorSpecificity(memories: ReadonlyArray<{
+    id: string;
+    anchorPaths: readonly string[];
+}>, fileChurn: AnchorChurn, totalCommits: number): AnchorAuditRow[];
+
 type MemoryPriority = "must_read" | "useful" | "background";
 /**
  * Normalized priority evidence. A caller fills only the signals it can compute; unknown ones default
@@ -934,6 +1186,12 @@ interface PrioritySignals {
     moduleOrDomainMatch: boolean;
     /** A memory tag matched a task token. */
     tagTaskMatch: boolean;
+    /**
+     * How much information the matched anchor carries in THIS repo, 0..1 (see `anchor-specificity.ts`).
+     * 1 (the default) means "unknown or highly specific" and preserves the historical behaviour
+     * exactly, so a repo without git history ranks as it always did.
+     */
+    anchorSpecificity?: number;
 }
 declare const DEFAULT_PRIORITY_SIGNALS: PrioritySignals;
 /** Convenience: build a full signal set from a partial one. */
@@ -1396,8 +1654,20 @@ interface CodeFileEntry {
 }
 interface CodeMap {
     version: 1;
+    /**
+     * When this map was last WRITTEN — i.e. when its content last changed, since an unchanged scan
+     * no longer rewrites the file (see `saveCodeMap`). Back-filled on load from the runtime sidecar
+     * or the file mtime; it is deliberately NOT part of the committed payload, because a per-run
+     * timestamp made every `sync` produce a diff and conflict on every `pull` for every developer.
+     */
     generated_at: string;
+    /**
+     * Absolute project root, back-filled on load. Never serialized: it embedded one developer's
+     * home directory in a shared file, so no two machines could produce the same bytes.
+     */
     root: string;
+    /** Digest of the serialized payload — the staleness key, replacing "was it regenerated?". */
+    content_hash?: string;
     files: Record<string, CodeFileEntry>;
 }
 interface BuildCodeMapOptions {
@@ -1409,7 +1679,23 @@ interface BuildCodeMapOptions {
 declare const CODE_MAP_DEFAULT_INCLUDE: string[];
 declare const CODE_MAP_DEFAULT_EXCLUDE: string[];
 declare function codeMapPath(paths: HaivePaths): string;
+/**
+ * Serialize a code-map so that the same source tree always produces the SAME BYTES, on any machine.
+ *
+ * Two fields used to break that and made the file unversionable: an absolute `root` (one developer's
+ * home directory) and a `generated_at` stamped on every run. Together they guaranteed a conflicting
+ * diff on every `sync` for every developer — the file could neither be committed nor ignored
+ * (`doctor` asks for it). Both now live outside the payload, and `files` keys are sorted so readdir
+ * order cannot reshuffle 500 KB of JSON.
+ */
+declare function serializeCodeMap(map: CodeMap): string;
+declare function codeMapContentHash(map: CodeMap): string;
 declare function loadCodeMap(paths: HaivePaths): Promise<CodeMap | null>;
+/**
+ * Write the map only when its content actually changed. An unchanged scan is a no-op, so the file
+ * mtime — and therefore every "is the index stale?" check downstream — moves on content change
+ * rather than on "did someone run sync?".
+ */
 declare function saveCodeMap(paths: HaivePaths, map: CodeMap): Promise<void>;
 declare function buildCodeMap(root: string, options?: BuildCodeMapOptions): Promise<CodeMap>;
 /**
@@ -1577,6 +1863,26 @@ interface HaiveConfig {
      * treat Hivelore as infrastructure, not an optional convention.
      */
     enforcement?: {
+        /**
+         * ONE knob that decides whether the gate refuses, and for whom. Pick this; leave the rest alone.
+         *
+         *   - "advisory" — reports everything, refuses nothing. For adopting Hivelore on a live repo.
+         *   - "balanced" (default) — refuses only on deterministic, code-bound findings: block sensors,
+         *     anti-pattern blocks, stale anchors on files the change touches, artifact hygiene.
+         *   - "strict"   — the above, plus process gates (briefing, session recap, decision coverage,
+         *     bootstrap) refusing at the sharing points (pre-push, CI) for agents and humans alike.
+         *
+         * `mode`, `processGate` and `humanCommits` below are the individual switches the posture sets;
+         * setting one explicitly overrides the posture for that switch only. This field exists because
+         * this object had grown to two dozen interacting knobs and the resulting verdict could not be
+         * predicted from the config by anyone, including the people who wrote it. `hivelore doctor`
+         * prints the effective posture and any overrides.
+         *
+         * One rule is not a posture knob and is not negotiable: process gates never refuse a local
+         * commit, at any posture. Blocking them on every pre-commit is what trained the `--no-verify`
+         * reflex on cold repos, and a bypassed gate protects nothing.
+         */
+        posture?: "advisory" | "balanced" | "strict";
         /** Enforcement posture: advisory reports only, warn in hooks, or block workflow gates. */
         mode?: "off" | "advisory" | "strict";
         /** Require get_briefing / mem_relevant_to before state-changing MCP tools. */
@@ -1637,6 +1943,24 @@ interface HaiveConfig {
          * block humans too.
          */
         humanCommits?: "relaxed" | "strict";
+        /**
+         * Whether the PROCESS gates (briefing-loaded, session-recap, decision-coverage, bootstrap) may
+         * REFUSE a push, or only report.
+         *
+         *   - "warn" (default): they are always advisory. Only deterministic, code-bound findings —
+         *     block sensors, anti-pattern blocks, stale anchors, artifact hygiene — can refuse.
+         *   - "block": the pre-v0.55.0 behaviour, where an agent's push is refused for not having
+         *     written a session recap.
+         *
+         * The default changed in v0.55.0 on field evidence. A user pushing tested code with a green
+         * SonarQube gate and zero violations was refused twice, both times entirely on process
+         * penalties: `briefing-missing (−35)`, `session-recap-missing (−20)`, `bootstrap-incomplete (−5)`.
+         * Not one penalty was about the code. The predictable response to that is `--no-verify`, which
+         * costs the developer the WHOLE gate — including the sensors, the part that actually protects.
+         * A gate routinely bypassed protects nothing, so the gate now spends its refusals only where it
+         * has deterministic evidence, and asks for the rest.
+         */
+        processGate?: "warn" | "block";
         /**
          * Pre-commit/pre-push decision-coverage behaviour. When true (default), the gate SURFACES the
          * relevant anchored decisions/policies itself and records them in the session marker at commit
@@ -2389,6 +2713,22 @@ declare function judgeProposedSensor(sensor: Sensor, input: {
     badExamples: string[];
     correctExamples?: string[];
 }): ProposedSensorVerdict;
+/**
+ * One wording for every sensor rejection, shared by the CLI (`sensors propose`) and the MCP
+ * (`propose_sensor`) so the two façades cannot drift.
+ *
+ * `fires-on-current` in particular used to say only "add or tighten `absent`", which assumes the
+ * pattern is imprecise. There is a second, very common cause the message never named: the pattern is
+ * exactly right and **the faulty code is still in the tree** — which is the normal state at the
+ * moment you document the problem. Requiring silence-on-current then makes arming a `block` sensor
+ * impossible precisely when you want to arm it. A field report hit this and had to infer the
+ * sequence (write the lesson → fix the code → come back and arm) from a bare refusal. Both causes
+ * are now named, and the warn-first path out is spelled with the exact command.
+ */
+declare function explainSensorRejection(verdict: ProposedSensorVerdict, context: {
+    style: "cli" | "mcp";
+    memoryId?: string;
+}): string;
 /**
  * A command oracle that exits non-zero has either FAILED an assertion (a real signal) or errored
  * before it could reach one — a missing module, an import/collection failure, a syntax error, or
@@ -3636,4 +3976,4 @@ interface ReviewDraftOptions {
 /** Template review learnings into proposed-memory drafts (reuses the scanner-ingest draft shape). */
 declare function reviewLearningsToDrafts(learnings: ReviewLearning[], options?: ReviewDraftOptions): MemoryDraft[];
 
-export { AUTOPILOT_DEFAULTS, type Activation, type ActivationContext, ActivationSchema, type AgentContext, type Anchor, AnchorSchema, type AntiPatternGate, type AppendFrictionInput, type AppendFrictionResult, type AppliedConflictResolution, type AstExport, type AutoPromoteRule, BRIDGE_MARKERS, BRIDGE_TARGETS, BRIDGE_TARGET_PATH, BRIEFING_MARKER_TTL_MS, BRIEFING_PRESET_DEFAULTS, type BehaviourCoverageInput, type BehaviourCoverageMetrics, type BehaviourOracleInfo, type BootstrapAssessment, type BootstrapGap, type BootstrapGate, type BootstrapMetrics, type BootstrapState, type BootstrapStateInput, type BreakingChange, type BridgeFileOutput, type BridgeMemoryEntry, type BridgeSensor, type BridgeTarget, type BriefingBudgetNumbers, type BriefingBudgetPreset, type BriefingMarker, type BriefingProofLineOptions, type BudgetPart, type BudgetSlice, type BuildCodeMapOptions, CHARS_PER_TOKEN, CODE_MAP_DEFAULT_EXCLUDE, CODE_MAP_DEFAULT_INCLUDE, CODE_MAP_FILE, CODE_STOPWORDS, CONFIG_FILE, type CaughtForYouOptions, type CaughtForYouRow, type CaughtForYouSummary, type CodeExport, type CodeExportKind, type CodeFileEntry, type CodeMap, type CodeMapQueryOptions, type CollectTimelineOpts, type CommandSensorSpec, type ConfidenceLevel, type ConfidenceThresholds, type ConflictCandidatePair, type ConflictCandidatesOpts, type ConflictResolution, type ContractCheck, type ContractDiffResult, type ContractFile, type ContractSnapshot, type CoverageGap, type CoverageOptions, CrossRepoProvenanceSchema, type CrossRepoReport, type CrossRepoSource, DECAY_DAYS, DEFAULT_AUTO_PROMOTE_RULE, DEFAULT_BRIEFING_EXCLUDE_TAGS, DEFAULT_CONFIDENCE_THRESHOLDS, DEFAULT_CONFIG, DEFAULT_DORMANT_DAYS, DEFAULT_PRIORITY_SIGNALS, type DashboardOptions, type DashboardReport, type DepChange, type DepTrackResult, type DependencySnapshot, type DetectStacksInput, type DetectableStack, type DistilledFailureLesson, type DocFrequency, type DormantRow, type DraftOptions, type DraftsOptions, ENV_WORKAROUND_TAGS, type EvalDelta, type EvalHistoryEntry, type EvalReport, type EvalSpec, type EvalTrend, FRICTION_FIELD_MAX, FRICTION_LOG_FILE, FRICTION_STATE_FILE, type FailureCoverageOptions, type FailureObservation, type FeedbackAdjustment, type FeedbackAdjustmentAction, type FeedbackAdjustmentOptions, type Finding, type FindingFormat, type FindingSeverity, type FrictionGroup, type FrictionKind, type FrictionReport, type FrictionState, type FrictionStateEntry, type FrictionStatus, GUESSABLE_THRESHOLD, type GateMissProposal, type GatePrecision, type GatePrecisionDelta, type GatePrecisionMetricDelta, type GateTuningSuggestion, type GenerateBridgesOptions, type GitCommit, type GitWatchPlan, type GitWatchState, HAIVE_DIR, HAIVE_OWNED_FILES, HANDOFF_FILENAME, HIVELORE_ATTRIBUTION, type HaiveConfig, type HaivePaths, type HotFile, type HotFileSource, type ImpactOptions, type ImpactRow, type ImpactScore, type ImpactSummary, type ImpactTier, type IncidentHints, type InvalidMemoryFile, LEGACY_CONFIG_FILE, type LexicalRankResult, type LoadedMemory, MEMORIES_DIR, MIN_WORD_LEN, type Memory, type MemoryDraft, type MemoryFrontmatter, MemoryFrontmatterSchema, type MemoryPriority, type MemoryScope, MemoryScopeSchema, type MemoryStatus, MemoryStatusSchema, type MemoryType, MemoryTypeSchema, type MemoryUsage, type MergeResult, type MetricDelta, PREVENTION_DEBOUNCE_MS, PROJECT_CONTEXT_FILE, PROJECT_CONTEXT_THROTTLE_MS, type PostIncidentLesson, type PreventionEvent, type PreventionEventDetail, type PreventionReceipt, type PreventionReceiptRow, type PreventionRow, type PreventionSource, type PreventionTrend, type PrioritySignals, type ProposedEvalSpec, type ProposedSensorVerdict, REVIEW_LEARNING_MARKER, RUNTIME_JOURNAL_FILENAME, type RecurrenceReport, type RecurrenceRow, type ResolveProjectInfo, type RetirementSignal, type RetrievalAggregate, type RetrievalCase, type RetrievalCaseResult, type ReviewDraftOptions, type ReviewLearning, type RuntimeJournalEntry, SCAFFOLD_MARKER_RE, SEED_QUALITY_FLOOR, SENSOR_ABSENT_LOOKBACK, SENSOR_ABSENT_WINDOW, SESSION_RECAP_TTL_MS, STACK_PACK_TAG, type ScaffoldLoopGap, type ScaffoldOptions, type ScaffoldStyle, type SeedProposal, type SelfEvalOptions, type Sensor, type SensorAggregate, type SensorCase, type SensorCaseResult, type SensorEvaluation, type SensorEvaluationOutcome, type SensorEvaluationStage, type SensorFlap, type SensorHealth, type SensorHit, type SensorRow, SensorSchema, type SensorSeed, type SensorSelfCheck, type SensorSuggestionOptions, type SensorTarget, type SensorWeakening, type SessionHandoffData, type SkillActivation, TEST_FRAMEWORKS, type TestFramework, type TestScaffold, type TierContractCheck, type TimelineEntry, type TopicStatusPair, type TruncateOptions, type TruncateResult, USAGE_FILE, USAGE_LOG_DIR, USAGE_LOG_FILE, type UncapturedFailure, type UncoveredAreaSuggestion, type UsageAggregate, type UsageEvent, type UsageIndex, type VerifyOptions, type VerifyResult, addedLineNumbersFromDiff, addedLinesFromDiff, aggregateRetrieval, aggregateSensors, aggregateUsage, allocateBudget, anchorMatchesComponent, antiPatternGateParams, appendEvalHistory, appendFrictionReport, appendPreventionEvent, appendProposedRetrievalCases, appendRuntimeJournalEntry, appendSensorEvaluations, appendUsageEvent, applyConflictResolution, applyFeedbackAdjustment, approveProposedCases, assessBehaviourCoverage, assessBootstrapState, assessScaffoldLoop, assessSensorHealth, bridgeMemorySummary, briefingMarkerPath, briefingMarkersDir, briefingProofLine, buildCodeMap, buildCoverageIndex, buildDashboard, buildDocFrequency, buildFrontmatter, buildHandoffMarkdown, buildPreventionReceipt, buildProposeCommand, buildReport, bumpRead, classifyMemoryPriority, codeMapPath, collectTimelineEntries, compactAutoRecapBody, compareEvalReports, compareGatePrecision, compareImpact, compileRegexSensor, componentOf, computeEvalTrend, computeGatePrecision, computeImpact, computePreventionTrend, computeRecurrence, computeScopeHash, configPath, contractLockPath, countSourceFilesOnDisk, deriveConfidence, deriveMainAreas, detectAgentContext, detectSensorWeakening, detectStacksFromManifests, diffContract, diffHasDistinctiveOverlap, distillFailureObservations, distinctiveCap, draftsFromFindings, emptyUsage, emptyUsageIndex, enforcementDir, estimateTokens, evalHistoryPath, evaluateSkillActivation, existingGateMissShas, extractActionsBriefBody, extractCorrectApproachExamples, extractReferencedPaths, extractReviewLearnings, extractSensorExamples, extractSnippet, extractTestFilePathsFromCommand, filterNewDrafts, findCoverageGaps, findLexicalConflictPairs, findProjectRoot, findTopicStatusConflictPairs, findUncapturedFailures, findingBody, findingToDraft, firstMemoryOneLine, formatFrictionIssue, frictionFingerprint, frictionLogPath, frictionStatePath, gatePassedShas, generateBridges, getUsage, globToRegExp, groupFriction, handoffAgeMs, handoffFilePath, hasPendingTestMarker, hasRecentBriefingMarker, hashProjectContext, incidentHintsFromDiff, incidentSuffix, inferModulesFromPaths, isAutoPromoteEligible, isAutoRecap, isCovered, isDecaying, isDistinctiveToken, isEnvWorkaroundMemory, isFreshIsoDate, isGlobPath, isHarnessErrorOutput, isLikelyGuessable, isNoiseSubject, isProductionCodeFile, isRetiredMemory, isSensorScannablePath, isSkill, isSkillSuppressed, isStackPackSeed, isStylisticRule, isTemplateProjectContext, judgeProposedSensor, lessonShortName, listMarkdownFilesRecursive, literalMatchesAllTokens, literalMatchesAnyToken, loadCodeMap, loadConfig, loadConfigSync, loadEvalHistory, loadFrictionState, loadMemoriesFromDir, loadMemoriesFromDirDetailed, loadMemory, loadPreventionEvents, loadSensorLedger, loadUsageIndex, looksLikeGenericAdvice, meetsSeedQualityFloor, memoryFilePath, memoryHasExcludedTag, memoryMatchesAnchorPaths, mergeHotFiles, mergeMemoryVersions, mineSensorSeedFromDiff, moduleNameOf, newMemoryId, normalizeFindingSeverity, normalizeFramework, normalizeFrictionSummary, normalizeKind, normalizeScaffoldStyle, normalizeSessionId, overallScore, parseEslintJson, parseFileAst, parseFindings, parseLessonFields, parseMemory, parseNpmAudit, parseSarif, parseSince, parseSonar, pathsOverlap, pickSnippetNeedle, pickTestFramework, planConflictResolution, planGitWatch, prepareBridgeData, preventionLogPath, priorityRank, prioritySignals, projectContextRecentlyEmitted, proposeGateMissDrafts, proposeSeedsFromCommits, pullCrossRepoSources, quarantineNote, queryCodeMap, rankMemoriesLexical, readFrictionReports, readRecentBriefingMarker, readRuntimeJournalTail, readSessionHandoff, readUsageEvents, recommendFeedbackAdjustment, recordApplied, recordPrevention, recordPreventionHits, recordProjectContextEmission, recordRejection, relPathFrom, renderBehaviourCoverageLine, renderBootstrapChecklist, renderCaughtForYou, renderPreventionReceipt, renderPreventionReceiptShare, resolveBriefingBudget, resolveConfigPath, resolveHaivePaths, resolveManifestFiles, resolveProjectInfo, retirementSignal, revertedShaFromCommit, reviewLearningsToDrafts, runRegexSensor, runSensors, runTierContract, runValidationContract, runtimeJournalPath, saveCodeMap, saveConfig, saveFrictionState, saveUsageIndex, scaffoldPostIncidentTest, scannableSensorTargets, scoreRetrievalCase, scoreSensorCase, scrubbedCommandEnv, selectCommandSensors, sensorAppliesToPath, sensorLedgerPath, sensorPatternBrittleness, sensorPromotedAtMap, sensorSelfCheck, sensorTargetsFromDiff, serializeMemory, setFrictionStatus, snapshotContract, specificityScore, stripPrivate, suggestGate, suggestSensorFromMemory, suggestSensorSeed, suggestTopicKey, summarizeCaughtForYou, summarizeImpact, synthesizeSelfEvalCases, tallyHotFiles, titleFromBody, tokenizeQuery, tokenizeWords, trackDependencies, trackReads, truncateToTokens, usageLogPath, usageLogSize, usagePath, verifyAnchor, watchContracts, withQuarantineNote, withoutQuarantineNote, writeBriefingMarker, writeSessionHandoff };
+export { AUTOPILOT_DEFAULTS, type Activation, type ActivationContext, ActivationSchema, type AgentContext, type Anchor, type AnchorAuditRow, type AnchorChurn, AnchorSchema, type AntiPatternGate, type AppendFrictionInput, type AppendFrictionResult, type AppliedConflictResolution, type AstExport, type AutoPromoteRule, BRIDGE_MARKERS, BRIDGE_TARGETS, BRIDGE_TARGET_PATH, BRIEFING_MARKER_TTL_MS, BRIEFING_PRESET_DEFAULTS, type BaselineHealth, type BehaviourCoverageInput, type BehaviourCoverageMetrics, type BehaviourOracleInfo, type BootstrapAssessment, type BootstrapGap, type BootstrapGate, type BootstrapMetrics, type BootstrapState, type BootstrapStateInput, type BreakingChange, type BridgeFileOutput, type BridgeMemoryEntry, type BridgeSensor, type BridgeTarget, type BriefingBudgetNumbers, type BriefingBudgetPreset, type BriefingMarker, type BriefingProofLineOptions, type BudgetPart, type BudgetSlice, type BuildCodeMapOptions, CHARS_PER_TOKEN, CODE_MAP_DEFAULT_EXCLUDE, CODE_MAP_DEFAULT_INCLUDE, CODE_MAP_FILE, CODE_STOPWORDS, CONFIG_FILE, CONTENT_CATCH_CODES, type CaughtForYouOptions, type CaughtForYouRow, type CaughtForYouSummary, type CodeExport, type CodeExportKind, type CodeFileEntry, type CodeMap, type CodeMapQueryOptions, type CollectTimelineOpts, type CommandSensorSpec, type ConfidenceLevel, type ConfidenceThresholds, type ConflictCandidatePair, type ConflictCandidatesOpts, type ConflictResolution, type ContractCheck, type ContractDiffResult, type ContractFile, type ContractSnapshot, type CoverageGap, type CoverageOptions, CrossRepoProvenanceSchema, type CrossRepoReport, type CrossRepoSource, DECAY_DAYS, DEFAULT_AUTO_PROMOTE_RULE, DEFAULT_BRIEFING_EXCLUDE_TAGS, DEFAULT_CONFIDENCE_THRESHOLDS, DEFAULT_CONFIG, DEFAULT_DORMANT_DAYS, DEFAULT_POSTURE, DEFAULT_PRIORITY_SIGNALS, DEFAULT_SPECIFICITY, type DashboardOptions, type DashboardReport, type DepChange, type DepTrackResult, type DependencySnapshot, type DetectStacksInput, type DetectableStack, type DistilledFailureLesson, type DocFrequency, type DormantRow, type DraftOptions, type DraftsOptions, ENV_WORKAROUND_TAGS, type EvalDelta, type EvalHistoryEntry, type EvalReport, type EvalSpec, type EvalTrend, FRICTION_FIELD_MAX, FRICTION_LOG_FILE, FRICTION_STATE_FILE, type FailureCoverageOptions, type FailureObservation, type FeedbackAdjustment, type FeedbackAdjustmentAction, type FeedbackAdjustmentOptions, type Finding, type FindingFormat, type FindingSeverity, type FrictionGroup, type FrictionKind, type FrictionReport, type FrictionState, type FrictionStateEntry, type FrictionStatus, GATE_REMINDER_WINDOW_MS, GUESSABLE_THRESHOLD, type GateFinding, type GateMissProposal, type GatePolicy, type GatePolicyInput, type GatePosture, type GatePrecision, type GatePrecisionDelta, type GatePrecisionMetricDelta, type GateSeverity, type GateStage, type GateTuningSuggestion, type GateVerdict, type GateVerdictInput, type GenerateBridgesOptions, type GitCommit, type GitWatchPlan, type GitWatchState, HAIVE_DIR, HAIVE_OWNED_FILES, HANDOFF_FILENAME, HIVELORE_ATTRIBUTION, type HaiveConfig, type HaivePaths, type HotFile, type HotFileSource, type ImpactOptions, type ImpactRow, type ImpactScore, type ImpactSummary, type ImpactTier, type IncidentHints, type InvalidMemoryFile, LEGACY_CONFIG_FILE, type LexicalRankResult, type LoadedMemory, MEMORIES_DIR, MIN_WORD_LEN, type Memory, type MemoryDraft, type MemoryFrontmatter, MemoryFrontmatterSchema, type MemoryPriority, type MemoryScope, MemoryScopeSchema, type MemoryStatus, MemoryStatusSchema, type MemoryType, MemoryTypeSchema, type MemoryUsage, type MergeResult, type MetricDelta, PREVENTION_DEBOUNCE_MS, PREVENTION_RECEIPT_MARKER, PROCESS_GATE_CODES, PROJECT_CONTEXT_FILE, PROJECT_CONTEXT_THROTTLE_MS, type PostIncidentLesson, type PreventionCommentFinding, type PreventionEvent, type PreventionEventDetail, type PreventionReceipt, type PreventionReceiptRow, type PreventionRow, type PreventionSource, type PreventionTrend, type PrioritySignals, type ProposedEvalSpec, type ProposedSensorVerdict, REVIEW_LEARNING_MARKER, RUNTIME_JOURNAL_FILENAME, type RecurrenceReport, type RecurrenceRow, type ResolveProjectInfo, type RetirementSignal, type RetrievalAggregate, type RetrievalCase, type RetrievalCaseResult, type ReviewDraftOptions, type ReviewLearning, type RuntimeJournalEntry, SCAFFOLD_MARKER_RE, SEED_QUALITY_FLOOR, SENSOR_ABSENT_LOOKBACK, SENSOR_ABSENT_WINDOW, SESSION_RECAP_TTL_MS, SETUP_GATE_CODES, STACK_PACK_TAG, type ScaffoldLoopGap, type ScaffoldOptions, type ScaffoldStyle, type SeedProposal, type SelfEvalOptions, type Sensor, type SensorAggregate, type SensorCase, type SensorCaseResult, type SensorEvaluation, type SensorEvaluationOutcome, type SensorEvaluationStage, type SensorFlap, type SensorHealth, type SensorHit, type SensorRow, SensorSchema, type SensorSeed, type SensorSelfCheck, type SensorSuggestionOptions, type SensorTarget, type SensorWeakening, type SessionHandoffData, type SkillActivation, TEST_FRAMEWORKS, type TestFramework, type TestScaffold, type TierContractCheck, type TimelineEntry, type TopicStatusPair, type TruncateOptions, type TruncateResult, USAGE_FILE, USAGE_LOG_DIR, USAGE_LOG_FILE, type UncapturedFailure, type UncoveredAreaSuggestion, type UsageAggregate, type UsageEvent, type UsageIndex, type VerifyOptions, type VerifyResult, WEAK_ANCHOR_CHURN_RATIO, addedLineNumbersFromDiff, addedLinesFromDiff, aggregateRetrieval, aggregateSensors, aggregateUsage, allocateBudget, anchorMatchesComponent, anchorSpecificity, antiPatternGateParams, appendEvalHistory, appendFrictionReport, appendPreventionEvent, appendProposedRetrievalCases, appendRuntimeJournalEntry, appendSensorEvaluations, appendUsageEvent, applyConflictResolution, applyFeedbackAdjustment, approveProposedCases, assessBehaviourCoverage, assessBootstrapState, assessScaffoldLoop, assessSensorHealth, auditAnchorSpecificity, bridgeMemorySummary, briefingMarkerPath, briefingMarkersDir, briefingProofLine, buildBaselineHealthFinding, buildCodeMap, buildCoverageIndex, buildDashboard, buildDocFrequency, buildFrontmatter, buildHandoffMarkdown, buildPreventionReceipt, buildProposeCommand, buildReport, bumpRead, churnForAnchors, classifyMemoryPriority, codeMapContentHash, codeMapPath, collectTimelineEntries, compactAutoRecapBody, compareEvalReports, compareGatePrecision, compareImpact, compileRegexSensor, componentOf, computeBaselineHealth, computeEvalTrend, computeGatePrecision, computeImpact, computePreventionTrend, computeRecurrence, computeScopeHash, configPath, contractLockPath, countSourceFilesOnDisk, decideVerdict, dedupeRefusals, deriveConfidence, deriveMainAreas, describePosture, detectAgentContext, detectSensorWeakening, detectStacksFromManifests, diffContract, diffHasDistinctiveOverlap, distillFailureObservations, distinctiveCap, draftsFromFindings, emptyUsage, emptyUsageIndex, enforcementDir, estimateTokens, evalHistoryPath, evaluateSkillActivation, existingGateMissShas, explainSensorRejection, extractActionsBriefBody, extractCorrectApproachExamples, extractReferencedPaths, extractReviewLearnings, extractSensorExamples, extractSnippet, extractTestFilePathsFromCommand, filterNewDrafts, findCoverageGaps, findLexicalConflictPairs, findProjectRoot, findTopicStatusConflictPairs, findUncapturedFailures, findingBody, findingToDraft, firstMemoryOneLine, formatFrictionIssue, frictionFingerprint, frictionLogPath, frictionStatePath, gatePassedShas, generateBridges, getUsage, globToRegExp, groupFriction, handoffAgeMs, handoffFilePath, hasPendingTestMarker, hasRecentBriefingMarker, hashProjectContext, incidentHintsFromDiff, incidentSuffix, inferModulesFromPaths, isAutoPromoteEligible, isAutoRecap, isCovered, isDecaying, isDistinctiveToken, isEnvWorkaroundMemory, isFreshIsoDate, isGlobPath, isHarnessErrorOutput, isLikelyGuessable, isNoiseSubject, isProductionCodeFile, isRetiredMemory, isSensorScannablePath, isSkill, isSkillSuppressed, isStackPackSeed, isStylisticRule, isTemplateProjectContext, isWeakAnchor, judgeProposedSensor, lessonShortName, listMarkdownFilesRecursive, literalMatchesAllTokens, literalMatchesAnyToken, loadCodeMap, loadConfig, loadConfigSync, loadEvalHistory, loadFrictionState, loadMemoriesFromDir, loadMemoriesFromDirDetailed, loadMemory, loadPreventionEvents, loadSensorLedger, loadUsageIndex, looksLikeGenericAdvice, meetsSeedQualityFloor, memoryFilePath, memoryHasExcludedTag, memoryMatchesAnchorPaths, mergeHotFiles, mergeMemoryVersions, mineSensorSeedFromDiff, moduleNameOf, newMemoryId, normalizeChurnPath, normalizeFindingSeverity, normalizeFramework, normalizeFrictionSummary, normalizeKind, normalizeScaffoldStyle, normalizeSessionId, overallScore, parseEslintJson, parseFileAst, parseFindings, parseLessonFields, parseMemory, parseNpmAudit, parseSarif, parseSince, parseSonar, pathsOverlap, pickSnippetNeedle, pickTestFramework, planConflictResolution, planGitWatch, prepareBridgeData, preventionLogPath, priorityRank, prioritySignals, projectContextRecentlyEmitted, proposeGateMissDrafts, proposeSeedsFromCommits, pullCrossRepoSources, quarantineNote, queryCodeMap, rankMemoriesLexical, readFrictionReports, readRecentBriefingMarker, readRuntimeJournalTail, readSessionHandoff, readUsageEvents, recommendFeedbackAdjustment, recordApplied, recordGateReminder, recordPrevention, recordPreventionHits, recordProjectContextEmission, recordRejection, relPathFrom, renderBehaviourCoverageLine, renderBootstrapChecklist, renderCaughtForYou, renderPreventionComment, renderPreventionReceipt, renderPreventionReceiptShare, resolveBriefingBudget, resolveConfigPath, resolveGatePolicy, resolveHaivePaths, resolveManifestFiles, resolveProjectInfo, retirementSignal, revertedShaFromCommit, reviewLearningsToDrafts, runRegexSensor, runSensors, runTierContract, runValidationContract, runtimeJournalPath, saveCodeMap, saveConfig, saveFrictionState, saveUsageIndex, scaffoldPostIncidentTest, scannableSensorTargets, scoreRetrievalCase, scoreSensorCase, scrubbedCommandEnv, selectCommandSensors, sensorAppliesToPath, sensorLedgerPath, sensorPatternBrittleness, sensorPromotedAtMap, sensorSelfCheck, sensorTargetsFromDiff, serializeCodeMap, serializeMemory, setFrictionStatus, shouldExpandGateReminder, snapshotContract, specificityScore, stripPrivate, suggestGate, suggestSensorFromMemory, suggestSensorSeed, suggestTopicKey, summarizeCaughtForYou, summarizeImpact, synthesizeSelfEvalCases, tallyHotFiles, titleFromBody, tokenizeQuery, tokenizeWords, trackDependencies, trackReads, truncateToTokens, usageLogPath, usageLogSize, usagePath, verifyAnchor, watchContracts, withQuarantineNote, withoutQuarantineNote, writeBriefingMarker, writeSessionHandoff };