@ikenxuan/amagi 7.0.0-beta.4 → 7.0.0-beta.6

package/dist/exports/compat.mjs

@@ -1,4 +1,4 @@
-import { $ as unwrap, A as douyinFetcher, B as xiaohongshuSign, C as ValidationError, Ct as parseDmSegMobileReply, D as createBoundKuaishouFetcher, E as xiaohongshuFetcher, F as bilibiliFetcher, G as createDouyinRoutes, H as createKuaishouRoutes, I as createBoundBilibiliFetcher, J as bilibiliUtils, K as passport_exports, L as createClient, M as requestPassportQrcode, N as sendPassportVerifyCode, O as kuaishouFetcher, P as validatePassportVerifyCode, Q as isSuccess, R as xiaohongshuUtils, S as ApiError, St as emitNetworkRetry, T as createBoundXiaohongshuFetcher, Tt as bv2av, U as kuaishouSign, V as kuaishouUtils, W as douyinUtils, X as AmagiThrownError, Y as createBilibiliRoutes, Z as isFailure, _ as validateBilibiliParams, _t as emitLogError, a as AdditionalType, at as wbi_sign, b as validateXiaohongshuParams, bt as emitLogWarn, c as createAmagiClient, ct as fetchResponse, d as assertValidBilibiliParams, dt as emitApiError, et as AMAGI_BUS_EVENT_NAMES, f as assertValidDouyinParams, ft as emitApiSuccess, g as createSuccessResponse, gt as emitLogDebug, h as createErrorResponse, ht as emitLog, i as DynamicType, it as qtparam, j as checkPassportQrcode, k as createBoundDouyinFetcher, l as kuaishouApiUrls, lt as isNetworkErrorResult, m as assertValidXiaohongshuParams, mt as emitHttpResponse, n as CreateApp, nt as KUAISHOU_PC_CAPTCHA_RESULT, o as MajorType, ot as bilibiliApiUrls, p as assertValidKuaishouParams, pt as emitHttpRequest, q as douyinSign, r as amagi, rt as parseKuaishouCaptcha, s as CommentType, st as fetchData, tt as KUAISHOU_H5_CAPTCHA_RESULT, u as douyinApiUrls, ut as amagiEvents, v as validateDouyinParams, vt as emitLogInfo, w as handleError, wt as av2bv, x as xiaohongshuApiUrls, xt as emitNetworkError, y as validateKuaishouParams, yt as emitLogMark, z as createXiaohongshuRoutes } from "../src-ocSC1FCs.mjs";
+import { $ as unwrap, A as douyinFetcher, B as xiaohongshuSign, C as ValidationError, Ct as parseDmSegMobileReply, D as createBoundKuaishouFetcher, E as xiaohongshuFetcher, F as bilibiliFetcher, G as createDouyinRoutes, H as createKuaishouRoutes, I as createBoundBilibiliFetcher, J as bilibiliUtils, K as passport_exports, L as createClient, M as requestPassportQrcode, N as sendPassportVerifyCode, O as kuaishouFetcher, P as validatePassportVerifyCode, Q as isSuccess, R as xiaohongshuUtils, S as ApiError, St as emitNetworkRetry, T as createBoundXiaohongshuFetcher, Tt as bv2av, U as kuaishouSign, V as kuaishouUtils, W as douyinUtils, X as AmagiThrownError, Y as createBilibiliRoutes, Z as isFailure, _ as validateBilibiliParams, _t as emitLogError, a as AdditionalType, at as wbi_sign, b as validateXiaohongshuParams, bt as emitLogWarn, c as createAmagiClient, ct as fetchResponse, d as assertValidBilibiliParams, dt as emitApiError, et as AMAGI_BUS_EVENT_NAMES, f as assertValidDouyinParams, ft as emitApiSuccess, g as createSuccessResponse, gt as emitLogDebug, h as createErrorResponse, ht as emitLog, i as DynamicType, it as qtparam, j as checkPassportQrcode, k as createBoundDouyinFetcher, l as kuaishouApiUrls, lt as isNetworkErrorResult, m as assertValidXiaohongshuParams, mt as emitHttpResponse, n as CreateApp, nt as KUAISHOU_PC_CAPTCHA_RESULT, o as MajorType, ot as bilibiliApiUrls, p as assertValidKuaishouParams, pt as emitHttpRequest, q as douyinSign, r as amagi, rt as parseKuaishouCaptcha, s as CommentType, st as fetchData, tt as KUAISHOU_H5_CAPTCHA_RESULT, u as douyinApiUrls, ut as amagiEvents, v as validateDouyinParams, vt as emitLogInfo, w as handleError, wt as av2bv, x as xiaohongshuApiUrls, xt as emitNetworkError, y as validateKuaishouParams, yt as emitLogMark, z as createXiaohongshuRoutes } from "../src-BHqC-g47.mjs";
 //#region src/exports/compat.ts
 /** 模块级只执行一次的迁移提示（不刷屏） */
 emitLogWarn("[@ikenxuan/amagi/compat] 你正在使用 v6 兼容入口；v7 迁移说明见 https://github.com/ikenxuan/amagi （v8 将移除 compat）");

package/dist/exports/sign-steps.cjs

@@ -0,0 +1,69 @@
+Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
+const require_steps = require("../steps-BO8NYQHx.cjs");
+//#region src/exports/sign-steps.ts
+/**
+* 反爬参数的**原子 step 工厂**：给 `client.<平台>.request` 做精细签名控制用。
+*
+* ## 它解决什么
+*
+* 端点声明里的 `sign` 早就能写成 `SignStep[]`，但 `client.<平台>.request` 这条裸请求路
+* 过去只能选一个注册名（`sign: 'a-bogus'`）或干脆不签（`sign: false`）——想「要 a_bogus
+* 但换个 msToken 长度」「只签 x_bogus 不要 secsdk」都没有出口。本入口把四平台的 step 工厂
+* 放出来，配合 `amagi.sign` 收 `SignDecl`，调用方可以自己列：
+*
+* ```ts
+* import { douyin } from '@ikenxuan/amagi/sign-steps'
+*
+* // 自己挑要哪些、调参数（这里用 200 长度的 msToken，且不加 secsdk 收尾）
+* await client.douyin.request.get(url, { amagi: { sign: [douyin.msToken(200), douyin.aBogus()] } })
+* ```
+*
+* runtime 按 `phase`（`prepare` → `token` → `sign` → `finalize`）稳定排序后依次执行，
+* 所以数组顺序写反也不翻车（`[douyin.aBogus(), douyin.msToken()]` 与
+* `[douyin.msToken(), douyin.aBogus()]` 等价）。
+*
+* ## 与默认签名同源
+*
+* 这些工厂就是端点声明和平台签名器表内部用的同一批（阶段 2 已把两条路统一到一份实现）。
+* 所以你手挑的 `[bilibili.wbi()]` 与不挑时的默认 `'wbi'` 压的是同一个签名器实例、同一份
+* `/nav` 缓存，签出来必然一致。带状态的签名器（B站 wbi keys、快手 hxfalcon count）是进程级共享的。
+*
+* ## 命名：按平台分命名空间
+*
+* step 工厂按平台归入四个命名空间对象（`douyin` / `bilibili` / `kuaishou` / `xiaohongshu`），
+* 而不是平铺到一个入口 —— `douyin.msToken()` 一眼看出归属，也不会随平台增多而重名。
+* `douyin.douyinBogus` / `douyin.douyinXBogus` 是抖音的常用组合预设
+* （`[msToken, aBogus, secsdk]` / `[…, xBogus, …]`）。
+*
+* 类型（`SignStep` / `SignPhase` / `SignFn` / `SignDecl`）不属于任何单一平台，平铺导出，
+* 方便写辅助函数的入参 / 返回值。
+*
+* @module @ikenxuan/amagi/sign-steps
+*/
+/** 抖音的反爬参数 step 工厂与组合预设 */
+const douyin = {
+	msToken: require_steps.msToken,
+	aBogus: require_steps.aBogus,
+	xBogus: require_steps.xBogus,
+	secsdk: require_steps.secsdk,
+	douyinBogus: require_steps.douyinBogus,
+	douyinXBogus: require_steps.douyinXBogus
+};
+/** B站的反爬参数 step 工厂 */
+const bilibili = {
+	wbi: require_steps.wbi,
+	qtparam: require_steps.qtparam
+};
+/** 快手的反爬参数 step 工厂 */
+const kuaishou = { hxfalcon: require_steps.hxfalcon };
+/** 小红书的反爬参数 step 工厂 */
+const xiaohongshu = {
+	xs: require_steps.xs,
+	traceId: require_steps.traceId,
+	rap: require_steps.rap
+};
+//#endregion
+exports.bilibili = bilibili;
+exports.douyin = douyin;
+exports.kuaishou = kuaishou;
+exports.xiaohongshu = xiaohongshu;

package/dist/exports/sign-steps.d.ts

@@ -0,0 +1,202 @@
+import { C as KuaishouLiveApiRequest, c as SignPhase, l as SignStep, o as SignDecl, s as SignFn } from "../endpoint-CxOrmO8L.js";
+//#region src/platforms/bilibili/sign/steps.d.ts
+/** `wbi`：URL 追加 `&wts=&w_rid=`（comments / userDynamicList / userSpaceInfo） */
+declare const wbi: () => SignStep;
+/**
+ * `qtparam`：视频流专属。登录判断 + fnval 档位 + wbi 签名强耦合，整体封成一个单元
+ * （fnval 依赖 vipStatus、且必须加在「基于原始 URL 的 wbi 签名」之后，拆开必错）。
+ */
+declare const qtparam: () => SignStep;
+//#endregion
+//#region src/platforms/douyin/sign/steps.d.ts
+/**
+ * `msToken`：本地随机令牌，长度按端点定（作品详情类 184、评论/音乐等 116）。
+ *
+ * phase = `'token'`：必须先于 a_bogus / x_bogus 进 URL —— 主签名算的是含 msToken 的整条 URL。
+ *
+ * 前置：URL 必须是绝对地址。**这道校验不能省** —— 本单元在 phase 序里先于 {@link aBogus} /
+ * {@link xBogus}，相对 URL 会在这里就撞上 `new URL()`，抛裸 `TypeError: Invalid URL`，把
+ * 后面那两句「前置条件不满足」的明确报错整个盖掉（信封 kind 仍是 internal，但 message
+ * 没法告诉调用方到底哪里不对）。
+ *
+ * **会覆盖 URL 里已有的 `msToken`**。对端点无影响（`build` 不再写这个参数）；对
+ * `client.<平台>.request` 那条路，调用方自己拼的值会被换掉。选「覆盖」而非「有则不动」，
+ * 是因为后者会让 `retryFresh` 的重试一直复用调用方那个过期 token —— Argus 按**单次请求的
+ * token 组**判定，重放必然同样被拦，重试就白跑了。真要自己掌控的调用方，不放本单元即可
+ * （`sign: [aBogus(), secsdk()]`），URL 里原有的 msToken 就会留着。
+ * @param length - `==` 之前的随机段长度
+ */
+declare const msToken: (length: number) => SignStep;
+/**
+ * `a_bogus` 签名（内部先补 webid，命中 ttwid 缓存才补）。
+ *
+ * 前置：URL 必须是绝对地址，不满足抛错（execute 归因 `kind: 'internal'`）。不含 secsdk ——
+ * 需要收尾签名的端点再 append 一个 {@link secsdk}。
+ */
+declare const aBogus: () => SignStep;
+/**
+ * `X-Bogus` 签名（内部先补 webid）。
+ *
+ * 前置：真实接口形态的长路径（≥3 段且带查询串），不满足抛错。不含 secsdk。
+ */
+declare const xBogus: () => SignStep;
+/**
+ * `x-secsdk-web-signature` 收尾：策略表内的 path 才改写整条 URL，表外原样返回（append 恒安全）。
+ *
+ * phase = `'finalize'`：必须是最后一步。
+ */
+declare const secsdk: () => SignStep;
+/**
+ * 抖音作品 / 接口类的常用组合：msToken + a_bogus + secsdk。
+ * @param msLen - msToken 随机段长度
+ */
+declare const douyinBogus: (msLen: number) => SignStep[];
+/**
+ * x_bogus 版组合：msToken + X-Bogus + secsdk（如 commentReplies）。
+ * @param msLen - msToken 随机段长度
+ */
+declare const douyinXBogus: (msLen: number) => SignStep[];
+//#endregion
+//#region src/platforms/kuaishou/sign/helpers.d.ts
+/**
+ * 快手 `__NS_hxfalcon` 组包所需的标准化载荷。
+ *
+ * 这里的 `url` 已经是参与签名的规范路径，而不是最终请求 URL。
+ */
+type KuaishouHxfalconPayload = {
+  url: string;
+  query: Record<string, string>;
+  form: Record<string, string>;
+  requestBody: Record<string, unknown>;
+};
+//#endregion
+//#region src/platforms/kuaishou/sign/index.d.ts
+/**
+ * 快手 `live_api` 请求签名结果。
+ */
+type KuaishouLiveApiSignature = {
+  url: string;
+  headers: Record<string, string>;
+  signResult: string;
+  signInput: string;
+  catVersion: string;
+};
+/**
+ * 快手签名器（**实例级**）。
+ *
+ * 签名状态（`count` / `startupRandom` / 匿名 `kww` 缓存）随实例走，不挂在模块级
+ * 单例上 —— 同进程内两个 client 的签名互不干扰：
+ * - `count` 每次签名递增，但只影响当前实例。
+ * - 匿名 `kww` 按实例缓存（同一实例内复用，不同实例各自生成）。
+ * - `startupRandom` 按实例生成。
+ */
+declare class KuaishouSigner {
+  private readonly runtimeState;
+  private readonly anonymousKwwCache;
+  constructor();
+  /**
+   * 获取当前纯算法运行时使用的 `caver`。
+   * @returns 快手 `caver` 值
+   */
+  getCatVersion(): string;
+  /**
+   * 生成快手请求头中的 `kww` 值（匿名分支按实例缓存）。
+   * @param cookie - 原始 Cookie 字符串
+   * @returns `kww` 请求头值
+   */
+  generateKww(cookie?: string): string;
+  /**
+   * 根据结构化签名载荷生成 `__NS_hxfalcon`。
+   *
+   * `count` 随实例递增：同一实例内连续签名结果不同（防重放），
+   * 但两个实例的 `count` 互不干扰。
+   *
+   * @param payload - 已标准化的快手签名载荷
+   * @returns 包含最终签名串、sign input 与 `caver` 的结果
+   */
+  generateHxfalconFromPayload(payload: KuaishouHxfalconPayload): Pick<KuaishouLiveApiSignature, 'signResult' | 'signInput' | 'catVersion'>;
+  /**
+   * 为快手 `live_api` / H5 URL 签名。
+   * @param url - 实际请求 URL
+   * @param cookie - 原始 Cookie 字符串
+   * @param signPath - 可选的规范签名路径
+   * @param requestBody - 参与签名的请求体（POST 端点必传，见 helpers 的说明）
+   * @returns 带签名 URL、附加请求头和调试信息
+   */
+  signLiveApiUrl(url: string, cookie?: string, signPath?: string, requestBody?: Record<string, unknown>): KuaishouLiveApiSignature;
+  /**
+   * 为结构化的快手 `live_api` 请求描述对象签名。
+   *
+   * 入参与静态类 {@link kuaishouSign} 相同，但状态随实例。
+   *
+   * @param request - 快手 `live_api` 请求描述对象
+   * @param cookie - 原始 Cookie 字符串
+   * @param requestBody - 参与签名的请求体
+   * @returns 带签名 URL、附加请求头和调试信息
+   */
+  signLiveApiRequest(request: KuaishouLiveApiRequest, cookie?: string, requestBody?: Record<string, unknown>): KuaishouLiveApiSignature;
+  /**
+   * 清空实例的签名状态（测试隔离用）。对称于 B站的 `WbiSigner.reset()`。
+   *
+   * 两份状态都清：
+   * - `runtimeState`：`count` 回到默认、`startupRandom` 重取（`catVersion` 一并归位）。
+   * - `anonymousKwwCache`：清空缓存值，下次 `generateKww` 重新生成匿名 `kww`。
+   *
+   * 这两个字段是 `private readonly` —— readonly 只禁止给字段重新赋值，改对象内部属性
+   * 仍然允许。这里复用 `createKuaishouPureRuntimeState()` 取初值，不必把 `state.ts` 的
+   * 默认常量对外暴露。不改签名算法本身的任何行为，只把状态清零。
+   */
+  reset(): void;
+}
+//#endregion
+//#region src/platforms/kuaishou/sign/steps.d.ts
+/**
+ * `__NS_hxfalcon` 签名（live_api 与 H5 共用一套算法，区别只在喂什么料）。
+ *
+ * `signer` 缺省用模块级 {@link sharedKuaishouSigner}（端点声明走这条）；`signers.ts`
+ * 需要注入独立实例时传入，这样注入的 `count` 状态才生效。
+ * @param signer - 签名器实例，缺省用共享实例
+ * @returns `sign` 阶段的签名步骤
+ */
+declare const hxfalcon: (signer?: KuaishouSigner) => SignStep;
+//#endregion
+//#region src/platforms/xiaohongshu/sign/steps.d.ts
+/**
+ * `x-s` + `x-s-common` + `x-t` + `x-xray-traceid` 四个签名头。
+ *
+ * @param method - GET 签 query、POST 签 body
+ * @param protocol - `'xys'` 传统 / `'xyw'` 绕 406（2026-03 后数据接口必用）
+ */
+declare const xs: (method: 'get' | 'post', protocol: 'xys' | 'xyw') => SignStep;
+/** `x-b3-traceid`（userNoteList / noteComments 需要），phase = `'finalize'` */
+declare const traceId: () => SignStep;
+/** `x-rap-param`（feed / 搜索 / 发布类需要），phase = `'finalize'`。api 入参去协议、保留 `//host/path` */
+declare const rap: () => SignStep;
+//#endregion
+//#region src/exports/sign-steps.d.ts
+/** 抖音的反爬参数 step 工厂与组合预设 */
+export declare const douyin: {
+  readonly msToken: typeof msToken;
+  readonly aBogus: typeof aBogus;
+  readonly xBogus: typeof xBogus;
+  readonly secsdk: typeof secsdk;
+  readonly douyinBogus: typeof douyinBogus;
+  readonly douyinXBogus: typeof douyinXBogus;
+};
+/** B站的反爬参数 step 工厂 */
+export declare const bilibili: {
+  readonly wbi: typeof wbi;
+  readonly qtparam: typeof qtparam;
+};
+/** 快手的反爬参数 step 工厂 */
+export declare const kuaishou: {
+  readonly hxfalcon: typeof hxfalcon;
+};
+/** 小红书的反爬参数 step 工厂 */
+export declare const xiaohongshu: {
+  readonly xs: typeof xs;
+  readonly traceId: typeof traceId;
+  readonly rap: typeof rap;
+};
+//#endregion
+export type { SignDecl, SignFn, SignPhase, SignStep };

package/dist/exports/sign-steps.mjs

@@ -0,0 +1,65 @@
+import { C as wbi, S as qtparam, d as douyinBogus, f as douyinXBogus, h as xBogus, m as secsdk, n as traceId, p as msToken, r as xs, s as hxfalcon, t as rap, u as aBogus } from "../steps-DQlwODdh.mjs";
+//#region src/exports/sign-steps.ts
+/**
+* 反爬参数的**原子 step 工厂**：给 `client.<平台>.request` 做精细签名控制用。
+*
+* ## 它解决什么
+*
+* 端点声明里的 `sign` 早就能写成 `SignStep[]`，但 `client.<平台>.request` 这条裸请求路
+* 过去只能选一个注册名（`sign: 'a-bogus'`）或干脆不签（`sign: false`）——想「要 a_bogus
+* 但换个 msToken 长度」「只签 x_bogus 不要 secsdk」都没有出口。本入口把四平台的 step 工厂
+* 放出来，配合 `amagi.sign` 收 `SignDecl`，调用方可以自己列：
+*
+* ```ts
+* import { douyin } from '@ikenxuan/amagi/sign-steps'
+*
+* // 自己挑要哪些、调参数（这里用 200 长度的 msToken，且不加 secsdk 收尾）
+* await client.douyin.request.get(url, { amagi: { sign: [douyin.msToken(200), douyin.aBogus()] } })
+* ```
+*
+* runtime 按 `phase`（`prepare` → `token` → `sign` → `finalize`）稳定排序后依次执行，
+* 所以数组顺序写反也不翻车（`[douyin.aBogus(), douyin.msToken()]` 与
+* `[douyin.msToken(), douyin.aBogus()]` 等价）。
+*
+* ## 与默认签名同源
+*
+* 这些工厂就是端点声明和平台签名器表内部用的同一批（阶段 2 已把两条路统一到一份实现）。
+* 所以你手挑的 `[bilibili.wbi()]` 与不挑时的默认 `'wbi'` 压的是同一个签名器实例、同一份
+* `/nav` 缓存，签出来必然一致。带状态的签名器（B站 wbi keys、快手 hxfalcon count）是进程级共享的。
+*
+* ## 命名：按平台分命名空间
+*
+* step 工厂按平台归入四个命名空间对象（`douyin` / `bilibili` / `kuaishou` / `xiaohongshu`），
+* 而不是平铺到一个入口 —— `douyin.msToken()` 一眼看出归属，也不会随平台增多而重名。
+* `douyin.douyinBogus` / `douyin.douyinXBogus` 是抖音的常用组合预设
+* （`[msToken, aBogus, secsdk]` / `[…, xBogus, …]`）。
+*
+* 类型（`SignStep` / `SignPhase` / `SignFn` / `SignDecl`）不属于任何单一平台，平铺导出，
+* 方便写辅助函数的入参 / 返回值。
+*
+* @module @ikenxuan/amagi/sign-steps
+*/
+/** 抖音的反爬参数 step 工厂与组合预设 */
+const douyin = {
+	msToken,
+	aBogus,
+	xBogus,
+	secsdk,
+	douyinBogus,
+	douyinXBogus
+};
+/** B站的反爬参数 step 工厂 */
+const bilibili = {
+	wbi,
+	qtparam
+};
+/** 快手的反爬参数 step 工厂 */
+const kuaishou = { hxfalcon };
+/** 小红书的反爬参数 step 工厂 */
+const xiaohongshu = {
+	xs,
+	traceId,
+	rap
+};
+//#endregion
+export { bilibili, douyin, kuaishou, xiaohongshu };