@zq-silk/yui 2.19.0 → 2.21.0

package/dist/executor/taskAgentCapabilities.js

@@ -3,7 +3,7 @@ import { projectAgentCapabilityConfig } from "./agentCapabilityConfig.js";
 import { activeRoleAgentBinding } from "../role/role.js";
 import { configuredAgentFingerprint, readAgentFailureContext } from "../runtime/agentFailureContext.js";
 import { resolveManagedTaskReader } from "../runtime/managedCaller.js";
-import { assertContextRecordReadable } from "../context/taskContext.js";
+import { assertTaskReadable } from "../context/taskContext.js";
 /** Resolve authority and scope before any native metadata process is started. */
 export function resolveTaskAgentCapabilities(query, store, environment = {}) {
     const { taskId, roleName, errorId } = query;
@@ -19,7 +19,7 @@ export function resolveTaskAgentCapabilities(query, store, environment = {}) {
     let expectedFingerprint;
     let expectedComponent;
     if (errorId !== undefined) {
-        assertContextRecordReadable(store, taskId, "task-event", errorId, environment);
+        assertTaskReadable(store, taskId, environment);
         const event = store.listEventsByType(taskId, ["runtime.agent-error"]).find(event => event.id === errorId);
         if (event === undefined || event.payload.roleName !== roleName) {
             throw usageError("Agent failure is not owned by this Task/Role.");

package/dist/output/rolePresentation.js

@@ -54,6 +54,7 @@ export function renderRoleDetails(title, role, input) {
         ...(!isEnabled(role) ? [`  Availability     ${roleDisabledReason(role)}`] : []),
         `  Active Agent     ${role.activeAgentId}`,
         `  Workspace        ${role.workspace}`,
+        `  Instance code    ${role.instanceCode ?? "-"} (display only; next Session launch)`,
         ...("taskId" in role ? [
             `  Desired environment ${role.executionEnvironment === undefined
                 ? "managed workspace"

package/dist/role/instanceCode.js

@@ -0,0 +1,7 @@
+export function validateInstanceCode(value) {
+    if (typeof value !== "string" || value.length === 0 || value.length > 24
+        || !/^[\p{L}\p{N}\p{M}_-]+$/u.test(value)) {
+        throw new Error("Instance code must be 1–24 UTF-16 units of Unicode letters, numbers, marks, '_' or '-'; omit '@'.");
+    }
+    return value;
+}

package/dist/role/role.js

@@ -1,4 +1,5 @@
 import { isDeepStrictEqual } from "node:util";
+import { validateInstanceCode } from "./instanceCode.js";
 import { assertRoleEnabled, validateEnabled } from "./availability.js";
 import { requireKnownFields } from "../domain/validation.js";
 import { jobScopeKey } from "../job/jobDefinition.js";
@@ -49,6 +50,7 @@ export function copyGlobalRoleToTaskRole(globalRole, taskId, now, name = globalR
     const timestamp = now.toISOString();
     return validateTaskRole({
         ...cloneProfile(globalRole),
+        ...(globalRole.instanceCode === undefined ? {} : { instanceCode: globalRole.instanceCode }),
         schemaVersion: 1,
         enabled: true,
         launchRevision: 1,
@@ -75,6 +77,8 @@ export function updateGlobalRole(role, patch, now) {
         updatedAt: now.toISOString()
     };
     clearProfileFields(updated, patch);
+    if (Object.hasOwn(patch, "instanceCode") && patch.instanceCode === undefined)
+        delete updated.instanceCode;
     updated.launchRevision = isDeepStrictEqual(desiredBefore, desiredLaunchProjection(updated))
         ? role.launchRevision
         : role.launchRevision + 1;
@@ -94,6 +98,8 @@ export function updateRole(role, patch, now) {
         updated.executionEnvironment = cloneJson(patch.executionEnvironment);
     }
     clearProfileFields(updated, patch);
+    if (Object.hasOwn(patch, "instanceCode") && patch.instanceCode === undefined)
+        delete updated.instanceCode;
     updated.launchRevision = isDeepStrictEqual(desiredBefore, desiredLaunchProjection(updated))
         ? role.launchRevision
         : role.launchRevision + 1;
@@ -222,6 +228,7 @@ function createRoleOwner(name, bindings, activeAgentId, workspace, now, profile,
     const timestamp = now.toISOString();
     return {
         ...cloneProfile(profile),
+        ...(profile.instanceCode === undefined ? {} : { instanceCode: validateInstanceCode(profile.instanceCode) }),
         enabled: true,
         launchRevision: 1,
         defaultAccess,
@@ -234,6 +241,8 @@ function createRoleOwner(name, bindings, activeAgentId, workspace, now, profile,
     };
 }
 function validateRoleOwner(role) {
+    if (role.instanceCode !== undefined)
+        validateInstanceCode(role.instanceCode);
     validateEnabled(role.enabled);
     if (role.schemaVersion !== 1) {
         throw new Error("Role schema version is invalid.");
@@ -303,6 +312,7 @@ function assertSessionOwnerMatchesRole(role, sessions) {
 }
 function cloneRolePatch(patch) {
     return {
+        ...(patch.instanceCode === undefined ? {} : { instanceCode: validateInstanceCode(patch.instanceCode) }),
         ...(patch.enabled === undefined ? {} : { enabled: patch.enabled }),
         ...(patch.name === undefined ? {} : { name: requireSafeIdentity(patch.name, "Role name") }),
         ...(patch.activeAgentId === undefined

package/dist/runtime/agentEndpoint.js

@@ -81,6 +81,7 @@ class BuiltinAgentEndpoint {
     driver;
     configuration;
     get nativeAccess() { return this.driver.nativeAccess; }
+    get appliedGeneratedTitle() { return this.driver.appliedGeneratedTitle; }
     get ownedProcessId() { return this.driver.ownedProcessId; }
     get nativeAccountHome() { return this.driver.nativeAccountHome; }
     capabilities;

package/dist/runtime/agentHost.js

@@ -120,7 +120,13 @@ export async function runAgentHost(input) {
     const recentSteerAttempts = new Map();
     await replayExitOutbox(input.home);
     const updateSnapshot = (next) => {
-        snapshot = validateSnapshot(next);
+        const { appliedGeneratedTitle: _oldTitle, ...rest } = next;
+        snapshot = validateSnapshot({
+            ...rest,
+            ...(session?.appliedGeneratedTitle === undefined ? {} : {
+                appliedGeneratedTitle: session.appliedGeneratedTitle
+            })
+        });
     };
     const authorityFields = () => ({
         ...(session === undefined ? {} : { endpointImplementation: session.configuration.implementation }),
@@ -374,6 +380,8 @@ export async function runAgentHost(input) {
                         && currentPayload.environment.YUI_ROLE === "operator")
                     ? {}
                     : { sessionTitle: previousControl.sessionTitle }),
+                ...(previousControl.previousSessionTitle === undefined
+                    ? {} : { previousSessionTitle: previousControl.previousSessionTitle }),
                 codexThread: disconnectedSession.configuration.threadOptions,
                 endpointImplementation: disconnectedSession.configuration.implementation,
                 ...(ownedTurn === undefined ? {} : { ownedTurn }),

package/dist/runtime/launchBroker.js

@@ -167,6 +167,9 @@ function validateProviderControl(control) {
             throw new Error("Agent Host Provider session title is invalid.");
         }
     }
+    if (control.previousSessionTitle !== undefined) {
+        text(control.previousSessionTitle, "previousSessionTitle");
+    }
     validateProviderAuthorityFence(control.authority);
 }
 function validateCodexThreadOptions(options) {

package/dist/runtime/runtimeBinding.js

@@ -15,6 +15,9 @@ export function createRuntimeBinding(input) {
         ...(input.nativeSessionId === undefined
             ? {}
             : { nativeSessionId: requireText(input.nativeSessionId, "Native session id") }),
+        ...(input.appliedGeneratedTitle === undefined ? {} : {
+            appliedGeneratedTitle: requireText(input.appliedGeneratedTitle, "Applied generated title")
+        }),
         ...(input.providerAuthority === undefined
             ? {}
             : { providerAuthority: validateProviderAuthorityFence(input.providerAuthority) })

package/dist/runtime/sessionTitle.js

@@ -1,29 +1,33 @@
 import { resolveTimeZone } from "../config/timeZone.js";
+import { validateInstanceCode } from "../role/instanceCode.js";
 const TITLE_SEPARATOR = " · ";
 export const MAX_SESSION_TITLE_LENGTH = 80;
 const TASK_TITLE_MAX_LENGTH = 20;
-export function taskRoleSessionTitle(task, roleName) {
-    const prefix = `Yui ${roleLabel(roleName)} ${normalizeSegment(task.id)}`;
+export function taskRoleSessionTitle(task, roleName, options = {}) {
+    const prefix = `Yui ${roleLabel(roleName)} ${normalizeSegment(task.id)}`
+        + (roleName === "leader" && options.executionAuthority === "planning" ? " Draft" : "")
+        + instanceSegment(options.instanceCode);
     const title = displayTitle(normalizeSegment(task.title), TASK_TITLE_MAX_LENGTH);
     const full = `${prefix}${TITLE_SEPARATOR}${title}`;
     if (full.length <= MAX_SESSION_TITLE_LENGTH)
         return full;
     if (prefix.length + TITLE_SEPARATOR.length + 1 > MAX_SESSION_TITLE_LENGTH) {
-        return truncate(prefix, MAX_SESSION_TITLE_LENGTH);
+        throw new Error("Session title identity exceeds the maximum length; shorten the Role name or instance code.");
     }
-    const titleLength = MAX_SESSION_TITLE_LENGTH - prefix.length - TITLE_SEPARATOR.length - 1;
+    const titleLength = MAX_SESSION_TITLE_LENGTH - prefix.length - TITLE_SEPARATOR.length;
     return `${prefix}${TITLE_SEPARATOR}${displayTitle(title, Math.max(titleLength, 1))}`;
 }
-export function resolveTaskRoleSessionTitle(existingTitle, task, roleName) {
+export function resolveTaskRoleSessionTitle(existingTitle, task, roleName, options = {}) {
     if (existingTitle !== undefined
         && existingTitle.length > 0
         && existingTitle.length <= MAX_SESSION_TITLE_LENGTH
-        && !/[\r\n\0]/u.test(existingTitle)) {
+        && !/[\r\n\0]/u.test(existingTitle)
+        && existingTitle !== options.generatedTitle) {
         return existingTitle;
     }
-    return taskRoleSessionTitle(task, roleName);
+    return taskRoleSessionTitle(task, roleName, options);
 }
-export function operatorSessionTitle(now, configuredTimeZone) {
+export function operatorSessionTitle(now, configuredTimeZone, instanceCode) {
     if (!(now instanceof Date) || !Number.isFinite(now.getTime())) {
         throw new TypeError("Operator session title date is invalid.");
     }
@@ -35,7 +39,23 @@ export function operatorSessionTitle(now, configuredTimeZone) {
     if (parts.month === undefined || parts.day === undefined) {
         throw new TypeError("Operator session title date is unavailable.");
     }
-    return `Yui${TITLE_SEPARATOR}Operator${TITLE_SEPARATOR}${parts.month}${parts.day}`;
+    const prefix = instanceCode === undefined
+        ? `Yui${TITLE_SEPARATOR}Operator`
+        : `Yui Operator${instanceSegment(instanceCode)}`;
+    return `${prefix}${TITLE_SEPARATOR}${parts.month}${parts.day}`;
+}
+export function globalRoleSessionTitle(roleName, now, configuredTimeZone, instanceCode) {
+    if (roleName === "operator")
+        return operatorSessionTitle(now, configuredTimeZone, instanceCode);
+    if (instanceCode === undefined)
+        return undefined;
+    const title = `Yui ${roleLabel(roleName)}${instanceSegment(instanceCode)}`;
+    if (title.length > MAX_SESSION_TITLE_LENGTH)
+        throw new Error("Session title identity exceeds the maximum length.");
+    return title;
+}
+function instanceSegment(value) {
+    return value === undefined ? "" : ` @${validateInstanceCode(value)}`;
 }
 function displayTitle(value, maxLength) {
     if (value.length <= maxLength)

package/dist/runtime/structuredProviderHost.js

@@ -384,6 +384,7 @@ class CodexStructuredProviderSession {
     onActivity;
     mirror;
     nativeAccountHome;
+    appliedGeneratedTitle;
     nativeAccess;
     #turnAttempts = new Map();
     adapterId = "codex";
@@ -445,12 +446,20 @@ class CodexStructuredProviderSession {
                 throw error;
             }
         }
-        if (control.sessionTitle !== undefined) {
+        const threadMetadata = nativeConfiguration.thread;
+        const nativeTitle = typeof threadMetadata === "object" && threadMetadata !== null
+            && !Array.isArray(threadMetadata) ? threadMetadata.name : undefined;
+        // A native rename belongs to the user. Missing metadata is not evidence
+        // that an old title is still ours; leave it alone on resume.
+        let appliedGeneratedTitle;
+        if (control.sessionTitle !== undefined && (control.mode === "new"
+            || (control.previousSessionTitle !== undefined && nativeTitle === control.previousSessionTitle))) {
             try {
                 await runtime.setConversationName({
                     conversationId,
                     name: control.sessionTitle
                 });
+                appliedGeneratedTitle = control.sessionTitle;
             }
             catch (error) {
                 onDiagnostic?.({
@@ -465,6 +474,7 @@ class CodexStructuredProviderSession {
         }
         const session = new CodexStructuredProviderSession(child, exit, processInstanceId, conversationId, runtime, onStarted, onTerminal, onGoal, onInput, onActivity, mirror, optionalId(initialized.codexHome));
         session.nativeAccess = createCodexNativeAccess(conversationId, initialized, channel, openingMessages, nativeConfiguration);
+        session.appliedGeneratedTitle = appliedGeneratedTitle;
         session.#activeTurnId = resumedActiveTurnId;
         const ownedTurn = control.kind === "restore" ? control.ownedTurn : undefined;
         session.#clientOwnedTurnId = ownedTurn?.turnId;

package/dist/runtime/tmuxAdapters.js

@@ -246,6 +246,7 @@ export class TmuxSessionHost {
             agentId: request.agentId,
             adapterId: request.adapterId,
             effective: request.effective,
+            ...(planned.generatedTitle === undefined ? {} : { generatedTitle: planned.generatedTitle }),
             ...(planned.launch.env.YUI_SESSION_TITLE === undefined
                 ? {}
                 : { sessionTitle: planned.launch.env.YUI_SESSION_TITLE }),
@@ -436,6 +437,9 @@ export class TmuxSessionHost {
                 roleName: request.owner.roleName
             }),
             hostCreated,
+            ...(providerSnapshot?.appliedGeneratedTitle === undefined ? {} : {
+                appliedGeneratedTitle: providerSnapshot.appliedGeneratedTitle
+            }),
             ...((providerSnapshot?.nativeSessionId ?? nativeSessionId) === undefined
                 ? {}
                 : { nativeSessionId: providerSnapshot?.nativeSessionId ?? nativeSessionId }),

package/dist/storage/sqliteSchema.js

@@ -276,6 +276,16 @@ const MINOR_UPGRADES = Object.freeze([{
         // No payload rewriting or historical revision invention. A newly opened
         // reader starts empty; zero is the initial token until the first mutation.
         sql: TASK_READ_REVISION_SCHEMA_SQL
+    }, {
+        fromVersion: "1.24",
+        toVersion: "1.25",
+        name: "role-instance-code-session-titles",
+        introducedIn: "next",
+        sourceChecksum: CURRENT_SCHEMA_CHECKSUM,
+        targetChecksum: CURRENT_SCHEMA_CHECKSUM,
+        // Optional Role presentation and generated-title provenance. Never infer
+        // ownership of historical titles, rewrite frozen profiles, or fill defaults.
+        sql: ""
     }]);
 export function storageMinorUpgradePlan(from) {
     if (from === CURRENT_STORAGE_VERSION)

package/dist/storage/storageVersions.js

@@ -1,4 +1,4 @@
-export const CURRENT_STORAGE_VERSION = "1.24";
+export const CURRENT_STORAGE_VERSION = "1.25";
 export const MIN_SUPPORTED_STORAGE_VERSION = "1.0";
 export const STORAGE_FORMAT = "yui-home";
 export function isStorageVersion(value) {

package/dist/task/taskAuthority.js

@@ -146,10 +146,14 @@ export function projectActor(environment) {
     }
     return "user";
 }
+/** Read-only Job requests carry the original identity, not the record's owner.
+ * The Controller authenticates it; mutations keep resolveJobCaller's target check. */
+export function resolveJobReadCaller(environment, taskId) {
+    return resolveJobCaller(environment, environment?.YUI_SESSION_SCOPE === "task" ? environment.YUI_TASK_ID ?? "" : taskId);
+}
 /**
- * Resolve the caller's Task, Role and native Session identity. The Controller
- * verifies it against durable state and supplies the current AgentRun. A Task
- * caller cannot control another Task; an incomplete identity is not a user.
+ * Resolve execution identity. The Controller verifies it against durable state;
+ * a Task caller cannot control another Task or infer user authority.
  */
 export function resolveJobCaller(environment, taskId) {
     const env = environment ?? {};

package/docs/cli-information-contract.md

@@ -88,6 +88,23 @@ use family discovery when a broader requirement/history audit is needed.
   decision/milestone/event, Role show/status/Session inspection, wake detail,
   InputRequest, Run context and frozen expansion use bounded detail reads.
 
+Ordinary Task reads authenticate the original caller but do not restrict data
+by its Task or Assignment ID. This single-user local product relies on local
+filesystem permissions and authenticated service transports, not Task ownership
+as a tenant boundary. Foreign current context identifies the caller's own Task
+and labels its authority `reference-only`. Search, records, artifacts and native
+conversation evidence do not switch identity, adopt another Run's instructions,
+or grant writes, inbox handling, dispatch or external effects. Explicit resource
+and Job-owned Role restrictions still apply. Native conversation tools need no
+Yui gateway or Task mapping; actual resource access and relevant scope suffice.
+
+Completed results remain readable. Simple questions need no reopen; the current
+Leader may reopen its own unarchived result when a same-result request or explicit
+unfulfilled commitment needs tracked diagnosis, evidence handoff, authority
+coordination or authorized delivery. Diagnosis stays read-only; reopening retains
+historical completion evidence and never lifts a stop, restores cancelled intent,
+promotes a planning Session or grants external effects.
+
 Use `--json` and read the top-level `data`. Run context and expansion use
 `data.context`; Run Context delta uses `data.contextDelta`. For a long detail, repeat that same read with
 `--cursor <contentPage.nextCursor>`. Concatenate `text` in offset order, checking

package/docs/cli-information-contract.zh-CN.md

@@ -68,6 +68,18 @@ Run 列表接受 Task 或 `task/work` 目标。
   决策/里程碑/事件、Role show/status/Session 检查、wake 详情、InputRequest、
   Run Context 与冻结展开使用有界详情读取。
 
+普通 Task 读取验证原调用者身份，但不按 Task 或 Assignment ID 隔离数据。Yui 是单用户本地产品，
+资源边界由本地文件权限和已认证服务传输承担，Task 归属不是租户边界。跨 Task 当前 Context
+保留调用者自己的 Task 身份，并标记 `reference-only`。搜索、记录、artifact 和原生会话证据
+不切换身份，不继承其他 Run 的指令，也不授予写入、inbox 处理、派工或外部效果权限。
+明确资源限制和 Job-owned Role 限制仍有效。原生会话读取无需 Yui 网关或 Task 映射；
+应使用实际合法可用的读取工具，并保持工作相关范围。
+
+completed 结果仍可读。简单问答无需重开；同结果请求或明确未履行承诺需要持续诊断、
+证据交接、必要权限协调或已授权交付时，当前 Leader 可自行重开自己的未归档结果。
+诊断仍只读；重开保留历史完成证据，不解除停止、不恢复取消意图、不升级 planning
+Session，也不授予外部效果权限。
+
 使用 `--json` 读取顶层 `data`；Run Context 和展开使用 `data.context`，Run Context delta 使用 `data.contextDelta`。
 长详情用同一读取命令加 `--cursor <contentPage.nextCursor>` 继续。按 offset 顺序拼接
 `text`，校验相同 source 与 digest，最后一次性解析 JSON。不要分别解析块，也不要把

package/docs/release-workflow.md

@@ -51,6 +51,60 @@ merely to avoid a version decision. Package versions remain distinct from protoc
 and persistent-storage contracts: their compatibility checks and required migrations
 are unchanged, and the storage rules below do not authorize a package release.
 
+### 2.21.0 compatibility and migration notes
+
+Ordinary Task, Assignment and frozen-context evidence reads now use the local
+resource boundary rather than Task ownership as a confidentiality boundary.
+Catalog/search and relevant records are readable without borrowing the target
+Task's identity or execution authority. Cross-Task context explicitly reports
+`reference-only`. Consumers must not treat readable records, returned instructions,
+or a frozen pack as permission to write, claim input, dispatch, or control work.
+Real user/tenant, filesystem, authenticated transport and explicit read limits
+remain. Native conversation reads use existing legal native tools, not a new gateway.
+
+Leader follow-up guidance permits the existing reopen operation for same-result
+tracked diagnosis, evidence handoff, necessary coordination or delivery authorized
+by the user's request or an explicit unfinished commitment. Simple questions stay
+completed, diagnosis stays read-only, and reopen does not lift stop, archive,
+cancelled-intent, Session, workspace or external-effect restrictions. Existing
+reopen and InputRequest operations remain separate; no completed-state write
+exception or automatic replay is introduced.
+
+Storage remains **1.25** and Controller/Host protocols remain v1; no migration is
+added. Runtime and Role Skill versions advance independently of the package.
+Exact-merge Core CI and the same runtime archive's fresh-install matrix gate npm
+publication. These deterministic checks do not establish model semantic behavior.
+Publishing does not authorize a global installation update or production restart.
+
+### 2.20.0 compatibility and migration notes
+
+This minor adds independent optional Role instance codes (`--instance-code` /
+`--clear-instance-code`) and a `Draft` marker for Leader Sessions with planning
+authority. Operator-only configuration does not propagate to Leader or other
+Roles. Task Role template copies remain independent; codes are presentation,
+not identity, authorization or launch-configuration drift. Full lowercase Task
+IDs remain unchanged. See [Role configuration](roles-and-configuration.md).
+
+New Sessions use the configured code. Normal Codex Host launches/resumes can refresh
+confirmed Yui-owned titles without forcing a stop/replacement. Historical untagged
+titles and recorded custom names are preserved. Codex resume naming requires
+the native name to match the previous generated title; missing metadata and
+user renames are left untouched. Title provenance advances only after a successful
+native naming receipt, not pre-start registration or live Host reuse. Other
+Providers receive generated names only on creation, never on resume. Provider
+naming remains best effort.
+
+Storage advances **1.24 → 1.25** through an additive, no-rewrite transition for
+optional Role code and Session title provenance. Older supported Homes follow
+the centralized contiguous chain; do not open an upgraded Home with older
+software. Controller/Host protocols remain v1. Publication does not authorize
+installing the release, migrating a production Home, restarting shared services,
+replacing Sessions or choosing codes for existing Roles.
+
+Release gates require exact-merge Core CI and the same runtime tarball's
+fresh-install matrix before npm `latest` publication. These deterministic
+checks do not establish real-model behavior.
+
 ### 2.19.0 compatibility and migration notes
 
 This minor adds message backlog and blocked-delivery monitoring with Operator

package/docs/release-workflow.zh-CN.md

@@ -36,6 +36,46 @@ Agent 选择一个预先声明的计划，设施从持久状态驱动该计划
 不能将不兼容冒称为兼容，也不为回避版本选择新增历史兼容机制。包版本与协议、
 持久存储契约仍然独立：兼容性检查和必要迁移要求不变，下文存储规则不授予发版权限。
 
+### 2.21.0 兼容性及迁移说明
+
+普通 Task、Assignment 和冻结上下文证据读取改按本地资源边界处理，不再将 Task
+归属本身作为保密边界。目录、搜索及相关记录可读，但不借用目标 Task 身份或执行权；
+跨 Task Context 明确标记 `reference-only`。调用方不得将可读记录、返回的指令或
+冻结包当作写入、领取输入、派发或控制执行的授权。真实用户／租户、文件系统、
+认证传输及明确阅读限制仍保留；原生会话读取复用合法原生工具，不增加专用网关。
+
+Leader 可依据同结果用户请求或明确未履行承诺，为需要跟踪的诊断、证据交接、
+必要协调或交付使用既有 reopen。简单问答保持 completed，诊断保持只读；重开
+不解除停止、归档、撤销意图、Session、工作区或外部效果限制。reopen 与 InputRequest
+仍是独立操作，不新增 completed 写入例外或自动重放。
+
+存储仍为 **1.25**，Controller/Host 协议仍为 v1，不新增迁移。Runtime 与 Role Skill
+版本独立递增。npm 发布仍要求准确合入 commit 的 Core CI，以及同一 runtime archive
+的全新安装矩阵通过；这些确定性检查不证明模型语义行为。发布不授权全局安装更新
+或生产重启。
+
+### 2.20.0 兼容性及迁移说明
+
+本 minor 增加按 Role 独立可选的实例码（`--instance-code` /
+`--clear-instance-code`），以及持有 planning 权限的 Leader Session 的 `Draft`
+标识。仅设置 Operator 不会传播到 Leader 或其他 Role；Task Role 模板副本保持
+独立。实例码仅供展示，不改变身份、权限、启动配置版本或完整小写 Task ID。
+详见 [Role 配置](roles-and-configuration.zh-CN.md)。
+
+新会话采用配置，正常 Codex Host 启动/恢复可刷新确认由 Yui 管理的标题，不强停或替换会话。
+旧的无来源标记标题和已记录的用户标题保留。Codex 恢复时仅在原生名字仍匹配上次
+生成标题时改名；原生信息缺失或用户已改名则跳过。标题来源仅在原生命名成功回执后
+推进，不因预启动登记或存活 Host 复用而变化。其他 Provider 仅在新建时传入生成名，
+恢复时不传入。Provider 命名仍为尽力能力。
+
+存储通过中央连续迁移从 **1.24 → 1.25**，只增加可选实例码和标题来源，
+不改写历史记录。较早的受支持 Home 沿既有迁移链升级，不可用旧程序打开升级后的
+Home。Controller/Host 协议仍为 v1。发布不授权安装升级、迁移生产 Home、
+重启共享服务、替换会话或为现有 Role 选择实例码。
+
+发布门禁要求准确合入 commit 的 Core CI 和同一 runtime tarball 的全平台
+fresh-install 矩阵通过后才向 npm `latest` 发布；这些确定性验证不证明真实模型行为。
+
 ### 2.19.0 兼容性及迁移说明
 
 本 minor 新增消息积压、投递阻塞监测及 Operator 告警（PR #492）。观测区分正常执行、

package/docs/roles-and-configuration.md

@@ -18,6 +18,55 @@ requiring a same-named global Role. A global Role is a creation template only
 when the requested Task Role does not exist. Availability, producer separation
 and the frozen review candidate still apply.
 
+## Optional instance codes and Session titles
+
+Each Role can independently set a display-only instance code. For example,
+configure only Operator, leaving Leader and all other Roles unset:
+
+```sh
+yui config role update operator --instance-code dev-bj
+yui config role show operator
+yui config role update operator --clear-instance-code
+yui task role update task-159 leader --instance-code dev-sg
+```
+
+`add` also accepts `--instance-code`. Codes accept 1–24 UTF-16 units of Unicode
+letters, numbers, combining marks, hyphen and underscore; omit `@`. Whitespace,
+controls, escapes and punctuation are rejected, not silently normalized.
+There is no Home-wide fallback. A Global Role's code is copied when that template
+creates a Task Role; later template changes do not rewrite the copy. Agent
+Profiles do not supply display codes. Use Task Role update/clear for an existing
+copy. Codes do not alter launch revisions, permissions, IDs or message routing.
+Choose recognizable values; codes are not globally unique identities. Use
+Session inspection and the actual Home/native identity when resolving ambiguity.
+
+Generated Task titles use `Yui Leader task-159 Draft @dev-sg · Task name`.
+`Draft` means the Leader Session has planning authority, including a retained
+planning Session after activation; delivery Sessions omit it. Other Role names
+and the full lowercase Task ID remain intact. Operator uses
+`Yui Operator @dev-bj · MMDD`; without a code its existing
+`Yui · Operator · MMDD` format remains. The date derives from Session creation
+and the configured timezone. Other Global Roles get a generated title when a
+code is configured. Descriptions are truncated first without splitting surrogate
+pairs; if the identity itself cannot fit the 80-unit title limit, launch fails
+with a bounded diagnostic instead of truncating the identity.
+
+Configuration does not rename, stop or recreate a live Session. New Sessions
+use it; a subsequent normal Host launch/resume can refresh confirmed Yui-owned titles,
+not historical records. Existing untagged titles and recorded user names stay
+untouched. Codex applies a resume rename only when its returned native name still
+matches the previous generated title; absent metadata or a user rename prevents
+the rename. Codex records only successfully applied names; live Host reuse,
+skipped naming and naming failures do not advance title provenance. Naming is
+best effort; unsupported Providers or failures do not invalidate the Session.
+Other Providers receive generated names only on creation, never on resume,
+to protect native user renames. No restart is performed to force a naming change.
+On the safe Codex resume path, clearing a custom Global Role's code restores
+`Yui role`; clearing Operator's code restores its unconfigured format.
+
+Storage 1.24 → 1.25 adds optional code/title provenance without rewriting
+historical payloads or inferring who named an old Session.
+
 ## Enable and disable
 
 Availability is configuration, separate from active Agent selection, Session

package/docs/roles-and-configuration.zh-CN.md

@@ -15,6 +15,44 @@ Task Role 是 Task 局部的；global Role 提供已配置的默认值和全局
 的 global Role。只有当请求的 Task Role 不存在时，global Role 才作为创建模板。
 可用性、producer 分离和冻结的审查候选仍然适用。
 
+## 可选实例码与会话标题
+
+每个 Role 独立配置仅用于展示的实例码。例如只设置 Operator，其他角色留空：
+
+```sh
+yui config role update operator --instance-code dev-bj
+yui config role show operator
+yui config role update operator --clear-instance-code
+yui task role update task-159 leader --instance-code dev-sg
+```
+
+`add` 也接受 `--instance-code`。允许 1–24 个 UTF-16 单位的 Unicode 字母、
+数字、组合标记、短横线和下划线，不输入 `@`。空白、控制字符、转义和其他标点
+直接拒绝，不静默清洗。没有 Home 级默认值；Global Role 作为模板创建 Task Role
+时复制其值，之后模板变化不回写。Agent Profile 不携带实例码；既有 Task Role
+通过自己的 update/clear 修改。实例码不改变启动版本、权限、内部 ID 或消息寻址，
+也不保证全局唯一；遇到歧义应查看实际 Home、Session 和原生身份。
+
+生成的 Task 标题为 `Yui Leader task-159 Draft @dev-sg · 任务名`。
+`Draft` 根据 Leader Session 的 planning 权限显示；Task 激活后保留的 planning
+会话仍显示 Draft，delivery 会话不显示。保留完整小写 Task ID。
+Operator 为 `Yui Operator @dev-bj · MMDD`；未配置保持
+`Yui · Operator · MMDD`，日期使用会话创建时间和配置时区。
+其他 Global Role 配置实例码后生成标题。80 单位总长度内优先截断任务名，
+不拆开代理对；身份部分无法容纳则明确报错，不静默截断。
+
+配置修改不会立即重命名、停止或重建活动会话。新会话采用新配置，后续正常
+Host 启动/恢复可刷新确认由 Yui 管理的标题，不改写历史记录。
+缺少来源标记的旧标题及已记录的用户标题保留。Codex 恢复时只有原生返回的
+名字仍等于上次生成标题才改名；原生信息缺失或用户已改名则跳过。
+Codex 只记录已成功应用的名称；复用存活 Host、命名失败或跳过不推进标题来源。
+Provider 命名为尽力能力；失败或不支持不会使会话失效。其他 Provider 仅在新建时
+传入生成名，恢复时不重新传入名称，以保护原生用户改名；不为改名主动重启。
+在可安全改名的 Codex 恢复路径，清除自定义 Global Role 实例码后恢复
+`Yui role`；Operator 恢复未配置格式。
+
+存储 1.24 → 1.25 增加可选实例码和生成标题来源，不回填历史记录或猜测标题所有权。
+
 ## 启用与停用
 
 启停是配置状态，与 Active Agent、Session 是否运行和 Task executionGate 分开：

package/docs/storage-baseline.md

@@ -2,7 +2,10 @@
 
 # Storage baseline 1.0
 
-Current storage is 1.24. The 1.23 → 1.24 transition adds transaction-maintained
+Current storage is 1.25. The 1.24 → 1.25 transition admits optional Role
+`instanceCode` and Session `generatedTitle` presentation fields without rewriting
+existing records. Untagged historical titles remain user-owned; no code or
+title provenance is inferred. The 1.23 → 1.24 transition adds transaction-maintained
 Task read-cache revisions for the scheduler's nine source tables. Inserts,
 updates and deletions invalidate only the affected Task; rollback also rolls
 back the token. These tokens are derived cache identities, never Task authority

package/docs/storage-baseline.zh-CN.md

@@ -2,7 +2,7 @@
 
 # 存储基线 1.0
 
-当前存储为 1.24。1.23 → 1.24 为调度器的九类来源表增加事务维护的 Task 读取缓存修订号。插入、更新和删除只使对应 Task 的缓存失效，回滚同时回滚修订号。该值仅是派生缓存标识，不是 Task 权限或 Home revision CAS 的替代。历史 payload 不变，旧 Task 在首次修改前使用隐含的零修订号。
+当前存储为 1.25。1.24 → 1.25 增加可选 Role `instanceCode` 和 Session `generatedTitle` 展示字段，不回填历史标题来源或实例码，不改写既有记录。1.23 → 1.24 为调度器的九类来源表增加事务维护的 Task 读取缓存修订号。插入、更新和删除只使对应 Task 的缓存失效，回滚同时回滚修订号。该值仅是派生缓存标识，不是 Task 权限或 Home revision CAS 的替代。历史 payload 不变，旧 Task 在首次修改前使用隐含的零修订号。
 同时增加两个局部索引，支持按精确运行观测身份查找，不再扫描或反序列化历史观测集合。
 
 1.22 → 1.23 新增全局 Shell Job、版本化脚本文件及每次运行的配置快照，不改写已有 Job、计划和历史记录。

package/docs/task-discovery.md

@@ -116,11 +116,11 @@ source records; no report text is parsed into status. Web explicitly labels
 these facts and offers category navigation. Selected detail survives paging,
 filtering and refresh; only the detail read can establish absence.
 
-Task Leader Sessions see only their own Task. Assignment-scoped Workers and
-Reviewers use existing authorized Run Context instead of whole-Task discovery;
-the catalog rejects their request before counting. Global non-Operator and
-incomplete managed identities are rejected. Historical Leader diagnostic reads
-retain their original Task scope. A cursor is scope/filter-bound continuation,
+Task Leaders, Workers and Reviewers may discover relevant ordinary records
+under the local resource's access rules; Task/Assignment ownership does not
+filter the catalog. Global non-Operator and incomplete or unknown managed
+identities remain rejected. Historical readers retain read-only identity,
+never another Task's execution authority. A cursor is scope/filter-bound continuation,
 not a credential. Read operations do not consume messages, acknowledge jobs,
 wake Roles or query providers.
 

package/docs/task-discovery.zh-CN.md

@@ -73,10 +73,10 @@ Brief。当前 Brief 通过 Task Context 读取；Context inspect 可校验 dige
 不解析报告正文推导状态。Web 明确标示这些事实并提供分类导航。
 已选详情不因分页、筛选或刷新而丢失；只有详情读取可以确认目标不存在。
 
-Task Leader Session 只能发现自己的 Task。Assignment-scoped Worker 和
-Reviewer 使用既有授权 Run Context，目录会在计数前拒绝其全 Task 发现请求。
-非 Operator 的 Global Session 和不完整的受管身份也会被拒绝。
-历史 Leader 的诊断读取保持原 Task 范围。游标绑定范围及参数，不是凭证。
+Task Leader、Worker 和 Reviewer 可按本地资源访问规则发现相关普通记录；
+目录不以 Task/Assignment 归属过滤数据。非 Operator 的 Global Session、
+不完整或未知的受管身份仍被拒绝。历史读取者保持只读身份，不获得其他 Task 的执行权。
+游标绑定范围及参数，不是凭证。
 读取不会消费 Message、确认 Job、唤醒 Role 或查询外部 provider。
 
 ## 成本边界