@zq-silk/yui 2.2.0 → 2.3.0

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.2.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/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

@@ -104,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

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.