@cerebriline/core 4.100.246 → 4.100.247

package/dist/session/team/team-session-coordinator.d.ts

@@ -4,7 +4,9 @@ import type { CoreSessionEvent } from "../../types/events";
 import type { ActiveSession, TeamRunUpdate } from "../../types/session";
 export declare function trackTeamRunState(session: ActiveSession, event: TeamEvent): void;
 export declare function dispatchTeamEventToBackend(rootSessionId: string, event: TeamEvent, invokeOptional: (method: string, ...args: unknown[]) => Promise<void>): Promise<void>;
-export declare function emitTeamProgress(session: ActiveSession, rootSessionId: string, event: TeamEvent, emit: (event: CoreSessionEvent) => void): void;
+/** Minimum gap between `team_progress` emits driven by telemetry events. */
+export declare const TEAM_PROGRESS_TELEMETRY_THROTTLE_MS = 1000;
+export declare function emitTeamProgress(session: ActiveSession, rootSessionId: string, event: TeamEvent, emit: (event: CoreSessionEvent) => void, now?: () => number): void;
 export declare function hasPendingTeamRunWork(session: ActiveSession): boolean;
 export declare function shouldAutoContinueTeamRuns(session: ActiveSession, finishReason: AgentResult["finishReason"]): boolean;
 export declare function notifyTeamRunWaiters(session: ActiveSession): void;

package/dist/tasks/task-tool.d.ts

@@ -3,9 +3,9 @@ import { z } from "zod";
 import { type ScheduledTaskResult, type ScheduleTaskOperationOptions } from "../cron/service/schedule-tool";
 import { type TodoTaskOperationOptions, type TodoTaskResult } from "./agenda-task-tool";
 export declare const TASKS_TOOL_NAME = "tasks";
-export declare const TASKS_SYSTEM_PROMPT_RULE = "# Tasks\n\nUse the `tasks` tool to manage durable Todo items and explicitly requested scheduled agent work.\n\n- Use `kind: \"todo\"` for meaningful follow-ups, handoffs, ideas, reminders, and other work that should remain visible after this session. This includes useful work you identify and suggest proactively. Agent-created Todos require user approval; Todos created directly by the user are approved immediately. Todo `available_at` controls availability in the list; it never schedules execution.\n- Use `kind: \"scheduled\"` only when the user explicitly asks Cline to execute work once at a future time or on a recurrence. One-time schedules require an exact future ISO 8601 `run_at` with an offset or Z. Recurring schedules require a five-field `cron_pattern` and may include an IANA `timezone`.\n- \"Remind me\" is ambiguous: ask whether the user wants a reviewed Todo note or an agent to execute work at that time when intent is unclear.\n- Never create both kinds for the same request unless the user explicitly requests both. Check existing items before creating a likely duplicate.\n- Todo instructions and scheduled prompts must be self-contained. Include the goal, constraints, relevant project context, and expected output.\n- Scheduled sessions run in the user's schedules home workspace, not this conversation's folder. Include absolute paths in the scheduled `prompt` for any project files or repositories the work must touch.\n- Never approve or start a Todo yourself. Only mutate schedules from an interactive user session, and only update, pause, resume, delete, or run one immediately when the user asks.";
+export declare const TASKS_SYSTEM_PROMPT_RULE = "# Tasks\n\nUse the `tasks` tool to manage durable Todo items and explicitly requested scheduled agent work.\n\n- Use `kind: \"todo\"` for meaningful follow-ups, handoffs, ideas, reminders, and other work that should remain visible after this session. This includes useful work you identify and suggest proactively. Agent-created Todos require user approval; Todos created directly by the user are approved immediately. Todo `available_at` controls availability in the list; it never schedules execution.\n- Use `kind: \"scheduled\"` only when the user explicitly asks Cline to execute work once at a future time or on a recurrence. One-time schedules require an exact future ISO 8601 `run_at` with an offset or Z. Recurring schedules require a five-field `cron_pattern` and default to the local timezone. Omit `timezone` unless the user explicitly requests a different timezone; never guess EST, UTC, or another zone. When a timezone is requested, use its IANA name (for example, America/New_York) so daylight-saving changes are handled.\n- \"Remind me\" is ambiguous: ask whether the user wants a reviewed Todo note or an agent to execute work at that time when intent is unclear.\n- Never create both kinds for the same request unless the user explicitly requests both. Check existing items before creating a likely duplicate.\n- Todo instructions and scheduled prompts must be self-contained. Include the goal, constraints, relevant project context, and expected output.\n- Scheduled sessions run in the user's schedules home workspace, not this conversation's folder. Include absolute paths in the scheduled `prompt` for any project files or repositories the work must touch.\n- Never approve or start a Todo yourself. Only mutate schedules from an interactive user session, and only update, pause, resume, delete, or run one immediately when the user asks.";
 /** Guidance used while the Todo kind is disabled and only schedules remain. */
-export declare const SCHEDULED_TASKS_SYSTEM_PROMPT_RULE = "# Tasks\n\nUse the `tasks` tool only when the user explicitly asks Cline to execute work once at a future time or on a recurrence. Always pass `kind: \"scheduled\"`.\n\n- One-time schedules require an exact future ISO 8601 `run_at` with an offset or Z. Recurring schedules require a five-field `cron_pattern` and may include an IANA `timezone`.\n- Never create a schedule proactively. Check existing schedules before creating a likely duplicate.\n- Make the scheduled `prompt` self-contained because it runs in a new unattended session in the user's schedules home workspace, not this conversation's folder. Include the goal, constraints, expected output, and absolute paths for any project files or repositories the work must touch.\n- Only update, pause, resume, delete, or run a schedule immediately when the user asks for that action.";
+export declare const SCHEDULED_TASKS_SYSTEM_PROMPT_RULE = "# Tasks\n\nUse the `tasks` tool only when the user explicitly asks Cline to execute work once at a future time or on a recurrence. Always pass `kind: \"scheduled\"`.\n\n- One-time schedules require an exact future ISO 8601 `run_at` with an offset or Z. Recurring schedules require a five-field `cron_pattern` and default to the local timezone. Omit `timezone` unless the user explicitly requests a different timezone; never guess EST, UTC, or another zone. When a timezone is requested, use its IANA name (for example, America/New_York) so daylight-saving changes are handled.\n- Never create a schedule proactively. Check existing schedules before creating a likely duplicate.\n- Make the scheduled `prompt` self-contained because it runs in a new unattended session in the user's schedules home workspace, not this conversation's folder. Include the goal, constraints, expected output, and absolute paths for any project files or repositories the work must touch.\n- Only update, pause, resume, delete, or run a schedule immediately when the user asks for that action.";
 export declare const TasksToolInputSchema: z.ZodDiscriminatedUnion<[z.ZodObject<{
     operation: z.ZodEnum<{
         list: "list";

package/dist/types/provider-settings.d.ts

@@ -17,13 +17,24 @@ export interface StoredProviderSettingsEntry {
     updatedAt: string;
     tokenSource: ProviderTokenSource;
 }
+/**
+ * One-shot repairs the legacy migration has already applied to this file.
+ * A repair reads legacy state that stays on disk forever, so without a marker
+ * it would re-apply on every launch and fight a user who undoes it.
+ */
+export interface StoredProviderRepairs {
+    /** Restored a bare legacy `awsProfile` onto an already-migrated entry. */
+    bedrockProfile?: boolean;
+}
 export interface StoredProviderSettings {
     version: 1;
     lastUsedProvider?: string;
     modes: StoredProviderModes;
+    repairs?: StoredProviderRepairs;
     providers: Record<string, StoredProviderSettingsEntry>;
 }
 export declare const StoredProviderModesSchema: z.ZodType<StoredProviderModes>;
+export declare const StoredProviderRepairsSchema: z.ZodType<StoredProviderRepairs>;
 export declare const StoredProviderSettingsEntrySchema: z.ZodType<StoredProviderSettingsEntry>;
 export declare const StoredProviderSettingsSchema: z.ZodType<StoredProviderSettings>;
 export declare function emptyStoredProviderSettings(): StoredProviderSettings;

package/dist/types/session.d.ts

@@ -165,6 +165,8 @@ export interface SessionPersistenceAdapter {
         limit: number;
         parentSessionId?: string;
         status?: string;
+        /** Only root sessions: excludes subagent and team-task child rows. */
+        rootOnly?: boolean;
     }): Promise<SessionRow[]>;
     updateSession(input: PersistedSessionUpdateInput): Promise<{
         updated: boolean;

package/dist/types/storage.d.ts

@@ -1,5 +1,23 @@
 import type { TeamRuntimeState, TeamTeammateSpec } from "@cerebriline/shared";
-import type { TeamEvent } from "../extensions/tools/team";
+import type { TeamEvent, TeamRuntimeStateDelta } from "../extensions/tools/team";
+/**
+ * One batched durable write: events to append to the history log plus the
+ * entities that changed since the previous batch. Applied atomically.
+ */
+export interface TeamPersistenceBatch {
+    /** Already-compacted durable events (see `toPersistableTeamEvent`). */
+    events: Array<{
+        type: string;
+        payload: unknown;
+    }>;
+    delta: TeamRuntimeStateDelta;
+    teammates: TeamTeammateSpec[];
+    /**
+     * Full state accessor for stores that cannot apply deltas (file fallback).
+     * Row-based stores must not call it.
+     */
+    getFullState: () => TeamRuntimeState;
+}
 import type { SessionStatus } from "./common";
 import type { SessionRecord } from "./sessions";
 export interface SessionStore {
@@ -27,6 +45,9 @@ export interface TeamStore {
         interruptedRunIds: string[];
     };
     handleTeamEvent(teamName: string, event: TeamEvent): Promise<void> | void;
+    /** Preferred write path: incremental, batched, single transaction. */
+    persistBatch(teamName: string, batch: TeamPersistenceBatch): Promise<void> | void;
+    /** Full rewrite of a team's state. Kept for callers outside the runtime. */
     persistRuntime(teamName: string, state: TeamRuntimeState, teammates: TeamTeammateSpec[]): Promise<void> | void;
     markInProgressRunsInterrupted(teamName: string, reason: string): Promise<string[]> | string[];
 }

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@cerebriline/core",
 	"description": "Cerebriline Core SDK for Node Runtime",
-	"version": "4.100.246",
+	"version": "4.100.247",
 	"repository": {
 		"type": "git",
 		"url": "git+https://github.com/mann1x/cline.git",
@@ -34,6 +34,18 @@
 		"./services/feature-flags/posthog": {
 			"types": "./dist/services/feature-flags/posthog.d.ts",
 			"import": "./dist/services/feature-flags/posthog.js"
+		},
+		"./remote/helper-entry": {
+			"types": "./dist/remote/remote-helper-entry.d.ts",
+			"import": "./dist/remote/remote-helper-entry.js"
+		},
+		"./cloud": {
+			"types": "./dist/cloud/index.d.ts",
+			"import": "./dist/cloud/index.js"
+		},
+		"./remote/helper": {
+			"types": "./dist/remote/remote-helper.d.ts",
+			"import": "./dist/remote/remote-helper.js"
 		}
 	},
 	"dependencies": {
@@ -69,9 +81,9 @@
 		"ws": "^8.20.0",
 		"yaml": "^2.8.2",
 		"zod": "^4.3.6",
-		"@cerebriline/agents": "4.100.246",
-		"@cerebriline/llms": "4.100.246",
-		"@cerebriline/shared": "4.100.246"
+		"@cerebriline/agents": "4.100.247",
+		"@cerebriline/llms": "4.100.247",
+		"@cerebriline/shared": "4.100.247"
 	},
 	"peerDependencies": {
 		"posthog-node": "^5.8.0"

package/dist/cron/runner/resource-limiter.d.ts

@@ -1,8 +0,0 @@
-export declare class ResourceLimiter {
-    private readonly globalMaxConcurrency;
-    private readonly activeExecutions;
-    constructor(globalMaxConcurrency: number);
-    acquire(scheduleId: string, executionId: string, maxParallel: number): boolean;
-    release(scheduleId: string, executionId: string): void;
-    getGlobalActiveCount(): number;
-}

package/dist/services/storage/team-events-retention.d.ts

@@ -1,25 +0,0 @@
-/**
- * How much of a team's event log its store keeps.
- *
- * Every team event was appended -- a row in `team_events`, a line in
- * `task-history.jsonl` -- for as long as the team lived, and none was ever
- * deleted. What reads the log (`readHistory`) reads the newest 200. So each
- * team keeps its newest {@link TEAM_EVENTS_KEPT}, cut back once every
- * {@link TEAM_EVENTS_PRUNE_EVERY} appends rather than on each one.
- */
-export declare const TEAM_EVENTS_KEPT = 1000;
-export declare const TEAM_EVENTS_PRUNE_EVERY = 100;
-/** A store's retention, as its options may set it (tests keep it small). */
-export interface TeamEventsRetention {
-    eventsKept?: number;
-    eventsPruneEvery?: number;
-}
-/**
- * Counts a store's appends per team, and says when one is due a prune: on
- * its first append since the store opened (a log left long by an older
- * build is cut then), and every `eventsPruneEvery` after.
- */
-export declare function createPruneSchedule(retention?: TeamEventsRetention): {
-    kept: number;
-    due(teamName: string): boolean;
-};