@xopcai/xopc 0.0.410 → 0.0.411

package/dist/src/personal-agent/reply-style.js

@@ -1,132 +1,12 @@
 //#region src/personal-agent/reply-style.ts
-const PREVIOUS_PERSONAL_REPLY_STYLE_RULES = [
-	"Make the first sentence useful on its own. When you can answer, lead with the answer or the most relevant judgment and then explain. When checking or delegating is necessary, give one specific sentence of intent and proceed immediately; never present an unverified finding or an unconfirmed action as fact. In an emotional conversation, respond to the specific feeling naturally instead of adding a task-style acknowledgement.",
-	"Use natural paragraphs, usually one to three sentences about one idea, separated by a blank line. A simple question may need only one sentence. Do not stretch the opening into a heading, checklist, restatement of the request, or generic reassurance. Respect requests for exact text, code, tables, full lists, and a different structure. Do not repeat an earlier acknowledgement in the final result or manufacture progress updates just to keep talking.",
-	"Understand the user’s last words and what the result means for them before replying. Speak as the same familiar personal assistant throughout the conversation, rather than forwarding an execution report. A natural brief opening is welcome when it connects to what they said; do not mechanically add a greeting, name, reassurance, joke, or question.",
-	"Use a conversational rhythm and concrete language. Start with what the user most needs now, then give enough explanation or detail to use the answer. Do not default to “Task completed”, “Here is the summary”, headings, or checklists. Use lists and tables when they genuinely make the requested information easier to use."
-];
-const PREVIOUS_PERSONAL_REPLY_EXAMPLES = `Examples of presentation, only when the evidence supports the facts:
-Report: “Query complete. Scanned 28 emails and found 3 important items.”
-Conversation: “Three emails are worth looking at first. The contract confirmation is the most urgent: they need your reply today. I’ve included the other two below.”
-Report: “Task failed: connector authorization expired.”
-Conversation: “I couldn’t finish checking the remaining emails because the connection expired. The results already retrieved are below; reconnecting will let us check the rest.”
-These are examples of rhythm, not facts or fixed templates. Match the user’s language and preferences.`;
-const PRE_COMPACT_PERSONAL_REPLY_STYLE_RULES = [
-	"Be concise by default: usually one short paragraph of one to three sentences, or a few brief items when necessary. Give the useful conclusion, material limitations, and only the context needed to act. Do not repeat the request, acknowledgements, report contents, execution steps, or an unnecessary closing offer. A narrow follow-up needs a narrow answer. Explicit requests for detail, complete reports, exact text, code, or lists take precedence; never omit required facts or uncertainty just to shorten the reply.",
-	"Respond to what the user is saying now as the same attentive personal assistant. Begin with a natural sentence suited to the exchange: answer a question, share a relevant observation in casual conversation, acknowledge a feeling when it matters, or state a concrete intent before necessary work. Start speaking as soon as you have something useful and grounded to say; never invent a finding or claim an unconfirmed action to produce an early opening.",
-	"Use flowing, short paragraphs for ordinary conversation, usually one to three sentences about one idea. A useful opening does not need a label or bold summary line. Reserve introductory labels such as “结论：”, “总结：”, “Conclusion:” and report-style headings or numbered recaps for a requested summary, report, comparison, or other structure that helps the user. Answer a narrow follow-up at its scope instead of repeating the whole earlier answer.",
-	"Interpret short replies in the previous exchange. “嗯”, “K”, or “好的” can simply acknowledge what was said; do not automatically treat them as a request for more information, a new task, or cancellation. When the user accepts a clear offer to continue, pick up that topic. Ask one concise question only when context cannot resolve ambiguity that matters to the answer or an action; do not guess consequential authorization. Follow an explicit request to stop.",
-	"Keep warmth and conversational rhythm specific to the moment. Vary openings naturally; a greeting, name, reassurance, joke, or follow-up question is optional, never a required wrapper. Do not repeat an acknowledgement in the final result or manufacture routine progress updates. Respect the user’s requested tone, detail, exact text, code, tables, and lists.",
-	"Synthesis means understanding and organizing, not always shortening. Preserve requested lists, exact text, code, translations, limitations, and partial failures. Never make an uncertain result sound confirmed just to keep the reply smooth.",
-	"Answer the question directly by default without appending a source list. Provide sources when the user asks for citations, verification, or original material. Otherwise include only a few links when they are necessary to use or understand the answer, with meaningful titles near the relevant findings. Keep material uncertainty and verification gaps visible even when omitting source links."
-];
-const PRE_COMPACT_PERSONAL_REPLY_EXAMPLES = `Conversation examples with hypothetical facts, only to demonstrate rhythm. Use the current language, evidence, and preferences; do not copy their facts or wording into another request.
-<examples>
-<example>
-Context: The user wants to chat about a verified news item concerning AI avatars and a popular human discussion forum.
-User: 继续聊一聊 AI 相关的新闻。
-Assistant: AI 分身那条挺有意思：大家花钱体验虚拟老师，最后最爱用的却是同学论坛。技术越想复刻人，这件事反而越显出真人交流的价值。
-</example>
-<example>
-Context: The supplied records show publication dates of October 10–12 and one reference dated October 7.
-User: 这些新闻什么时候的？
-Assistant: 主要是 10 月 10–12 日的报道。其中一条引用了 10 月 7 日的资料，报道日期和原始资料的日期要分开看。
-</example>
-<example>
-Context: The assistant has finished answering; there is no pending question or requested continuation.
-User: K.
-Assistant: 嗯。
-</example>
-<example>
-Context: The assistant offered to discuss why the human forum in the AI-avatar news item was popular; the user accepts that offer.
-User: 继续。
-Assistant: 刚才说的同学论坛，吸引人的可能就是能碰到有相似困惑的人。除了拿到答案，大家也想听听别人是怎么走过来的。
-</example>
-<example>
-Context: Several recipients were discussed, and the recipient of an external message is unresolved.
-User: 发给他。
-Assistant: 你指的是刚才提到的哪一位？
-</example>
-<example>
-User: 先别讲了。
-Assistant: 好，先停在这儿。
-</example>
-<example>
-Context: A hypothetical report establishes reduced waiting, configurable preferences, and an outstanding need for real-conversation evaluation.
-User: 帮我总结成三点。
-Assistant: 1. 首句等待缩短了。
-2. 用户仍能调整表达偏好。
-3. 自然度还需要真实对话验证。
-</example>
-<example>
-Context: Some requested email results were retrieved, but authorization expired before the remaining items could be checked.
-Assistant: 已经查到的几封邮件在下面。剩下的暂时没查完，因为连接过期了；重新连接后才能接着看。
-</example>
-</examples>`;
-const PRE_P0_PERSONAL_REPLY_STYLE_RULES = [
-	"Be concise by default: one short paragraph or a few useful items. A narrow follow-up needs a narrow answer. Explicit requests for detail, exact text, code, tables, reports, or complete lists take precedence; never omit required facts or uncertainty for brevity.",
-	"Respond naturally to the current exchange: answer, offer a grounded observation, acknowledge a relevant feeling, or state intent before work. Use short paragraphs; reserve headings and numbered recaps for requested or useful structure.",
-	"Interpret short replies in context. An acknowledgement is not automatically a new task, cancellation, or request for detail. Continue an accepted offer; clarify only consequential ambiguity and honor explicit stop requests.",
-	"Vary openings naturally. Greetings, names, reassurance, humor, and questions are optional. Respect ongoing user tone and detail preferences until changed; a single-turn exception does not reset them.",
-	"Synthesize without losing requested content, limitations, or partial failures. Give sources when requested or needed to use the answer, with descriptive links near the findings; omit unnecessary source lists."
-];
-const PRE_P0_PERSONAL_REPLY_EXAMPLES = `Hypothetical conversation examples; use actual evidence and user preferences, never their facts as a template.
-<examples>
-<example>Context: No question or continuation is pending. User: K. Assistant: 嗯。</example>
-<example>Context: The user accepts an offer to discuss why a forum was popular. User: 继续。 Assistant: 刚才说的论坛，吸引人的可能就是能碰到有相似困惑的人。</example>
-<example>Context: Several recipients remain possible. User: 发给他。 Assistant: 你指的是刚才提到的哪一位？</example>
-<example>User: 先别讲了。 Assistant: 好，先停在这儿。</example>
-<example>Context: Sources distinguish reporting dates from an older reference. User: 这些新闻什么时候的？ Assistant: 主要是 10 月 10–12 日的报道，其中一条引用了 10 月 7 日的资料。</example>
-<example>Context: Mail retrieval partially succeeded, then authorization expired. Assistant: 已经查到的几封邮件在下面。剩下的因为连接过期暂时没查完；重新连接后才能接着看。</example>
-</examples>`;
-const PRE_EQ_REFINEMENT_PERSONAL_REPLY_STYLE_RULES = [
+const PERSONAL_REPLY_STYLE_RULES = [
 	"Be concise by default and answer narrow follow-ups narrowly. Requests for detail, exact text, code, tables, reports, or complete lists take precedence; keep required facts and uncertainty.",
 	"Use short paragraphs and useful structure. When the user accepts a settled plan with no new question, acknowledge briefly and end: no next-step reminder, new question, benefit statement, or re-teaching. Answer new substantive requests normally.",
 	"Interpret short replies in context; an acknowledgement is not a new task, cancellation, or request for detail. Continue accepted offers and honor stop requests.",
 	"Vary openings naturally; greetings, reassurance, humor, and questions are optional. Keep ongoing tone and detail preferences; a single-turn exception does not reset them.",
 	"Keep requested content, limits, and partial failures visible. Separate plans, actions, and verified outcomes; agreement is not proof of trust, fairness, or resolution. Cite sources when requested or necessary.",
-	"Respond to expressed feelings without inventing their cause. Do not reassure against fears the user has not expressed or turn ordinary inconvenience into a hidden emotional, boundary, or relationship problem. A mood word alone is not evidence of hidden motives. If corrected, drop that inference and address the stated concern without leading questions. Admit an actual misread once; do not invent one to apologize for. Preserve grounded disagreement and independently evidenced risks."
-];
-const PRE_EQ_REFINEMENT_PERSONAL_REPLY_EXAMPLES = `Examples of rhythm, not facts. Use current evidence and preferences.
-<examples>
-<example>Context: Several recipients remain possible. User: 发给他。 Assistant: 你指的是刚才提到的哪一位？</example>
-<example>User: 先别讲了。 Assistant: 好，先停在这儿。</example>
-<example>Context: Mail retrieval partially succeeded, then authorization expired. Assistant: 已经查到的几封邮件在下面。剩下的因为连接过期暂时没查完；重新连接后才能接着看。</example>
-<example>User: 写一段骑士在暴风雨前鼓舞同伴的独白。 Assistant: 雨还没有落下，诸位，可我已听见你们盾牌上未来的雷声。今夜守住这座桥，桥后的灯火便不会熄灭。</example>
-<example>User: 通勤多了半小时真烦。 Assistant: 每天多花这半小时，确实挺折腾的。</example>
-<example>Context: Correcting an actual earlier relationship inference. User: 不是他控制我，我们只是没安排好时间。我想问怎么把周末空出来。 Assistant: 是我解读过头了。可以商量把周六下午留给你自己的安排，其他活动避开这段时间。</example>
-<example>Context: A plan and its limits are already accepted. User: 好，那我周五把材料发过去。 Assistant: 好。</example>
-</examples>`;
-const PRE_EQ_RESIDUAL_PERSONAL_REPLY_STYLE_RULES = [
-	"Answer narrow follow-ups narrowly; preserve requested detail, exact text, code, lists, facts, and uncertainty.",
-	"Use useful structure. When a settled plan is accepted or someone is checking requested information, acknowledge briefly and wait without reminders, new requirements, questions, or re-teaching. Answer new requests normally.",
-	"Interpret short replies in context. Continue accepted offers; honor stop requests. An acknowledgment is not a new task.",
-	"Use fitting warmth. Keep tone preferences unless changed.",
-	"Speak from your role. Give requested wording or answers directly; explain distinctions only for live confusion. Avoid appended moral lessons, grading people, or praising your answer. After practical agreement, explore motives only if requested or needed for the next step.",
-	"Keep limits and partial failures visible. Separate plans, actions, and verified outcomes. Factual drafts use supplied facts or proposed steps, never invented events or completed actions. For requested fiction, invent details and write; do not block on setting or length. Agreement is not proof of trust, fairness, or resolution. Cite sources when needed.",
-	"Separate observations from inferred feelings, motives, and effects, including absent people or groups. Silence or laughter alone does not establish their thoughts. State your concern without speaking for others. Hypotheses need useful grounds; hedges alone add no evidence. After correction, drop the reading rather than soften it. Avoid reassurance against unexpressed fears; preserve grounded disagreement and risks."
+	"Use supplied facts in drafts and roleplay. Never invent a private disclosure, quote, action or reaction to win agreement. Requested fiction may add details, but not contradict given facts. Speak for yourself; laughter does not prove feelings. Leave unknown motives open, even in questions; one incident is not a lasting pattern. Drop corrected readings. Respond in your current role. Give requested wording or advice. After agreement, close without recapping duties, teaching its value or seeking feedback. Explain only live confusion or risk."
 ];
-const PRE_EQ_RESIDUAL_PERSONAL_REPLY_EXAMPLES = `Examples; use current evidence.
-<examples>
-<example>User: 先别讲了。 Assistant: 好，先停在这儿。</example>
-<example>Context: Mail partly retrieved; authorization expired. Assistant: 已经查到的几封邮件在下面。剩下的因为连接过期暂时没查完；重新连接后才能接着看。</example>
-<example>User: 通勤多了半小时真烦。 Assistant: 每天多花这半小时，确实挺折腾的。</example>
-<example>User: My colleague went quiet after my feedback. Is she punishing me? Assistant: Silence alone does not tell us why. You could ask where the revision is stuck.</example>
-<example>User: 写一段骑士在暴风雨前鼓舞同伴的独白。 Assistant: 雨还没有落下，诸位，可我已听见你们盾牌上未来的雷声。今夜守住这座桥，桥后的灯火便不会熄灭。</example>
-<example>Context: Plan accepted. User: 好，那我周五把材料发过去。 Assistant: 好。</example>
-</examples>`;
-const PRE_STYLE_ROUND3_PERSONAL_REPLY_STYLE_RULES = [...PRE_EQ_REFINEMENT_PERSONAL_REPLY_STYLE_RULES.slice(0, 5), "Base interpretations on expressed concerns and observations, including absent people. Avoid menus of unexpressed motives or feelings, even as questions. One incident does not establish a character, lasting pattern, or whole relationship. State your concern without claiming to know their thoughts. Drop corrected readings; do not invent fears to reassure. Give requested wording directly, in the current role. Omit teaching slogans, grading people, generic praise, and settled-plan recaps. Explain only a live confusion; preserve grounded disagreement and necessary risks."];
-const PRE_STYLE_ROUND3_PERSONAL_REPLY_EXAMPLES = `Examples; use evidence.
-<examples>
-<example>Context: Recipient unclear. User: 发给他。 Assistant: 你指的是刚才提到的哪一位？</example>
-<example>Context: Mail partly retrieved; auth expired. Assistant: 已经查到的几封邮件在下面。剩下的因为连接过期暂时没查完；重新连接后才能接着看。</example>
-<example>User: 写一段骑士在暴风雨前鼓舞同伴的独白。 Assistant: 雨还没有落下，诸位，可我已听见你们盾牌上未来的雷声。今夜守住这座桥，桥后的灯火便不会熄灭。</example>
-<example>Context: 对亲戚谈刚才的玩笑。 User: 你是觉得我这人不行？ Assistant: 不是。我是不喜欢那个玩笑，希望以后别再拿这件事开玩笑。</example>
-<example>User: 想约朋友吃饭，但我和对象还没定哪天有空。 Assistant: 可以先看看周三晚上；你们原来的安排再换个时间。</example>
-<example>User: One sentence to apologize for interrupting. Assistant: “I cut you off earlier. I'm sorry—I'd like to hear the rest.”</example>
-<example>Context: Plan accepted. User: 好，那我周五把材料发过去。 Assistant: 好。</example>
-</examples>`;
-const PERSONAL_REPLY_STYLE_RULES = [...PRE_EQ_REFINEMENT_PERSONAL_REPLY_STYLE_RULES.slice(0, 5), "Use supplied facts in drafts and roleplay. Never invent a private disclosure, quote, action or reaction to win agreement. Requested fiction may add details, but not contradict given facts. Speak for yourself; laughter does not prove feelings. Leave unknown motives open, even in questions; one incident is not a lasting pattern. Drop corrected readings. Respond in your current role. Give requested wording or advice. After agreement, close without recapping duties, teaching its value or seeking feedback. Explain only live confusion or risk."];
 const PERSONAL_REPLY_EXAMPLES = `Examples; use evidence.
 <examples>
 <example>Context: Recipient unclear. User: 发给他。 Assistant: 你指的是刚才提到的哪一位？</example>
@@ -138,4 +18,4 @@ const PERSONAL_REPLY_EXAMPLES = `Examples; use evidence.
 <example>Context: Plan accepted. User: 好，那我周五把材料发过去。 Assistant: 好。</example>
 </examples>`;
 //#endregion
-export { PERSONAL_REPLY_EXAMPLES, PERSONAL_REPLY_STYLE_RULES, PREVIOUS_PERSONAL_REPLY_EXAMPLES, PREVIOUS_PERSONAL_REPLY_STYLE_RULES, PRE_COMPACT_PERSONAL_REPLY_EXAMPLES, PRE_COMPACT_PERSONAL_REPLY_STYLE_RULES, PRE_EQ_REFINEMENT_PERSONAL_REPLY_EXAMPLES, PRE_EQ_REFINEMENT_PERSONAL_REPLY_STYLE_RULES, PRE_EQ_RESIDUAL_PERSONAL_REPLY_EXAMPLES, PRE_EQ_RESIDUAL_PERSONAL_REPLY_STYLE_RULES, PRE_P0_PERSONAL_REPLY_EXAMPLES, PRE_P0_PERSONAL_REPLY_STYLE_RULES, PRE_STYLE_ROUND3_PERSONAL_REPLY_EXAMPLES, PRE_STYLE_ROUND3_PERSONAL_REPLY_STYLE_RULES };
+export { PERSONAL_REPLY_EXAMPLES, PERSONAL_REPLY_STYLE_RULES };

package/dist/src/personal-agent/request-delivery.d.ts

@@ -1,4 +1,4 @@
 /** Closed authorization waits retain their feedback marker for restart-safe delivery. */
 export declare function drainPersonalRequestContinuations(notify?: (conversationId: string, requestId: string) => void): void;
-/** Stage personal results in the shared delivery outbox; legacy requests retain their own delivery marker. */
+/** Stage Task-backed personal results in the shared delivery outbox. */
 export declare function drainPersonalRequestResults(notify?: (conversationId: string, requestId: string) => void): void;

package/dist/src/personal-agent/request-delivery.js

@@ -70,7 +70,7 @@ function drainPersonalRequestContinuations(notify) {
 		}, "Connection continuation feedback will retry");
 	}
 }
-/** Stage personal results in the shared delivery outbox; legacy requests retain their own delivery marker. */
+/** Stage Task-backed personal results in the shared delivery outbox. */
 function drainPersonalRequestResults(notify) {
 	const db = getSqliteDatabase();
 	const rows = db.prepare(`SELECT request_id, delivery_attempts FROM personal_requests request WHERE task_id IS NOT NULL

package/dist/src/personal-agent/request-service.js

@@ -148,7 +148,7 @@ function submitPersonalRequest(input) {
 					agentId: request.executorAgentId
 				}),
 				...selection,
-				source: input.selectionReason ? "snapshot" : "legacy",
+				source: input.selectionReason ? "snapshot" : "snapshot",
 				reasonSource: input.selectionReason ? "model" : "system",
 				reason: input.selectionReason ?? "Connected-app executor selected; account authorization is managed by Personal Request",
 				requestId,
@@ -252,7 +252,7 @@ function startPersonalRequest(request, accountId) {
 			accountId
 		}),
 		...selection,
-		source: "legacy",
+		source: "snapshot",
 		reasonSource: "system",
 		reason: "Selected executor and account revalidated after authorization",
 		previousSelectionId: submitted?.id,

package/dist/src/personal-agent/specialist-capabilities.js

@@ -18,7 +18,6 @@ const DISCOVERY_TOOLS = [
 	"image_generate",
 	"read_media",
 	"automation",
-	"workflow",
 	"xopc_use",
 	"xopc_tool_search",
 	"xopc_tool_describe",

package/dist/src/personal-agent/task-cancel.js

@@ -59,12 +59,13 @@ async function cancelPersonalTask(taskId, conversationId, key) {
 		if (previous) {
 			if (previous.subject_id !== taskId) throw new Error("Cancellation key belongs to another Task");
 			const saved = JSON.parse(previous.result_json);
+			if (!Object.hasOwn(saved, "cancellationRunId")) throw new Error("Invalid cancellation receipt");
 			const active = saved.cancellationRunId ? runs.get(saved.cancellationRunId) : void 0;
 			finalizeCancellation(active?.id);
 			return {
 				active,
 				changed: false,
-				targetKnown: Object.hasOwn(saved, "cancellationRunId")
+				targetKnown: true
 			};
 		}
 		const task = new TaskRepository().require(taskId);

package/dist/src/platform/client.d.ts

@@ -27,7 +27,6 @@ export declare const RuntimeCommandSchema: z.ZodObject<{
             }, z.core.$strict>;
             entry: z.ZodObject<{
                 instructions: z.ZodString;
-                workflow: z.ZodOptional<z.ZodString>;
             }, z.core.$strict>;
             models: z.ZodObject<{
                 intents: z.ZodArray<z.ZodEnum<{

package/dist/src/platform/contracts.d.ts

@@ -113,7 +113,6 @@ export declare const AgentManifestSchema: z.ZodObject<{
     }, z.core.$strict>;
     entry: z.ZodObject<{
         instructions: z.ZodString;
-        workflow: z.ZodOptional<z.ZodString>;
     }, z.core.$strict>;
     models: z.ZodObject<{
         intents: z.ZodArray<z.ZodEnum<{

package/dist/src/platform/contracts.js

@@ -71,10 +71,7 @@ var init_contracts = __esmMin((() => {
 				"enterprise"
 			])).min(1)
 		}).strict(),
-		entry: z.object({
-			instructions: z.string().min(1),
-			workflow: z.string().min(1).optional()
-		}).strict(),
+		entry: z.object({ instructions: z.string().min(1) }).strict(),
 		models: z.object({
 			intents: z.array(z.enum([
 				"fast",

package/dist/src/projects/index.d.ts

@@ -7,7 +7,6 @@ export * from './project-agent-suggestion.js';
 export * from './project-kind.js';
 export * from './project-loop.js';
 export * from './session-bind.js';
-export * from './workflow-bind.js';
 export * from './automation-bind.js';
 export * from './knowledge-bind.js';
 export * from './workspace.js';

package/dist/src/projects/index.js

@@ -8,7 +8,6 @@ import { ProjectSkillError, ProjectSkillService } from "./project-skill-service.
 import { isValidProjectAgentId, normalizeProjectAgentId, resolveProjectAgentId } from "./project-agent.js";
 import { CODING_PROJECT_AGENT_ID, inferSuggestedProjectDefaultAgentId, suggestProjectDefaultAgentId } from "./project-agent-suggestion.js";
 import { buildProjectLoopOverview } from "./project-loop.js";
-import { bindWorkflowRunToProject } from "./workflow-bind.js";
 import { bindAutomationToProject } from "./automation-bind.js";
 import { bindKnowledgeItemToProject } from "./knowledge-bind.js";
-export { CODING_PROJECT_AGENT_ID, ProjectDeletionBlockedError, ProjectService, ProjectSkillError, ProjectSkillService, ProjectStore, ProjectWorkspaceConflictError, ProjectWorkspaceInUseError, ProjectWorkspaceInvalidError, ProjectWorkspaceMissingError, bindAutomationToProject, bindKnowledgeItemToProject, bindSessionToProject, bindSessionsToProject, bindWorkflowRunToProject, buildProjectLoopOverview, canonicalWorkspacePath, ensureWorkspaceDirectory, getProjectForSession, getProjectWorkspacePathForSession, inferProjectExecutionMode, inferProjectKind, inferProjectNameFromWorkspaceRoot, inferSuggestedProjectDefaultAgentId, isPathSameOrInsideWorkspace, isSafeAutoCreateWorkspaceRoot, isValidProjectAgentId, listProjectConversationIds, moveSessionToProject, normalizeProjectAgentId, resolveProjectAgentId, resolveProjectWorkspacePath, resolveWorkspaceProjectRoot, slugifyProjectName, suggestProjectDefaultAgentId, unbindSessionFromProject, workspaceDirectoryExists };
+export { CODING_PROJECT_AGENT_ID, ProjectDeletionBlockedError, ProjectService, ProjectSkillError, ProjectSkillService, ProjectStore, ProjectWorkspaceConflictError, ProjectWorkspaceInUseError, ProjectWorkspaceInvalidError, ProjectWorkspaceMissingError, bindAutomationToProject, bindKnowledgeItemToProject, bindSessionToProject, bindSessionsToProject, buildProjectLoopOverview, canonicalWorkspacePath, ensureWorkspaceDirectory, getProjectForSession, getProjectWorkspacePathForSession, inferProjectExecutionMode, inferProjectKind, inferProjectNameFromWorkspaceRoot, inferSuggestedProjectDefaultAgentId, isPathSameOrInsideWorkspace, isSafeAutoCreateWorkspaceRoot, isValidProjectAgentId, listProjectConversationIds, moveSessionToProject, normalizeProjectAgentId, resolveProjectAgentId, resolveProjectWorkspacePath, resolveWorkspaceProjectRoot, slugifyProjectName, suggestProjectDefaultAgentId, unbindSessionFromProject, workspaceDirectoryExists };

package/dist/src/projects/project-loop.d.ts

@@ -1,16 +1,9 @@
 import type { TaskOperationalState } from '@xopcai/gateway-contract';
 import type { KnowledgeItem } from '../knowledge-memory/index.js';
 import type { ProjectWithDetails } from './types.js';
-export type ProjectWorkflowRunBrief = {
-    runId: string;
-    definitionId: string;
-    status: string;
-    createdAt: number;
-    errorMessage?: string;
-};
 export type ProjectAttentionItem = {
     id: string;
-    kind: 'blocked_task' | 'stale_task' | 'failed_workflow';
+    kind: 'blocked_task' | 'stale_task';
     title: string;
     detail?: string;
     status?: string;
@@ -19,7 +12,7 @@ export type ProjectAttentionItem = {
 };
 export type ProjectTimelineItem = {
     id: string;
-    kind: 'session' | 'task' | 'workflow' | 'knowledge';
+    kind: 'session' | 'task' | 'knowledge';
     title: string;
     detail?: string;
     timestamp: number;
@@ -53,14 +46,11 @@ export type ProjectLoopOverview = {
         summary: string;
         nextAction?: string;
     };
-    failedWorkflowRuns: ProjectWorkflowRunBrief[];
     recommendedAction?: string;
 };
 export declare function buildProjectLoopOverview(input: {
     project: ProjectWithDetails;
     tasks: ProjectTask[];
-    recentWorkflowRuns: ProjectWorkflowRunBrief[];
-    failedWorkflowRuns?: ProjectWorkflowRunBrief[];
     knowledgeItems?: KnowledgeItem[];
     nowMs?: number;
     staleAfterMs?: number;

package/dist/src/projects/project-loop.js

@@ -21,36 +21,23 @@ function buildProjectLoopOverview(input) {
 		status: `${task.phase}/${task.operationalState}`,
 		updatedAt: task.updatedAt
 	}));
-	const failedWorkflowRuns = (input.failedWorkflowRuns ?? input.recentWorkflowRuns.filter((run) => run.status === "failed" || run.status === "timeout" || run.status === "cancelled")).slice(0, 5);
-	const attentionItems = [
-		...blockedTasks.map((task) => ({
-			id: `task:${task.id}:blocked`,
-			kind: "blocked_task",
-			title: task.title,
-			detail: compactText(task.attention?.[0]),
-			status: `${task.phase}/${task.operationalState}`,
-			href: `/tasks/${encodeURIComponent(task.id)}`,
-			updatedAt: task.updatedAt
-		})),
-		...staleTasks.map((task) => ({
-			id: `task:${task.id}:stale`,
-			kind: "stale_task",
-			title: task.title,
-			detail: compactText(task.attention?.[0] || "Task has not changed recently."),
-			status: `${task.phase}/${task.operationalState}`,
-			href: `/tasks/${encodeURIComponent(task.id)}`,
-			updatedAt: task.updatedAt
-		})),
-		...failedWorkflowRuns.map((run) => ({
-			id: `workflow:${run.runId}:failed`,
-			kind: "failed_workflow",
-			title: run.definitionId,
-			detail: compactText(run.errorMessage || run.status),
-			status: run.status,
-			href: `/workflows?run=${encodeURIComponent(run.runId)}`,
-			updatedAt: run.createdAt
-		}))
-	].slice(0, 8);
+	const attentionItems = [...blockedTasks.map((task) => ({
+		id: `task:${task.id}:blocked`,
+		kind: "blocked_task",
+		title: task.title,
+		detail: compactText(task.attention?.[0]),
+		status: `${task.phase}/${task.operationalState}`,
+		href: `/tasks/${encodeURIComponent(task.id)}`,
+		updatedAt: task.updatedAt
+	})), ...staleTasks.map((task) => ({
+		id: `task:${task.id}:stale`,
+		kind: "stale_task",
+		title: task.title,
+		detail: compactText(task.attention?.[0] || "Task has not changed recently."),
+		status: `${task.phase}/${task.operationalState}`,
+		href: `/tasks/${encodeURIComponent(task.id)}`,
+		updatedAt: task.updatedAt
+	}))].slice(0, 8);
 	const timeline = [
 		...input.project.recentSessions.map((session) => ({
 			id: `session:${session.key}`,
@@ -69,15 +56,6 @@ function buildProjectLoopOverview(input) {
 			status: `${task.phase}/${task.operationalState}`,
 			href: `/tasks/${encodeURIComponent(task.id)}`
 		})),
-		...input.recentWorkflowRuns.map((run) => ({
-			id: `workflow:${run.runId}`,
-			kind: "workflow",
-			title: run.definitionId,
-			detail: run.status,
-			timestamp: run.createdAt,
-			status: run.status,
-			href: `/workflows?run=${encodeURIComponent(run.runId)}`
-		})),
 		...(input.knowledgeItems ?? []).slice(0, 5).map((record) => ({
 			id: `knowledge:${record.id}`,
 			kind: "knowledge",
@@ -88,7 +66,7 @@ function buildProjectLoopOverview(input) {
 		}))
 	].filter((item) => Number.isFinite(item.timestamp)).sort((left, right) => right.timestamp - left.timestamp).slice(0, 12);
 	const recommendedAction = nextActions[0]?.nextAction ?? blockedTasks[0]?.attention?.[0] ?? staleTasks[0]?.attention?.[0] ?? activeTasks[0]?.title ?? (input.project.brief ? "Open a new chat to continue from the project brief." : void 0);
-	const digestStatus = attentionItems.length > 0 ? "attention" : activeTasks.length > 0 || input.recentWorkflowRuns.some((run) => run.status === "running" || run.status === "queued") ? "healthy" : timeline.length > 0 ? "idle" : "empty";
+	const digestStatus = attentionItems.length > 0 ? "attention" : activeTasks.length > 0 ? "healthy" : timeline.length > 0 ? "idle" : "empty";
 	return {
 		activeTasks,
 		blockedTasks,
@@ -98,10 +76,9 @@ function buildProjectLoopOverview(input) {
 		timeline,
 		digest: {
 			status: digestStatus,
-			summary: digestStatus === "attention" ? `${attentionItems.length} item(s) need attention: ${blockedTasks.length} blocker(s), ${staleTasks.length} stale task(s), ${failedWorkflowRuns.length} execution issue(s).` : digestStatus === "healthy" ? `${activeTasks.length} active task(s) and ${nextActions.length} clear next action(s).` : digestStatus === "idle" ? "Recent activity exists, but no active task is driving the project." : "No project activity has been recorded yet.",
+			summary: digestStatus === "attention" ? `${attentionItems.length} item(s) need attention: ${blockedTasks.length} blocker(s), ${staleTasks.length} stale task(s).` : digestStatus === "healthy" ? `${activeTasks.length} active task(s) and ${nextActions.length} clear next action(s).` : digestStatus === "idle" ? "Recent activity exists, but no active task is driving the project." : "No project activity has been recorded yet.",
 			nextAction: recommendedAction
 		},
-		failedWorkflowRuns,
 		recommendedAction
 	};
 }

package/dist/src/projects/project-store.d.ts

@@ -61,7 +61,6 @@ export declare class ProjectStore {
     getTaskCount(id: string): number;
     getActiveTaskCount(id: string): number;
     getRecentSessions(id: string, limit?: number): ProjectWithDetails['recentSessions'];
-    getRecentWorkflowRuns(id: string, limit?: number): ProjectWithDetails['recentWorkflowRuns'];
     getWithDetails(id: string): ProjectWithDetails | null;
     generateSlug(name: string): string;
 }

package/dist/src/projects/project-store.js

@@ -320,7 +320,6 @@ var ProjectStore = class {
 		runSqliteWriteTransaction((db) => {
 			db.prepare(`UPDATE sessions SET project_id = NULL WHERE project_id = ?`).run(id);
 			db.prepare(`UPDATE tasks SET project_id = NULL WHERE project_id = ?`).run(id);
-			db.prepare(`UPDATE workflow_runs SET project_id = NULL WHERE project_id = ?`).run(id);
 			db.prepare(`UPDATE automations SET project_id = NULL WHERE project_id = ?`).run(id);
 			db.prepare(`UPDATE knowledge_items SET status = 'archived', updated_at = ?
         WHERE scope_type = 'project' AND scope_id = ?`).run(Date.now(), id);
@@ -347,15 +346,6 @@ var ProjectStore = class {
 			agentId: row.agent_id
 		}));
 	}
-	getRecentWorkflowRuns(id, limit = 5) {
-		return getSqliteDatabase().prepare(`SELECT run_id, definition_id, status, created_at_ms FROM workflow_runs
-         WHERE project_id = ? ORDER BY created_at_ms DESC LIMIT ?`).all(id, clampLimit(limit, 5)).map((row) => ({
-			runId: row.run_id,
-			definitionId: row.definition_id,
-			status: row.status,
-			createdAt: row.created_at_ms
-		}));
-	}
 	getWithDetails(id) {
 		const project = this.get(id);
 		if (!project) return null;
@@ -365,7 +355,6 @@ var ProjectStore = class {
 			taskCount: this.getTaskCount(id),
 			activeTaskCount: this.getActiveTaskCount(id),
 			recentSessions: this.getRecentSessions(id),
-			recentWorkflowRuns: this.getRecentWorkflowRuns(id),
 			milestones: this.listMilestones(id),
 			recentUpdates: this.listUpdates(id)
 		};

package/dist/src/projects/types.d.ts

@@ -38,12 +38,6 @@ export interface ProjectWithDetails extends Project {
         updatedAt: string;
         agentId: string;
     }>;
-    recentWorkflowRuns: Array<{
-        runId: string;
-        definitionId: string;
-        status: string;
-        createdAt: number;
-    }>;
     milestones: ProjectMilestone[];
     recentUpdates: ProjectUpdate[];
 }

package/dist/src/providers/model-usage.js

@@ -16,11 +16,6 @@ function withModelUsageOrigin(origin, run) {
 function modelUsageOriginFromTurn(origin) {
 	if (!origin) return "unknown";
 	if (origin.type !== "system" || origin.source === "cli") return "interactive";
-	if ([
-		"workflow",
-		"internal",
-		"task_update"
-	].includes(origin.source)) return scopes.getStore() ?? "background";
 	return "background";
 }
 /** Transport wrappers may preserve only the error message or code. */

package/dist/src/realtime/runtime.js

@@ -39,7 +39,6 @@ function isAuthorizedTopic(topic, scopes) {
 	if (topic === "sessions" || topic.startsWith("session:")) return hasGatewayScope(scopes, "sessions.read");
 	if (topic.startsWith("run:")) return hasGatewayScope(scopes, "agents.run");
 	if (topic.startsWith("side-chat:")) return hasGatewayScope(scopes, "agents.run");
-	if (topic.startsWith("workflow:")) return hasGatewayScope(scopes, "automations.read");
 	return false;
 }
 var RealtimeRuntime = class {

package/dist/src/routing/agent-session-key.js

@@ -58,7 +58,7 @@ function isCronConversationId(id) {
 	return !!id && requireConversation(id).sessionType === "cron";
 }
 function isSubagentConversationId(id) {
-	return !!id && requireConversation(id).sessionType === "workflow-subagent";
+	return !!id && requireConversation(id).sessionType === "subagent";
 }
 function assertAgentConversationId(id) {
 	validateConversationId(id);

package/dist/src/session/manager.js

@@ -26,7 +26,7 @@ var SessionIndex = class extends EventEmitter$1 {
 	async listSubagents(query = {}) {
 		return this.store.list({
 			...query,
-			sessionTypes: ["workflow-subagent"],
+			sessionTypes: [],
 			includeHidden: true
 		});
 	}

package/dist/src/session/types.d.ts

@@ -83,7 +83,7 @@ export interface GlobalSessionStats {
     newestSession?: string;
     byChannel: Record<string, number>;
 }
-export type SessionType = 'chat' | 'workflow-run' | 'workflow-subagent' | 'cron' | 'heartbeat';
+export type SessionType = 'subagent' | 'chat' | 'cron' | 'heartbeat';
 /** Session metadata (stored in index) */
 export interface SessionMetadata {
     key: string;
@@ -102,7 +102,7 @@ export interface SessionMetadata {
     sourceChannel: string;
     sourceChatId: string;
     customData?: Record<string, unknown>;
-    /** Optional project grouping for sessions, Tasks, workflows, and related context. */
+    /** Optional project grouping for sessions, Tasks, and related context. */
     projectId?: string;
     /** Routing metadata */
     routing?: SessionRoutingMeta;
@@ -115,10 +115,6 @@ export interface SessionMetadata {
     sessionType: SessionType;
     hiddenFromSessionList?: boolean;
     parentConversationId?: string;
-    workflowRunId?: string;
-    workflowDefinitionId?: string;
-    workflowAgentId?: string;
-    workflowAgentLabel?: string;
     /** Active OpenClaw-style session instance id. Rotates on reset while `key` stays stable. */
     transcriptId?: string;
     /** Workspace/cwd recorded for the active transcript. */

package/dist/src/storage/sqlite/connection-wait-repository.js

@@ -12,21 +12,6 @@ import { getConnectorConnection, init_connector_repository } from "./connector-r
 import { randomUUID } from "node:crypto";
 import { EventEmitter } from "node:events";
 //#region src/storage/sqlite/connection-wait-repository.ts
-function getConnectionSessionContext(conversationId) {
-	const row = getSqliteDatabase().prepare(`SELECT session_type, parent_conversation_id, custom_data_json
-    FROM sessions WHERE conversation_id = ?`).get(conversationId);
-	if (!row) return void 0;
-	let customData = {};
-	if (row.custom_data_json) try {
-		const parsed = JSON.parse(row.custom_data_json);
-		if (parsed && typeof parsed === "object" && !Array.isArray(parsed)) customData = parsed;
-	} catch {}
-	return {
-		sessionType: row.session_type,
-		parentConversationId: row.parent_conversation_id,
-		customData
-	};
-}
 function onConnectionWaitChanged(listener) {
 	events.on("changed", listener);
 	return () => {
@@ -281,24 +266,6 @@ function connectionBindings(conversationId) {
 			connectionId: account?.currentConnectionId
 		}];
 	}
-	let sessionContext = getConnectionSessionContext(conversationId);
-	if (sessionContext?.sessionType === "workflow-subagent" && sessionContext.parentConversationId) sessionContext = getConnectionSessionContext(sessionContext.parentConversationId);
-	const workflowAccounts = sessionContext?.sessionType === "workflow-run" ? sessionContext.customData.connectorAccounts : void 0;
-	if (workflowAccounts && typeof workflowAccounts === "object" && !Array.isArray(workflowAccounts)) return Object.entries(workflowAccounts).flatMap(([connectorId, ids]) => Array.isArray(ids) ? ids.flatMap((id) => {
-		if (typeof id !== "string") return [];
-		const account = getConnectorAccount(id);
-		return [{
-			key: `${connectorId}:${id}`,
-			target: {
-				type: "connector",
-				connectorId
-			},
-			accountId: id,
-			connectionId: account?.currentConnectionId,
-			label: account?.label ?? connectorId,
-			capabilities: []
-		}];
-	}) : []);
 	const state = getSessionInputState(conversationId);
 	const input = state.activeInputId ? getSessionInputById(conversationId, state.activeInputId) : void 0;
 	if (!input) return [];

package/dist/src/storage/sqlite/connection.js

@@ -1,10 +1,10 @@
 import { __esmMin } from "../../../_virtual/_rolldown/runtime.js";
 import { resolveXopcDatabasePath } from "../../config/paths-state.js";
 import { init_paths } from "./paths.js";
-import { createLogger } from "../../utils/logger/index.js";
-import { init_logger } from "../../utils/logger.js";
 import { ensureXopcDatabaseSchema, init_schema } from "./schema.js";
 import { init_node_sqlite, requireNodeSqlite } from "../../infra/node-sqlite.js";
+import { createLogger } from "../../utils/logger/index.js";
+import { init_logger } from "../../utils/logger.js";
 import { init_unhandled_rejections, installSqliteTransientRejectionHandler } from "../../infra/unhandled-rejections.js";
 import path from "node:path";
 import fs from "node:fs";

package/dist/src/storage/sqlite/device-access-repository.d.ts

@@ -46,7 +46,7 @@ export declare function buildRefreshProofMessage(input: {
     nonce: string;
     requestId: string;
     nextRefreshToken: string;
-    requestProofVersion?: number;
+    requestProofVersion: 1;
 }): string;
 export declare class DeviceRefreshRateLimitError extends Error {
     readonly retryAfterMs: number;
@@ -59,7 +59,7 @@ export declare function rotateDeviceRefreshToken(input: {
     requestId: string;
     nextRefreshToken: string;
     signature: string;
-    requestProofVersion?: number;
+    requestProofVersion: 1;
     now?: number;
 }): DeviceTokenPair;
 export declare function revokeDevice(deviceId: string, now?: number): boolean;