@zq-silk/yui 1.1.0 → 2.0.0

package/skills/yui-leader/references/task-plugins.md

@@ -1,7 +1,7 @@
 # Task-local capabilities
 
 Read this before creating, validating or activating a Task-local plugin.
-Use the stable Session CLI's capability directory and read the exact schema
+Use the `yui` CLI's capability directory and read the exact schema
 before each unfamiliar operation. Prefer an existing tool, composition or
 one-off script unless a reusable named capability is useful.
 
@@ -17,7 +17,9 @@ the exact plugin id, digest, environment, trust and phase, within its remaining
 uses and validity. A source change cannot inherit an old digest's grant.
 Trusted-local subprocesses are not an OS sandbox.
 
-Never issue your own grants, impersonate Operator, change global configuration,
+Use [source-authorized capabilities](authorization.md) when original user input
+already authorizes the exact Task plugin/resource. Never invent grants,
+impersonate Operator, change global configuration,
 or modify the core installation, namespace or carrying Endpoint to obtain a
 tool. Request only a genuinely missing resource or trust boundary, not authority
 already available. Plugin grants do not authorize unrelated external effects.

package/skills/yui-operator/SKILL.md

@@ -227,8 +227,15 @@ a dormant Role and verify the complete binding before the next launch.
 
 ## Present current progress
 
-Use JSON reads and their top-level `data` field. Report the facts needed to
-understand the outcome:
+Use JSON reads and their top-level `data` field.
+Use Global Context's `pending`/`recent` pages to find Messages, then
+`role message show operator <id>` for the original. A successful send receipt
+contains saved identity and delivery/control facts, not another copy of the
+submitted body. Follow Runtime's bounded-read contract for list continuations
+and long `contentPage` details; do not decode `output` as nested JSON or print
+an entire Context again merely to extract one already-returned reference.
+
+Report the facts needed to understand the outcome:
 
 - Task ID, Projects, recorded bases, and lifecycle;
 - current WorkItems, ownership, dependencies, and acceptance state;

package/skills/yui-runtime/SKILL.md

@@ -17,8 +17,8 @@ workspace layout, native transcript, or an earlier AgentRun.
 ## Enter through the current context
 
 There are two normal Task entry points. A user may continue directly with the
-current, unrevoked Leader Session: read current context using the Session CLI
-with `task context <task-id> --json`. Do not request a self-wake, reopen a Task,
+current, unrevoked Leader Session: read current context using
+`yui task context <task-id> --json`. Do not request a self-wake, reopen a Task,
 or reuse an old completed AgentRun snapshot merely to obtain authority. Pending
 delivery, unknown execution evidence and missing reports do not themselves
 revoke Session authority. Task lifecycle, scope, Assignment, workspace and
@@ -27,26 +27,35 @@ 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.
 
+Ordinary commands use `yui` from the intended launch environment's PATH and
+`YUI_HOME`. Session/native identity, Task/Assignment/workspace authority and
+Controller protocol/storage checks still apply; they do not distinguish every
+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.
+
 For every explicitly dispatched managed Task AgentRun:
 
 1. Read the exact AgentRun identity from the newest Bootstrap Envelope.
-2. Before acting, load its authorized pack with the Session CLI named by the
-   current Session Manifest:
+2. Before acting, load its authorized pack using the current Session Manifest's
+   Context command and the exact Task/Run identity:
 
    ```sh
-   "$YUI_SESSION_CLI" task run context "$YUI_TASK_ID/<run-id>" --json
+   yui task run context "<task-id>/<run-id>" --json
    ```
 
 3. Verify that the returned Task, AgentRun, Role, purpose, Snapshot digest, workspace,
    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 pack summaries and pointers first. Expand only an authorized ref when
+4. Use the pack's `pointers` (including each pointer's summary) first. They are
+   the single readable-ref inventory; `deltaRefs` contains only changed identities.
+   Expand only an authorized ref when
    its full value is needed, selecting it by the pointer's exact `store` and
    `refId`:
 
    ```sh
-   "$YUI_SESSION_CLI" task run context expand "$YUI_TASK_ID/<run-id>" <ref-id> --store <store> --mode full --json
+   yui task run context expand "<task-id>/<run-id>" <ref-id> --store <store> --mode full --json
    ```
 
    `--store` is required, even when the ref id is unique. Select both fields
@@ -119,14 +128,47 @@ 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. Read the referenced Message in full
-from Session Context. Native/transport acceptance is not implementation, and
+Context reads never consume queue entries. Global Context returns bounded
+`pending` and `recent` discovery pages, not Message bodies. 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.
+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.
 Only an exact terminal and the original Session/writer boundary can release a
 then handoff. An accepted or unconfirmed steer must not be submitted again by
 changing its request id or composing then. A conclusive rejection permits an
 explicit new control attempt; uncertainty does not.
 
+## Read bounded information completely when required
+
+Structured CLI results live in the top-level `data`, not a JSON-encoded
+`output` string. Task current Context includes bounded current facts and
+message references; it does not include event or terminal Run history.
+`collections` and `attention` identify incomplete discovery. Use
+`task context list <task> --store <store> [--cursor <cursor>]` to discover one
+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.
+
+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
+`--cursor <contentPage.nextCursor>` until `complete: true`. Concatenate `text`
+in offset order and parse the combined JSON once, retaining the same source
+and digest. A source-change error requires a fresh read, not mixing old and
+new chunks. Never use a read cursor to repeat a mutation.
+
+Read all pages of a relevant original requirement, result, or authorization
+before acting on it. For a wake, read its complete fixed window and the
+referenced original Messages; the wake itself contains pointers, not reports.
+For unrelated discovery, stop once the necessary evidence is found. Task
+event deltas retain their fixed upper bound and are history, not replacement
+current state. No read acknowledges implementation or consumes a queue.
+
 ## Preserve intent and authority
 
 An analysis, diagnosis, or review request is read-only unless the user also

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

@@ -87,7 +87,9 @@ is not Candidate acceptance, Review, Integration or Task completion.
 
 ## Archive separately
 
-Completion does not authorize archive. The Operator obtains authorization for
+Completion does not authorize archive. A delivery Leader with original user
+authorization may use [ordinary archive](../../yui-leader/references/authorization.md);
+this grants no force or abandonment authority. Otherwise the Operator obtains authorization for
 the exact Task, checks archive eligibility, then uses `--integrated` for verified
 merged delivery or `--abandon` for deliberate non-delivery. General archive
 approval never implies `--force` authority. Preserve the Task record.