@zq-silk/yui 2.7.1 → 2.8.1

package/skills/yui-reviewer/SKILL.md

@@ -90,6 +90,35 @@ request a follow-up Round yourself.
 Use Project Skills, Policy and Knowledge for project-specific checks. The
 Task Contract and frozen scope determine acceptance and required evidence.
 
+## Derive scenarios, then inspect the complete candidate
+
+Read the frozen Task/WorkItem requirements, non-goals and applicable decisions
+before using the author's explanation. The frozen Brief is a summary and material
+index, not the contract body. Follow its relevant same-Task commit-pinned artifact
+references with `task artifact read <task> <path> <commit>`; expand Context pointers
+and their content pages as required. A path in prose grants no additional access.
+Report missing or conflicting evidence instead of replacing it with a newer head.
+
+Derive observable expectations from requirements and independent contracts, not
+from the current implementation or its mocks. Trace the complete authorized
+change and necessary callers, consumers, state and side effects. Select
+complementary perspectives according to risk: user paths, producer/consumer
+contracts, state/data invariants, failure and partial recovery, authorization,
+and whether verification tests the actual contract. Multiple perspectives do
+not require multiple Agents or every perspective on every task.
+
+Turn applicable perspectives into concrete scenarios, expected behavior and
+evidence. Challenge important assumptions with the smallest reachable
+counterexample; check normal controls and non-goals too. A shared assumption
+between a mock and implementation is not independent confirmation. Reuse valid
+checks; do not run external-resource validation without its exact authorization.
+Stop neither at the changed lines nor after finding a few defects.
+
+For an ordinary full re-review, inspect the current complete frozen candidate
+and requirements, using the repair delta, prior finding dispositions and still
+applicable evidence as guidance, not a scope ceiling. An explicitly assigned
+Delta Recheck retains its narrower equivalence contract above.
+
 Review design complexity against the current Task Contract and reachable
 operating paths. Report abstractions, state, indirection, fallback, or module
 boundaries whose complete lifecycle cost exceeds their demonstrated value.
@@ -117,6 +146,12 @@ 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.
+Include a short account of the perspectives/scenarios actually inspected and
+material unexamined risks, not a copied checklist. Each confirmed finding should
+identify its trigger, violated expectation, impact and supporting evidence;
+merge one root cause without losing its affected entry points. Distinguish
+uncertain reachability or missing verification from a confirmed defect. There
+is no finding quota, mandatory perspective count or claim of exhaustive coverage.
 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

package/skills/yui-reviewer/VERSION

@@ -1 +1 @@
-2
+3

package/skills/yui-runtime/SKILL.md

@@ -79,6 +79,15 @@ installation with the same protocol and storage versions. If the entry or Home
 is wrong or unavailable, report that fact and use the explicitly authorized
 entry/environment; do not guess another installation or clear Session identity.
 
+Desktop commands may carry only `CODEX_THREAD_ID`. The CLI resolves that native
+identity in the selected Home's current Session registry before routing Task or
+Global operations. Environment and Manifest values are location hints, not
+continuing grants. Conflicting, unregistered, replaced or revoked identities
+do not become public-user callers; a plain user terminal has no managed/native
+identity. `inbox list` reports the resolved current identity. Do not add or clear
+environment fields to repair a mismatch. Without a Manifest environment pointer,
+`session skills` returns current Skill paths and the Session's captured profile.
+
 For every explicitly dispatched managed Task AgentRun:
 
 1. Read the exact AgentRun identity from the newest Bootstrap Envelope.
@@ -93,8 +102,15 @@ For every explicitly dispatched managed Task AgentRun:
    and Adapter match the Envelope and Session Manifest. Stop and report a
    context-load failure if the pack is missing, stale, unauthorized, malformed,
    or mismatched. Never request an inline/full-prompt fallback.
-4. Use the pack's `pointers` (including each pointer's summary) first. They are
-   the single readable-ref inventory; `deltaRefs` contains only changed identities.
+4. Use the entry's `pointers` (including each pointer's summary) first. They are
+   a bounded window into the frozen readable-ref inventory. `pointerPage`
+   reports total/complete/nextCursor; discover further relevant refs with
+   `task run context <task>/<run> --view refs [--cursor <cursor>]`.
+   `deltaRefs` samples changed identities, with `deltaRefsTotal` reporting coverage.
+   `--view full` explicitly reads the complete pack when needed; do not load or
+   traverse every historical reference merely to make an entry window complete.
+   If `input.directiveOmitted` is true, read the complete assigned input with
+   `--view input` before acting; its entry summary is not the instruction body.
    Expand only an authorized ref when
    its full value is needed, selecting it by the pointer's exact `store` and
    `refId`:
@@ -173,13 +189,20 @@ TUI, with the configured Agent, permissions and workspace unchanged. A live
 unmanaged Session is not silently replaced or adopted; use an explicit Session
 lifecycle action before enabling controlled delivery.
 
-Context reads never consume queue entries. Global Context returns bounded
-`pending` and `recent` discovery pages, not Message bodies. Read a referenced
+Context reads never consume queue entries. Global Context returns a bounded
+`pending` discovery page, not Message bodies, Profile bodies, recent history or
+accumulated retry details. The Manifest retains the exact Role profile.
+Read a referenced
 original with `role message show <role> <message-id> --json`. Follow a pending
 page's `nextCursor` using `role message list <role> --pending --cursor <cursor>`
 when it is incomplete; accepted delivery does not erase the Message from the
 separate all-message list. Native/transport acceptance is not implementation, and
 `interrupt-requested` is not a stopped Turn or stopped background resources.
+`role message list <role> --diagnostics` projects repeated classified failures
+from original evidence with first/latest occurrence, count and recovery evidence.
+`--diagnostic <key>` pages the original affected observations. Counts cover
+distinct observations, not repeated polling of one identity. A recovery notice
+is neither an input acknowledgement nor proof that prior effects were undone.
 Saving a Task Message or Brief is not notification delivery to Operator. A
 Task Role uses the existing Task InputRequest path for a genuinely missing
 user decision, not global Role input controls or fabricated progress questions.
@@ -238,15 +261,32 @@ Retirement preserves the original claim and records the management decision;
 it neither fabricates an acknowledgement nor proves native execution stopped.
 An unfinished claim fences its Assignment, not unrelated work of the same Role.
 
-In-flight, unknown, previously delivered, explicit interrupt-then and
+In-flight, unknown, not-yet-delivered explicit interrupt-then and
 unsettled steer inputs retain their existing owner/receipt and report a bounded
 reason instead of being taken over. Use existing exact-receipt recovery when
 needed; do not change request IDs, clear identity, or copy input to bypass it.
 A steer with no control receipt was not submitted; it may be explicitly handled
 and acknowledged in its authorized inbox, without converting it into a queue.
 An accepted notification still follows its normal handling path, not another
-inbox delivery. Original Messages, wake windows and handling receipts remain
-readable after acknowledgement.
+native delivery. Accepted Global inputs, delivered Leader windows and current
+Assignment continuations remain in the inbox until explicitly handled. Claim the
+received entry, inspect its originals and existing effects, then ack with a
+concrete disposition (including result or effect receipt references when useful).
+This claim never sends the input again. A current rightful successor may settle
+an accepted Global input or Leader window while retaining the original delivery
+target; it must inspect prior effects first. Pending/unknown acceptance stays
+blocked and cannot use claim as a replay path.
+
+An ack belongs to the exact original and revision: fixed windows pin
+`message.updated` event identities, including same-timestamp edits. A later
+revision still needs its own handling. Before Task completion, settle handled
+user-input windows; native acceptance or a terminal does not settle them.
+Original Messages, wake windows and handling receipts remain readable after
+acknowledgement. Lost context, Session continuation and installation upgrades
+do not reset receipts. If ack fails after an external effect, read back the
+original claim and the external receipt before retrying the same ack; do not
+repeat the effect. This is durable handling evidence, not arbitrary external
+exactly-once execution.
 
 ## Read bounded information completely when required
 
@@ -259,6 +299,12 @@ family, then `task context inspect <task> --store <store> --ref <refId>
 --digest <digest>` to read its exact current value. Common Task lists use the
 same `items`, `total`, `complete`, and `nextCursor` contract. Do not treat the
 first page or a summary as complete requirements.
+The 32 KiB compact-JSON read budget includes nested data, cursors and structure;
+summaries are at most 512 UTF-8 bytes. Current Task Message discovery excludes
+explicit acknowledgements and retirements, not uncertain delivery. Use
+`--view current` for its continuation and the default all view for history.
+Skill checks remain metadata-only; unusually large checks use the same explicit
+document pagination. A small default window is not a request to fetch all history.
 
 Long detail reads return `contentPage` instead of the ordinary value (under
 `data.context` for Run context/expand, `data.contextDelta` for Run Context delta). Repeat the same read with

package/skills/yui-runtime/VERSION

@@ -1 +1 @@
-3
+6

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

@@ -143,11 +143,30 @@ If exact native stop or inspection fails, read the persisted diagnostic and
 resolve that resource boundary; do not kill arbitrary processes, clear unknown
 execution records, or modify managed refs, tmux Sessions or state files.
 
-Breaking upgrades require a clean runtime environment; Yui does not discover,
-convert or inherit historical Hosts and processes. Storage migration is a
-separate explicit operation, not proof of runtime continuity. Do not interpret
-missing compatibility diagnostics as permission to reuse an old process,
-discard pending intent or bypass exact ownership and stop confirmation.
+Compatible upgrades preserve logical Sessions. Build generations and historical
+Skill packages are provenance, not continuation gates. Load current stable
+Skills and current authority; never change a user's model, account, native
+permissions or workspace to make an upgrade work.
+
+Within Host control/event v1, status advertises `controlCapabilities` and the
+loaded `hostImplementation`, independently of `endpointImplementation`. Missing
+capabilities or `eventDelivery` are unreported, not healthy. A Controller must
+not repeatedly send an unsupported `reconcile-turn`; the existing raw Inbox
+still permits exact event consumption without executing the input again.
+Current Hosts retain unpersisted original facts during a filesystem failure;
+keep that process alive until persistence recovers. Those volatile bytes cannot
+be recovered after process loss merely by restarting the Controller.
+
+Program/storage upgrade success does not mean Host replacement succeeded.
+Compatible live Hosts may continue, including busy ones. A new Host may resume
+the same native Session only through the existing authorized lifecycle after
+exact execution, background resources and writer release are proven. An idle
+status, a stopped proxy or a missing control field is insufficient. Unknown
+effects preserve the original Session, input and resources; do not force-kill,
+replay, hot-replace loaded modules or silently create a new Session. Existing
+explicit stop/replacement authority is separate from an ordinary upgrade.
+Unsupported protocols require an explicit bounded recovery plan, not arbitrary
+historical Host adoption. Storage migration remains independently fenced.
 
 After repeated failure of the same bounded recovery, report the observed
 cause, impact and smallest remaining options. Do not broaden cleanup or add