@zq-silk/yui 0.16.1 → 1.0.0-alpha

package/dist/workspace/cleanupInspection.js

@@ -36,10 +36,7 @@ export function cleanupFailure(reason, detail, expected, observed, status = "blo
     throw new CleanupInspectionError([{ resource: "git-workspace", reason, status,
             detail, expected, observed, sources: [], actions: [] }]);
 }
-/** Describe exact differences without disclosing paths outside this Task.
- * Legacy locations are displayed only for this Task's exact branch identity;
- * displaying a historical location is not accepting it as migration proof.
- */
+/** Describe exact differences without disclosing paths outside this Task. */
 export function workspacePathValue(workspace, path) {
     const inside = (root) => {
         const value = relative(root, path);
@@ -52,11 +49,6 @@ export function workspacePathValue(workspace, path) {
         const taskPath = inside(join(home, "workspaces", "tasks", workspace.owner.taskId));
         if (taskPath !== undefined)
             return `<task>/${taskPath}`;
-        const legacyPath = inside(join(home, "workspaces", "worktree"));
-        const parts = legacyPath?.split("/");
-        const taskSegment = workspace.entries.find(e => e.access === "write")?.branch.split("/")[1];
-        if (parts?.length === 3 && parts[1] === taskSegment)
-            return `<legacy-worktree>/${legacyPath}`;
     }
     const local = inside(workspace.root);
     return local === undefined ? "[outside authorized Task paths]" : `<owner>/${local}`;

package/dist/worktree/managedWorkspace.js

@@ -34,7 +34,7 @@ export function isTaskOwnedWorkspace(workspace, taskId, taskRoot, bindings) {
 export function createManagedWorkspace(input, now) {
     const timestamp = now.toISOString();
     return validateManagedWorkspace({
-        schemaVersion: 2,
+        schemaVersion: 1,
         owner: validateOwner(input.owner),
         root: resolve(requireText(input.root, "Managed workspace root")),
         entries: normalizeEntries(input.entries),
@@ -43,8 +43,8 @@ export function createManagedWorkspace(input, now) {
     });
 }
 export function validateManagedWorkspace(workspace) {
-    if (workspace.schemaVersion !== 2) {
-        throw new Error("Managed workspace must use schemaVersion 2.");
+    if (workspace.schemaVersion !== 1) {
+        throw new Error("Managed workspace must use schemaVersion 1.");
     }
     validateOwner(workspace.owner);
     if (resolve(requireText(workspace.root, "Managed workspace root")) !==

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

@@ -2,6 +2,15 @@
 
 # Session, AgentRun and notifications
 
+Global Session stop/replacement uses the same exact native-execution quiescence
+boundary as Task Sessions. A departed Host or archived Session alone is not
+proof that an accepted input ended: its retained Provider binding is inspected
+and stopped before settling occupancy. Global stop evidence is retained as a
+record-only system Message, without submitting another native input. Pending
+notifications cannot restart an explicitly stopped Session; normal Host detach
+preserves an active Session and remains reconnectable. A switch after a partial
+failure still settles the retained input before selecting a new conversation.
+
 ## Authority
 
 Task, WorkItem, Message, Decision, Artifact and Project Knowledge preserve
@@ -28,6 +37,7 @@ yui task context <task> --json
 yui task context delta <task> --after <coreCursor>
 yui task context inspect <task> --store <store> --ref <id>
 yui task run context <task/run> --json
+yui task run context expand <task/run> <ref-id> --store <store> --mode full --json
 ```
 
 Task Context is a bounded authorized working set with a current core cursor.
@@ -43,6 +53,37 @@ 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.
 
+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
+records. Synthesis reads the selected Producer results from that Snapshot.
+Writable Projects come from the Run's captured effective authority; live
+activity is a separate observation, not part of the frozen contract.
+Expansion always requires both `store` and `refId`, even for a unique id.
+
+New Task execution requires an initial Snapshot. Missing evidence does not make
+a retained Run unreadable: inspection, failure settlement and explicit retirement
+remain available to Leader/Operator, and unrelated work can proceed. Submission
+and exact frozen-context reads fail locally when that evidence is absent or has
+drifted. An explicit ordinary retry creates a new Run and Snapshot from current
+authorized facts, without reconstructing the old snapshot; Review and synthesis
+reuse still require exact frozen evidence. Subsequent observed/steered input may
+omit its own Snapshot because it does not establish a new Assignment.
+Storage uses the 1.0 baseline; the independent converter preserves these records
+without making missing optional execution evidence a Home-wide blocker.
+
+Operational failures are scoped to their owner, not treated as proof that the
+whole Controller must stop. Optional resource reaping and continuation metadata
+checks report failures without blocking normal scheduling. Provider retry
+admission is isolated per Session; continuation observation is isolated per Task.
+Job and Global input errors identify their Task/Job or Role and retain the
+original cause. Committed observations stay committed; failed observations do
+not acknowledge input, imply quiescence, or authorize another send or deletion.
+Use the existing status, stop/cancel, retire, acknowledge and explicit retry
+operations for the affected owner. Structural storage corruption, authority
+failure and unconfirmed external effects still require diagnosis at their
+respective boundaries, not a catch-all default or synthetic successful result.
+
 Current Task reads also expose untargeted user/Operator messages to the Task's
 current Worker and Reviewer Sessions, including requirements added after their
 Run snapshot was frozen. Use `task message list/show` or Task Context inspect
@@ -122,13 +163,10 @@ channel once; Worker/Reviewer failures use the existing Leader channel. No new
 recovery Agent is started, and there need not be a Run or Session to record the
 failure.
 
-Storage 35→36 archives original historical error payloads and marks their
-unrecorded launch configuration as unavailable. It never reconstructs old model,
-account or settings choices from current Roles.
-
-Storage 36→37 narrows that context to native metadata selectors and the requested
-model/effort. Full old snapshots remain in migration audit, not in the active
-reader. Reading a failure's model options does not validate Task permissions,
+Failure context records native metadata selectors and the requested model/effort.
+Unrecorded configuration stays unavailable; it is never reconstructed from current
+Roles. Opaque audit bytes are not read as current configuration.
+Reading a failure's model options does not validate Task permissions,
 Review state, workspace entries or the current Session bootstrap protocol.
 The three failure ingresses retain their native fencing/classification, while
 record creation and deduplication share one writer and supervisor notices use
@@ -294,6 +332,11 @@ yui task execution start <task>
 yui task execution stop <task> --force --reason <reason>
 ```
 
+`task run retire` accepts only `--expected-progress-at` for its progress fence;
+the former `--progress-at` alias is removed. Retiring an active Run still requires
+its exact progress, Agent/Adapter and, when bound, native Session identity;
+the renamed entry does not relax quiescence or retirement authority.
+
 Task execution start/stop controls Task admission, not Task acceptance.
 Stop first fences new Yui work, then interrupts each exact owned native input
 and confirms its terminal before removing the attachment. This also covers

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

@@ -2,6 +2,12 @@
 
 # Session、AgentRun 与通知
 
+Global Session 停止／替换与 Task Session 共用精确的原生执行静止确认边界。
+Host 消失或 Session 已入历史不代表已接受输入结束：须先检查并停止保留的
+Provider binding，再结算执行占用。Global 停止证据保存为仅记录的 system Message，
+不触发新的原生输入。待投递通知不能重启已明确停止的 Session；普通 Host 脱离仍
+保留 active Session，可正常重连。部分切换失败后，仍须先结算旧输入再选择新会话。
+
 ## 权威
 
 Task、WorkItem、Message、Decision、Artifact 和 Project Knowledge 保存持久工作。
@@ -25,6 +31,7 @@ yui task context <task> --json
 yui task context delta <task> --after <coreCursor>
 yui task context inspect <task> --store <store> --ref <id>
 yui task run context <task/run> --json
+yui task run context expand <task/run> <ref-id> --store <store> --mode full --json
 ```
 
 Task Context 是一个有界的、获授权的工作集，带有当前 core 游标。delta 在一个固定
@@ -37,6 +44,28 @@ Run Context 冻结 Assignment、来源引用、生效配置和工作区边界。
 和消息正文，而不是把加载成功当成交付物。规划 Pack 不暴露 Project 写范围或 Task 完成
 权限。
 
+新 Run（包括规划、Review 和消息续接）必须在派发前绑定明确冻结的 Snapshot。
+Context 读取校验完整身份与内容 digest，然后直接读取已保存的值，不重新收集当前
+Task 记录。聚合执行从该 Snapshot 读取已选择的 Producer 结果；可写 Project 来自
+Run 捕获的生效授权。当前活动状态仍是独立观察，不属于冻结合同。
+展开引用必须同时指定 `store` 与 `refId`，即使 id 唯一也不能省略 store。
+
+新的 Task 执行需要首个 Snapshot。保留的 Run 缺失执行证据时，仍可供
+Leader／Operator 查看、结算失败或显式废弃，无关工作继续推进。提交执行和读取
+确切冻结上下文在证据缺失、漂移时局部失败。显式普通重试根据当前授权事实创建
+新的 Run 和 Snapshot，不补造旧快照；Review／结果汇总的确切复用仍需冻结证据。
+后续原生输入或 steer 可以没有独立 Snapshot，因为它们不建立新的 Assignment。
+存储采用 1.0 基线；独立转换器保留这些记录，不把可选执行证据缺失扩大为
+整个 Home 的转换阻塞。
+
+运行异常按所属对象限制影响，不等同于整个 Controller 必须停摆。可选的资源回收
+和 continuation 元数据检查失败会报告诊断，不阻断正常调度；Provider 重试准入
+按 Session 隔离，continuation 观察按 Task 隔离。Job 和全局输入错误包含
+Task／Job 或 Role 身份，并保留原始原因。已提交的观察仍然有效，失败的观察不代表
+输入已确认、进程已停止，也不授权再次发送或删除。对受影响对象使用既有的查看、
+停止／取消、废弃、确认和显式重试入口。存储结构损坏、权限失败及未知外部效果，
+仍在各自边界明确诊断，不用统一兜底值或伪造成功绕过。
+
 当前 Task 读取也会把无定向目标的 user/Operator 消息暴露给该 Task 当前的 Worker 和
 Reviewer Session，包括在它们 Run 快照冻结之后新增的需求。用 `task message list/show`
 或 Task Context inspect 来读取那些原始记录。这不改写冻结的 Assignment，也不授予投递
@@ -103,11 +132,9 @@ retry 把被拒绝批次及后续排队输入交回现有 mailbox，不把旧 wa
 错误通过既有 Operator 通道通知一次；Worker／Reviewer 仍通知 Leader。不启动新的
 恢复 Agent，也不为了记录错误制造 Run 或 Session。
 
-存储 `35→36` 迁移保留历史错误原始 payload，并将当时未记录的启动配置标为不可用，
-不会从当前 Role 猜测过去的模型、账户或 settings 选择。
-
-存储 `36→37` 将该上下文收窄为原生元数据查询选项和请求的模型／effort。旧完整快照
-留在迁移审计中，不由运行时双读。查看模型选项不再校验 Task 权限、Review 状态、
+错误上下文记录原生元数据查询选项和请求的模型／effort。未记录的配置保持不可用，
+不会从当前 Role 猜测过去的选择，也不会把不透明审计字节当作当前配置读取。
+查看模型选项不校验 Task 权限、Review 状态、
 工作区条目或当前 Session 引导协议。三类错误入口保留各自的原生身份检查与分类，
 错误创建、去重统一一个写入入口，上级通知统一使用事件路由边界。
 
@@ -239,6 +266,10 @@ yui task execution start <task>
 yui task execution stop <task> --force --reason <reason>
 ```
 
+`task run retire` 的进度围栏只接受 `--expected-progress-at`，移除旧的
+`--progress-at` 别名。退役活动 Run 仍要求精确进度、Agent/Adapter 及已绑定的
+原生 Session 身份，不放宽静止性检查或退役权限。
+
 Task execution start/stop 控制 Task 准入，而不是 Task 验收。stop 先围住新的 Yui 工作，
 然后中断每一条被拥有的确切原生输入，并在移除 attachment 之前确认其终态。这也覆盖没有
 Run 的普通 Leader 通知。未知的原生状态阻塞清理；仅停止一个代理绝不证明一个共享 Turn

package/docs/observability/README.md

@@ -56,6 +56,53 @@ Claude execution process dying closes its exact input and marks its Session
 failed, even while the supervising Host remains alive. A deliberately stopped
 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
+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.
+
+Session observations include direct chat and notifications without an AgentRun.
+The selected native identity is counted once; foreground activity must match its
+exact current input. Earlier Turns and replaced Sessions cannot supply its
+activity. Waiting, quiet, diagnostic-needed, unknown, stopped, ended and unsettled
+background work remain distinct. An operation without a terminal is not an
+everlasting heartbeat. Quiet/diagnostic windows come from the existing runtime
+policy; the read time is not a new activity timestamp. This is a recorded selected
+Session view, not a live process probe or an inventory of historical resources.
+Controller-owned bounded Provider retry waits remain waiting, not stopped or
+waiting for user approval. A successor's activity uses its own exact input.
+
+Progress comes from the original Brief and completion record, with source time;
+activity and tokens do not create a percentage, ETA or semantic checkpoint.
+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
+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
+uses the original Message form, explicit intent and receipt. Unsent inputs remain
+protected across automatic refresh.
+
+Delivery reuses Publication coverage, including adoption, and keeps
+reported/verified, missing/stale/head-unavailable distinct. On-demand evidence
+shows original Integration checks, fixed Review candidates and original Reviewer
+reports. Review completion is not semantic approval; skipped/missing checks are
+not passes. Workspace ownership does not prove cleanup safety: the existing
+read-only `task archive-preflight` is referenced, not automatically run. There
+are no new accept, publish or archive buttons. Usage retains known/partial/unknown.
+
+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.
+These reads do not start a runtime, fetch a remote, write business state, require
+a migration, or introduce a new persistent protocol.
+
 ## Execution audit
 
 `execution audit` aggregates existing Task, Run, wake, Session, Review,

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

@@ -49,6 +49,43 @@ AgentRun，Role 状态也包含其原生准入/活动；当某个 WorkItem 处
 监督它的 Host 仍存活。一个已被有意停止、且原生输入已结算的 Session 是空闲状态，
 而不是虚假的运行时失败。
 
+## Web 用户关注与进展
+
+Task 详情优先展示「需要你处理」「会话活动」「任务进展」「关键结论」。
+InputRequest 保留原回答入口和有界 Context 计数；部分读取不等于空待办。
+技术关注从既有执行投影取得负责人；有负责人不代表已开始处理，诊断提示
+也不自动成为新的用户授权。
+
+会话观察包含没有 AgentRun 的直聊与通知。选用的原生身份只计一次，前台活动
+必须匹配当前精确输入；旧 Turn、旧 Session 的活动不能借给新输入。
+等待、安静、需诊断、未知、停止、该轮结束和后台未结清保持区分；
+没有终态的操作不是永久心跳。时间窗复用既有 runtime policy，读取时间不冒充
+活动时间。这是已记录选用会话的视图，不是实时进程探测或历史资源盘点。
+Controller 已负责的有界 Provider 重试显示为等待，不误称停止或等待用户审批；
+后继输入的活动仍须匹配它自己的精确身份。
+
+进度来自原 Brief 和完成记录，标注来源时间；活动、token 不产生百分比、
+ETA 或实质检查点。当前 Decision 展示理由与来源，已替代决定留在历史；
+报告与建议不改称用户批准。独立观察失败时，核心 Context 仍可读取。
+
+「成果与证据」仅按需读文件。固定提交的文本阅读在刷新和读取新列表后仍保留，
+切换版本必须显式选择；固定版本缺失就报错，不回退 HEAD。
+HTML／脚本只作为文本，不执行预览。复制来源不发送内容，讨论仍走原 Message
+表单、显式意图及回执；自动刷新保留未提交输入。
+
+交付复用 Publication 覆盖及采用记录，区分 reported/verified 和
+missing/stale/head-unavailable。按需证据展示原 Integration 检查、
+固定 Review 候选及原始 Reviewer 报告；Review completed 不等于语义通过，
+skipped／缺失检查不算通过。工作区所有权不证明可清理；既有只读
+`task archive-preflight` 仅作为操作指引，不自动运行。没有新增验收、发布、
+归档按钮，用量仍保留 known/partial/unknown。
+
+所有入口沿用本地 Web token 与 Task 边界。
+`GET /api/tasks/<id>/artifacts` 列出固定仓库版本；
+`?path=<relative-path>&commit=<full-commit>` 读取该版本文本；
+`GET /api/tasks/<id>/evidence` 读取原检查／Review／工作区记录。
+读取不启动运行时、不访问远端、不写业务状态、不引入迁移或新持久协议。
+
 ## 执行审计
 
 `execution audit` 汇总既有的 Task、Run、wake、Session、Review、Integration、

package/docs/project-refresh.md

@@ -7,6 +7,15 @@ the Project's configured remote and stable branch. Stable and development
 branches must match. The per-Project maintenance fence covers the operation;
 Task workspaces and their recorded bases are not refreshed by this command.
 
+## Project ownership
+
+`yui project clone <name> <remote>` creates a Home-managed checkout by default.
+Add `--external` to clone into `<configured defaultWorkspace>/<name>` and retain
+external ownership. This is a supported public option in help and completion;
+it does not remove the existing confirmation, branch verification or workspace
+isolation boundaries. `project add` can bind an existing external checkout;
+`project migrate` explicitly moves one into Home-managed storage.
+
 ## Two separate facts
 
 The checkout HEAD and a local remote-tracking ref are distinct observations.

package/docs/project-refresh.zh-CN.md

@@ -6,6 +6,14 @@
 规范 checkout。stable 与 development branch 必须一致。操作全程持有 per-Project
 maintenance fence；不会刷新 Task 工作区或改写其记录的基线。
 
+## Project 所有权
+
+`yui project clone <name> <remote>` 默认创建 Home 管理的 checkout。
+添加 `--external` 会克隆到 `<已配置的 defaultWorkspace>/<name>`，保留 external
+所有权。这是帮助和补全中公开支持的选项，不绕过现有确认、分支校验或工作区隔离
+边界。`project add` 可绑定已有 external checkout；`project migrate` 可明确将其
+迁入 Home 管理的存储。
+
 ## 两个独立事实
 
 checkout HEAD 与本地 remote-tracking ref 是不同的观察。refresh 将精确分支获取到

package/docs/provider-retry.md

@@ -48,6 +48,41 @@ panel. `cancel` withdraws this recovery chain; `disable` also disables future
 chains on the current Provider binding. Neither interrupts an admitted Turn.
 `enable` does not replay historical failures. Existing Task/Role authority applies.
 
+## Failure evidence and Agent handoff
+
+The retry projection includes the original input reference (never copied console
+text), exact Session/attempt identities, the preserved error, the latest Turn
+failure and earlier chain references. A changed error that still satisfies the
+same safe retry rule continues within the original budget. Loss of that rule,
+authority or budget stops automatic submission.
+
+Task errors retain their original `runtime.agent-error` evidence and notify the
+Leader, or the Operator when the affected Role is the Leader. Global failures
+retain record-only Messages in their own Role inbox, including intermediate
+failed attempts; these are evidence, not new input that cancels recovery.
+When Global recovery stops or its effect is unknown, a deduplicated system
+Message carries the facts to the existing Operator. If the Operator itself
+failed, or no Operator is configured, the notice remains visible for the user
+or successor without submitting a self-recovery prompt.
+
+Malformed JSON frames and failing protocol listeners close the affected channel
+with the original cause. Unrelated valid protocol notifications remain ignorable.
+The existing Host Inbox carries the diagnostic to Task/Global consumers without
+inventing a native terminal, clearing a writer fence or replaying input.
+
+Endpoint cleanup preserves stop/close errors, the exact implementation and client
+identities, last observed drain facts and pending effects. A failed inspection is
+not an empty resource list. Later owned cleanup steps, including control-socket
+closure, still run; cleanup failures retain their causes and produce a failing
+Host exit rather than silent success. Timeout reports never claim quiescence.
+
+The optional detached-child metadata reconciler retains its existing bounded
+query, backoff and circuit pause. Unavailable observations preserve writer
+ownership and expose their original error, exact targets and sampling count.
+The first failure and circuit-limit crossing use existing deduplicated error
+events; metadata sampling does not start model work or declare a parent result.
+No new default metadata collector, retry worker or durable state schema is added.
+
 ## Supported boundary and adoption
 
 Current controlled Codex Hosts advertise exact recovery support. The native