@zq-silk/yui 2.1.0 → 2.3.0

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

@@ -27,12 +27,61 @@ Agent 选择一个预先声明的计划，设施从持久状态驱动该计划
 发布 npm；每项外部效果仍需 Task 的实际授权。仅包含 PR、CI 和合并步骤也是合法的交付
 计划，`ReleaseWorkflow` 这个名称不授予包发布、全局 CLI 更新或 Controller 替换权限。
 
-用户明确要求「发布新版本」但没有指定级别时，根据实际变更和项目版本规则，仅选择
-minor（中版本）或 patch（小版本）。major（大版本）必须得到用户对大版本或具体 major
-版本号的明确授权。如果破坏性变更无法诚实地用 minor/patch 表达，说明兼容性冲突，
-等待必要的明确用户选择：既不能静默发布 major，也不能把不兼容行为冒称为兼容。
-这不要求为了回避选择而新增历史兼容机制。包发布版本与存储迁移版本是不同契约，
-下文的存储规则不授予包发布权限。
+用户明确要求「发布新版本」时，新功能或接口／行为不兼容变更使用 minor（中版本），
+纯兼容修复可使用 patch（小版本）。不兼容本身不要求 major 或再次确认版本级别；
+只有用户明确要求 major（大版本）时才发布 major。
+
+这是 Yui 项目专属的编号约定，不是通常 SemVer 的向后兼容承诺：minor 也可能不兼容。
+用户升级前应阅读兼容性及迁移说明；发布说明必须列明受影响的契约与新接口用法，
+不能将不兼容冒称为兼容，也不为回避版本选择新增历史兼容机制。包版本与协议、
+持久存储契约仍然独立：兼容性检查和必要迁移要求不变，下文存储规则不授予发版权限。
+
+### 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` 入口、显式模型／工具配置、持久本地会话、上下文压缩、
+离线评估，以及 Task 交接／Leader 写域修复和 Web 布局改善。
+
+2.1.0 独立 Agent 的公开 `createAgent({ onEvent })` 已被替换。
+JavaScript 调用方继续传入 `onEvent` 时不会再触发该回调，Turn 仍可能完成，
+但事实仅保留在内存中。升级前必须调整调用方；虽然编号为 minor，这仍是不兼容变化。
+
+必要的有序记录使用 `recorder.record`：内核等待记录确认，拒绝会停止新增效果。
+可选展示／遥测使用同步 `observer.observe`：失败写入 `observerErrors`，不停止 Turn。
+Observer 必须自行排队异步工作，不能返回 Promise。旧异步持久化回调应改为：
+
+```js
+const agent = createAgent({
+  provider,
+  tools,
+  recorder: { record: persistEvent }, // async (event) => { await durableWrite(event); }
+  observer: { observe: renderEvent }, // 可选，同步
+});
+```
+
+检查 `result.recording` 的记录证据及 `result.error`；记录失败代码由
+`event_sink_failed` 改为 `recording_failed`。不要把必要持久化放入 Observer。
+已有 Task 和历史报告仍可读取，但新 Review 必须有冻结 Candidate／原报告证据，
+缺少的历史证据不会自动补造。上下文超预算时，压缩需要显式 compressor。
+上述说明不授予全局 CLI 安装、Home 迁移或 Controller 重启权限。
 
 下文操作及示例说明如何执行已经获授权的效果，不是 Task 完成或合并后默认运行的步骤。
 

package/docs/roles-and-configuration.md

@@ -62,6 +62,38 @@ different contracts. Provider bypass does not grant writes to another Project.
 Managed workspace owner, exact Assignment and resource grants enforce Yui
 operations; broad native permissions are not an OS sandbox.
 
+A write-intent delivery Leader launched in its own Task-owned main workspace
+captures that workspace's bound writable Projects without needing an open
+WorkItem. Accepted results do not remove this direct-delivery scope. An explicit
+Assignment (including an empty write scope) remains authoritative for assigned
+execution. Planning, read-intent execution and global Roles do not acquire this
+Task-main scope; Reviewer writes remain confined to their exact Review workspace.
+Project effects recheck the current Session's frozen scope as well as Task
+lifecycle and workspace ownership. The scope does not authorize stable Project
+checkouts, other Tasks, private Worker/Review workspaces or Home mutations.
+
+Managed Leader Integration targets must name the Task-main branch, and that
+branch must actually be checked out in the captured Task-main directory.
+Admission, checks and target CAS revalidate this boundary; `--target` does not
+grant access to another worktree in the same repository.
+
+`integration abort` may confirm an already-applied CAS as committed without
+granting new Project writes. It still verifies current delivery identity,
+captured Task-main ownership, actual checkout, candidate and check/Job evidence.
+An unadvanced CAS remains a Project effect and requires the full write scope.
+
+An existing empty-scope Session stays empty after a runtime update, including
+ordinary failed-Run retries. Resume cannot change captured Profile access or
+Project write scope. Inspect
+`yui task role session inspect <task> leader --json` (`session.effective`), then
+request `yui task role session new <task> leader --reason "<adopt new scope>"`.
+When replacing your own Session, end the turn. After Yui confirms cleanup and
+launches the successor, inspect its captured `executionAuthority`,
+`profileAccess`, `writeProjectIds` and workspace before editing. A replacement
+request is not proof of adoption. Exact Run Context and launch environment
+derive their write scope from the same frozen effective snapshot; models,
+effort, accepted Candidates and their acceptance history are unchanged.
+
 Yui supplies its generic Role Skills and Context pointers. Project Skills remain
 ordinary Project files discovered natively by the Agent. Project Knowledge is
 maintained under `YUI_HOME`; copying repository material into a prompt does not

package/docs/roles-and-configuration.zh-CN.md

@@ -52,6 +52,32 @@ Provider 权限策略、Profile 访问意图和 Project 写范围是不同的合
 不授予对另一个 Project 的写入。受管工作区 owner、精确 Assignment 和资源 grant
 落实 Yui 操作；宽泛的原生权限不是 OS 沙箱。
 
+以 write 意图在自己 Task-owned main 工作区启动的 delivery Leader，从该工作区
+捕获已绑定 Project 的写域，不要求存在 open WorkItem；已接受结果也不会移除这个
+直接交付写域。显式 Assignment（包括空写域）仍决定受派发执行的范围。
+Planning、read 意图执行和全局 Role 不获得这个 Task-main 写域；Reviewer 仍只可写
+精确的 Review 工作区。Project 实际操作重新校验当前 Session 的冻结写域、Task
+生命周期和工作区 owner；它不授权稳定 Project checkout、其他 Task、私有
+Worker/Review 工作区或 Home 修改。
+
+受管 Leader 的 Integration 目标必须是 Task-main 分支，且该分支实际 checkout
+在捕获的 Task-main 目录。入场、检查及目标 CAS 都重新校验此边界；
+`--target` 不授予对同仓库另一工作区的写入。
+
+`integration abort` 可以把已发生的 CAS 确认为 committed，而不授予新项目写域。
+结算仍校验当前 delivery 身份、捕获的 Task-main 归属、实际 checkout、
+候选及检查/Job 证据。未执行的 CAS 仍是项目写操作，必须具备完整写域。
+
+运行时更新后，旧的空写域 Session 仍保持空域，包括失败 Run 的普通 retry。
+Resume 不改变捕获的 Profile 访问意图或项目写域。先用
+`yui task role session inspect <task> leader --json` 读取 `session.effective`，
+再通过 `yui task role session new <task> leader --reason "<采用新写域>"`
+请求正式替换。替换自己时应结束当前 turn。Yui 确认清理并启动 successor 后，
+读回其 `executionAuthority`、`profileAccess`、`writeProjectIds` 和 workspace，
+确认后再编辑；替换请求本身不证明采用成功。精确 Run Context 与启动环境从同一
+冻结 effective snapshot 取得写域；模型、effort、accepted Candidate 和原验收
+历史保持不变。
+
 Yui 提供其通用 Role Skill 和 Context 指针。Project Skill 仍是由 Agent 原生发现的
 普通 Project 文件。Project Knowledge 维护在 `YUI_HOME` 下；把仓库材料复制进 prompt
 并不使其成为权威 Knowledge。

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` 查看它确切的权限和选项；阅读一份生命周期文档不授权

package/i18n/README.zh-CN.md

@@ -137,8 +137,9 @@ Agent 可以重新读取任务上下文，继续兼容的 Session，或在必要
 想直观看进展，可以在另一个终端运行 `yui web`。本地 Web 展示同一份任务与
 待回答问题，也允许发送消息、回答问题，以及显式 queue、steer 或 interrupt Task 输入。
 这些经认证的 Task 控制复用 CLI 的相同操作，不是另一套需要同步的任务系统。
-详情优先展示用户待办、原生会话活动、任务进展和关键结论；固定文件成果与交付证据
-按需展开。详见[用户关注与进展](../docs/observability/README.zh-CN.md#web-用户关注与进展)。
+详情分为四个页签：概览（用户待办、任务进展和关键决定）、交付（工作项、评审、
+集成与远程交付，按需读取）、运行（Role、原生会话活动、进行中的执行和用量）、
+记录（决定、里程碑、执行与问题的时间线）。详见[用户关注与进展](../docs/observability/README.zh-CN.md#web-用户关注与进展)。
 详见 [Web 权限](../docs/architecture/capabilities-and-resources.zh-CN.md#cli-与-web)
 和[输入时机](../docs/managed-turn-and-session-runtime.zh-CN.md#输入时机queuesteer-与-interrupt)。
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zq-silk/yui",
-  "version": "2.1.0",
+  "version": "2.3.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

@@ -19,6 +19,15 @@ not copied reports. Follow Runtime's `nextCursor` and `contentPage` rules:
 read the full relevant window and originals before disposition, without
 unconditionally walking unrelated history.
 
+Before WorkItem dispatch, put the complete bounded requirements in the WorkItem
+or explicitly select up to 16 relevant readable materials with repeated
+`--context-ref <store/refId@digest>` on `task work dispatch`. Obtain exact IDs and
+digests from current Task context list/inspect. Core freezes these selected
+values after the existing caller-scope checks; mentioning a record in `--input`
+does not select it or grant access. Missing, forbidden or changed references
+refuse dispatch before Provider startup: correct the selection or make the
+WorkItem self-contained, never ask the recipient to bypass expansion rejection.
+
 ## Select the applicable stage
 
 Use current lifecycle, latest intent and the Session's actual planning/delivery

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

@@ -378,7 +378,8 @@ After a ReviewRound is terminal, the Leader or authorized Operator owns
 `task work review cleanup <task>/<round>`. Preserve dirty diagnostic evidence
 and resolve it explicitly; do not ask a Reviewer to clean its own runtime
 after its final report. Cleanup can remain advisory at completion. Ordinary
-archive requires settled resources; explicitly authorized force archive preserves
+archive requires settled business and stopped execution, not complete physical
+release; safe resource retention is reported separately. Explicitly authorized force archive preserves
 unresolved resources and diagnostics under the shared
 [archive contract](../../yui-runtime/references/publication.md). The Leader
 does not gain independent archive authorization. An original explicit user

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

@@ -33,6 +33,10 @@ the files there, then run `integration continue`. No preceding
 `resolve --option manual-resolution` is required for an ordinary conflict.
 Core completes the matching Git operation, records the candidate, runs or
 recovers its exact checks and advances the original target by CAS.
+Keep that same attempt for ordinary resolution and record its rationale in
+the existing resolution/report evidence. A detached HEAD during a matching
+rebase is normal. Start another attempt only for a real input/baseline change
+or evidenced inability to resume safely, explaining that decision.
 
 Do not close the Task execution gate, stop unrelated work, create an
 InputRequest or end in passive waiting merely because Git conflicted.
@@ -86,6 +90,22 @@ Inspect all Jobs owned by the exact attempt, including an unbound Job;
 cancel and establish quiescence by exact identity before reusing or cleaning
 resources. Successful Job evidence and Task acceptance remain separate.
 
+After terminal settlement, `task integration cleanup <task>/<integration>`
+can release clean exact-owner temporary resources without waiting for Task
+archive. Save necessary reports in Task artifacts/results first. Cleanup
+preserves the attempt, fixed checks/logs and target receipts. Failure or abort
+never authorizes deleting uncommitted resolutions; preserve dirty material
+and resolve its disposition explicitly. Acknowledging an unknown Job is not
+physical stop evidence: cleanup also rechecks the recorded runner generation
+and physical workspace/log/runtime references. When those are proven absent,
+the acknowledged unknown result remains historical evidence, not a permanent
+physical-cleanup blocker.
+The same physical checks apply to every executed terminal Job, including a
+successful one: surviving child processes are not stopped by a result receipt.
+Integration resource preflight includes runtime ownership and renamed cleanup
+claims; retain unverified material for diagnosis without inferring new deletion
+authority from Task archive admission.
+
 Direct Task-main delivery is an alternative only when current delivery
 authority, ownership and the Task contract already permit it, with no other
 writer or active check using that workspace. Do not edit managed refs or the

package/skills/yui-operator/SKILL.md

@@ -268,6 +268,10 @@ After an authorized PR/MR operation or before archive, read
 [publication and archive boundaries](../yui-runtime/references/publication.md).
 Record confirmed delivery facts promptly. Completion does not authorize
 archive, and ordinary archive approval does not authorize `--force`.
+Distinguish settled business and stopped execution from safely retained
+physical resources. Ordinary archive may retain the latter; follow the shared
+archive diagnostics and exact cleanup actions instead of requesting force
+merely for old terminal Integration worktrees or preserved diagnostics.
 When the user explicitly authorizes force archive for an eligible terminal
 Task, archive even if delivery proof or cleanup is incomplete. Report the
 warnings and retained resources without claiming merge verification or physical

package/skills/yui-reviewer/SKILL.md

@@ -28,6 +28,11 @@ WorkItem Develop workspace, and never become a ChangeSet source.
 
 For a dispatched Review, the AgentRun Context Pack identifies the ReviewRound,
 frozen Project commits, and assigned workspace. Inspect those exact commits.
+For a Run-backed Candidate, read its frozen `source-run` reference whose
+`evidenceOf` names that Candidate, including every content page of the original
+report. A summary or a newer Run is not a replacement. Missing historical
+evidence is a bounded infrastructure diagnosis, not permission to read outside
+the inventory or require the Leader to manually copy a report.
 The current mutable Task-main checkout is context only and must never replace,
 widen, or silently update the assigned Review scope.
 
@@ -99,6 +104,9 @@ judgment; it does not accept the WorkItem or complete the Task. Preserve the
 ReviewRound record and workspace, and report any diagnostic changes. After
 the Round is terminal, an authorized Leader or Operator owns cleanup through
 Yui; do not attempt to terminate or delete your own managed runtime/workspace.
+Keep scratch in the supplied runtime `TMPDIR` and put required diagnostic
+evidence in durable results/artifacts; resource release must not erase the
+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.

package/skills/yui-runtime/SKILL.md

@@ -26,6 +26,10 @@ resource boundaries still apply; a planning Session does not gain delivery
 authority merely because the Task becomes active.
 Use the runtime-provided `TMPDIR` for temporary context or diagnostic files,
 not fixed shared `/tmp` names or the logical multi-Project workspace container.
+Save durable reports in Task artifacts/results before releasing their temporary
+workspace. Integration history and check evidence outlive its worktree; a
+terminal attempt is not an unresolved business input merely because resources
+remain. Cleanup inspects exact ownership and preserves unknown or dirty data.
 
 Ordinary commands use `yui` from the intended launch environment's PATH and
 `YUI_HOME`. Session/native identity, Task/Assignment/workspace authority and
@@ -178,6 +182,13 @@ public view. This offline view is only guidance, not an authenticated permission
 or a way to switch Roles. An incomplete or stale managed identity must not be
 cleared to obtain public execution authority.
 
+For Codex, the native `CODEX_THREAD_ID` takes precedence over the transport's
+`YUI_NATIVE_SESSION_ID`; a newly created thread can legitimately lack the latter.
+Other adapters do not borrow Codex identity for offline discovery. A missing
+transport variable or hidden help entry alone does not prove Session failure.
+Discovery does not establish that a Session is current: actual execution still
+revalidates Session, Task/Assignment, workspace, resource and Grant boundaries.
+
 When capability discovery appears in that view, use `capability search` for
 templates and `capability describe <name> --task
 <task-id> --input '<json>'` for supported exact authorization assessments.

package/skills/yui-runtime/references/publication.md

@@ -94,6 +94,14 @@ the exact Task, checks archive eligibility, then uses `--integrated` for verifie
 merged delivery or `--abandon` for deliberate non-delivery. General archive
 approval never implies `--force` authority. Preserve the Task record.
 
+Ordinary archive requires settled business, exact delivery (or authorized
+abandonment), and proven stopped execution. It commits logical archive before
+one foreground resource cleanup. Safe physical retention—dirty diagnostics,
+missing-path recovery gaps, or remaining Git registrations—is not a reason to
+force archive or rewrite old Integration outcomes. Terminal failed/superseded
+Integration history stays readable; an active/conflicted attempt or unknown
+execution still requires settlement.
+
 With explicit force authorization for a completed or cancelled (retired) Task, use
 `yui task archive <task> (--integrated|--abandon) --force`. Force commits the
 archive and stops new Task scheduling before attempting safe foreground cleanup.
@@ -108,10 +116,18 @@ cannot be safely released stay owned and traceable. Late runtime events remain
 source evidence, not authority to resume or settle unknown input.
 
 Read `task show <task> --json` for `data.archive.warnings`,
-`data.archive.retainedResources` and `data.archive.cleanupEvents`;
-`task context` also retains the original records/events. A successful archive
+`data.archive.retainedResources` and `data.archive.cleanupEvents`. These bounded
+views include counts and inspection actions; read the existing paginated
+`task event list` and Task context resource inventory for omitted evidence.
+A successful archive
 exit means `archived=true`, not that cleanup fully succeeded. `cleanupFinished`
 means the foreground pass finished, not that every resource was removed.
+`allResourcesReleased` separately requires release evidence and no retained
+resources. Historical warnings do not disappear after a successful later pass.
 If cleanup was interrupted, the Task stays archived. Repeating archive only
-reports current facts; use explicit, exact-owner resource operations after
-inspection instead of re-running broad cleanup. No background retry is implied.
+reports current facts. After inspecting the exact retained owner/reason, use
+`task archive-cleanup <task>` for one new bounded pass, or the reported
+WorkItem/Review/Integration cleanup entry. Every pass rechecks current identity,
+runtime and Git registration facts; it is not an atomic batch and does not
+discard unknown material. Registry-only remnants require the existing resource
+inspection route, not a global `worktree prune`. No background retry is implied.

package/skills/yui-worker/SKILL.md

@@ -109,3 +109,6 @@ reject it for missing headings or invalid JSON.
 
 Leave managed workspaces intact after handoff. Their owner lifecycle and
 cleanup belong to the Leader and Yui Core.
+Keep disposable tools/cache in the supplied runtime `TMPDIR`, not the logical
+multi-Project container. Preserve required handoff evidence in durable
+results/artifacts before its temporary workspace is released.