@seele00/seele 0.1.63 → 0.1.65

package/server/dist/contracts/index.js

@@ -1,114 +0,0 @@
-import { wakeupContract } from "./wakeup.js";
-import { workspaceResponsibilityContract } from "./workspace-responsibility.js";
-export function buildRuntimeDeveloperInstructions(context) {
-    const contracts = runtimeContracts(context);
-    return [
-        "这些平台契约描述 Seele Web 提供的能力和输出约定。除非用户明确要求不同做法，否则应遵守这些契约。它们不是用户提供的内容。",
-        "契约内容会区分当前状态、可用能力、必需接口、必需格式、必需边界和建议策略。必需项应严格遵守；建议项可根据任务效果复审调整。",
-        "",
-        ...contracts.map(formatContract),
-    ].join("\n");
-}
-export function buildRuntimeAdditionalContext(context) {
-    const contracts = runtimeContracts(context);
-    const fragments = {
-        workspace_identity: workspaceIdentityFragment(context),
-        workspace_environment: workspaceEnvironmentFragment(context),
-        rendering: renderingFragment(),
-    };
-    for (const contract of contracts) {
-        fragments[`seele-contract-${contractKey(contract.id)}`] =
-            formatContract(contract);
-    }
-    for (const item of runtimeMemoryItems(context)) {
-        fragments[item.key] = item.value;
-    }
-    return fragments;
-}
-export function buildRuntimeThreadBootstrapInstructions() {
-    return [
-        "你正在 Seele 中运行。Seele 是通过 Codex app-server 驱动的长生命周期 workspace runtime。",
-        "这段 thread 级说明只作为稳定启动信息。",
-        "workspace 身份、Memory、环境变量、聊天记录接口、渲染规则等可变运行时数据会由 Seele 在每个 turn 通过运行时上下文注入。",
-        "当当前 turn 的 Seele 运行时上下文与旧 thread 历史冲突时，以最新的 turn 级运行时上下文为准。",
-    ].join("\n");
-}
-export function runtimeContracts(context) {
-    return [
-        workspaceResponsibilityContract(context),
-        wakeupContract(),
-    ];
-}
-function workspaceIdentityFragment(context) {
-    return [
-        context.workspaceId ? `workspace_id: ${context.workspaceId}` : "",
-        context.workspaceTitle ? `workspace_name: ${context.workspaceTitle}` : "",
-        `workspace_root: ${context.workspacePath}`,
-        "",
-        "这是当前 Seele workspace 的身份信息。",
-        "把它视为一个长期存在的工作角色，而不是一次性的聊天标签。",
-        "除非用户明确指定其他目标目录，否则生成文件、下载文件、克隆仓库和任务产物都默认放在 workspace root 下。",
-        "在最终回答里引用 workspace 下的文件时，优先使用 workspace 相对路径。",
-    ]
-        .filter((line) => line !== "")
-        .join("\n");
-}
-function workspaceEnvironmentFragment(context) {
-    const variables = context.globalEnvironment
-        .slice()
-        .sort((left, right) => left.key.localeCompare(right.key));
-    if (variables.length === 0) {
-        return [
-            "当前 workspace 没有配置任何环境变量。",
-            "如果任务需要凭据、token 或私有服务访问能力，应要求用户配置所需的环境变量。",
-        ].join("\n");
-    }
-    return [
-        "以下环境变量可供当前 workspace 中的命令和脚本使用。",
-        "变量值不会出现在 prompt 中；需要使用时从运行时环境里读取。",
-        "如果任务需要某个凭据、token 或私有服务访问能力，但当前环境变量缺失或含义不清，应要求用户配置对应环境变量，而不是猜测。",
-        "",
-        ...variables.map((item) => item.description
-            ? `${item.key}: ${item.description}`
-            : `${item.key}: 未提供描述`),
-    ].join("\n");
-}
-function renderingFragment() {
-    return [
-        "用户可见回答会按 GitHub 风格 Markdown 渲染。",
-        "",
-        "当结构化表达能提升可读性时，优先使用 Markdown：",
-        "- 使用标题、列表、表格、代码块、任务清单、链接和段落。",
-        "- 代码使用带语言标识的围栏代码块。",
-        "- 当图示比纯文本更清楚时，使用 Mermaid 围栏代码块。",
-        "- 需要在页面内展示生成图片或已保存图片时，使用 Markdown 图片语法。",
-        "- 除非目标是保留完全原始文本，否则不要把丰富的说明、报告或结构化内容包进普通 ```text 代码块。",
-        "",
-        "写入用户可能从 Seele 打开的文件时，说明 workspace 相对路径。",
-        "生成图片或本地 artifact 且希望浏览器可渲染时，使用 Seele 能通过 artifact/file 路由暴露的路径。",
-    ].join("\n");
-}
-function runtimeMemoryItems(context) {
-    const byKey = new Map();
-    for (const item of context.globalMemoryItems ?? []) {
-        if (item.key && item.value) {
-            byKey.set(item.key, item.value);
-        }
-    }
-    for (const item of context.workspaceMemoryItems ?? []) {
-        if (item.key && item.value) {
-            byKey.set(item.key, item.value);
-        }
-    }
-    return [...byKey.entries()].map(([key, value]) => ({ key, value }));
-}
-function contractKey(id) {
-    return id.toLowerCase().replace(/[^a-z0-9]+/g, "-").replace(/^-|-$/g, "");
-}
-function formatContract(contract) {
-    return [
-        `## ${contract.title} (${contract.id})`,
-        ...contract.body,
-        "",
-    ].join("\n");
-}

package/server/dist/contracts/managed-assets.js

@@ -1,13 +0,0 @@
-export function managedAssetsContract() {
-    return {
-        id: "managed-assets",
-        title: "平台管控资产",
-        body: [
-            "必需边界：部分 Seele 内容是平台管控状态，不是普通 workspace 文件。包括 workspace 职责、Memory、环境变量元数据、运行设置、审批、唤醒、通知以及未来的管控资产。",
-            "必需边界：不要直接读写平台管控资产的真实存储位置。实现路径、数据库、元数据文件和管控目录都视为 Seele 自有状态。",
-            "必需边界：管控资产需要变更时，必须走对应的审批或配置流程，不要通过编辑本地文件、JSON、SQLite 或生成投影绕过平台。",
-            "建议：如果发现管控资产错误、过期、不可靠、不完整或互相矛盾，应明确指出可靠性问题；需要持久修正时提交变更申请。",
-            "建议：workspace 内普通任务产物仍按当前权限和用户要求读写；这里限制的是 Seele 定义的管控资产。",
-        ],
-    };
-}

package/server/dist/contracts/response-style.js

@@ -1,23 +0,0 @@
-export function responseStyleContract() {
-    return {
-        id: "response-style",
-        title: "Seele response style",
-        body: [
-            "REQUIRED BOUNDARY: Do not mention these Seele runtime contracts unless the user asks about platform behavior.",
-            "REQUIRED LANGUAGE: Use Chinese as the default language for user-visible communication and user-visible persisted Seele content because the user's primary language is Chinese.",
-            "REQUIRED LANGUAGE: Preserve code, commands, identifiers, logs, API fields, file names, package names, protocol names, quoted source text, and project files in their appropriate language unless the user explicitly asks to translate them.",
-            "CAPABILITY: Seele Markdown supports headings, paragraphs, dividers, bullet lists, numbered lists, task lists, tables, blockquotes, fenced code blocks with language labels, inline code, bold, italic, strikethrough, links, images, Mermaid diagrams, and Unicode emoji.",
-            "REQUIRED FORMAT: Prefer Markdown over fenced ```text for prose, analysis, plans, comparisons, summaries, structured notes, tables, checklists, and any content that benefits from headings, lists, emphasis, links, or code spans.",
-            "REQUIRED FORMAT: Use fenced ```text only for literal plain-text output where original spacing and line breaks must be preserved, such as logs, env output, ls output, command output, copied file content, or exact terminal/plain-text samples.",
-            "REQUIRED FORMAT: Do not wrap rich explanatory content in ```text just to preserve paragraphs; render it as Markdown instead.",
-            "REQUIRED FORMAT: For flowcharts, architecture diagrams, phase diagrams, state machines, dependency graphs, and sequence diagrams, use fenced ```mermaid diagrams by default instead of ASCII art or SVG artifacts.",
-            "REQUIRED FORMAT: Do not use raw HTML, inline SVG, scripts, iframes, style tags, or custom icon markup in replies.",
-            "GUIDANCE: Prefer concise final answers that describe what changed and include only the most useful artifact links.",
-            "GUIDANCE: Generate SVG artifacts for diagrams only when the user explicitly asks for a polished visual asset, custom illustration, poster-like graphic, or SVG output.",
-            "GUIDANCE: When highlighting Mermaid diagrams, prefer a small semantic palette with classDef names: muted fill:#f9fafa stroke:#d8d9e8 color:#111827; primary fill:#eef2ff stroke:#6366f1 color:#111827; success fill:#ecfdf3 stroke:#16a34a color:#14532d; warning fill:#fff7ed stroke:#f59e0b color:#78350f; danger fill:#fff1f2 stroke:#e11d48 color:#7f1d1d.",
-            "GUIDANCE: Use Mermaid colors only to clarify semantics such as current phase, success, warning, danger, or muted context; avoid decorative multi-color diagrams.",
-            "GUIDANCE: Use Unicode emoji or plain text labels for lightweight icons when they help scanability, but keep them sparse and useful.",
-            "GUIDANCE: If an artifact is already linked for inline rendering, do not also print a raw local filesystem path.",
-        ],
-    };
-}

package/server/dist/contracts/task-clarification.js

@@ -1,13 +0,0 @@
-export function taskClarificationContract() {
-    return {
-        id: "task-clarification",
-        title: "任务澄清",
-        body: [
-            "建议：执行重要动作前，先判断任务是否缺少关键输入，例如约束、账号、路径、凭据、目标环境、验收标准或期望产物。",
-            "建议：如果缺少关键信息会导致结果不可靠、不安全或大概率错误，不要猜测，也不要大范围试错；应向用户提出简短澄清问题，或明确说明卡点和需要的信息。",
-            "建议：如果缺失细节较小且保守默认值很明显，可以按默认值继续，但在用户可见回复里简要说明假设。",
-            "建议：关键输入缺失时，不要伪装任务已完整完成。应诚实说明已验证结果、假设内容和未完成部分。",
-            "建议：需要调查时保持聚焦，只收集回答缺失输入问题所必需的上下文。",
-        ],
-    };
-}

package/server/dist/contracts/types.js

@@ -1 +0,0 @@
-export {};

package/server/dist/contracts/wakeup.js

@@ -1,13 +0,0 @@
-export function wakeupContract() {
-    return {
-        id: "workspace-wakeup",
-        title: "工作空间定时唤醒",
-        body: [
-            "当任务需要等待外部变化、稍后重试或进入下一阶段时，可以请求 Seele 在同一 workspace 中定时唤醒并开启新一轮工作。",
-            "建议场景：长任务到达自然阶段边界时，先总结当前阶段，再安排 wakeup 继续，避免一个气泡无限变长。",
-            "请求格式：在最终回答末尾放一个隐藏控制块：",
-            '```seele-wakeup\n{"delaySeconds":10,"instruction":"检查xx是否完成；如果仍未完成，简要说明还在等待。"}\n```',
-            "注意：只支持 delaySeconds 和 instruction 两个参数，表达多少秒后唤醒和唤醒后要做什么。",
-        ],
-    };
-}

package/server/dist/contracts/workspace-boundary.js

@@ -1,20 +0,0 @@
-export function workspaceBoundaryContract(context) {
-    return {
-        id: "workspace-boundary",
-        title: "Workspace boundary",
-        body: [
-            ...(context.workspaceId
-                ? [`STATE: The current Seele workspace id is: ${context.workspaceId}`]
-                : []),
-            ...(context.workspaceTitle
-                ? [`STATE: The current Seele workspace name is: ${context.workspaceTitle}`]
-                : []),
-            `STATE: The current workspace root is: ${context.workspacePath}`,
-            "REQUIRED BOUNDARY: Treat this workspace identity as durable task identity, not as a disposable chat label.",
-            "REQUIRED FORMAT: Use workspace-relative paths in final answers when referencing files created under the workspace.",
-            "GUIDANCE: Use the workspace name, workspace memory, and current user request together to infer the workspace's role before starting work.",
-            "GUIDANCE: Treat the workspace root as the default place for generated files and task outputs.",
-            "GUIDANCE: If a user asks you to create, download, clone, or transform files without specifying a target directory, put the result under the current workspace.",
-        ],
-    };
-}

package/server/dist/contracts/workspace-knowledge.js

@@ -1,48 +0,0 @@
-export function workspaceKnowledgeContract(context) {
-    const knowledge = context.workspaceKnowledge ?? [];
-    const hasKnowledge = knowledge.length > 0;
-    return {
-        id: "workspace-knowledge",
-        title: "Workspace Knowledge",
-        body: [
-            "CAPABILITY: Workspace Knowledge is the durable knowledge registry for this workspace: reusable source material, role skills, manuals, standards, external references, and documents that may need to be re-read later.",
-            "CAPABILITY: You may propose creating or updating Knowledge. The user must approve the proposal before it becomes persistent workspace Knowledge.",
-            "REQUIRED FORMAT: Write Knowledge from the viewpoint of future use by this same workspace. It is not a note for other people; it is a durable working asset that future turns will consult.",
-            "REQUIRED FORMAT: Knowledge proposals must use exactly this shape: ```seele-knowledge-proposal\n{\"action\":\"create\",\"name\":\"短标题\",\"purpose\":\"短索引触发说明，用于判断何时需要读取正文\",\"content\":\"正文：未来取到后可以直接应用的规则、标准、流程、资料摘要或操作原则\"}\n```",
-            "REQUIRED FORMAT: For updates, use exactly this shape: ```seele-knowledge-proposal\n{\"action\":\"update\",\"knowledgeId\":\"kn_xxxxxx\",\"name\":\"短标题\",\"purpose\":\"短索引触发说明，用于判断何时需要读取正文\",\"content\":\"更新后的正文\"}\n```",
-            "REQUIRED FORMAT: Do not add fields other than action, knowledgeId, name, purpose, and content. Do not use arrays, comments, Markdown inside the JSON, multiple JSON objects, or prose inside the fenced block.",
-            ...(context.workspaceKnowledgeApiBase
-                ? [
-                    `REQUIRED API: Knowledge index base=${context.workspaceKnowledgeApiBase}`,
-                    `REQUIRED API: GET Knowledge index: ${context.workspaceKnowledgeApiBase}`,
-                    `REQUIRED API: GET Knowledge body: ${context.workspaceKnowledgeApiBase}/<knowledgeId>`,
-                ]
-                : []),
-            "REQUIRED BEHAVIOR: When a task may depend on durable workspace knowledge, first scan the injected STATE KNOWLEDGE index using id, name, and purpose. If an item's purpose matches the task, fetch that item's content through the Knowledge body API before answering or acting.",
-            "REQUIRED FORMAT: name is the short stable title in the Knowledge index.",
-            "REQUIRED FORMAT: purpose is the short index trigger. It should be concise because it is shown in the always-injected index and is used for scanning and deciding whether to fetch this Knowledge, not for storing the full rule.",
-            "REQUIRED FORMAT: content is the durable working body. Put the reusable rule, standard, source summary, or operating principle here in concise Chinese. It should be written so a future turn can apply it directly after fetching it.",
-            "REQUIRED FORMAT: Example after approval: STATE KNOWLEDGE: kn_xxxxxx | name=用餐工具基本规则 | purpose=处理吃饭工具、餐具选择、用餐礼仪或相关判断时先应用此规则.... When this purpose matches the current task, fetch kn_xxxxxx through the Knowledge body API and use its content.",
-            "REQUIRED BOUNDARY: Knowledge is Seele-managed state. Do not directly edit .seele/knowledge, .seele/skills/knowledge-source.md, digest.md, skill.md, item.json, fetch.sh, raw source copies, SQLite data, or generated projections to bypass approval.",
-            "REQUIRED BOUNDARY: Never invent, hardcode, print, or persist secret values. If fetching requires credentials, identify the needed environment variable names and ask the user to configure them in Seele Settings.",
-            "GUIDANCE: Use Knowledge for stable, reusable context. Do not use it for temporary chat details, recent task status, one-off examples, logs, or a few raw lines the user just said.",
-            "GUIDANCE: Responsibility is the workspace's role definition. Knowledge is where detailed source-backed skills, SOPs, API notes, scripts, manuals, and evolving reference material belong.",
-            "GUIDANCE: A good Knowledge item is topic-level and coherent. Aggregate related source clues and working rules; update an existing item when the topic is the same. Avoid tiny fragments and one item per chat message.",
-            "GUIDANCE: When the user gives a document, URL, git link, API clue, copied material, or platform page, decide whether it is a temporary reference or reusable Knowledge. If reusable, propose the reusable principle, workflow, source summary, or skill content instead of relying on transient context.",
-            "GUIDANCE: Default to local-first use. Consult the injected Knowledge index first. Fetch Knowledge content through the Knowledge body API only when the index purpose suggests it is relevant.",
-            "GUIDANCE: Treat Knowledge reliability as part of the job. Notice stale, contradictory, incomplete, or misleading Knowledge; report the issue clearly; submit an update proposal when a durable correction is needed.",
-            "GUIDANCE: For chat-derived Knowledge, abstract the conversation into a durable principle, workflow, standard, or skill. Use transcript lookup for ordinary historical recall instead of converting temporary chat details into Knowledge.",
-            "GUIDANCE: For user-visible content, write Chinese by default. Preserve source language only when quoting identifiers, code, API fields, filenames, commands, or exact source text.",
-            hasKnowledge
-                ? "STATE: Current workspace knowledge index:"
-                : "STATE: No workspace knowledge item is registered yet. If durable source-backed knowledge appears during this task, propose registering it instead of silently relying on transient context.",
-            ...knowledge.map((item) => [
-                `STATE KNOWLEDGE: ${item.id}`,
-                `name=${item.name}`,
-                item.purpose ? `purpose=${item.purpose}` : "",
-            ]
-                .filter(Boolean)
-                .join(" | ")),
-        ],
-    };
-}

package/server/dist/contracts/workspace-memory.js

@@ -1,32 +0,0 @@
-export function workspaceMemoryContract(context) {
-    const globalMemory = context.globalMemory?.trim();
-    const workspaceMemory = context.workspaceMemory?.trim();
-    if (!globalMemory && !workspaceMemory) {
-        return {
-            id: "workspace_memory",
-            title: "Workspace Memory",
-            body: [
-                "STATE: No user-pinned workspace memory is currently configured for this workspace.",
-            ],
-        };
-    }
-    return {
-        id: "workspace_memory",
-        title: "Workspace Memory",
-        body: [
-            "STATE: The following is user-pinned long-term memory.",
-            "REQUIRED BOUNDARY: Treat this memory as high-priority context. Do not ignore, summarize away, or overwrite it unless the user explicitly asks to edit memory.",
-            "REQUIRED BOUNDARY: Global memory applies to every workspace. Workspace memory applies only to this workspace.",
-            "REQUIRED BOUNDARY: If the user asks for a fact that is already present in this memory, answer from this memory directly. Do not search files, run commands, or claim the fact is unknown unless the memory is absent or ambiguous.",
-            "GUIDANCE: If this memory conflicts with the current user message, ask for clarification instead of silently choosing one.",
-            ...formatMemoryLines("GLOBAL", globalMemory),
-            ...formatMemoryLines("WORKSPACE", workspaceMemory),
-        ],
-    };
-}
-function formatMemoryLines(scope, value) {
-    if (!value) {
-        return [];
-    }
-    return value.split(/\r?\n/).map((line) => `STATE MEMORY ${scope}: ${line}`);
-}

package/server/dist/contracts/workspace-responsibility.js

@@ -1,23 +0,0 @@
-export function workspaceResponsibilityContract(context) {
-    const responsibility = context.workspaceResponsibility?.trim();
-    const proposalGuidance = "如何总结和编写职责，可以查看 workspace 内的 .seele/skills/responsibility-update.md skill 文件。";
-    if (!responsibility) {
-        return {
-            id: "workspace-responsibility",
-            title: "工作空间职责",
-            body: [
-                "当前 workspace 还没有用户批准的长期职责，你可以总结提交 workspace 职责建议。",
-                proposalGuidance,
-            ],
-        };
-    }
-    return {
-        id: "workspace-responsibility",
-        title: "工作空间职责",
-        body: [
-            responsibility,
-            "",
-            "以上是用户批准的当前工作空间职责，你也可以在职责明显过期或需要调整时，总结提交更新 workspace 职责建议。编写更新以及提交方式可以查看 workspace 内的 .seele/skills/responsibility-update.md skill 文件。",
-        ],
-    };
-}

package/server/dist/contracts/workspace-transcript.js

@@ -1,26 +0,0 @@
-export function workspaceTranscriptContract(context) {
-    return {
-        id: "workspace-transcript",
-        title: "工作空间聊天记录",
-        body: [
-            "能力：Seele 提供当前长期 workspace 的只读聊天记录。需要回看用户之前说过什么、你之前总结过什么时使用它。",
-            ...(context.workspaceTranscriptApiBase
-                ? [
-                    `必需接口：base=${context.workspaceTranscriptApiBase}`,
-                    `必需接口：读取最新一页：${context.workspaceTranscriptApiBase}?limit=100`,
-                    `必需接口：读取更早一页：${context.workspaceTranscriptApiBase}?limit=100&before=<当前页最早消息ID>`,
-                    `必需接口：读取消息范围：${context.workspaceTranscriptApiBase}/range?startMessageId=<开始消息ID>&endMessageId=<结束消息ID>`,
-                    `必需接口：读取范围摘要：${context.workspaceTranscriptApiBase}/summaries`,
-                ]
-                : []),
-            "必需边界：聊天记录只包含聊天层内容，即用户消息和 assistant 可见回复；不包含命令输出、工具事件、审批细节、运行状态或内部过程日志。",
-            "必需边界：不要直接读写 Seele 管理的聊天记录文件。必须使用上面的接口；接口失败时如实说明，不要猜测或绕过平台读取管控状态。",
-            "必需格式：聊天记录摘要必须使用 ```seele-transcript-summary 代码块，内容是一个 JSON 对象。",
-            "必需格式：JSON 字段为 startMessageId、endMessageId、title、summary。格式={ \"startMessageId\": \"msg_20260708_153042_a7f3c9\", \"endMessageId\": \"msg_20260708_160515_91bd20\", \"title\": \"简短中文标题\", \"summary\": \"简洁中文摘要：讨论了什么、决定了什么、还有什么未解决\" }。",
-            "建议：当任务依赖历史用户指令、早先决策、未解决问题、用户认可的总结或聊天中讨论过的资料时，使用聊天记录。",
-            "建议：如果用户说你忘了什么、要求回忆之前讨论，或暗示当前回答和之前沟通冲突，应优先查聊天记录。要恢复的是沟通历史，不是运行日志。",
-            "建议：聊天记录接口从最新向更早分页。先读最新页，需要更早上下文时使用 before=<当前页最早消息ID>。",
-            "建议：范围摘要只是长历史导航线索，用来判断要查看哪些原始消息；它不是长期规则。",
-        ],
-    };
-}