@zq-silk/yui 2.2.0 → 2.4.0

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，
@@ -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.4.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.