@roll-agent/smart-reply-agent 1.3.1 → 1.3.3

package/SKILL.md

@@ -32,7 +32,7 @@ npm 包名：`@roll-agent/smart-reply-agent`
 
 完整 inputSchema 可通过 `roll agent tools smart-reply-agent`（或 `--json`）查询。
 
-- `generate_reply(candidateMessage, conversationHistory?, candidateInfo?, preferredBrand?, channelType?, defaultWechatId?, industryVoiceId?, turnIndex?, modelConfig?, target)`
+- `generate_reply(candidateMessage, conversationHistory?, candidateInfo?, preferredBrand?, preferredBrandId?, channelType?, defaultWechatId?, industryVoiceId?, turnIndex?, modelConfig?, target)`
   调用 Reply Authority Service 的 `POST /generate-signed-reply`，返回 `suggestedReply`、`signedEnvelope`、`envelopeExp`、`confidence`、`stage` 和可选 `diagnostics`。`target` 为必填，至少包含 `platform=zhipin`、`conversationId`、`candidateId`，以及以下两种 recruiter 绑定方式之一：
   1. 直接传完整绑定：`tenantId + recruiterBinding`
   2. 便利代理模式：`recruiterUsername`（smart-reply 会先调用 `POST /resolve-recruiter-binding` 解析出 `tenantId + recruiterBinding`）
@@ -54,8 +54,8 @@ npm 包名：`@roll-agent/smart-reply-agent`
 
   - 调用前应先尝试从页面读取 `candidateInfo.communicationPosition`、`candidateInfo.expectedLocation`、`candidateInfo.expectedPosition`
   - 能读到就如实透传；读不到就省略该字段
-  - `preferredBrand` 为可选页面信号：若 `browser-use-agent` 提取到的 `communicationPosition` 含连字符类分隔符（`-` / `－` / `—` / `–`），则取第一段透传；没有分隔符就省略该字段
-  - 严禁把通用岗位名（如“餐饮兼职服务员”“门店服务员”）或候选人现/前雇主公司名塞进 `preferredBrand`
+  - `preferredBrand` / `preferredBrandId` 为可选页面信号，只能原样透传 `browser-use-agent` `zhipin_get_candidate_info` 的输出字段：沟通职位带 `[品牌ID]` 尾缀（如 `咖啡早班店员-接受小白-免费咖啡[10027]`）时工具会输出 `preferredBrandId`，只透传它；老格式 `品牌名-职位` 时工具输出 `preferredBrand`，只透传它；都读不到就都省略
+  - 不要自行从 `communicationPosition` 解析品牌（服务端会以 `candidateInfo.communicationPosition` 为权威自行提取品牌 ID 并对账）；严禁把通用岗位名（如“餐饮兼职服务员”“门店服务员”）、候选人现/前雇主公司名或新格式的第一段塞进 `preferredBrand`
 
   Minimal valid input 示例（代理模式）：
 
@@ -116,6 +116,7 @@ npm 包名：`@roll-agent/smart-reply-agent`
 - 实际回复生成、reply-policy、FactGate、ReplyGate、年龄校验都在云端执行
 - `modelConfig.reasoning` 会透传给 Reply Authority Service；raw reasoning/thinking 文本不会作为业务输出返回
 - 返回的 `signedEnvelope` 为 v2 信封，已绑定 `tenantId + recruiterBinding + conversationId + candidateId`；浏览器发送主链路应优先使用 `browser-use-agent.zhipin_generate_reply_preview(...) -> zhipin_send_prepared_reply(preparedReplyId)`
+- 若服务端返回 `replyVariants`，`generate_reply` 只做协议透传；它不会隐藏 `signedEnvelope`，也不会执行 judge / `/reply-feedback`。需要双稿闭环时，主链路必须改用 `browser-use-agent.zhipin_generate_reply_preview(...) -> zhipin_judge_prepared_reply(...) -> zhipin_send_prepared_reply(...)`
 - 调用失败时抛 `ReplyAuthorityRequestError`，携带 `meta: {url, timeoutMs, requestId}` 与 `Error.cause` 链。通过 `roll run` 运行时 stderr 会展开 `cause: ...` 行用于定位；透传的 `x-request-id` 可跨服务端追踪
 - `diagnostics.brandResolutionSource="none"`、`diagnostics.resolvedBrand=""`、`diagnostics.ageGate.status="unknown"` 都是合法服务端结果，不代表 tool 调用失败。是否补问用户或转人工，是 orch 层策略，不是本 Agent 的重试条件
 
@@ -136,13 +137,13 @@ npm 包名：`@roll-agent/smart-reply-agent`
    - `candidateInfo.communicationPosition`
    - `candidateInfo.expectedLocation`
    - `candidateInfo.expectedPosition`
-   - `preferredBrand`：若 `browser-use-agent` 从 `communicationPosition` 里识别到“品牌-职位”格式，则透传第一段；否则保持缺省
+   - `preferredBrand` / `preferredBrandId`：原样透传 `zhipin_get_candidate_info` 的输出字段（新命名 `…[品牌ID]` 给 `preferredBrandId`，老命名“品牌-职位”给 `preferredBrand`，互斥）；否则保持缺省
    - 如果读不到，保持缺省；不要用通用岗位名或候选人公司名冒充品牌
 4. 调用 `smart-reply-agent.generate_reply(..., target)`：
    - 直接模式：传 `target.tenantId + target.recruiterBinding`
    - 代理模式：只传 `target.recruiterUsername=username`，由 smart-reply 代调用 `POST /resolve-recruiter-binding`
-5. `smart-reply-agent.generate_reply(..., target)` 获取 `suggestedReply + signedEnvelope`
-6. 若需要在 BOSS 浏览器中展示生成过程并发送，优先改用 `browser-use-agent.zhipin_generate_reply_preview(...) -> zhipin_send_prepared_reply(preparedReplyId)`，不要把 `signedEnvelope` 作为跨 Agent 编排参数传递
+5. `smart-reply-agent.generate_reply(..., target)` 获取 `suggestedReply + signedEnvelope`，并在服务端开启双稿时透传 `replyVariants`
+6. 若需要在 BOSS 浏览器中展示生成过程、隐藏 `signedEnvelope`、执行默认 judge 或回传 `/reply-feedback`，优先改用 `browser-use-agent.zhipin_generate_reply_preview(...) -> zhipin_judge_prepared_reply(...) -> zhipin_send_prepared_reply(preparedReplyId, variantDecision?)`，不要把 `signedEnvelope` 作为跨 Agent 编排参数传递
 
 ## Recommended roll.config.yaml
 

package/dist/index.js

@@ -1 +1 @@
-import{defineAgent as e}from"@roll-agent/sdk";import{defineTool as r}from"@roll-agent/sdk";import{z as t}from"zod";import{createHash as o}from"node:crypto";import{z as n}from"zod";var i=["REPLY_AUTHORITY_URL","REPLY_AUTHORITY_BEARER_TOKEN","REPLY_AUTHORITY_TIMEOUT_MS"],a=/^[0-9a-f]{8}$/,s=n.object({present:n.boolean(),fingerprint:n.string().regex(a).optional()}),c=n.record(s);function p(e,r=process.env){return Object.fromEntries(e.map(e=>{const t=r[e];return"string"==typeof t&&t.length>0?[e,{present:!0,fingerprint:l(t)}]:[e,{present:!1}]}))}function l(e){return o("sha256").update(e).digest("hex").slice(0,8)}var g=t.object({effectiveEnvSources:c}),m=r({name:"diagnostic_status",description:"返回 smart-reply 运行态进程中已声明环境变量的存在状态与短指纹",input:t.object({}),output:g,execute:async(e,r)=>(r.logger.info("Querying smart-reply diagnostic status"),{effectiveEnvSources:p(i)})});import{defineTool as f}from"@roll-agent/sdk";import{generateSignedReply as u,ReplyAuthorityRequestError as d}from"@roll-agent/reply-authority-client";import{CandidateInfoSchema as y,CandidateLocationSignalIntentValues as E,CandidateLocationSignalSchema as R,CandidateLocationSignalSourceValues as T,FunnelStageSchema as _,FunnelStageValues as v,GenerateReplyToolInputSchema as h,GenerateSignedReplyRequestSchema as O,GenerateSignedReplyResponseSchema as S,ModelConfigSchema as U,ProviderConfigSchema as Y,ProviderConfigsSchema as b,ReasoningConfigSchema as x,RecruiterBindingSchema as A,ReplyAuthorityErrorResponseSchema as I,ReplyAuthorityTargetSchema as j,ResolvedReplyAuthorityTargetSchema as L,ResolveRecruiterBindingRequestSchema as P,ResolveRecruiterBindingResponseSchema as $}from"@roll-agent/reply-authority-client";var k=f({name:"generate_reply",description:"根据候选人消息生成智能招聘回复，并向 Reply Authority Service 请求签名信封；调用方必须提供 target 以绑定会话和招聘者身份，可直接传 tenantId+recruiterBinding，或只传 recruiterUsername 交给 smart-reply 代理解析。",input:h,output:S,execute:async(e,r)=>{r.logger.info(`Processing message: ${e.candidateMessage.slice(0,50)}...`);const t=await u(e);return r.logger.info(`Signed reply generated. Stage: ${t.stage}, Confidence: ${t.confidence}`),t}}),z=e({name:"smart-reply-agent",tools:[k,m]});z.listen().catch(e=>{console.error("Fatal error:",e),process.exit(1)});
+import{defineAgent as e}from"@roll-agent/sdk";import{defineTool as r}from"@roll-agent/sdk";import{z as t}from"zod";import{createHash as o}from"node:crypto";import{z as n}from"zod";var i=["REPLY_AUTHORITY_URL","REPLY_AUTHORITY_BEARER_TOKEN","REPLY_AUTHORITY_TIMEOUT_MS"],a=/^[0-9a-f]{8}$/,s=n.object({present:n.boolean(),fingerprint:n.string().regex(a).optional()}),c=n.record(s);function p(e,r=process.env){return Object.fromEntries(e.map(e=>{const t=r[e];return"string"==typeof t&&t.length>0?[e,{present:!0,fingerprint:l(t)}]:[e,{present:!1}]}))}function l(e){return o("sha256").update(e).digest("hex").slice(0,8)}var g=t.object({effectiveEnvSources:c}),m=r({name:"diagnostic_status",description:"返回 smart-reply 运行态进程中已声明环境变量的存在状态与短指纹",input:t.object({}),output:g,execute:async(e,r)=>(r.logger.info("Querying smart-reply diagnostic status"),{effectiveEnvSources:p(i)})});import{defineTool as f}from"@roll-agent/sdk";import{generateSignedReply as u,ReplyAuthorityRequestError as d}from"@roll-agent/reply-authority-client";import{CandidateInfoSchema as y,CandidateLocationSignalIntentValues as E,CandidateLocationSignalSchema as R,CandidateLocationSignalSourceValues as T,FunnelStageSchema as _,FunnelStageValues as v,GenerateReplyToolInputSchema as h,GenerateSignedReplyRequestSchema as O,GenerateSignedReplyResponseSchema as S,ModelConfigSchema as U,ProviderConfigSchema as Y,ProviderConfigsSchema as b,ReasoningConfigSchema as x,RecruiterBindingSchema as A,ReplyAuthorityErrorResponseSchema as I,ReplyFeedbackBodySchema as j,ReplyFeedbackResponseSchema as L,ReplyFeedbackRubricResponseSchema as P,ReplyGateAdvisoryCodeSchema as $,ReplyAuthorityTargetSchema as k,ReplyVariantFindingSchema as z,ReplyVariantItemSchema as H,ReplyVariantKindSchema as M,ReplyVariantsSchema as B,ResolvedReplyAuthorityTargetSchema as w,ResolveRecruiterBindingRequestSchema as C,ResolveRecruiterBindingResponseSchema as F}from"@roll-agent/reply-authority-client";var K=f({name:"generate_reply",description:"根据候选人消息生成智能招聘回复，并向 Reply Authority Service 请求签名信封；调用方必须提供 target 以绑定会话和招聘者身份，可直接传 tenantId+recruiterBinding，或只传 recruiterUsername 交给 smart-reply 代理解析。",input:h,output:S,execute:async(e,r)=>{r.logger.info(`Processing message: ${e.candidateMessage.slice(0,50)}...`);const t=await u(e);return r.logger.info(`Signed reply generated. Stage: ${t.stage}, Confidence: ${t.confidence}`),t}}),N=e({name:"smart-reply-agent",tools:[K,m]});N.listen().catch(e=>{console.error("Fatal error:",e),process.exit(1)});

package/dist/tools/generate-reply.d.ts

@@ -40,6 +40,7 @@ export declare const generateReply: import("@roll-agent/sdk").ToolDefinition<{
         intent?: "nearby_store" | "store_address" | "expected_area" | undefined;
     }[] | undefined;
     preferredBrand?: string | undefined;
+    preferredBrandId?: number | undefined;
     channelType?: "public" | "private" | undefined;
     defaultWechatId?: string | undefined;
     industryVoiceId?: string | undefined;
@@ -70,4 +71,20 @@ export declare const generateReply: import("@roll-agent/sdk").ToolDefinition<{
     latencyMs?: number | undefined;
     shouldExchangeWechat?: boolean | undefined;
     diagnostics?: Record<string, unknown> | undefined;
+    replyVariants?: {
+        groupId: string;
+        recommended: "draft";
+        items: {
+            variant: "draft" | "revised";
+            suggestedReply: string;
+            signedEnvelope: string;
+            envelopeExp: number;
+        }[];
+        findings: {
+            code: "too_many_questions" | "audit_tone" | "reply_overpacked" | "off_axis_fact_disclosure";
+            description: string;
+        }[];
+        rubricVersion: string;
+        rubricHash: string;
+    } | undefined;
 }>;

package/dist/types/reply-authority.d.ts

@@ -1,2 +1,2 @@
-export { CandidateInfoSchema, CandidateLocationSignalIntentValues, CandidateLocationSignalSchema, CandidateLocationSignalSourceValues, FunnelStageSchema, FunnelStageValues, GenerateReplyToolInputSchema, GenerateSignedReplyRequestSchema, GenerateSignedReplyResponseSchema, ModelConfigSchema, ProviderConfigSchema, ProviderConfigsSchema, ReasoningConfigSchema, RecruiterBindingSchema, ReplyAuthorityErrorResponseSchema, ReplyAuthorityTargetSchema, ResolvedReplyAuthorityTargetSchema, ResolveRecruiterBindingRequestSchema, ResolveRecruiterBindingResponseSchema, } from "@roll-agent/reply-authority-client";
-export type { CandidateInfo, CandidateLocationSignal, FunnelStage, GenerateReplyToolInput, GenerateSignedReplyRequest, GenerateSignedReplyResponse, ModelConfig, ProviderConfig, ProviderConfigs, ReasoningConfig, RecruiterBinding, ReplyAuthorityTarget, ResolvedReplyAuthorityTarget, ResolveRecruiterBindingRequest, ResolveRecruiterBindingResponse, } from "@roll-agent/reply-authority-client";
+export { CandidateInfoSchema, CandidateLocationSignalIntentValues, CandidateLocationSignalSchema, CandidateLocationSignalSourceValues, FunnelStageSchema, FunnelStageValues, GenerateReplyToolInputSchema, GenerateSignedReplyRequestSchema, GenerateSignedReplyResponseSchema, ModelConfigSchema, ProviderConfigSchema, ProviderConfigsSchema, ReasoningConfigSchema, RecruiterBindingSchema, ReplyAuthorityErrorResponseSchema, ReplyFeedbackBodySchema, ReplyFeedbackResponseSchema, ReplyFeedbackRubricResponseSchema, ReplyGateAdvisoryCodeSchema, ReplyAuthorityTargetSchema, ReplyVariantFindingSchema, ReplyVariantItemSchema, ReplyVariantKindSchema, ReplyVariantsSchema, ResolvedReplyAuthorityTargetSchema, ResolveRecruiterBindingRequestSchema, ResolveRecruiterBindingResponseSchema, } from "@roll-agent/reply-authority-client";
+export type { CandidateInfo, CandidateLocationSignal, FunnelStage, GenerateReplyToolInput, GenerateSignedReplyRequest, GenerateSignedReplyResponse, ModelConfig, ProviderConfig, ProviderConfigs, ReasoningConfig, RecruiterBinding, ReplyFeedbackBody, ReplyFeedbackResponse, ReplyFeedbackRubricResponse, ReplyGateAdvisoryCode, ReplyAuthorityTarget, ReplyVariantFinding, ReplyVariantItem, ReplyVariantKind, ReplyVariants, ResolvedReplyAuthorityTarget, ResolveRecruiterBindingRequest, ResolveRecruiterBindingResponse, } from "@roll-agent/reply-authority-client";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@roll-agent/smart-reply-agent",
-  "version": "1.3.1",
+  "version": "1.3.3",
   "type": "module",
   "repository": {
     "type": "git",
@@ -41,8 +41,8 @@
   },
   "dependencies": {
     "zod": "^3.25.76",
-    "@roll-agent/sdk": "0.2.0",
-    "@roll-agent/reply-authority-client": "0.3.0"
+    "@roll-agent/reply-authority-client": "0.5.0",
+    "@roll-agent/sdk": "0.2.0"
   },
   "devDependencies": {
     "@types/node": "^22.0.0"