dsh-deeppilot 0.9.6 → 0.9.8

package/docs/NPM_PUBLISHING.md

@@ -79,6 +79,32 @@
 4. `0.9.5` 已完成首次 OIDC 身份认证发布；npm 绑定显示 `Valid`（有效），
    来源证明签名、压缩包摘要与两个支持宿主的注册表安装核验通过。首次运行的末尾
    核对因缓存失败，其上传步骤成功；发布证据及边界见 `docs/DSH_RELEASE_MEMORY.md`。
+5. `0.9.6` 复现了同一形态：OIDC 上传与来源证明步骤成功，紧随其后的核对步骤在
+   12 次重试后仍抛 `读取 npm 发布信息失败（dsh-deeppilot/0.9.6，HTTP 404）`，
+   整次运行结论因此为失败。事后核验 `npm view dsh-deeppilot dist-tags --prefer-online`
+   得到 `latest = 0.9.6`、发布时间与该版本的来源证明均齐全，确认根因是注册表元数据
+   的可见性延迟，不是上传失败。该窗口已在 0.9.7 放宽：最多 24 次核对、间隔 5 秒
+   线性递增并封顶 20 秒（约 7 分钟），仍然只读元数据、不重复上传包。这样既避免
+   「上传成功 + 核对延迟」在 Actions 页留下误导性的红色结论，也不会把真正的失败
+   伪装成成功——超出窗口依旧抛错。
+6. `0.9.7` 是放宽窗口后的第一次发布，也是首次全绿的发布：工作流在附注标签
+   `v0.9.7`（提交 `bf18755`）上运行，19 个步骤全部成功，包含此前两次失败的末尾
+   核对。发布后核验：注册表 `latest = 0.9.7`、来源证明类型为
+   `https://slsa.dev/provenance/v1`；在全新隔离 profile 中从 npm 安装该版本，并在
+   真实 `0.2.1-alpha.5` 宿主上启动，`/phone/health` 返回 200 且 `serverVersion`
+   为 `0.9.7`。公开 GitHub Release 之前先完成了这一步安装验证。
+7. `0.9.8` 的本地发布清单在**待发布工作树**上执行并通过（详细数字见
+   `docs/RELEASE_NOTES-0.9.8.md` 第三节）：`npm ci`、单元测试 581 项
+   （580 通过、0 失败、1 项既有待办）、类型检查、构建前后 `lib/` 逐文件
+   sha256 一致、`check:config-schema`（仍针对锁定的 `0.2.0-rc.2` CLI）、
+   helper 的 Go 测试、`bin/SHA256SUMS` 6/6。宿主侧本轮改用
+   **`0.2.1-rc.2`**：隔离 `DSH_HOME` 下改动前被拒绝激活（单键 `engines.dsh`
+   要求 + `Exact-version exemption: not active`），扩围后组合树含插件与
+   web-app 补丁、真实启动出现 4 条 `[deeppilot]`，插件自有端口 3098 的
+   `/phone/health` 返回 200 且 `serverVersion` 为 `0.9.8`。打包为 68 个条目。
+   本轮还确认了一个易漏点：升版本号必须同步重录
+   `tests/apply-baseline.snapshot.json`，否则 `npm test` 会失败——已写入
+   `AGENTS.md` 的发布流程第 1 步。
 
 ## 五、官方资料
 

package/lib/index.d.ts

@@ -1,5 +1,9 @@
 import z from "@deepseek-ai/schemastery";
 import { Context } from "@deepseek-ai/cordis";
+//#region src/device-auth.d.ts
+declare const DEVICE_SCOPES: readonly ['sessions.read', 'prompt.send', 'sessions.manage', 'interactions.respond', 'notifications.register', 'schedule.manage'];
+type DeviceScope = (typeof DEVICE_SCOPES)[number];
+//#endregion
 //#region src/wire-errors.d.ts
 /**
  * 错误词表（error vocabulary）的唯一属主。
@@ -198,12 +202,50 @@ type MutationDispatchResult<T> = {
   replayed?: boolean;
 };
 //#endregion
-//#region src/device-auth.d.ts
-declare const DEVICE_SCOPES: readonly ['sessions.read', 'prompt.send', 'sessions.manage', 'interactions.respond', 'notifications.register', 'schedule.manage'];
-type DeviceScope = (typeof DEVICE_SCOPES)[number];
+//#region src/command-api.d.ts
+interface CommandSummary {
+  name: string;
+  description: string;
+  definitionId?: string;
+  input?: {
+    hint: string;
+    attachments?: boolean;
+  };
+}
+interface CommandCatalog {
+  commands: CommandSummary[];
+  permissions: boolean;
+  export: boolean;
+}
+interface CommandExecution {
+  commandId: string;
+  result: {
+    kind: 'success' | 'error';
+    text?: string;
+    sourceEventSeq?: number;
+  };
+}
+interface CommandAttachment {
+  type: 'image' | 'document';
+  name: string;
+  mediaType: string;
+  data: string;
+}
+interface PermissionOption {
+  value: string;
+  name: string;
+  description?: string;
+  confirmation: boolean;
+}
+interface PermissionCatalog {
+  options: PermissionOption[];
+  currentValue?: string;
+}
 //#endregion
 //#region src/protocol.d.ts
 interface WelcomeCapabilities {
+  /** 会话命令目录、执行、权限与原生日志导出入口。缺省不支持。 */
+  commands?: boolean;
   historyPaging: boolean;
   replay: boolean;
   approvals: boolean;
@@ -214,6 +256,8 @@ interface WelcomeCapabilities {
   /** Bridge emits s2c.notify for all four notification categories. */
   notifyAllCategories?: boolean;
   models: boolean;
+  /** Session-scoped user-invocable skill metadata and invalidation notices. */
+  skills?: boolean;
   sessionManagement: boolean;
   /** Bridge can fork a session at an exact event boundary. */
   sessionFork?: boolean;
@@ -348,6 +392,12 @@ interface MessageProjection {
   ts: number;
   truncated?: boolean;
 }
+/** Metadata only: loading instructions remains the Host's responsibility. */
+interface SkillSummary {
+  name: string;
+  description: string;
+  modelInvocable: boolean;
+}
 type NotifyCategory = 'turn.completed' | 'approval.required' | 'question.asked' | 'session.error';
 /**
  * One offline-push-worthy event (same facts as s2c.notify / pending frames,
@@ -391,6 +441,28 @@ interface PendingSnapshotPayload {
 }
 //#endregion
 //#region src/host-api.d.ts
+interface CommandsApiLike {
+  list(req: RpcRequestLike<{
+    sessionId: string;
+  }>): Promise<RpcResponseLike<CommandCatalog>>;
+  execute(req: RpcRequestLike<{
+    sessionId: string;
+    line: string;
+    attachments: CommandAttachment[];
+    expectedDefinitionId?: string;
+  }>): Promise<RpcResponseLike<CommandExecution>>;
+  permissions(req: RpcRequestLike<{
+    sessionId: string;
+  }>): Promise<RpcResponseLike<PermissionCatalog>>;
+  feedback(req: RpcRequestLike<{
+    sessionId: string;
+    text: string;
+    category?: string;
+  }>): Promise<RpcResponseLike<void>>;
+  export(req: RpcRequestLike<{
+    sessionId: string;
+  }>, signal: AbortSignal): Promise<Response>;
+}
 interface RpcOk<T> {
   ok: true;
   value: T;
@@ -441,6 +513,11 @@ interface SessionsApiLike {
   models?(req: RpcRequestLike<{
     sessionId: string;
   }>): Promise<RpcResponseLike<HostSessionModels>>;
+  skills?(req: RpcRequestLike<{
+    sessionId: string;
+  }>): Promise<RpcResponseLike<{
+    skills: SkillSummary[];
+  }>>;
   selectModel?(req: RpcRequestLike<{
     sessionId: string;
     provider: string;
@@ -729,6 +806,7 @@ interface ApiStreamItemLike {
   payload: MuxFrameLike;
 }
 interface ApiProxyLike {
+  commands?: CommandsApiLike;
   sessions: SessionsApiLike;
   workspace?: WorkspaceApiLike;
   schedule?: ScheduleApiLike;
@@ -952,6 +1030,12 @@ declare class HostBridge {
     mediaType?: string;
     data: string;
   } | null>;
+  commandOperation(operation: 'list' | 'execute' | 'permissions' | 'feedback', payload: Record<string, unknown>): Promise<SessionManagementResult<unknown>>;
+  exportSession(sessionId: string, signal: AbortSignal): Promise<Response>;
+  /** 由会话目录决定技能可见性；不读取正文，也不把本机路径发给移动端。 */
+  sessionSkills(sessionId: string): Promise<SessionManagementResult<{
+    skills: SkillSummary[];
+  }>>;
   sessionModels(sessionId: string): Promise<ModelBridgeResult<HostSessionModels>>;
   selectSessionModel(sessionId: string, selection: HostModelSelection): Promise<ModelBridgeResult<HostModelSelection>>;
   renameSession(sessionId: string, title: string): Promise<SessionManagementResult<string>>;