@zq-silk/yui 0.15.8 → 0.15.11

package/skills/yui-runtime/SKILL.md

@@ -91,6 +91,33 @@ Global context grants no Task implementation workspace. Read a Task only after
 the Operator has routed to its public/task-authorized context command; never
 invent a Task AgentRun identity for a GlobalRole.
 
+A GlobalRole's durable input uses the same three actions as a Task Role,
+addressed by the Role's own name instead of a Task: `yui role message
+queue|steer <global-role>` and `yui role interrupt <global-role>`. Queue and steer
+save an owned Message; bare interrupt records a control request, not a new
+Message. Each uses a stable request id and that Role's own Session; none fabricates a Task or
+runId to reuse Task-scoped delivery. `queue` delivers at the Role's next legal
+opportunity and is idempotent by request id. `steer` and `interrupt` affect only
+the exact current native Turn — a stale `--expected-target`, an incapable plan,
+or an unproven delivery leaves the Message saved and reports the reason, and
+`interrupt` stops only through the Provider's native cancel with an optional
+`--then-message` naming one already-saved GlobalRole Message. When the Role holds
+no live managed Turn, a steer or interrupt is `NO_ACTIVE_TURN` and never falls
+back to another action.
+
+New controlled Global Sessions use the existing Host console, not the native
+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
+`interrupt-requested` is not a stopped Turn or stopped background resources.
+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.
+
 ## Preserve intent and authority
 
 An analysis, diagnosis, or review request is read-only unless the user also

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

@@ -20,3 +20,23 @@ Completion does not authorize archive. 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.
+
+With explicit force authorization for a completed or retired Task, use
+`yui task archive <task> (--integrated|--abandon) --force`. Force commits the
+archive and stops new Task scheduling before attempting safe foreground cleanup.
+Missing/stale delivery evidence, unresolved execution and cleanup errors become
+warnings with retained resource references; they do not block that commit.
+Authority, lifecycle, identity and mandatory audit persistence still fail closed.
+
+Force does not verify a merge, accept work, stop unknown execution, discard dirty
+data or imply abandonment. Keep the requested disposition and original
+Publication/completion evidence. Unverified local commits and resources that
+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 `archive.warnings`, `retainedResources` and
+cleanup events; `task context` also retains the original records/events. A
+successful archive exit means `archived=true`, not that cleanup fully succeeded.
+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.