opencode-swarm 7.112.0 → 7.112.1

package/dist/hooks/knowledge-injector.d.ts

@@ -9,6 +9,8 @@ import { recordKnowledgeShown } from './knowledge-application.js';
 import { buildEscalationBriefing, readRecentEscalations } from './knowledge-escalator.js';
 import { recordKnowledgeEvent } from './knowledge-events.js';
 import type { RankedEntry } from './knowledge-reader.js';
+import { recordLessonsShown } from './knowledge-reader.js';
+import { confirmEntriesPhase } from './knowledge-store.js';
 import type { DirectivePriority, KnowledgeConfig, MessageWithParts } from './knowledge-types.js';
 import { searchKnowledge } from './search-knowledge.js';
 /** Marker that uniquely identifies the delegate directive block in a transcript. */
@@ -97,4 +99,6 @@ export declare const _internals: {
     recordKnowledgeShown: typeof recordKnowledgeShown;
     readRecentEscalations: typeof readRecentEscalations;
     buildEscalationBriefing: typeof buildEscalationBriefing;
+    recordLessonsShown: typeof recordLessonsShown;
+    confirmEntriesPhase: typeof confirmEntriesPhase;
 };

package/dist/hooks/knowledge-reader.d.ts

@@ -35,6 +35,21 @@ export interface RankedEntry extends KnowledgeEntryBase {
     };
 }
 declare function transactShownFile(shownFile: string, mutate: (data: Record<string, string[]>) => Record<string, string[]> | null): Promise<boolean>;
+/**
+ * Records the set of knowledge IDs actually injected during a phase under the
+ * canonical `Phase N` key in `.swarm/.knowledge-shown.json`, so
+ * {@link updateRetrievalOutcome} can later attribute the phase's outcome to
+ * exactly those entries.
+ *
+ * Ownership (issue #1768): the shown-set write lives HERE at the injector layer
+ * (which knows the final rendered set), NOT inside `readMergedKnowledge` (which
+ * only sees the widened pre-rerank pool). Multiple injectors (architect +
+ * delegate) may write the same `Phase N` key within one phase, so the key is
+ * **union-merged** (dedup-safe) rather than overwritten — otherwise the last
+ * writer would clobber earlier id sets and those entries would receive no
+ * outcome attribution.
+ */
+export declare function recordLessonsShown(directory: string, lessonIds: string[], currentPhase: string): Promise<void>;
 export declare function readMergedKnowledge(directory: string, config: KnowledgeConfig, context?: ProjectContext, opts?: {
     skipScopeFilter?: boolean;
 }): Promise<RankedEntry[]>;
@@ -52,5 +67,6 @@ export declare const _internals: {
     scoreDirectiveAgainstContext: typeof scoreDirectiveAgainstContext;
     transactShownFile: typeof transactShownFile;
     recordKnowledgeEvent: typeof recordKnowledgeEvent;
+    recordLessonsShown: typeof recordLessonsShown;
 };
 export {};

package/dist/hooks/knowledge-store.d.ts

@@ -47,6 +47,29 @@ export declare function findNearDuplicate<T extends {
     lesson: string;
 }>(candidate: string, entries: T[], threshold?: number): T | undefined;
 export declare function computeConfidence(confirmedByCount: number, autoGenerated: boolean): number;
+/**
+ * Soft cap on the number of {@link PhaseConfirmationRecord}s retained per entry.
+ * Distinct-phase COUNT is the signal that matters (skill-maturity gate,
+ * `✓`/`✓✓` markers); the array itself only needs enough history to represent
+ * realistic multi-phase confirmation. Capped for hygiene on long-lived entries;
+ * oldest records are evicted. Issue #1768.
+ */
+export declare const MAX_CONFIRMED_BY = 50;
+/**
+ * Confirm that a set of knowledge entries was surfaced during a phase, by
+ * appending a {@link PhaseConfirmationRecord} to each entry's `confirmed_by`
+ * (issue #1768 defect 3). Retrieval/injection is the confirmation signal —
+ * previously `confirmed_by` only grew on near-duplicate re-add, so the
+ * skill-maturity `distinctPhases >= 2` gate was unsatisfiable in practice.
+ *
+ * Reuses {@link reinforceSwarmKnowledgeEntry} as the canonical writer so
+ * `confidence` stays consistent with `confirmed_by` (it recomputes confidence
+ * and applies the same-phase dedup + inactive-entry guard). All entries are
+ * mutated in ONE locked `transactKnowledge` transaction (mirroring the curator
+ * batch pattern) — never one lock per id. Fail-open: confirmation is
+ * best-effort and must never break injection.
+ */
+export declare function confirmEntriesPhase(directory: string, ids: string[], phaseNumber: number, projectName: string): Promise<void>;
 export declare const OUTCOME_SIGNAL_SMOOTHING = 4;
 export declare function computeOutcomeSignal(outcomes?: RetrievalOutcome): number;
 export declare function inferTags(lesson: string): string[];