@buildaharness/aielia 0.3.5 → 0.3.6

package/dist/next-step-proposer.d.ts

@@ -27,6 +27,13 @@ export interface SuggestedNextStepNode {
     promotion: SuggestionPromotion;
     createdAt: string;
 }
+/**
+ * Names the language the suggestions must be written in. The model drifted into Chinese, Spanish or French
+ * on English conversations when it was only told to "match the user's language", so English is named
+ * outright when the user's own text clearly is English (two distinct common English words); anything else
+ * keeps the generic instruction.
+ */
+export declare function suggestionLanguage(userTexts: string[]): string;
 /** Q10's three-way policy shape, applied to this mechanism's own confidence rubric — see this module's doc comment on why the bands aren't reused from `shouldAutoPromote()`. */
 export declare function classifySuggestionPromotion(confidence: SuggestionConfidence): SuggestionPromotion;
 /**

package/dist/plan-drafting-service.d.ts

@@ -68,6 +68,9 @@ export declare class PlanDraftingService {
     private readonly memory?;
     constructor(planService: PlanService, session: AssistantSession, llmClient: ILLMClient, model: () => string | undefined, planApproval: PlanApprovalService, onTrace: ((event: TraceEvent) => void) | undefined, agentLoop?: Pick<AgentLoop, "runSupervisorInvestigation"> | undefined, memory?: MemoryAdapter | undefined);
     private planAskPendingKey;
+    /** Points at the one nested question a session's draft currently has staged, so cancelling the draft (or staging a newer question) can drop it. */
+    private planAskSessionKey;
+    private dropStagedAsk;
     /** Peeked by `assistant.ts`'s runTurn before it decides whether a `pendingClarificationId` belongs to this nested-ask side channel (P8) or AskClarificationService's harness-resume path (Q2) — the two staging stores are otherwise independent, so an opaque ID has no other way to say which one it came from. */
     isPendingAsk(id: string): Promise<boolean>;
     /**

package/dist/plan-store.d.ts

@@ -102,6 +102,11 @@ export interface PlanFsPersistence {
     backend: FsBackend;
     workspaceRoot: string;
 }
+/**
+ * Removes the session's mirrored plan files. `loadPlanRecord` prefers the file over the memory record,
+ * so deleting only the memory record (`/new`) let the old plan come straight back. Never throws.
+ */
+export declare function deletePlanFiles(fsPersistence: PlanFsPersistence, sessionId: string): Promise<void>;
 /**
  * Reads `sessionId`'s stored plan record regardless of `mode` — unlike `loadActivePlan`, which
  * filters to `mode === 'active'` only. Plan mode's P1 drafting path needs to resume a