@flowy-agent-store/client 0.1.0-beta.4 → 0.1.0-beta.5

package/dist/index.cjs

@@ -276,7 +276,7 @@ var WebSocketTransport = class {
 /** Header the server mints the per-call connection id under. */
 const CONNECTION_HEADER = "x-app-server-connection-id";
 /** Protocol version this binding announces on the one-shot handshake. */
-const PROTOCOL_VERSION = "fp-1";
+const PROTOCOL_VERSION = "fp-7";
 /**
 * Protocol method → REST route. Verified from handler bodies, not from the
 * route list (a route existing does not prove which method it mirrors).
@@ -334,7 +334,10 @@ const HTTP_ROUTES = {
 		body: [
 			"content",
 			"idempotency_key",
-			"attachments"
+			"attachments",
+			"mentions",
+			"model",
+			"reasoning_effort"
 		],
 		source: "conversation_send() -> send_conversation_message_for_user (shared with the WS arm)"
 	},
@@ -795,7 +798,9 @@ var ConversationClient = class {
 			name: input.name,
 			model,
 			workspace: input.workspaceId ? { id: input.workspaceId } : void 0,
-			reasoning_effort: input.reasoningEffort || void 0
+			reasoning_effort: input.reasoningEffort || void 0,
+			agent_id: input.agentId || void 0,
+			team_id: input.teamId || void 0
 		});
 	}
 	update(conversationId, input) {
@@ -828,17 +833,33 @@ var ConversationClient = class {
 	}
 	/**
 	* R15（W10）：`attachments` 是**会话工作区内的绝对路径**（图片附件）。
+	* doc `27` §4.1：`mentions` 是**本轮挂载的技能**（`kind: "skill"`）——技能的正文与
+	* 不可变快照都随这一轮走；`agent` / `connector` 在 send 上没有载体，服务端会以
+	* `invalid_request` **明确拒绝**（不是静默不挂）。
+	*
+	* 两者缺省都不上 wire，保持老调用方的形状逐字不变；服务端只接受会话工作区内的真实
+	* 文件（越界 / 相对路径 / 不存在一律拒），准入见 `nomifun-app-server` 的
+	* `resolve_conversation_attachments` 与 `send_mention_skills`。
 	*
-	* 缺省不传，保持老调用方的 wire 形状逐字不变；服务端只接受会话工作区内的真实
-	* 文件（越界 / 相对路径 / 不存在一律拒），具体准入见
-	* `nomifun-app-server` 的 `resolve_conversation_attachments`。
+	* 第 4 个参数同时接受旧的 `string[]`（附件）与选项对象——再堆一个位置参数会让调用点
+	* 变成一串没有名字的布尔/数组。
 	*/
-	send(conversationId, content, idempotencyKey, attachments = []) {
+	send(conversationId, content, idempotencyKey, options = {}) {
+		const attachments = Array.isArray(options) ? options : options.attachments ?? [];
+		const mentions = Array.isArray(options) ? [] : options.mentions ?? [];
+		const model = Array.isArray(options) ? void 0 : options.model;
+		const reasoningEffort = Array.isArray(options) ? void 0 : options.reasoningEffort;
 		return this.transport.request("conversation/send", {
 			conversation_id: conversationId,
 			content,
 			idempotency_key: idempotencyKey,
-			...attachments.length > 0 ? { attachments } : {}
+			...attachments.length > 0 ? { attachments } : {},
+			...mentions.length > 0 ? { mentions } : {},
+			...model ? { model: {
+				provider_id: model.provider_id,
+				model: model.model
+			} } : {},
+			...reasoningEffort ? { reasoning_effort: reasoningEffort } : {}
 		});
 	}
 	cancel(conversationId) {
@@ -1063,7 +1084,19 @@ var ConnectorClient = class {
 	status(connectorId) {
 		return this.transport.request("connector/status", { connector_id: connectorId });
 	}
-	/** Run a connection probe; the server persists the result. */
+	/**
+	* Run a connection probe and report what the connector currently offers —
+	* including each tool's `input_schema`.
+	*
+	* It really connects: a stdio connector gets its child process spawned, an
+	* HTTP/SSE one gets `initialize` + `tools/list`. The result is **persisted**,
+	* so this is also what refreshes the tool list `get()` reads back.
+	*
+	* Named `test` and not `probe` on purpose: this repo's split is `test` for the
+	* action (wire `connector/test`, `test_connection`) and `probe` for its
+	* artifact (`ConnectorProbeResult`, `probe_status`), and every method here is
+	* the last segment of its wire method.
+	*/
 	test(connectorId) {
 		return this.transport.request("connector/test", { connector_id: connectorId });
 	}
@@ -1088,9 +1121,17 @@ var ConnectorClient = class {
 	* The host holds the transport, its headers and its OAuth token; this sends a
 	* tool name and an argument object and nothing else — you cannot name a URL,
 	* a command or a header. Whether the pair is callable at all is the host's
-	* `[connector_proxy]` allowlist, so expect `policy_denied` on a host whose
-	* operator has not listed this tool (that is the default, not a
-	* misconfiguration).
+	* `[connector_proxy]` policy: once its operator turns the proxy on, the
+	* enabled connectors are callable, and `allow` / `deny` are that operator's
+	* optional narrowing and subtraction. So `policy_denied` means either that
+	* the host never turned the proxy on, or that this pair was narrowed out or
+	* explicitly denied — not that a tool name was misspelled in a list you were
+	* supposed to maintain.
+	*
+	* Arguments are passed through verbatim (there is no client-side schema
+	* check); `get()` / `test()` return each tool's `input_schema` so you can see
+	* what it takes, and a parameter the server rejects comes back as
+	* `is_error: true`, not as a rejected promise.
 	*
 	* Resolves even when the tool itself failed — check `is_error`. It rejects
 	* only when the call never reached the tool: `connector_call_timeout`,
@@ -1389,7 +1430,12 @@ function toWire(input) {
 		steps: input.steps,
 		command_id: input.commandId,
 		idempotency_key: input.idempotencyKey,
-		mentions: input.mentions
+		mentions: input.mentions,
+		model: input.model ? {
+			provider_id: input.model.provider_id,
+			model: input.model.model
+		} : void 0,
+		reasoning_effort: input.reasoningEffort || void 0
 	};
 }
 function toTeamWire(input) {

package/dist/index.d.cts

@@ -1,4 +1,4 @@
-import { AgentDetail, AgentRunInput, AgentSummary, AnswerDecisionInput, CancelRunInput, ClientCapabilities, ClientInfo, ConnectorCallResult, ConnectorDetail, ConnectorProbeResult, ConnectorStatusView, ConnectorSummary, ContextUsage, ConversationCreateInput, ConversationEvent, ConversationMessage, ConversationMessagesPage, ConversationMessagesQuery, ConversationModelOptions, ConversationSendReceipt, ConversationUpdateInput, ConversationView, ImportDetail, ImportRequest, ImportResult, ImportSummary, InitializeResult, InstallOutcome, InstallRequest, InstallResult, InstallStatus, MarketplaceAddRequest, MarketplaceDetail, MarketplaceRefreshResult, MarketplaceRemoveResult, MarketplaceSummary, ModelSummary, OAuthStartResult, OAuthStatusView, RunEvent, RunEventsQuery, RunPlan, RunReceipt, RunResult, RunStatus, RunView, ServerNotification, SkillDetail, SkillFileContent, SkillFileList, SkillSummary, SteerRunInput, StoreInstallResult, StoreItem, StoreItemKind, StoreList, TeamDetail, TeamRunInput, TeamRunReceipt, TeamSummary, WorkspaceRevokeResult, WorkspaceView } from "@flowy-agent-store/protocol";
+import { AgentDetail, AgentRunInput, AgentSummary, AnswerDecisionInput, CancelRunInput, ClientCapabilities, ClientInfo, ConnectorCallResult, ConnectorDetail, ConnectorProbeResult, ConnectorStatusView, ConnectorSummary, ContextUsage, ConversationCreateInput, ConversationEvent, ConversationMessage, ConversationMessagesPage, ConversationMessagesQuery, ConversationModelOptions, ConversationSendReceipt, ConversationUpdateInput, ConversationView, ImportDetail, ImportRequest, ImportResult, ImportSummary, InitializeResult, InstallOutcome, InstallRequest, InstallResult, InstallStatus, MarketplaceAddRequest, MarketplaceDetail, MarketplaceRefreshResult, MarketplaceRemoveResult, MarketplaceSummary, MentionRef, ModelSummary, OAuthStartResult, OAuthStatusView, ProviderWithModel, RunEvent, RunEventsQuery, RunPlan, RunReceipt, RunResult, RunStatus, RunView, ServerNotification, SkillDetail, SkillFileContent, SkillFileList, SkillSummary, SteerRunInput, StoreInstallResult, StoreItem, StoreItemKind, StoreList, TeamDetail, TeamRunInput, TeamRunReceipt, TeamSummary, WorkspaceRevokeResult, WorkspaceView } from "@flowy-agent-store/protocol";
 //#region src/transport.d.ts
 export type NotificationListener = (notification: ServerNotification) => void;
 /**
@@ -196,6 +196,46 @@ export declare class AgentClient {
 }
 //#endregion
 //#region src/conversations.d.ts
+/**
+ * Options for `send()`.
+ *
+ * Two scopes, deliberately different (doc `27` §4.1 and doc `29` §5.1):
+ *
+ * - **per turn** — `attachments` and `mentions` are this turn's payload, and
+ *   nothing else changes;
+ * - **per conversation, taking effect this turn** — `model` and
+ *   `reasoningEffort` are *sticky*: they are written to the conversation and
+ *   every later turn keeps them, because the Nomi runtime is built from the
+ *   persisted row. The host refuses them while a turn is running (`conflict`).
+ *
+ * Every field is **additive**: absent means the exact wire shape callers sent
+ * before that field existed, and a plain `send()` never writes the conversation.
+ */
+export interface ConversationSendOptions {
+  /** Absolute paths inside the conversation's workspace (images only). */
+  attachments?: string[];
+  /**
+   * Skills to mount for **this turn** (`kind: "skill"`).
+   *
+   * The ids are `skill/list`'s ids (the skill's own name, not an
+   * `install/status` component id). A turn is the only scope a Skill has here:
+   * the conversation's frozen snapshot is create-time and immutable.
+   */
+  mentions?: MentionRef[];
+  /**
+   * Model to switch the conversation to **from this turn on** (doc `29` §5.1).
+   *
+   * Sticky, not per-turn: the Nomi runtime is built from the persisted row, so
+   * the value is written to the conversation and every later turn keeps it.
+   * Omit it and the conversation's current model stays untouched.
+   */
+  model?: ProviderWithModel;
+  /**
+   * Reasoning level to switch the conversation to **from this turn on**
+   * (doc `29` §5.1). Same sticky scope as `model`.
+   */
+  reasoningEffort?: string;
+}
 export declare class ConversationClient {
   private readonly transport;
   constructor(transport: Transport);
@@ -207,12 +247,18 @@ export declare class ConversationClient {
   messages(query: ConversationMessagesQuery): Promise<ConversationMessagesPage>;
   /**
    * R15（W10）：`attachments` 是**会话工作区内的绝对路径**（图片附件）。
+   * doc `27` §4.1：`mentions` 是**本轮挂载的技能**（`kind: "skill"`）——技能的正文与
+   * 不可变快照都随这一轮走；`agent` / `connector` 在 send 上没有载体，服务端会以
+   * `invalid_request` **明确拒绝**（不是静默不挂）。
+   *
+   * 两者缺省都不上 wire，保持老调用方的形状逐字不变；服务端只接受会话工作区内的真实
+   * 文件（越界 / 相对路径 / 不存在一律拒），准入见 `nomifun-app-server` 的
+   * `resolve_conversation_attachments` 与 `send_mention_skills`。
    *
-   * 缺省不传，保持老调用方的 wire 形状逐字不变；服务端只接受会话工作区内的真实
-   * 文件（越界 / 相对路径 / 不存在一律拒），具体准入见
-   * `nomifun-app-server` 的 `resolve_conversation_attachments`。
+   * 第 4 个参数同时接受旧的 `string[]`（附件）与选项对象——再堆一个位置参数会让调用点
+   * 变成一串没有名字的布尔/数组。
    */
-  send(conversationId: string, content: string, idempotencyKey: string, attachments?: string[]): Promise<ConversationSendReceipt>;
+  send(conversationId: string, content: string, idempotencyKey: string, options?: string[] | ConversationSendOptions): Promise<ConversationSendReceipt>;
   cancel(conversationId: string): Promise<ConversationView>;
   delete(conversationId: string): Promise<{
     conversation_id: string;
@@ -326,7 +372,19 @@ export declare class ConnectorClient {
   get(connectorId: string): Promise<ConnectorDetail>;
   /** Combined auth × probe status. `connected` only when auth is ready AND the last probe succeeded. */
   status(connectorId: string): Promise<ConnectorStatusView>;
-  /** Run a connection probe; the server persists the result. */
+  /**
+   * Run a connection probe and report what the connector currently offers —
+   * including each tool's `input_schema`.
+   *
+   * It really connects: a stdio connector gets its child process spawned, an
+   * HTTP/SSE one gets `initialize` + `tools/list`. The result is **persisted**,
+   * so this is also what refreshes the tool list `get()` reads back.
+   *
+   * Named `test` and not `probe` on purpose: this repo's split is `test` for the
+   * action (wire `connector/test`, `test_connection`) and `probe` for its
+   * artifact (`ConnectorProbeResult`, `probe_status`), and every method here is
+   * the last segment of its wire method.
+   */
   test(connectorId: string): Promise<ConnectorProbeResult>;
   /** Check the current OAuth state for a connector. */
   authStatus(connectorId: string): Promise<OAuthStatusView>;
@@ -343,9 +401,17 @@ export declare class ConnectorClient {
    * The host holds the transport, its headers and its OAuth token; this sends a
    * tool name and an argument object and nothing else — you cannot name a URL,
    * a command or a header. Whether the pair is callable at all is the host's
-   * `[connector_proxy]` allowlist, so expect `policy_denied` on a host whose
-   * operator has not listed this tool (that is the default, not a
-   * misconfiguration).
+   * `[connector_proxy]` policy: once its operator turns the proxy on, the
+   * enabled connectors are callable, and `allow` / `deny` are that operator's
+   * optional narrowing and subtraction. So `policy_denied` means either that
+   * the host never turned the proxy on, or that this pair was narrowed out or
+   * explicitly denied — not that a tool name was misspelled in a list you were
+   * supposed to maintain.
+   *
+   * Arguments are passed through verbatim (there is no client-side schema
+   * check); `get()` / `test()` return each tool's `input_schema` so you can see
+   * what it takes, and a parameter the server rejects comes back as
+   * `is_error: true`, not as a rejected promise.
    *
    * Resolves even when the tool itself failed — check `is_error`. It rejects
    * only when the call never reached the tool: `connector_call_timeout`,

package/dist/index.d.mts

@@ -1,4 +1,4 @@
-import { AgentDetail, AgentRunInput, AgentSummary, AnswerDecisionInput, CancelRunInput, ClientCapabilities, ClientInfo, ConnectorCallResult, ConnectorDetail, ConnectorProbeResult, ConnectorStatusView, ConnectorSummary, ContextUsage, ConversationCreateInput, ConversationEvent, ConversationMessage, ConversationMessagesPage, ConversationMessagesQuery, ConversationModelOptions, ConversationSendReceipt, ConversationUpdateInput, ConversationView, ImportDetail, ImportRequest, ImportResult, ImportSummary, InitializeResult, InstallOutcome, InstallRequest, InstallResult, InstallStatus, MarketplaceAddRequest, MarketplaceDetail, MarketplaceRefreshResult, MarketplaceRemoveResult, MarketplaceSummary, ModelSummary, OAuthStartResult, OAuthStatusView, RunEvent, RunEventsQuery, RunPlan, RunReceipt, RunResult, RunStatus, RunView, ServerNotification, SkillDetail, SkillFileContent, SkillFileList, SkillSummary, SteerRunInput, StoreInstallResult, StoreItem, StoreItemKind, StoreList, TeamDetail, TeamRunInput, TeamRunReceipt, TeamSummary, WorkspaceRevokeResult, WorkspaceView } from "@flowy-agent-store/protocol";
+import { AgentDetail, AgentRunInput, AgentSummary, AnswerDecisionInput, CancelRunInput, ClientCapabilities, ClientInfo, ConnectorCallResult, ConnectorDetail, ConnectorProbeResult, ConnectorStatusView, ConnectorSummary, ContextUsage, ConversationCreateInput, ConversationEvent, ConversationMessage, ConversationMessagesPage, ConversationMessagesQuery, ConversationModelOptions, ConversationSendReceipt, ConversationUpdateInput, ConversationView, ImportDetail, ImportRequest, ImportResult, ImportSummary, InitializeResult, InstallOutcome, InstallRequest, InstallResult, InstallStatus, MarketplaceAddRequest, MarketplaceDetail, MarketplaceRefreshResult, MarketplaceRemoveResult, MarketplaceSummary, MentionRef, ModelSummary, OAuthStartResult, OAuthStatusView, ProviderWithModel, RunEvent, RunEventsQuery, RunPlan, RunReceipt, RunResult, RunStatus, RunView, ServerNotification, SkillDetail, SkillFileContent, SkillFileList, SkillSummary, SteerRunInput, StoreInstallResult, StoreItem, StoreItemKind, StoreList, TeamDetail, TeamRunInput, TeamRunReceipt, TeamSummary, WorkspaceRevokeResult, WorkspaceView } from "@flowy-agent-store/protocol";
 //#region src/transport.d.ts
 export type NotificationListener = (notification: ServerNotification) => void;
 /**
@@ -196,6 +196,46 @@ export declare class AgentClient {
 }
 //#endregion
 //#region src/conversations.d.ts
+/**
+ * Options for `send()`.
+ *
+ * Two scopes, deliberately different (doc `27` §4.1 and doc `29` §5.1):
+ *
+ * - **per turn** — `attachments` and `mentions` are this turn's payload, and
+ *   nothing else changes;
+ * - **per conversation, taking effect this turn** — `model` and
+ *   `reasoningEffort` are *sticky*: they are written to the conversation and
+ *   every later turn keeps them, because the Nomi runtime is built from the
+ *   persisted row. The host refuses them while a turn is running (`conflict`).
+ *
+ * Every field is **additive**: absent means the exact wire shape callers sent
+ * before that field existed, and a plain `send()` never writes the conversation.
+ */
+export interface ConversationSendOptions {
+  /** Absolute paths inside the conversation's workspace (images only). */
+  attachments?: string[];
+  /**
+   * Skills to mount for **this turn** (`kind: "skill"`).
+   *
+   * The ids are `skill/list`'s ids (the skill's own name, not an
+   * `install/status` component id). A turn is the only scope a Skill has here:
+   * the conversation's frozen snapshot is create-time and immutable.
+   */
+  mentions?: MentionRef[];
+  /**
+   * Model to switch the conversation to **from this turn on** (doc `29` §5.1).
+   *
+   * Sticky, not per-turn: the Nomi runtime is built from the persisted row, so
+   * the value is written to the conversation and every later turn keeps it.
+   * Omit it and the conversation's current model stays untouched.
+   */
+  model?: ProviderWithModel;
+  /**
+   * Reasoning level to switch the conversation to **from this turn on**
+   * (doc `29` §5.1). Same sticky scope as `model`.
+   */
+  reasoningEffort?: string;
+}
 export declare class ConversationClient {
   private readonly transport;
   constructor(transport: Transport);
@@ -207,12 +247,18 @@ export declare class ConversationClient {
   messages(query: ConversationMessagesQuery): Promise<ConversationMessagesPage>;
   /**
    * R15（W10）：`attachments` 是**会话工作区内的绝对路径**（图片附件）。
+   * doc `27` §4.1：`mentions` 是**本轮挂载的技能**（`kind: "skill"`）——技能的正文与
+   * 不可变快照都随这一轮走；`agent` / `connector` 在 send 上没有载体，服务端会以
+   * `invalid_request` **明确拒绝**（不是静默不挂）。
+   *
+   * 两者缺省都不上 wire，保持老调用方的形状逐字不变；服务端只接受会话工作区内的真实
+   * 文件（越界 / 相对路径 / 不存在一律拒），准入见 `nomifun-app-server` 的
+   * `resolve_conversation_attachments` 与 `send_mention_skills`。
    *
-   * 缺省不传，保持老调用方的 wire 形状逐字不变；服务端只接受会话工作区内的真实
-   * 文件（越界 / 相对路径 / 不存在一律拒），具体准入见
-   * `nomifun-app-server` 的 `resolve_conversation_attachments`。
+   * 第 4 个参数同时接受旧的 `string[]`（附件）与选项对象——再堆一个位置参数会让调用点
+   * 变成一串没有名字的布尔/数组。
    */
-  send(conversationId: string, content: string, idempotencyKey: string, attachments?: string[]): Promise<ConversationSendReceipt>;
+  send(conversationId: string, content: string, idempotencyKey: string, options?: string[] | ConversationSendOptions): Promise<ConversationSendReceipt>;
   cancel(conversationId: string): Promise<ConversationView>;
   delete(conversationId: string): Promise<{
     conversation_id: string;
@@ -326,7 +372,19 @@ export declare class ConnectorClient {
   get(connectorId: string): Promise<ConnectorDetail>;
   /** Combined auth × probe status. `connected` only when auth is ready AND the last probe succeeded. */
   status(connectorId: string): Promise<ConnectorStatusView>;
-  /** Run a connection probe; the server persists the result. */
+  /**
+   * Run a connection probe and report what the connector currently offers —
+   * including each tool's `input_schema`.
+   *
+   * It really connects: a stdio connector gets its child process spawned, an
+   * HTTP/SSE one gets `initialize` + `tools/list`. The result is **persisted**,
+   * so this is also what refreshes the tool list `get()` reads back.
+   *
+   * Named `test` and not `probe` on purpose: this repo's split is `test` for the
+   * action (wire `connector/test`, `test_connection`) and `probe` for its
+   * artifact (`ConnectorProbeResult`, `probe_status`), and every method here is
+   * the last segment of its wire method.
+   */
   test(connectorId: string): Promise<ConnectorProbeResult>;
   /** Check the current OAuth state for a connector. */
   authStatus(connectorId: string): Promise<OAuthStatusView>;
@@ -343,9 +401,17 @@ export declare class ConnectorClient {
    * The host holds the transport, its headers and its OAuth token; this sends a
    * tool name and an argument object and nothing else — you cannot name a URL,
    * a command or a header. Whether the pair is callable at all is the host's
-   * `[connector_proxy]` allowlist, so expect `policy_denied` on a host whose
-   * operator has not listed this tool (that is the default, not a
-   * misconfiguration).
+   * `[connector_proxy]` policy: once its operator turns the proxy on, the
+   * enabled connectors are callable, and `allow` / `deny` are that operator's
+   * optional narrowing and subtraction. So `policy_denied` means either that
+   * the host never turned the proxy on, or that this pair was narrowed out or
+   * explicitly denied — not that a tool name was misspelled in a list you were
+   * supposed to maintain.
+   *
+   * Arguments are passed through verbatim (there is no client-side schema
+   * check); `get()` / `test()` return each tool's `input_schema` so you can see
+   * what it takes, and a parameter the server rejects comes back as
+   * `is_error: true`, not as a rejected promise.
    *
    * Resolves even when the tool itself failed — check `is_error`. It rejects
    * only when the call never reached the tool: `connector_call_timeout`,

package/dist/index.mjs

@@ -275,7 +275,7 @@ var WebSocketTransport = class {
 /** Header the server mints the per-call connection id under. */
 const CONNECTION_HEADER = "x-app-server-connection-id";
 /** Protocol version this binding announces on the one-shot handshake. */
-const PROTOCOL_VERSION = "fp-1";
+const PROTOCOL_VERSION = "fp-7";
 /**
 * Protocol method → REST route. Verified from handler bodies, not from the
 * route list (a route existing does not prove which method it mirrors).
@@ -333,7 +333,10 @@ const HTTP_ROUTES = {
 		body: [
 			"content",
 			"idempotency_key",
-			"attachments"
+			"attachments",
+			"mentions",
+			"model",
+			"reasoning_effort"
 		],
 		source: "conversation_send() -> send_conversation_message_for_user (shared with the WS arm)"
 	},
@@ -794,7 +797,9 @@ var ConversationClient = class {
 			name: input.name,
 			model,
 			workspace: input.workspaceId ? { id: input.workspaceId } : void 0,
-			reasoning_effort: input.reasoningEffort || void 0
+			reasoning_effort: input.reasoningEffort || void 0,
+			agent_id: input.agentId || void 0,
+			team_id: input.teamId || void 0
 		});
 	}
 	update(conversationId, input) {
@@ -827,17 +832,33 @@ var ConversationClient = class {
 	}
 	/**
 	* R15（W10）：`attachments` 是**会话工作区内的绝对路径**（图片附件）。
+	* doc `27` §4.1：`mentions` 是**本轮挂载的技能**（`kind: "skill"`）——技能的正文与
+	* 不可变快照都随这一轮走；`agent` / `connector` 在 send 上没有载体，服务端会以
+	* `invalid_request` **明确拒绝**（不是静默不挂）。
+	*
+	* 两者缺省都不上 wire，保持老调用方的形状逐字不变；服务端只接受会话工作区内的真实
+	* 文件（越界 / 相对路径 / 不存在一律拒），准入见 `nomifun-app-server` 的
+	* `resolve_conversation_attachments` 与 `send_mention_skills`。
 	*
-	* 缺省不传，保持老调用方的 wire 形状逐字不变；服务端只接受会话工作区内的真实
-	* 文件（越界 / 相对路径 / 不存在一律拒），具体准入见
-	* `nomifun-app-server` 的 `resolve_conversation_attachments`。
+	* 第 4 个参数同时接受旧的 `string[]`（附件）与选项对象——再堆一个位置参数会让调用点
+	* 变成一串没有名字的布尔/数组。
 	*/
-	send(conversationId, content, idempotencyKey, attachments = []) {
+	send(conversationId, content, idempotencyKey, options = {}) {
+		const attachments = Array.isArray(options) ? options : options.attachments ?? [];
+		const mentions = Array.isArray(options) ? [] : options.mentions ?? [];
+		const model = Array.isArray(options) ? void 0 : options.model;
+		const reasoningEffort = Array.isArray(options) ? void 0 : options.reasoningEffort;
 		return this.transport.request("conversation/send", {
 			conversation_id: conversationId,
 			content,
 			idempotency_key: idempotencyKey,
-			...attachments.length > 0 ? { attachments } : {}
+			...attachments.length > 0 ? { attachments } : {},
+			...mentions.length > 0 ? { mentions } : {},
+			...model ? { model: {
+				provider_id: model.provider_id,
+				model: model.model
+			} } : {},
+			...reasoningEffort ? { reasoning_effort: reasoningEffort } : {}
 		});
 	}
 	cancel(conversationId) {
@@ -1062,7 +1083,19 @@ var ConnectorClient = class {
 	status(connectorId) {
 		return this.transport.request("connector/status", { connector_id: connectorId });
 	}
-	/** Run a connection probe; the server persists the result. */
+	/**
+	* Run a connection probe and report what the connector currently offers —
+	* including each tool's `input_schema`.
+	*
+	* It really connects: a stdio connector gets its child process spawned, an
+	* HTTP/SSE one gets `initialize` + `tools/list`. The result is **persisted**,
+	* so this is also what refreshes the tool list `get()` reads back.
+	*
+	* Named `test` and not `probe` on purpose: this repo's split is `test` for the
+	* action (wire `connector/test`, `test_connection`) and `probe` for its
+	* artifact (`ConnectorProbeResult`, `probe_status`), and every method here is
+	* the last segment of its wire method.
+	*/
 	test(connectorId) {
 		return this.transport.request("connector/test", { connector_id: connectorId });
 	}
@@ -1087,9 +1120,17 @@ var ConnectorClient = class {
 	* The host holds the transport, its headers and its OAuth token; this sends a
 	* tool name and an argument object and nothing else — you cannot name a URL,
 	* a command or a header. Whether the pair is callable at all is the host's
-	* `[connector_proxy]` allowlist, so expect `policy_denied` on a host whose
-	* operator has not listed this tool (that is the default, not a
-	* misconfiguration).
+	* `[connector_proxy]` policy: once its operator turns the proxy on, the
+	* enabled connectors are callable, and `allow` / `deny` are that operator's
+	* optional narrowing and subtraction. So `policy_denied` means either that
+	* the host never turned the proxy on, or that this pair was narrowed out or
+	* explicitly denied — not that a tool name was misspelled in a list you were
+	* supposed to maintain.
+	*
+	* Arguments are passed through verbatim (there is no client-side schema
+	* check); `get()` / `test()` return each tool's `input_schema` so you can see
+	* what it takes, and a parameter the server rejects comes back as
+	* `is_error: true`, not as a rejected promise.
 	*
 	* Resolves even when the tool itself failed — check `is_error`. It rejects
 	* only when the call never reached the tool: `connector_call_timeout`,
@@ -1388,7 +1429,12 @@ function toWire(input) {
 		steps: input.steps,
 		command_id: input.commandId,
 		idempotency_key: input.idempotencyKey,
-		mentions: input.mentions
+		mentions: input.mentions,
+		model: input.model ? {
+			provider_id: input.model.provider_id,
+			model: input.model.model
+		} : void 0,
+		reasoning_effort: input.reasoningEffort || void 0
 	};
 }
 function toTeamWire(input) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flowy-agent-store/client",
-  "version": "0.1.0-beta.4",
+  "version": "0.1.0-beta.5",
   "description": "Transport-agnostic App Server client (docs/agent-store/07 §2.2)",
   "type": "module",
   "license": "Apache-2.0",
@@ -25,7 +25,7 @@
     "dist"
   ],
   "dependencies": {
-    "@flowy-agent-store/protocol": "0.1.0-beta.4"
+    "@flowy-agent-store/protocol": "0.1.0-beta.5"
   },
   "scripts": {
     "build": "tsdown",