@zq-silk/yui 2.2.0 → 2.4.0

package/dist/web/webTaskSurface.js

@@ -1,14 +1,17 @@
-import { readArtifactCapability } from "../artifacts/artifactCapability.js";
 import { openTaskArtifactRepository } from "../artifacts/taskArtifactRepository.js";
+import { compareTextArtifacts, readArtifactPreview } from "./webMaterials.js";
+import { readTaskSearchSource } from "../context/taskSearch.js";
 import { applyGlobalInputControl } from "../commands/globalRoleCommands.js";
-import { applyTaskInputControl, sendTaskMessageCommand, updateTaskMetadataCommand } from "../commands/taskCommands.js";
+import { applyTaskInputControl, runTaskCommand, sendTaskMessageCommand, updateTaskMetadataCommand } from "../commands/taskCommands.js";
+import { runTaskActivationCommand } from "../commands/taskActivationCommands.js";
 import { runTaskInputCommand } from "../commands/taskInputCommands.js";
-import { inspectTaskContext, readTaskContext, readTaskContextDelta, withContextObservations } from "../context/taskContext.js";
+import { inspectTaskContext, listTaskContext, readTaskContext, readTaskContextDelta, withContextObservations } from "../context/taskContext.js";
 import { BUILTIN_CAPABILITIES } from "../kernel/builtinCapabilities.js";
 import { capabilitySchemaError } from "../kernel/capabilitySchema.js";
 import { recordGlobalInterruptResult, recordGlobalSteerResult } from "../message/globalInterrupt.js";
 import { recordTaskInterruptResult } from "../message/taskInterrupt.js";
 import { AGENT_HOST_CONTROL_PROTOCOL, foldInterruptLiveReceipt, foldSteerLiveReceipt, sendAgentHostCancelControl, sendAgentHostSteerControl } from "../runtime/agentHost.js";
+import { validateOrdinaryTaskArchive } from "../task/ordinaryArchive.js";
 import { webLocalMutation, WebRequestRejected } from "./webMutation.js";
 const DEFAULT_WEB_HOST_CONTROL = {
     steer: sendAgentHostSteerControl,
@@ -29,7 +32,7 @@ function controlTarget(taskId, input) {
  * its token before using this port; input never supplies a caller or Role.
  * Managed capability RPC keeps its own Session authentication unchanged.
  */
-export function createWebTaskSurface(store, options = {}, observations = [], hostControl = DEFAULT_WEB_HOST_CONTROL) {
+export function createWebTaskSurface(store, options = {}, observations = [], hostControl = DEFAULT_WEB_HOST_CONTROL, lifecycle) {
     const environment = {};
     const commandOptions = { ...options, environment, runtime: undefined };
     // Notifications are after the outer transaction. Their failure must not be
@@ -39,26 +42,120 @@ export function createWebTaskSurface(store, options = {}, observations = [], hos
             ? { kind: "role", taskId, roleName: "leader" } : { kind: "task", taskId });
     };
     return {
+        workbench: (taskId) => store.transaction(tx => {
+            const task = tx.getTask(taskId);
+            if (!task)
+                throw new WebRequestRejected("Task not found.");
+            const brief = tx.getTaskBrief(taskId);
+            const clip = (value) => value === undefined ? undefined
+                : value.length > 1200 ? value.slice(0, 1200) + "…" : value;
+            return {
+                core: readTaskContext(tx, taskId, environment),
+                task: {
+                    id: task.id, title: clip(task.title), status: task.status, updatedAt: task.updatedAt,
+                    executionGate: task.executionGate, priority: task.priority, tags: task.tags?.slice(0, 16).map(value => clip(value)),
+                    projectBindings: task.projectBindings.slice(0, 32),
+                    description: clip(task.description), completionSummary: clip(task.completionSummary),
+                    retirementSummary: clip(task.retirementSummary), archiveSummary: clip(task.archiveSummary),
+                    archiveReason: clip(task.archiveReason),
+                    activationRequest: task.activationRequest && {
+                        disposition: task.activationRequest.disposition,
+                        outcome: clip(task.activationRequest.outcome),
+                        operation: { requestId: task.activationRequest.operation.requestId }
+                    }
+                },
+                evidence: {
+                    reviews: tx.listReviewRounds(taskId).sort((a, b) => b.createdAt.localeCompare(a.createdAt)).slice(0, 3)
+                        .map(round => ({
+                        id: round.id, status: round.status, runId: round.reviewerRunId,
+                        excerpt: round.reviewerRunId ? clip(tx.getRun(taskId, round.reviewerRunId)?.result?.output) : undefined
+                    })),
+                    integrations: tx.listIntegrationAttempts(taskId).sort((a, b) => b.createdAt.localeCompare(a.createdAt)).slice(0, 3)
+                        .map(attempt => ({
+                        id: attempt.id, status: attempt.status, summary: clip(attempt.summary),
+                        checks: attempt.checks?.slice(0, 8).map(check => ({ name: clip(check.name), outcome: check.outcome }))
+                    }))
+                },
+                brief: brief && {
+                    objective: clip(brief.objective), currentFocus: clip(brief.currentFocus),
+                    leaderSummary: clip(brief.leaderSummary), technicalApproach: clip(brief.technicalApproach),
+                    boundaries: brief.boundaries?.slice(0, 8).map(value => clip(value)),
+                    updatedAt: brief.updatedAt
+                }
+            };
+        }),
+        projects: (after) => {
+            const projects = store.listProjects().filter(project => project.status === "active")
+                .sort((a, b) => a.id.localeCompare(b.id));
+            const remaining = projects.filter(project => after === undefined || project.id.localeCompare(after) > 0);
+            const page = remaining.slice(0, 40);
+            return { projects: page.map(({ id, name }) => ({ id, name: name.slice(0, 200) })),
+                total: projects.length, nextCursor: remaining.length > page.length ? page.at(-1).id : null };
+        },
+        create: (input) => {
+            const result = webLocalMutation(store, tx => {
+                // A lost response must be reconciled, never create another Task.
+                if (tx.listTasks().some(task => tx.listMessages(task.id)
+                    .some(message => message.submissionKey === input.requestId))) {
+                    throw new Error("This creation request was already saved; inspect the Task catalog before continuing.");
+                }
+                const created = runTaskCommand(["create", input.title,
+                    ...input.projectIds.flatMap(id => ["--project", id])], tx, commandOptions);
+                if (created.kind !== "output")
+                    throw new Error("Unexpected Task creation result.");
+                const taskId = created.data.task.id;
+                updateTaskMetadataCommand(tx, taskId, { description: input.requirements }, commandOptions);
+                const submitted = sendTaskMessageCommand(tx, taskId, input.requirements, commandOptions, undefined, input.plan ? "discuss" : "record", input.requestId);
+                return { task: submitted.task, submission: submitted.feedback, messageId: submitted.message.id };
+            });
+            notify(result.task.id, input.plan);
+            return result;
+        },
+        activate: (taskId, requestId) => {
+            const result = webLocalMutation(store, tx => runTaskActivationCommand([
+                "request", taskId, "--request-id", requestId, "--environment", "empty"
+            ], tx, commandOptions));
+            notify(taskId);
+            return result.kind === "output" ? result.data : result;
+        },
+        archive: async (taskId) => {
+            if (!lifecycle)
+                throw new WebRequestRejected("Ordinary archive is unavailable.");
+            // Preflight rejection precedes any physical effects; later errors remain
+            // unknown and must be reconciled from the Task and archive diagnostics.
+            webLocalMutation(store, tx => validateOrdinaryTaskArchive(tx, taskId, commandOptions));
+            return lifecycle.archive(taskId);
+        },
         evidence: (taskId) => store.transaction(reader => {
             if (reader.getTask(taskId) === null)
                 throw new WebRequestRejected("Task not found.");
             return { taskId, integrations: reader.listIntegrationAttempts(taskId),
                 reviews: reader.listReviewRounds(taskId), workspaces: reader.listManagedWorkspaces(taskId) };
         }),
-        artifacts: async (taskId) => {
+        artifacts: async (taskId, selectedCommit, offset = 0) => {
             if (store.getTask(taskId) === null)
                 throw new WebRequestRejected("Task not found.");
             const repo = openTaskArtifactRepository(store.rootDirectory(), taskId);
-            const commit = await repo.head();
+            if (selectedCommit !== undefined && !repo.exists())
+                throw new WebRequestRejected("Artifact revision unavailable.");
+            const commit = selectedCommit ?? await repo.head();
             const entries = commit === null ? [] : await repo.list(commit);
-            return { taskId, commit, entries };
+            if (!Number.isSafeInteger(offset) || offset < 0 || offset > entries.length)
+                throw new WebRequestRejected("Invalid artifact offset.");
+            return { taskId, commit, entries: entries.slice(offset, offset + 40), total: entries.length,
+                nextOffset: offset + 40 < entries.length ? offset + 40 : null };
         },
-        artifact: async (taskId, relativePath, commit) => {
+        artifact: async (taskId, relativePath, commit, offset = 0) => {
             if (store.getTask(taskId) === null)
                 throw new WebRequestRejected("Task not found.");
             // The browser always names a fixed revision. Never substitute HEAD after
             // a missing object, and never execute/render artifact HTML as an app.
-            return readArtifactCapability(store.rootDirectory(), taskId, { relativePath, commit });
+            return readArtifactPreview(store.rootDirectory(), taskId, { taskId, relativePath, commit }, offset);
+        },
+        artifactDiff: async (taskId, relativePath, commit, beforeCommit, offset = 0) => {
+            if (store.getTask(taskId) === null)
+                throw new WebRequestRejected("Task not found.");
+            return compareTextArtifacts(store.rootDirectory(), taskId, { taskId, relativePath, commit: beforeCommit }, { taskId, relativePath, commit }, offset);
         },
         globalState: (roleName) => {
             const role = store.getGlobalRole(roleName);
@@ -247,7 +344,15 @@ export function createWebTaskSurface(store, options = {}, observations = [], hos
         },
         read: async (taskId) => withContextObservations(readTaskContext(store, taskId, environment), observations),
         delta: (taskId, input) => readTaskContextDelta(store, taskId, input, environment),
+        searchSource: (taskId, input) => readTaskSearchSource(store, taskId, input, environment),
         inspect: (taskId, input) => inspectTaskContext(store, taskId, input, environment),
+        // The same paged family discovery as `task context list`: summaries and
+        // exact references, never bodies; continuations keep their filters.
+        list: (taskId, input) => listTaskContext(store, taskId, input.store, {
+            ...(input.status === undefined ? {} : { status: input.status }),
+            ...(input.cursor === undefined ? {} : { cursor: input.cursor }),
+            ...(input.limit === undefined ? {} : { limit: input.limit })
+        }, environment),
         update: (taskId, input) => {
             const descriptor = BUILTIN_CAPABILITIES.find((entry) => entry.name === "task.update");
             const error = capabilitySchemaError(descriptor.inputSchema, { taskId, patch: input });

package/dist/workspace/gitChangeSetCapture.js

@@ -1,5 +1,6 @@
 import { execFile } from "node:child_process";
 import { promisify } from "node:util";
+import { supportedGit } from "../repository/gitCompatibility.js";
 const executeFile = promisify(execFile);
 export async function captureManagedGitChanges(input) {
     await assertManagedHead(input);
@@ -61,8 +62,9 @@ async function assertManagedHead(input) {
     return headCommit;
 }
 async function git(args) {
+    const program = supportedGit();
     try {
-        const result = await executeFile("git", [...args], {
+        const result = await executeFile(program.path, [...args], {
             encoding: "utf8",
             maxBuffer: 16 * 1024 * 1024,
             timeout: 120_000

package/docs/managed-turn-and-session-runtime.md

@@ -276,6 +276,15 @@ Queue/steer require `--request-id`; steer/interrupt require `--expected-target`.
 These commands retain the caller's existing Session authority; do not fabricate
 a Task/Run or borrow the browser's user authority. Configuration remains under
 `config role`, lifecycle under `session`. New controlled Global Sessions use the Host console.
+The current controlled Codex Operator and Task Leader can also open a native
+TUI view from Web Terminal. Its authenticated loopback relay attaches to the
+Host's existing App Server connection and exact Thread. Complete text prompts,
+steer and interrupt reuse Host admission and settlement; native server requests
+retain their original request/Thread/Turn identity. Configuration overrides and
+new/forked Threads are rejected. Web uses the existing terminal writer lease;
+other browser windows remain read-only until the writer detaches. Closing this
+view does not stop the Host or Provider. Conversation and native history remain
+views of the same Provider facts, not a second Task message store.
 A live unmanaged Session is not silently adopted; an explicit Session lifecycle
 action is needed first.
 

package/docs/managed-turn-and-session-runtime.zh-CN.md

@@ -223,6 +223,13 @@ queue/steer 要求 `--request-id`，steer/interrupt 要求 `--expected-target`
 配置仍使用 `config role`，生命周期使用 `session`。新的受控 Global Session 使用 Host console。活动的非受管 Session
 不会被静默采用，需要先执行显式的 Session 生命周期操作。
 
+当前受控 Codex Operator 与 Task Leader 也可从 Web Terminal 打开原生 TUI 视图。
+经过认证的本地 relay 连接 Host 现有 App Server 连接中的精确 Thread；完整文本、
+steer 和 interrupt 复用 Host 准入与回执，原生问题/审批保留原 request/Thread/Turn
+身份。配置覆盖和新建/派生 Thread 被拒绝。Web 复用已有终端 writer lease，
+其他窗口在 writer 脱离前保持只读。关闭视图不会停止 Host 或 Provider。会话与
+原生历史仍来自同一 Provider 事实，不建立另一份 Task 消息存储。
+
 ## 精确结果
 
 原生终态只结算相匹配的那次执行。已知的原生 Turn ID 必须匹配；串行流可以使用已证明的

package/docs/observability/README.md

@@ -58,8 +58,16 @@ Session with settled native input is idle rather than a false runtime failure.
 
 ## Web attention and progress
 
-Task detail prioritizes **needs your input**, **Session activity**, **Task progress**
-and **key conclusions**. InputRequests retain their original answer controls and
+Task detail has four tabs. **Overview** shows needs your input, Task progress,
+goal and key Decisions. **Delivery** shows WorkItems, Reviews, Integration and
+remote delivery, files and workspaces; its evidence is read when the tab opens.
+**Runtime** shows Roles with their Session activity, open execution and
+operations, usage and diagnostics. **Records** is a paged timeline of Decisions,
+milestones, executions and questions plus Task facts; finished rows read their
+exact record when opened. Messages live in the Discussion dock, oldest first,
+with earlier ones listed on request.
+
+InputRequests retain their original answer controls and
 bounded Context counts; a partial read is not an empty inbox. Technical attention
 names the owner from the existing execution projection. An assigned owner does
 not imply work started, and a diagnostic hint is not new user authorization.
@@ -81,7 +89,7 @@ Current Decisions show their rationale/source; superseded ones remain in history
 Reports and recommendations are not relabelled as user approval. Core Context
 remains readable when its independent observation fails.
 
-**Results and evidence** reads files only on request. A selected commit-pinned
+**Delivery** reads files only on request. A selected commit-pinned
 text survives refresh and newer file listings; switching versions is explicit.
 A missing revision fails visibly, never substitutes HEAD. HTML/scripts stay
 text, never an executing preview. Copying a source sends nothing; discussion
@@ -100,6 +108,8 @@ All routes use the local Web token and Task boundary.
 `GET /api/tasks/<id>/artifacts` lists a fixed repository revision;
 `?path=<relative-path>&commit=<full-commit>` reads its exact text file.
 `GET /api/tasks/<id>/evidence` reads original check/Review/workspace records.
+`GET /api/tasks/<id>/list?store=<family>[&status&cursor&limit]` returns the same
+paged summaries as `task context list`.
 These reads do not start a runtime, fetch a remote, write business state, require
 a migration, or introduce a new persistent protocol.
 

package/docs/observability/README.zh-CN.md

@@ -51,7 +51,12 @@ AgentRun，Role 状态也包含其原生准入/活动；当某个 WorkItem 处
 
 ## Web 用户关注与进展
 
-Task 详情优先展示「需要你处理」「会话活动」「任务进展」「关键结论」。
+Task 详情分为四个页签。「概览」展示需要你处理的事项、任务进展、目标和关键决定；
+「交付」展示工作项、评审、集成与远程交付、文件和工作区，打开页签时才读取证据；
+「运行」展示各 Role 及其会话活动、进行中的执行与操作、用量和诊断；
+「记录」是决定、里程碑、执行与问题的分页时间线及任务信息，已结束的条目展开时
+才读取精确记录。消息在讨论侧栏中按时间正序显示，更早的消息按需列出。
+
 InputRequest 保留原回答入口和有界 Context 计数；部分读取不等于空待办。
 技术关注从既有执行投影取得负责人；有负责人不代表已开始处理，诊断提示
 也不自动成为新的用户授权。
@@ -68,7 +73,7 @@ Controller 已负责的有界 Provider 重试显示为等待，不误称停止
 ETA 或实质检查点。当前 Decision 展示理由与来源，已替代决定留在历史；
 报告与建议不改称用户批准。独立观察失败时，核心 Context 仍可读取。
 
-「成果与证据」仅按需读文件。固定提交的文本阅读在刷新和读取新列表后仍保留，
+「交付」仅按需读文件。固定提交的文本阅读在刷新和读取新列表后仍保留，
 切换版本必须显式选择；固定版本缺失就报错，不回退 HEAD。
 HTML／脚本只作为文本，不执行预览。复制来源不发送内容，讨论仍走原 Message
 表单、显式意图及回执；自动刷新保留未提交输入。
@@ -83,7 +88,9 @@ skipped／缺失检查不算通过。工作区所有权不证明可清理；既
 所有入口沿用本地 Web token 与 Task 边界。
 `GET /api/tasks/<id>/artifacts` 列出固定仓库版本；
 `?path=<relative-path>&commit=<full-commit>` 读取该版本文本；
-`GET /api/tasks/<id>/evidence` 读取原检查／Review／工作区记录。
+`GET /api/tasks/<id>/evidence` 读取原检查／Review／工作区记录；
+`GET /api/tasks/<id>/list?store=<family>[&status&cursor&limit]` 返回与
+`task context list` 相同的分页摘要。
 读取不启动运行时、不访问远端、不写业务状态、不引入迁移或新持久协议。
 
 ## 执行审计

package/docs/release-workflow.md

@@ -51,6 +51,59 @@ merely to avoid a version decision. Package versions remain distinct from protoc
 and persistent-storage contracts: their compatibility checks and required migrations
 are unchanged, and the storage rules below do not authorize a package release.
 
+### 2.4.0 compatibility and migration notes
+
+This minor ships the unified Web Task/Operator conversations and same-thread
+Codex terminal access, Task workbench, settings, text materials, pinned
+Markdown/image previews, bounded search and exact selection references,
+Task-owned HTTP previews, current-Session model/Slash controls, Skill browsing
+and explicit bindings. Knowledge applicability, complete frozen Skill packages,
+and sourced usage/cost evidence are included. Git 2.29+ compatibility and the
+Task109 model-validation, terminal-reader isolation and unknown-send recovery
+fixes are included; Task110's unmerged work is not part of this release.
+
+Storage is now **1.6**. Use the supported centralized, contiguous same-major
+upgrade path for older supported Homes; do not edit stored records manually.
+Historical missing cost remains unknown. Old Skill provenance is not rebuilt
+from today's files: if restoring an old Session reports missing frozen-package
+evidence, follow its new-Session guidance while preserving the old history.
+Current model adoption is connection-local and does not change future defaults;
+exit the Host-owned native TUI before changing its model (closing a viewer only
+detaches it). Unknown sends must be inspected by their original request ID,
+not replayed from a fresh tab. These are explicit behavioral boundaries, not
+a general backward-compatibility promise.
+
+The [Task109 report](testing/web-coverage-final.md) records Linux browser and
+real-model evidence with its original platform and sandbox limitations.
+Official CI/package smoke is separate evidence, not macOS browser/live-model
+coverage. Real-model checks remain opt-in. Publishing this package does not
+upgrade the global CLI, migrate a user's Home or restart their Controller.
+
+### 2.3.0 compatibility and migration notes
+
+This minor release separates Task acceptance and verified remote delivery from
+immutable Integration history and temporary workspace cleanup. Integration
+history remains readable after its workspace is released.
+
+Automation that previously treated leftover workspaces as an unconditional
+archive blocker must now inspect business settlement, exact delivery and runtime
+quiescence separately from physical cleanup. Ordinary archive releases safe
+resources child-first and retains dirty, unknown or live resources with their
+ownership and diagnostics. `--force` is separate explicit authority; it neither
+proves delivery or quiescence nor permits discarding retained data.
+
+For an ordinary Integration conflict, resolve and stage files in that attempt's
+workspace, then run `yui task integration continue <task>/<integration>`.
+Do not create a replacement attempt or require a manual-resolution decision
+just for a normal Git conflict. Cleanup uses exact ownership and Git
+registrations; missing paths alone do not establish that cleanup is complete.
+
+These are behavioral changes under Yui's minor-version convention. There is no
+new persistent schema or storage migration in 2.3.0. Existing Task and
+Integration evidence is preserved. This package release does not itself
+install the global CLI, activate a runtime or restart a Controller. Users
+upgrading from 2.1.0 must also apply the 2.2.0 API guidance below.
+
 ### 2.2.0 compatibility and migration notes
 
 This minor release adds the independent `yui agent` entry, explicit model/tool

package/docs/release-workflow.zh-CN.md

@@ -36,6 +36,46 @@ Agent 选择一个预先声明的计划，设施从持久状态驱动该计划
 不能将不兼容冒称为兼容，也不为回避版本选择新增历史兼容机制。包版本与协议、
 持久存储契约仍然独立：兼容性检查和必要迁移要求不变，下文存储规则不授予发版权限。
 
+### 2.4.0 兼容性及迁移说明
+
+本 minor 发布统一 Web Task／Operator 对话及同 Thread Codex 终端、任务工作台、
+设置、文本材料、固定版本 Markdown／图片预览、有界检索与精确选区引用、
+Task-owned HTTP 预览、当前 Session 模型／Slash 操作，以及 Skill 浏览和显式绑定。
+同时包含 Knowledge 适用范围、完整冻结 Skill 包、具来源的用量／费用证据、
+Git 2.29+ 支持，以及 Task109 的模型校验、终端读者隔离和未知发送恢复修复。
+Task110 尚未合入的工作不属于本版本。
+
+存储版本现为 **1.6**。旧的受支持 Home 应走集中、连续的同主版本升级路径，
+不要手工修改存储记录。历史缺失费用仍为未知；旧 Skill 来源不会从今天的文件
+补造。恢复旧 Session 若提示缺少冻结包证据，应保留旧历史并按提示建立新 Session。
+当前模型操作只作用于本次连接，不修改未来默认值；切换模型前须退出 Host 持有的
+原生 TUI，关闭浏览器查看器仅断开查看。未知发送必须查询原 request-id，
+不能通过新标签页重放。这些是明确的行为边界，不是一般向后兼容承诺。
+
+[Task109 报告](testing/web-coverage-final.md) 保留 Linux 浏览器和真实模型证据，
+以及原平台／沙箱限制。正式 CI／安装包冒烟是独立证据，不代表 macOS 浏览器或
+真实模型覆盖。真实模型测试保持 opt-in。发布本包不会升级全局 CLI、迁移用户
+Home 或重启其 Controller。
+
+### 2.3.0 兼容性及迁移说明
+
+本次 minor 将 Task 验收与已核验的远端交付、不可变 Integration 历史、
+临时工作区清理分开。释放工作区后，Integration 历史仍可读取。
+
+此前把残留工作区一律视为归档阻塞的自动化，现在应分别检查业务结算、
+精确交付与运行时静默，以及物理清理结果。普通归档按子资源优先释放安全资源，
+保留脏、未知或仍存活的资源及其所有权、诊断。`--force` 需要单独明确授权；
+它不证明交付或静默，也不允许丢弃被保留的数据。
+
+普通 Integration 冲突应在原 attempt 的工作区解决并 stage，然后执行
+`yui task integration continue <task>/<integration>`。不要仅因普通 Git 冲突
+另建 attempt 或要求 manual-resolution 决策。清理依赖精确所有权与 Git 登记；
+路径缺失本身不代表清理完成。
+
+这些是 Yui minor 编号约定下的行为变化。2.3.0 没有新的持久 schema 或存储迁移，
+保留现有 Task 与 Integration 证据。发布包本身不会安装全局 CLI、激活运行时
+或重启 Controller。从 2.1.0 升级的用户还需遵循下文 2.2.0 API 指引。
+
 ### 2.2.0 兼容性及迁移说明
 
 本 minor 增加独立 `yui agent` 入口、显式模型／工具配置、持久本地会话、上下文压缩、

package/docs/storage-baseline.md

@@ -2,11 +2,48 @@
 
 # Storage baseline 1.0
 
-Current storage is 1.2. The declared 1.1 → 1.2 transition adds optional
+Current storage is 1.6. The declared 1.5 → 1.6 transition adds optional
+source-attributed monetary evidence to canonical runtime observations. Existing
+observations remain unchanged: absent amounts and prices stay unknown. The SQL
+layout is unchanged.
+
+The declared 1.3 → 1.4 transition gives Project
+Knowledge applicability and exact version history, and updates proposal
+fingerprints to include applicability and replacement intent. It restores
+`scope`/`expiresWhen` only from an exact matching accepted proposal. Migrated
+knowledge starts at version 1 of the observed head; older proposals remain
+available, but missing historical edits are not invented. Frozen Context
+snapshots and their digests are unchanged. The SQL layout is unchanged.
+
+The declared 1.2 → 1.3 transition adds optional exact Session fences to
+structured inputs and permits their explicit nondelivery reason without an
+Assignment. Existing Role-addressed inputs remain unchanged.
+
+The declared 1.1 → 1.2 transition adds optional
 CapabilityGrant authorization-source evidence and native-human input/archive
 audit records. Existing valid Operator grants remain unchanged; migration does
 not infer or invent past user authority. The SQL layout is unchanged.
 
+The 1.4 → 1.5 transition introduces complete Skill package references in
+effective launch snapshots and Session Manifests. Historical records and their
+digests are preserved byte-for-byte; missing package metadata explicitly means
+legacy entrypoint-only/unrecorded evidence. Migration cannot recover resources
+that were never captured. Existing running Hosts keep their original inputs;
+restoring a legacy Session requires explicitly selecting a new Session. No
+ordinary reader backfills historical versions from mutable sources.
+
+New launches snapshot raw resources under `runtime/skill-packages/<digest>`.
+The version covers sorted relative paths, SHA-256 byte digests, sizes and
+executable flags. Builtin Skills share a complete sibling tree to preserve
+cross-Role references; configured Skills are bounded to their own directory.
+Symlinks and special files are rejected, as are packages exceeding 2,048 files,
+8 MiB per file, 32 MiB total or 32 directory levels. Scripts are retained,
+never run on import. Sources must be readable and physically rooted.
+Sessions and AgentRuns retain the compact source/version/inventory pointers;
+file bodies stay in the package. Changing a source affects a new Session only.
+Lost or corrupted packages fail closed rather than being rebuilt from current
+sources.
+
 Yui 1.0.0 starts from one clean persistent contract. The package version,
 storage schema, record envelopes and Controller protocol are separate
 identities; none is inferred from another.

package/docs/storage-baseline.zh-CN.md

@@ -2,6 +2,28 @@
 
 # 存储基线 1.0
 
+当前存储为 1.5。已声明的 1.3 → 1.4 迁移为正式项目知识增加适用信息和精确版本历史，
+并将提案指纹扩展到适用范围、失效条件及替代意图。仅从精确匹配的已接受提案恢复
+`scope`/`expiresWhen`；存量知识以已观察到的当前内容建立版本 1，不臆造缺失的修改历史。
+已有提案的身份、审批和来源保留，冻结的 Context 快照及摘要不改写。物理 SQL 结构不变。
+
+既有 1.2 → 1.3 迁移为结构化输入增加可选的精确 Session 限定和无 Assignment
+时的明确未投递原因；既有按 Role 寻址的输入保持原样，不推断历史 Session 选择。
+
+1.4 → 1.5 在现有 effective launch 和 Session
+Manifest 中新增完整 Skill 包引用，不改 SQL 布局。历史记录与摘要原样保留；
+缺少包元数据明确表示旧版只记录入口正文或没有装载证据，不能拿当前源目录
+补造历史版本。运行中的旧 Host 保留原输入；恢复缺少包快照的旧 Session 时
+会给出需要显式创建新 Session 的诊断，不在普通读取中迁移或回填。
+
+新 Session 将资源保存到 `runtime/skill-packages/<digest>`，摘要覆盖排序后的
+相对路径、原始文件字节摘要、大小与可执行标志。内置 Skills 共享完整兄弟目录，
+保留跨 Role 相对引用；自定义 Skill 限于其自身目录。拒绝符号链接、特殊文件，
+以及超过 2,048 个文件、单文件 8 MiB、总计 32 MiB 或 32 层目录的包。
+脚本只保存，不因装载而执行。Session、AgentRun、CLI 和 Web 复用精简来源、
+版本与资源清单引用，不复制大文件正文。源更新只影响新 Session；快照丢失或
+损坏明确报错，不从当前源目录重建。
+
 Yui 1.0.0 从唯一、纯净的持久化契约开始。软件包版本、存储结构、记录封装和
 Controller 协议是相互独立的身份，不能从其中一个推断另一个。
 

package/docs/task-delivery.md

@@ -305,17 +305,21 @@ yui task archive <task> (--integrated|--abandon) --force
 
 ### Ordinary archive
 
-Active work and inputs must be settled, and managed resources clean and safely
-removable. WorkItem results must be integrated or deliberately abandoned;
+Active work and inputs must be settled, and execution proven stopped.
+WorkItem results must be integrated or deliberately abandoned;
 Review, Lane and Integration resources must be settled. With `--integrated`,
 each Project requiring code delivery needs a merged, verified Publication
 covering its accepted head, either exactly or through valid explicit candidate
 adoption. `--abandon` records deliberate non-delivery,
 not verified merge.
 
-Missing/stale coverage, unresolved execution or dirty worktrees prevent ordinary
-archive. Resolve the reported facts before an explicit retry; no implicit reset
+Missing/stale coverage or unresolved execution prevents ordinary archive.
+Dirty or otherwise unsafe temporary resources are retained after the logical
+archive commit; they do not require force merely to archive. No implicit reset
 or force deletion occurs.
+For `--abandon`, a clean Task-main at its exact recorded Project baseline can
+be released without a Publication. New unverified commits remain protected.
+Pending or running Reviews are unsettled business, not just retained directories.
 
 ### Explicit force archive
 
@@ -345,11 +349,22 @@ current ownership, not a second cleanup queue.
 An archive result with `archived=true` proves archival, not that cleanup fully
 succeeded. Even `cleanupFinished` means the foreground pass finished, not that
 every resource was removed. Repeating archive reports current facts and does
-not replay cleanup. After inspection, use explicit exact-owner resource
-operations for safe cleanup; no background retry or broader deletion authority
+not replay cleanup. After inspection, use `yui task archive-cleanup <task>` to
+retry safe exact-owner cleanup. `allResourcesReleased` reports the current pass
+and remaining ownership separately from historical warnings; no background retry or broader deletion authority
 is implied. Both archive paths preserve Task history and recovery information.
 Archived Tasks cannot reopen.
 
+Interrupted runtime cleanup may leave an adjacent `.cleanup-*` directory.
+Retries inspect these claims as well as the original path: only an exact Owner
+marker and no live process references permit deletion. Missing or mismatched
+markers remain retained with their path for explicit diagnosis; absence of the
+original directory alone never proves release. Unresolved claims also prevent
+reactivating the same runtime. Executed-Job physical checks use that same claim
+inventory before ordinary archive commits; acknowledgement does not bypass a
+live or unverified renamed runtime. This uses the existing resource owner and receipt,
+not a second cleanup queue.
+
 Resource GC is a separate, opt-in quarantine path. A runtime subtree moves once:
 the parent receipt owns recovery of its contents, and redundant child registry
 entries are removed in the same registry transaction. Independently owned Git
@@ -411,8 +426,21 @@ Preflight is an observation, not a removal permit. Cleanup reloads the same
 checks and Git verifies ownership/dirt again at removal. A Task-main clone's
 dependent registrations are expected before child cleanup and must be absent
 before clone removal. Archive preserves new dirt even in a failed Integration
-workspace; the separate explicit Integration cleanup command keeps its existing
-disposable-conflict behavior. A finished force cleanup means the foreground
+workspace; explicit Integration cleanup also preserves dirt and durable logs.
+An acknowledged unknown Job result remains unknown: cleanup additionally needs
+fresh evidence that its exact runner generation and physical path references
+are absent. Successful, failed, timed-out and cancelled executed Jobs need the
+same physical evidence; a terminal result does not prove surviving children
+stopped. Only Jobs cancelled/rejected before any execution effect bypass it.
+Cleanup first checks Job results and exact runner exit, then stops only settled,
+exactly owned Roles. It repeats full path-reference checks after that stop and
+before deleting any child workspace or committing ordinary archive. An idle
+reusable Role sharing the workspace is not itself a reason to skip its normal
+stop; surviving or unverified references still prevent release.
+Integration resource preflight also checks runtime ownership and cleanup claims
+with the deletion inspector. Unverified physical material is retained without
+turning it into a new ordinary-archive business gate.
+A finished cleanup means the foreground
 attempt ended, not that every resource was released. Current retained references
 and exact physical runtime evidence remain separate from historical diagnostics.
 

package/docs/task-delivery.zh-CN.md

@@ -138,7 +138,7 @@ Review 时跳过刷新，该新鲜度字段为 null。重复完成不重新观
 干净且已提交的 Task-main 快照。当有一条新的 user/Operator 消息仍在等待 Leader
 投递时，它也会拒绝完成。当前原生轮次必须结束，待处理的通知才能到达；随后 Leader
 读取原始消息并重新评估完成。这派生自既有的 Message 和 mailbox 投递，而不是第二套
-确认或工作流状态。终态工作区清理在完成时可以只是建议。普通归档要求清理已结算；
+确认或工作流状态。终态工作区清理在完成时可以只是建议。普通归档要求业务及执行已结算；
 明确授权的 force 归档可以保留下文所述的未解决资源。被选作结果的 Artifact 必须是
 固定的、存在的且 Task 局部的。
 
@@ -235,13 +235,15 @@ yui task archive <task> (--integrated|--abandon) --force
 
 ### 普通归档
 
-活动工作与输入必须已了结，受管资源干净且可安全移除。WorkItem 结果必须已集成或
+活动工作与输入必须已了结，并证明执行已停止。WorkItem 结果必须已集成或
 有意放弃；Review、Lane 和 Integration 资源必须已结算。使用 `--integrated` 时，
 每个需要代码交付的 Project 都要求已合并且已验证的 Publication，通过精确匹配
 或有效显式采用候选覆盖其验收 head。`--abandon` 记录有意不交付，而不是已验证合并。
 
-缺失或陈旧的覆盖、未解决的执行或脏 worktree 会阻止普通归档。先解决报告的事实，
-再显式重试；不会隐式 reset 或强制删除。
+缺失或陈旧的覆盖、未解决的执行会阻止普通归档。脏 worktree 或其他无法安全移除的
+临时资源在逻辑归档后保留，不会仅因这些残留而要求 force；不会隐式 reset 或强制删除。
+`--abandon` 可释放 HEAD 精确等于已记录 Project 基线的干净 Task-main，无需 Publication；
+未验证的新增提交仍保留。pending/running Review 属于未结清业务，而不只是保留目录。
 
 ### 明确授权的 force 归档
 
@@ -265,9 +267,17 @@ Force 不验证合并、不验收工作、不证明物理静止、不丢弃脏
 
 归档结果中的 `archived=true` 证明已归档，不证明清理全部成功。即使 `cleanupFinished`
 也只代表前台清理已走完，不代表资源全部移除。重复归档只报告当前事实，不重放清理。
-检查后通过显式的精确 owner 资源操作进行安全清理；不隐含后台重试或更广泛的删除
+检查后通过 `yui task archive-cleanup <task>` 显式重试精确 owner 的安全清理。
+`allResourcesReleased` 将当前轮次及剩余所有权与历史警告分开报告；不隐含后台重试或更广泛的删除
 权限。两条归档路径都保留 Task 历史与恢复信息。已归档的 Task 不能重开。
 
+runtime 清理中断可能留下相邻的 `.cleanup-*` 认领目录。重试同时检查这些目录和原路径，
+只有 Owner marker 精确匹配且没有存活进程引用时才删除。marker 缺失或不匹配时保留目录，
+并给出路径供显式诊断；原目录不存在本身不证明资源已释放。未解决的认领也阻止同一 runtime
+重新激活。此过程复用已有资源 owner 和回执，不引入第二套清理队列。
+实际启动过的 Job 的物理检查在普通归档提交前复用同一认领目录清单；
+确认未知结果不能跳过仍被进程引用或无法核实的重命名 runtime。
+
 资源 GC 是独立、显式启用的隔离路径。同一 runtime 子树只移动一次，由父目录
 回执负责恢复完整内容；重复的子目录 registry 记录在同一事务内移除。
 独立 Git worktree 或仍需保留的子资源会阻止移动其父目录，不删除 Task 记录或成果。
@@ -311,8 +321,15 @@ Task Leader reader 也可读取。这里的 `--force` 仅选择要检查的行
 
 预检是观察，不是删除凭据。清理会重新读取同一组检查，Git 删除时再验证身份和脏状态。
 Task-main clone 在子工作区清理前存在关联 Git 注册是正常现象，但移除 clone 前它们必须
-已释放。归档会保留失败 Integration 工作区中新出现的脏文件；独立的显式 Integration
-清理命令保留既有的可丢弃冲突现场合同。force 清理完成只表示这次前台尝试结束，不表示
+已释放。归档与独立的显式 Integration 清理均保留脏文件和持久日志。
+确认 unknown Job 不会改写其未知结果；清理还需重新验证精确 runner 进程代次及物理路径引用
+均已消失。成功、失败、超时或取消的已执行 Job 也要求同样的物理证据；终态结果不能证明
+存活子进程已停止。只有执行产生任何效果前已取消或拒绝的 Job 可跳过检查。
+清理先检查 Job 结果与精确 runner 退出，再停止执行已结算且归属精确的 Role；
+停止后、删除任何子工作区或提交普通归档前，重新执行完整路径引用检查。
+共享工作区的可复用空闲 Role 可以进入正常停止流程；残留或无法核实的引用仍阻止释放。
+Integration 资源预检与删除共享 runtime 归属和认领目录检查；无法验证的物理材料保留，
+不会因此新增普通归档的业务准入门槛。清理完成只表示这次前台尝试结束，不表示
 全部资源已释放；当前保留引用、精确物理运行时证据与历史诊断仍是不同事实。
 
 清理前用每个命令的 `--help` 查看它确切的权限和选项；阅读一份生命周期文档不授权