@zq-silk/yui 2.3.0 → 2.5.0

package/dist/web/webTaskSurface.js

@@ -1,7 +1,9 @@
-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, listTaskContext, readTaskContext, readTaskContextDelta, withContextObservations } from "../context/taskContext.js";
 import { BUILTIN_CAPABILITIES } from "../kernel/builtinCapabilities.js";
@@ -9,6 +11,7 @@ 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,6 +344,7 @@ 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.

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/cli-information-contract.md

@@ -20,7 +20,7 @@ schema migration or new snapshot/cache store is introduced.
 | What changed? | `task context delta <task> --after <cursor>` | Immutable events with a fixed upper bound, not a snapshot of current mutable state |
 | Which Global input? | `session context <role>` | Identity, profile, authority, current native Turn/retry and separate bounded pending/recent Message pages |
 | Read Global input | `role message list <role> [--pending]`, `role message show <role> <id>` | Scoped discovery, then exact original; queue acceptance never erases history |
-| What arrived in this wake? | `task wake show <task> <wake>` | Fixed window and Message/Run/Event read pointers, not duplicated bodies |
+| What arrived in this wake? | `task wake show <task> <wake>` | Fixed-window inputs/results, attributed optional summaries and exact original reads; `--history` expands diagnostics |
 | What was assigned? | `task run context <task>/<run>` | Frozen authority and a single `pointers` inventory with summaries; changed identities in `deltaRefs`; current observations remain separate |
 | Which configuration is real? | `task role session inspect <task> <role>` | Task/Role identity, desired binding, frozen Session, current Provider binding, retry and explicit Host observation; no full Task/Role copies or Provider conversation history |
 

package/docs/cli-information-contract.zh-CN.md

@@ -18,7 +18,7 @@ CLI 调用成功，不代表 Task、原生 Turn 或远端投递完成。
 | 发生了什么变化？ | `task context delta <task> --after <cursor>` | 固定上界内的不可变事件，不是可变当前状态的快照 |
 | Global 收到了什么？ | `session context <role>` | 身份、Profile、权限、当前原生 Turn/retry，以及分别有界的 pending/recent Message 页 |
 | 读取 Global 输入 | `role message list <role> [--pending]`、`role message show <role> <id>` | 在自身范围内发现，再读完整原文；队列接受不删除历史 |
-| 本次唤醒带来什么？ | `task wake show <task> <wake>` | 固定窗口与 Message/Run/Event 读取指针，不重复正文 |
+| 本次唤醒带来什么？ | `task wake show <task> <wake>` | 固定窗口的输入/结果、标明来源的可选摘要和确切原文入口；`--history` 展开诊断历史 |
 | 分配了什么？ | `task run context <task>/<run>` | 冻结授权与一份带摘要的 `pointers` 目录；`deltaRefs` 表示变化身份；当前观察独立 |
 | 实际配置是什么？ | `task role session inspect <task> <role>` | Task/Role 身份、期望绑定、冻结 Session、当前 Provider 绑定、retry 与显式 Host 观察；不复制整个 Task/Role 或 Provider 会话历史 |
 

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

@@ -69,6 +69,14 @@ Run Pack is a reference directory: read the relevant requirement and message
 bodies before acting, rather than treating a successful load as the deliverable.
 Planning Packs expose no Project write scope or Task-completion permission.
 
+The Manifest pointer is a recovery locator, not a read receipt. Load its exact
+`yui-runtime`, Role Skills and profile on first entry, a new/version-changed
+Session, or missing context after compaction/recovery. Reuse instructions only
+when the same-version full content is still available; Yui stores no "already
+read" state. Always refresh dynamic facts. Leader notifications use
+`currentCommand`; dispatched AgentRuns use the actual Run ID with
+`loadCommand`/`expandCommand`, never their placeholder templates.
+
 Every new Run, including planning, Review and continuation, binds an explicit
 frozen Snapshot before dispatch. Context reads validate its full identity and
 content digest, then read its stored values without rebuilding current Task
@@ -123,6 +131,20 @@ Human input, explicit execution entry and activation failure are delivered
 promptly through the existing wake mechanism. Worker results retain their
 aggregation window. Busy native input still preserves pending messages.
 
+Normal and retry notifications share the same bounded presentation: factual
+change labels, attributed optional author summaries, and original read entries.
+An author can begin a Message/report with `Yui-Summary: <one line>` (summary
+at most 512 UTF-8 bytes). It remains in the original record; no schema migration,
+summary store, read-acknowledgement or extra model call is involved. Missing or
+oversized summaries fall back to facts without clipping qualifications.
+Summaries never grant authority, accept results or mark reviews approved.
+
+`task wake show <task> <wake>` now defaults to inputs/results and explicit
+references, including older referenced originals. It omits unrelated diagnostic
+events and merely started Runs; `--history` restores full fixed-window discovery.
+Both views retain the fixed window, deduplication, exact detail commands and
+bounded `contentPage` continuations. Read decision-relevant originals in full.
+
 | Evidence | Disposition |
 | --- | --- |
 | Busy with proven non-acceptance | Preserve input; a new transport attempt may use the same Session |
@@ -276,6 +298,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

@@ -55,6 +55,21 @@ Run Context 冻结 Assignment、来源引用、生效配置和工作区边界。
 和消息正文，而不是把加载成功当成交付物。规划 Pack 不暴露 Project 写范围或 Task 完成
 权限。
 
+Manifest 指针是恢复定位入口，不是已读凭据。首次进入、新会话、版本变化、压缩或恢复后
+说明缺失时，从其确切路径加载 `yui-runtime`、Role Skills 和 profile；仅当同版本全文仍在
+当前可用上下文中，才复用而不机械重读。系统不保存“已经读过”状态。动态事实仍须刷新：
+Leader 通知使用 `currentCommand`，显式 AgentRun 使用真实 Run ID 的
+`loadCommand`/`expandCommand`，不可直接执行占位模板。
+
+正常和重试通知共用有界呈现：流程事实、标明作者来源的可选摘要与原文入口。Agent 可在
+Message/报告首行写 `Yui-Summary: <单行摘要>`（摘要最多 512 UTF-8 字节），保留失败、
+未验证、待决定等限定。摘要存在原文本身，不新增数据格式、摘要存储、已读状态或模型调用；
+缺失或超长时使用事实模板，不截断关键限定。摘要不是授权、验收或审查通过结论。
+
+`task wake show <task> <wake>` 默认展示消息、结果与明确引用（包括窗口外原文），
+不再枚举无关诊断事件和仅启动的 Run；`--history` 展开完整固定窗口历史。两个视图保留
+去重、固定窗口、确切原文命令及 `contentPage` 续读。决策所依赖的原文仍须全文读取。
+
 新 Run（包括规划、Review 和消息续接）必须在派发前绑定明确冻结的 Snapshot。
 Context 读取校验完整身份与内容 digest，然后直接读取已保存的值，不重新收集当前
 Task 记录。聚合执行从该 Snapshot 读取已选择的 Producer 结果；可写 Project 来自
@@ -223,6 +238,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/release-workflow.md

@@ -51,6 +51,60 @@ 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.5.0 compatibility and migration notes
+
+This minor includes Task110's notification and context-loading improvements.
+Normal and recovery notifications share bounded facts, optional attributed
+author summaries and exact action entries. A summary is not acceptance or
+authority: relevant requirements, user messages and execution results must
+still be read in full.
+
+Session instructions name the required Skills explicitly. Reuse is conditional
+on the complete same-version instructions remaining available in context;
+first entry, changed instructions or missing/compacted content require loading
+the exact Manifest and referenced files again. There is no persistent read
+receipt, instruction cache or additional model call for summarization.
+
+`task wake show` now focuses on relevant messages, results and referenced
+evidence by default. Use `--history` for the broader fixed-window diagnostic
+view and follow pagination when present. Consumers must not treat the focused
+view as all history. Original records, exact older references, deduplication,
+snapshot boundaries and unknown-input no-replay rules are preserved.
+
+No storage migration is added; storage remains **1.6**. Deterministic tests and
+package smoke do not prove real-model instruction reuse or compaction recovery.
+Byte measurements are not token savings and can increase for a simple first
+entry. Publishing this package does not upgrade a global CLI, migrate a Home
+or restart a Controller.
+
+### 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

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

@@ -36,6 +36,45 @@ Agent 选择一个预先声明的计划，设施从持久状态驱动该计划
 不能将不兼容冒称为兼容，也不为回避版本选择新增历史兼容机制。包版本与协议、
 持久存储契约仍然独立：兼容性检查和必要迁移要求不变，下文存储规则不授予发版权限。
 
+### 2.5.0 兼容性及迁移说明
+
+本 minor 包含 Task110 的通知和上下文加载优化。正常与恢复通知共用有界事实、
+可选且注明来源的作者摘要及精确行动入口。摘要不是验收或授权：相关需求、
+用户消息和执行结果仍须全文读取。
+
+会话说明显式列出所需 Skill。只有完整的同版本说明仍在可用上下文中时才能复用；
+首次进入、说明变更或内容缺失／被压缩时，须重新加载精确 Manifest 及其引用文件。
+没有新增持久已读回执、说明缓存或专用模型摘要调用。
+
+`task wake show` 默认聚焦相关消息、结果及引用证据；如需更完整的固定窗口诊断，
+使用 `--history`，有分页时继续读取。调用方不能将聚焦视图当作全部历史。
+原始记录、精确旧引用、去重、快照边界及未知输入不得重放的规则保持不变。
+
+本版不新增存储迁移，存储仍为 **1.6**。确定性测试及安装包冒烟不证明真实模型
+会复用说明或在压缩后正确补读；字节测量不是 token 节省，简单首次进入的开销
+可能增加。发布本包不会升级全局 CLI、迁移 Home 或重启 Controller。
+
+### 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 历史、

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-discovery.md

@@ -25,6 +25,34 @@ and semantic progress.
 
 ## Query and page contract
 
+### Project knowledge
+
+Current Task and Run Context select active knowledge only from the bound
+projects. `scope` and `expiresWhen` are free text: the Agent reads the original
+and decides whether it applies to the actual task. Engineering does not infer
+semantic expiry or execute knowledge content. Explicit Operator retirement
+removes an entry from future current Context; frozen Run evidence is unchanged.
+Context pointers expose applicability and version, with complete source and
+prior versions available through the exact detail read.
+
+`project knowledge list` and `project knowledge proposals list` return compact
+`items/total/complete/nextCursor` pages (`--limit`, `--cursor`); `--all` includes
+retired knowledge or decided proposals respectively. `show` returns the exact
+knowledge/proposal, or `contentPage` for a long record: continue with its cursor
+and concatenate `text` in offset order before parsing. Mutation receipts contain
+identities, not the entire Project. Web’s Task Records → Project knowledge uses
+the same paged discovery and exact source reader.
+
+Proposal identity includes project, source Task/Decision/Milestone/commit,
+title, body, scope, expiry condition and superseded knowledge ID. Only outer
+whitespace is trimmed; internal whitespace, case and Unicode remain significant.
+An omitted condition differs from a supplied one; omit a condition in a
+replacement proposal to clear it upon `accept --update`. A repeated identical
+proposal reuses its existing pending/accepted identity. Changed applicability
+still requires the existing Operator approval, including explicit `--update`
+for a same-title replacement. Each effective update or retirement increments
+the formal version and preserves its exact prior content and provenance.
+
 ```sh
 yui task list --project project-1 --status active --limit 20 --json
 yui task list --attention openInputs --json

package/docs/testing/verification-levels.md

@@ -50,12 +50,12 @@ is required.
 ## Permanent core smoke
 
 `npm test` and `npm run test:core` build the checkout and run the maintained suite.
-The stable suite owns current storage 1.2 and its declared 1.0/1.1 minor
+The stable suite owns current storage 1.6 and its declared 1.0/1.1/1.2/1.3/1.4/1.5 minor
 transition. It contains no undeclared historical format compatibility path.
 
 Current coverage includes:
 
-1. Fresh storage 1.2, exact schema/record validation, no initialization over
+1. Fresh storage 1.6, exact schema/record validation, no initialization over
    unknown data, and rejection of old integer formats without mutation.
 2. Exact-version staging, mismatched-target refusal, same-major contiguous
    minor preflight, explicit maintenance-owner identity across handover, and

package/i18n/README.zh-CN.md

@@ -40,7 +40,7 @@ Yui 是面向编程 Agent 的本地控制面。你只需用自然语言把目标
 npm 包包含 Linux x64、Mac Intel 和 Apple Silicon 的 Yui 预编译程序。
 同一份包在三个平台验证后发布，运行时只选择对应平台的程序。
 
-需要 Linux x64 / glibc 或 macOS（x64 或 Apple Silicon）、Git、tmux，以及
+需要 Linux x64 / glibc 或 macOS（x64 或 Apple Silicon）、Git 2.29.0 或更新版本、tmux，以及
 Node.js `^20.17.0`、`^22.9.0`、`^24.0.0` 或 `^26.0.0`。macOS 上可用
 `brew install tmux` 安装 tmux。最简单的方式是先安装 Codex CLI 或 Claude
 Code CLI，并确保它已经可以使用你自己的账号正常工作。Yui 负责协调 Agent，

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zq-silk/yui",
-  "version": "2.3.0",
+  "version": "2.5.0",
   "description": "Local control plane for long-running native agent CLI sessions backed by tmux.",
   "license": "MIT",
   "private": false,

package/skills/yui-leader/SKILL.md

@@ -14,10 +14,11 @@ their summaries. Resolve links relative to the file containing them.
 
 Current Context is a bounded working set, not all Task history. Use
 `task context list <task> --store <store>` or a domain list for discovery,
-then an exact detail read. A wake contains original Message/Run read pointers,
-not copied reports. Follow Runtime's `nextCursor` and `contentPage` rules:
-read the full relevant window and originals before disposition, without
-unconditionally walking unrelated history.
+then an exact detail read. A wake contains attributed change summaries and
+original Message/Run pointers, not complete reports. Follow `yui-runtime`'s
+`nextCursor` and `contentPage` rules: read the complete focused wake view and
+relevant originals before disposition; use `wake show --history` only when
+window history/diagnostics matter. Summaries never decide completion.
 
 Before WorkItem dispatch, put the complete bounded requirements in the WorkItem
 or explicitly select up to 16 relevant readable materials with repeated

package/skills/yui-leader/references/execution.md

@@ -420,7 +420,8 @@ notification; no active AgentRun is required.
 
 Before ending authorized execution:
 
-1. Inspect the wake delta, resolve every referenced Worker or Reviewer AgentRun
+1. Inspect the focused wake inputs/results (expand `--history` when needed),
+   resolve every referenced Worker or Reviewer AgentRun
    with `yui task run show`, read each original result in full, and make the
    next decision.
 2. Persist actual WorkItem lifecycle and material Brief, Decision, Milestone,

package/skills/yui-operator/SKILL.md

@@ -30,6 +30,9 @@ another reader's understanding or action. Do not narrate dispatch, attach,
 heartbeat, sampling, unchanged waiting, or routine recovery.
 
 A `[Yui updates]` message is a wake envelope containing durable references.
+Follow `yui-runtime`'s conditional instruction loading and attributed summary
+contract for both Global Message inputs and these notices. Summaries locate
+originals; they cannot grant user authority or prove result acceptance.
 Read those exact records before responding and combine related updates into one
 user-level summary. Do not create a Codex Goal, polling loop, private monitoring
 task, or synthetic progress message; future durable events will wake the

package/skills/yui-reviewer/SKILL.md

@@ -110,8 +110,10 @@ frozen Review or its original report.
 
 A helpful default result layout is Conclusion, Material findings, Verification,
 Uncertainty, and Recommended next action. Markdown or JSON are both acceptable.
-Yui preserves the original text and does not parse, normalize, or reject it for
-missing headings, field names, or formatting.
+Yui preserves the original text and does not parse a verdict or reject it for
+missing headings, field names, or formatting. Follow `yui-runtime`'s optional
+`Yui-Summary:` first-line convention for attributed notification text; retain
+material findings and uncertainty rather than implying automatic approval.
 
 For normal software delivery, follow the applicable Project Policy. The
 Leader decides whether risk warrants one independent Task-final Review of the