@njuptlzf/agent-chat-server 0.1.2 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (65) hide show
  1. package/dist/audit.d.ts +54 -0
  2. package/dist/audit.js +133 -0
  3. package/dist/authz.d.ts +134 -0
  4. package/dist/authz.js +238 -0
  5. package/dist/events.d.ts +33 -0
  6. package/dist/events.js +169 -0
  7. package/dist/index.d.ts +16 -0
  8. package/dist/index.js +4 -0
  9. package/dist/main.d.ts +1 -0
  10. package/dist/main.js +126 -0
  11. package/dist/manifest.d.ts +147 -0
  12. package/dist/manifest.js +491 -0
  13. package/dist/mcp-config.d.ts +87 -0
  14. package/dist/mcp-config.js +353 -0
  15. package/dist/model-config.d.ts +123 -0
  16. package/dist/model-config.js +371 -0
  17. package/dist/model-failover.d.ts +42 -0
  18. package/dist/model-failover.js +82 -0
  19. package/dist/models-api.d.ts +98 -0
  20. package/dist/models-api.js +326 -0
  21. package/dist/persona-config.d.ts +112 -0
  22. package/dist/persona-config.js +368 -0
  23. package/dist/persona-trial.d.ts +50 -0
  24. package/dist/persona-trial.js +77 -0
  25. package/dist/product-routes.d.ts +35 -0
  26. package/dist/product-routes.js +92 -0
  27. package/dist/server.d.ts +162 -0
  28. package/dist/server.js +2572 -0
  29. package/dist/session.d.ts +218 -0
  30. package/dist/session.js +545 -0
  31. package/dist/sqlite-stores.d.ts +173 -0
  32. package/dist/sqlite-stores.js +921 -0
  33. package/dist/stores.d.ts +506 -0
  34. package/dist/stores.js +614 -0
  35. package/dist/testing.d.ts +42 -0
  36. package/dist/testing.js +47 -0
  37. package/dist/trial-grant.d.ts +40 -0
  38. package/dist/trial-grant.js +24 -0
  39. package/dist/usage-report.d.ts +23 -0
  40. package/dist/usage-report.js +68 -0
  41. package/dist/util.d.ts +3 -0
  42. package/dist/util.js +5 -0
  43. package/package.json +15 -9
  44. package/scripts/agentchat-integrate.mjs +607 -607
  45. package/src/audit.ts +169 -169
  46. package/src/authz.ts +307 -307
  47. package/src/events.ts +206 -206
  48. package/src/index.ts +26 -26
  49. package/src/main.ts +142 -142
  50. package/src/manifest.ts +562 -562
  51. package/src/mcp-config.ts +385 -385
  52. package/src/model-config.ts +424 -424
  53. package/src/model-failover.ts +95 -95
  54. package/src/models-api.ts +360 -360
  55. package/src/persona-config.ts +436 -436
  56. package/src/persona-trial.ts +121 -121
  57. package/src/product-routes.ts +102 -102
  58. package/src/server.ts +2647 -2647
  59. package/src/session.ts +688 -688
  60. package/src/sqlite-stores.ts +1040 -1040
  61. package/src/stores.ts +899 -899
  62. package/src/testing.ts +80 -80
  63. package/src/trial-grant.ts +62 -62
  64. package/src/usage-report.ts +86 -86
  65. package/src/util.ts +6 -6
@@ -0,0 +1,54 @@
1
+ /**
2
+ * 审计链纯函数层。
3
+ * Memory 与 Sqlite 两实现共用:规范化 JSON、逐行摘要、链校验、敏感键守卫、
4
+ * purge 段聚合。这里只有算法,没有 I/O——存储层负责把行喂进来。
5
+ */
6
+ /** 模型切换未落地,写点先引用这个常量留缝。 */
7
+ export declare const MODEL_SWITCH = "model.switch";
8
+ /** 创世行的 prev_hash(起点锚定后不要求链首=创世,首行 prev 存这个值是默认姿势,不参与校验)。 */
9
+ export declare const GENESIS_HASH: string;
10
+ /** 参与摘要的字段域:id 不入摘要;at/actor/roles/action/target/result/reason/meta。 */
11
+ export interface ChainRow {
12
+ id: number;
13
+ at: string;
14
+ actor: string;
15
+ roles: string[];
16
+ action: string;
17
+ target: string | null;
18
+ result: string;
19
+ reason: string | null;
20
+ meta: Record<string, unknown>;
21
+ prevHash: string;
22
+ hash: string;
23
+ }
24
+ /** 递归按「键字典序 + 紧凑分隔符」规范化;数组保持序。同义不同形(键序/空白)→ 同串。 */
25
+ export declare function canonicalize(value: unknown): string;
26
+ /** hash = sha256_hex(prev_hash ‖ 规范化 payload)。payload 键序由 canonicalize 保证。 */
27
+ export declare function rowHash(prevHash: string, row: Omit<ChainRow, "id" | "prevHash" | "hash">): string;
28
+ export declare function assertNoSensitiveKeys(meta: Record<string, unknown>, path?: string): void;
29
+ /** purge 段白名单(5B):一段连续被删 id + 段尾行存储 hash(删前读取)。 */
30
+ export interface PurgeSegment {
31
+ from_id: number;
32
+ to_id: number;
33
+ last_hash: string;
34
+ }
35
+ /** 把待删行(按 id 升序)聚成连续段。 */
36
+ export declare function segmentsFrom(rows: Array<{
37
+ id: number;
38
+ hash: string;
39
+ }>): PurgeSegment[];
40
+ export interface VerifyResult {
41
+ ok: boolean;
42
+ rows: number;
43
+ /** 起点锚定:校验从当前最老行起。空表 null。 */
44
+ checkedFromId: number | null;
45
+ /** 摘要不符(内容被改)或白名单段衔接核对不符。 */
46
+ brokenAtId: number | null;
47
+ /** 未经 purge 记录的 id 空洞——首个缺失行的 id(疑似恶意删行,等同断链报告)。 */
48
+ gapAtId: number | null;
49
+ }
50
+ /**
51
+ * 按 id 升序扫全表重算链(三条口径)。`rows` 须已按 id 升序——
52
+ * 存储层负责排序,这里不重排(verify 是全表扫,顺序错误是装配 bug,不该被静默吞掉)。
53
+ */
54
+ export declare function verifyChain(rows: ChainRow[]): VerifyResult;
package/dist/audit.js ADDED
@@ -0,0 +1,133 @@
1
+ import { createHash } from "node:crypto";
2
+ /**
3
+ * 审计链纯函数层。
4
+ * Memory 与 Sqlite 两实现共用:规范化 JSON、逐行摘要、链校验、敏感键守卫、
5
+ * purge 段聚合。这里只有算法,没有 I/O——存储层负责把行喂进来。
6
+ */
7
+ /** 模型切换未落地,写点先引用这个常量留缝。 */
8
+ export const MODEL_SWITCH = "model.switch";
9
+ /** 创世行的 prev_hash(起点锚定后不要求链首=创世,首行 prev 存这个值是默认姿势,不参与校验)。 */
10
+ export const GENESIS_HASH = "0".repeat(64);
11
+ /** 递归按「键字典序 + 紧凑分隔符」规范化;数组保持序。同义不同形(键序/空白)→ 同串。 */
12
+ export function canonicalize(value) {
13
+ return JSON.stringify(normalize(value));
14
+ }
15
+ function normalize(v) {
16
+ if (Array.isArray(v))
17
+ return v.map(normalize);
18
+ if (v !== null && typeof v === "object") {
19
+ return Object.fromEntries(Object.entries(v)
20
+ .sort(([a], [b]) => (a < b ? -1 : a > b ? 1 : 0))
21
+ .map(([k, x]) => [k, normalize(x)]));
22
+ }
23
+ return v;
24
+ }
25
+ /** hash = sha256_hex(prev_hash ‖ 规范化 payload)。payload 键序由 canonicalize 保证。 */
26
+ export function rowHash(prevHash, row) {
27
+ const payload = canonicalize({
28
+ at: row.at,
29
+ actor: row.actor,
30
+ roles: row.roles,
31
+ action: row.action,
32
+ target: row.target,
33
+ result: row.result,
34
+ reason: row.reason,
35
+ meta: row.meta,
36
+ });
37
+ return createHash("sha256").update(prevHash + payload).digest("hex");
38
+ }
39
+ /**
40
+ * 红线②守卫:meta 落库前递归查敏感键名。命中抛错 + stderr——
41
+ * 写审计的代码有 bug 也不该把 key/token 带进表里。
42
+ *
43
+ * 语义=词集而非子串(实现时对方案字面正则 /key|token|…/i 的修正,review 时可推翻):
44
+ * 子串会误杀 写点白名单里的 `tokens`(token 计数,非凭据),且 `cost_per_token`
45
+ * 一类合法键也躲不过;词集按 camel/snake/kebab 拆词后整词匹配,
46
+ * `api_key/refreshToken/COOKIE_ID` 照杀,`tokens/monkey` 放行。
47
+ */
48
+ const SENSITIVE_WORDS = /^(key|keys|token|secret|secrets|credential|credentials|authorization|cookie|cookies|apikey|accesskey|accesstoken|authtoken|refreshtoken|bearer)$/i;
49
+ function sensitiveHit(key) {
50
+ return key
51
+ .replace(/([a-z0-9])([A-Z])/g, "$1 $2")
52
+ .toLowerCase()
53
+ .split(/[^a-z0-9]+/)
54
+ .some((w) => SENSITIVE_WORDS.test(w));
55
+ }
56
+ export function assertNoSensitiveKeys(meta, path = "meta") {
57
+ for (const [k, v] of Object.entries(meta)) {
58
+ if (sensitiveHit(k)) {
59
+ const where = `${path}.${k}`;
60
+ console.error(`audit: rejected sensitive meta key ${where}`);
61
+ throw new Error(`audit meta rejected: sensitive key ${where}`);
62
+ }
63
+ if (v !== null && typeof v === "object") {
64
+ if (Array.isArray(v)) {
65
+ v.forEach((x, i) => x !== null && typeof x === "object" && assertNoSensitiveKeys(x, `${path}.${k}[${i}]`));
66
+ }
67
+ else {
68
+ assertNoSensitiveKeys(v, `${path}.${k}`);
69
+ }
70
+ }
71
+ }
72
+ }
73
+ /** 把待删行(按 id 升序)聚成连续段。 */
74
+ export function segmentsFrom(rows) {
75
+ const segs = [];
76
+ for (const r of rows) {
77
+ const last = segs[segs.length - 1];
78
+ if (last && r.id === last.to_id + 1)
79
+ last.to_id = r.id;
80
+ else
81
+ segs.push({ from_id: r.id, to_id: r.id, last_hash: r.hash });
82
+ segs[segs.length - 1].last_hash = r.hash; // 段尾 hash 随延伸滚动
83
+ }
84
+ return segs;
85
+ }
86
+ /**
87
+ * 按 id 升序扫全表重算链(三条口径)。`rows` 须已按 id 升序——
88
+ * 存储层负责排序,这里不重排(verify 是全表扫,顺序错误是装配 bug,不该被静默吞掉)。
89
+ */
90
+ export function verifyChain(rows) {
91
+ const base = { ok: true, rows: rows.length, checkedFromId: rows[0]?.id ?? null, brokenAtId: null, gapAtId: null };
92
+ if (!rows.length)
93
+ return base;
94
+ // 白名单:ops.audit.purge 行的 meta.segments。篡改它自身会被逐行重算抓到(它在链内, 自我闭环)。
95
+ const segments = [];
96
+ for (const r of rows) {
97
+ if (r.action !== "ops.audit.purge")
98
+ continue;
99
+ const segs = r.meta["segments"];
100
+ if (!Array.isArray(segs))
101
+ continue;
102
+ for (const s of segs) {
103
+ if (s && typeof s === "object") {
104
+ const { from_id, to_id, last_hash } = s;
105
+ if (typeof from_id === "number" && typeof to_id === "number" && typeof last_hash === "string") {
106
+ segments.push({ from_id, to_id, last_hash });
107
+ }
108
+ }
109
+ }
110
+ }
111
+ let brokenAtId = null;
112
+ let gapAtId = null;
113
+ for (let i = 0; i < rows.length; i++) {
114
+ const r = rows[i];
115
+ const prev = i > 0 ? rows[i - 1] : null;
116
+ if (prev && r.id !== prev.id + 1) {
117
+ // 空洞:须被某段白名单「恰等区间」背书,且空洞后首存活行 prev_hash == 段 last_hash。
118
+ const seg = segments.find((s) => s.from_id === prev.id + 1 && s.to_id === r.id - 1);
119
+ if (!seg)
120
+ gapAtId ??= prev.id + 1;
121
+ else if (seg.last_hash !== r.prevHash)
122
+ brokenAtId ??= r.id;
123
+ }
124
+ else if (prev && r.prevHash !== prev.hash) {
125
+ brokenAtId ??= r.id; // 无空洞却断衔接:腰删未重连/前缀被换
126
+ }
127
+ if (rowHash(r.prevHash, r) !== r.hash)
128
+ brokenAtId ??= r.id; // 首行不做创世要求,但本行内容照验
129
+ if (brokenAtId !== null && gapAtId !== null)
130
+ break;
131
+ }
132
+ return { ...base, ok: brokenAtId === null && gapAtId === null, brokenAtId, gapAtId };
133
+ }
@@ -0,0 +1,134 @@
1
+ import type { DatabaseSync } from "node:sqlite";
2
+ import { type Model } from "casbin";
3
+ import type { MembershipStore } from "./stores.ts";
4
+ /**
5
+ * 权限内核。
6
+ *
7
+ * role-as-subject,不用 g 继承做判定:model 的 matcher 是 `r.sub == p.sub`,
8
+ * 请求方先把「用户意味着哪些主体」解析成 roles(user/member/admin/本人 id),
9
+ * 每个主体各 enforce 一次,some 即放行。member **不进 g 表**——它由
10
+ * membership.member_until 现算,会随时间说谎的映射是反模式。
11
+ * 解析后仍把用户本人 id 当一个 sub 试一次:给个人开个案豁免(p 行 v0=用户 id)
12
+ * 不需要动角色。
13
+ */
14
+ export declare const MODEL_TEXT = "\n[request_definition]\nr = sub, obj, act\n\n[policy_definition]\np = sub, obj, act\n\n[role_definition]\ng = _, _\n\n[policy_effect]\ne = some(where (p.eft == allow))\n\n[matchers]\nm = r.sub == p.sub && r.obj == p.obj && r.act == p.act\n";
15
+ /**
16
+ * casbin Adapter 的 node:sqlite 直连实现(标准 casbin_rule schema,
17
+ * 自写 adapter 约百行,避免给 better-sqlite3 开第二个原生依赖)。
18
+ * 写操作走 enforcer API(addPolicy 等)由 casbin 回调到这里,内存态与库同步。
19
+ */
20
+ export declare class SqliteCasbinAdapter {
21
+ private readonly db;
22
+ constructor(db: DatabaseSync);
23
+ loadPolicy(model: Model): Promise<void>;
24
+ /** 全量重写(低频运维路径;enforcer.savePolicy 才会调)。 */
25
+ savePolicy(model: Model): Promise<boolean>;
26
+ addPolicy(_sec: string, ptype: string, rule: string[]): Promise<void>;
27
+ removePolicy(_sec: string, ptype: string, rule: string[]): Promise<void>;
28
+ removeFilteredPolicy(_sec: string, ptype: string, fieldIndex: number, ...fieldValues: string[]): Promise<void>;
29
+ }
30
+ export interface CasbinRule {
31
+ sub: string;
32
+ obj: string;
33
+ act: string;
34
+ }
35
+ export interface RoleAssignment {
36
+ userId: string;
37
+ role: string;
38
+ }
39
+ /** server 消费的授权面(Authz 的真实实现 + casbin 加载失败的降级实现)。 */
40
+ export interface AuthzLike {
41
+ ready(): boolean;
42
+ rolesFor(userId: string): Promise<string[]>;
43
+ rolesOf(userId: string): Promise<string[]>;
44
+ allowed(userId: string, obj: string, act: string): Promise<boolean>;
45
+ listPolicies(): Promise<CasbinRule[]>;
46
+ addPolicy(sub: string, obj: string, act: string): Promise<void>;
47
+ removePolicy(sub: string, obj: string, act: string): Promise<void>;
48
+ listAssignments(): Promise<RoleAssignment[]>;
49
+ assignRole(userId: string, role: string): Promise<void>;
50
+ revokeRole(userId: string, role: string): Promise<void>;
51
+ }
52
+ /** 角色 → 当日上限。<=0 或缺省 = 不限轮;token 兜底全员同额。 */
53
+ export interface LimitsConfig {
54
+ freeDailyRuns?: number;
55
+ memberDailyRuns?: number;
56
+ dailyTokenQuota?: number;
57
+ memberDailyTokenQuota?: number;
58
+ memberMonthlyTokenPool?: number;
59
+ /** 按人格(账本产品)覆盖;缺省继承产品级。 */
60
+ personas?: Record<string, LimitsConfig>;
61
+ }
62
+ export declare function capsForRoles(roles: string[], limits: LimitsConfig): {
63
+ runCap?: number;
64
+ tokenCap?: number;
65
+ };
66
+ /** 某人格的生效上限 = 产品级 + `limits.personas.<id>` 覆盖(逐字段)。 */
67
+ export declare function limitsForPersona(limits: LimitsConfig, persona: string): LimitsConfig;
68
+ /**
69
+ * 额度按**当前会话的人格**取,不再由全局 `member` 角色决定。
70
+ * `isMember` 必须是「这个人格的账本」是否在期(admin 恒真)——
71
+ * 否则买了 A 人格会解锁 B 人格的次数。
72
+ */
73
+ export declare function capsForPersona(limits: LimitsConfig, persona: string, isMember: boolean): {
74
+ runCap?: number;
75
+ tokenCap?: number;
76
+ };
77
+ /**
78
+ * 结算拆账(唯一算式):池先冲,冲不下的走余额。
79
+ * 已知边界:部分覆盖时 toolCalls 服务费按全额算(computeSpendCents 的第二项不随
80
+ * billable 缩小)——池 600 万 vs 单轮 ~2.3 万,跨界轮每年个位数,误差可接受,
81
+ * 真财务模型时再按 billable/total 比例化。
82
+ */
83
+ export declare function poolSplit(total: number, poolRemaining: number): {
84
+ poolPart: number;
85
+ billable: number;
86
+ };
87
+ /**
88
+ * 组装好的授权面:casbin enforcer + membership 动态角色 + 管理页要用的读写原语。
89
+ * 用 create() 构造(newEnforcer 是 async,构造器不能 await)。
90
+ */
91
+ export declare class Authz implements AuthzLike {
92
+ private readonly enf;
93
+ private readonly membership;
94
+ private readonly now;
95
+ private constructor();
96
+ /**
97
+ * seed 直写表(幂等:INSERT OR IGNORE),再交给 enforcer 加载——空表才种,
98
+ * 尊重管理页后来撤销/追加的策略。种子来自 manifest(出核:core 不内置
99
+ * 业务词汇,规范 违规清单第一条);缺省空数组 = 空库零策略。
100
+ */
101
+ static create(db: DatabaseSync, membership: MembershipStore, now?: () => Date, seedPolicies?: readonly CasbinRule[]): Promise<Authz>;
102
+ /** casbin 侧是否健康(加载失败由装配方降级)。装配成功恒真。 */
103
+ ready(): boolean;
104
+ /** 用户此刻意味着哪些主体:user ∪ member(动态)∪ 静态角色 ∪ 本人 id ∪ __admin__ 兼容。 */
105
+ rolesFor(userId: string): Promise<string[]>;
106
+ /** 不含「本人 id」直判的纯角色视图(whoami/前端显隐用)。 */
107
+ rolesOf(userId: string): Promise<string[]>;
108
+ allowed(userId: string, obj: string, act: string): Promise<boolean>;
109
+ /** 封号判定独立于 casbin(身份闸),这里只把 account:ban 的管理动作交给策略。 */
110
+ canBan(userId: string): Promise<boolean>;
111
+ listPolicies(): Promise<CasbinRule[]>;
112
+ addPolicy(sub: string, obj: string, act: string): Promise<void>;
113
+ removePolicy(sub: string, obj: string, act: string): Promise<void>;
114
+ listAssignments(): Promise<RoleAssignment[]>;
115
+ assignRole(userId: string, role: string): Promise<void>;
116
+ revokeRole(userId: string, role: string): Promise<void>;
117
+ }
118
+ /**
119
+ * casbin 加载失败的降级面:ready()=false 让业务数据走 fail-closed(503);
120
+ * 角色恒为 ["user"] 让依赖角色的展示面(whoami/feedback 优先级)fail-open 到最小
121
+ * 口径——它不抛错、不阻断与授权无关的通道。管理面被 ready() 检查挡在 503 后。
122
+ */
123
+ export declare class UnavailableAuthz implements AuthzLike {
124
+ ready(): boolean;
125
+ rolesFor(userId: string): Promise<string[]>;
126
+ rolesOf(): Promise<string[]>;
127
+ allowed(): Promise<boolean>;
128
+ listPolicies(): Promise<CasbinRule[]>;
129
+ addPolicy(): Promise<void>;
130
+ removePolicy(): Promise<void>;
131
+ listAssignments(): Promise<RoleAssignment[]>;
132
+ assignRole(): Promise<void>;
133
+ revokeRole(): Promise<void>;
134
+ }
package/dist/authz.js ADDED
@@ -0,0 +1,238 @@
1
+ import { newEnforcer, newModelFromString } from "casbin";
2
+ /**
3
+ * 权限内核。
4
+ *
5
+ * role-as-subject,不用 g 继承做判定:model 的 matcher 是 `r.sub == p.sub`,
6
+ * 请求方先把「用户意味着哪些主体」解析成 roles(user/member/admin/本人 id),
7
+ * 每个主体各 enforce 一次,some 即放行。member **不进 g 表**——它由
8
+ * membership.member_until 现算,会随时间说谎的映射是反模式。
9
+ * 解析后仍把用户本人 id 当一个 sub 试一次:给个人开个案豁免(p 行 v0=用户 id)
10
+ * 不需要动角色。
11
+ */
12
+ export const MODEL_TEXT = `
13
+ [request_definition]
14
+ r = sub, obj, act
15
+
16
+ [policy_definition]
17
+ p = sub, obj, act
18
+
19
+ [role_definition]
20
+ g = _, _
21
+
22
+ [policy_effect]
23
+ e = some(where (p.eft == allow))
24
+
25
+ [matchers]
26
+ m = r.sub == p.sub && r.obj == p.obj && r.act == p.act
27
+ `;
28
+ function assertion(model, sec, ptype) {
29
+ return model.model.get(sec)?.get(ptype);
30
+ }
31
+ /**
32
+ * casbin Adapter 的 node:sqlite 直连实现(标准 casbin_rule schema,
33
+ * 自写 adapter 约百行,避免给 better-sqlite3 开第二个原生依赖)。
34
+ * 写操作走 enforcer API(addPolicy 等)由 casbin 回调到这里,内存态与库同步。
35
+ */
36
+ export class SqliteCasbinAdapter {
37
+ db;
38
+ constructor(db) {
39
+ this.db = db;
40
+ }
41
+ async loadPolicy(model) {
42
+ const rows = this.db
43
+ .prepare("SELECT ptype, v0, v1, v2, v3, v4, v5 FROM casbin_rule ORDER BY id")
44
+ .all();
45
+ for (const r of rows) {
46
+ const ptype = String(r.ptype);
47
+ const ast = assertion(model, ptype.startsWith("p") ? "p" : "g", ptype);
48
+ if (!ast)
49
+ continue;
50
+ const rule = [r.v0, r.v1, r.v2, r.v3, r.v4, r.v5].map(String).filter((v) => v !== "");
51
+ ast.policy.push(rule);
52
+ }
53
+ }
54
+ /** 全量重写(低频运维路径;enforcer.savePolicy 才会调)。 */
55
+ async savePolicy(model) {
56
+ this.db.prepare("DELETE FROM casbin_rule").run();
57
+ const ins = this.db.prepare("INSERT OR IGNORE INTO casbin_rule (ptype, v0, v1, v2, v3, v4, v5) VALUES (?, ?, ?, ?, ?, ?, ?)");
58
+ const dump = (sec, ptype) => {
59
+ const ast = assertion(model, sec, ptype);
60
+ for (const rule of ast?.policy ?? []) {
61
+ const padded = [...rule, "", "", "", "", "", ""].slice(0, 6);
62
+ ins.run(ptype, ...padded);
63
+ }
64
+ };
65
+ dump("p", "p");
66
+ dump("g", "g");
67
+ return true;
68
+ }
69
+ async addPolicy(_sec, ptype, rule) {
70
+ const padded = [...rule, "", "", "", "", "", ""].slice(0, 6);
71
+ this.db
72
+ .prepare("INSERT OR IGNORE INTO casbin_rule (ptype, v0, v1, v2, v3, v4, v5) VALUES (?, ?, ?, ?, ?, ?, ?)")
73
+ .run(ptype, ...padded);
74
+ }
75
+ async removePolicy(_sec, ptype, rule) {
76
+ const padded = [...rule, "", "", "", "", "", ""].slice(0, 6);
77
+ this.db
78
+ .prepare("DELETE FROM casbin_rule WHERE ptype = ? AND v0 = ? AND v1 = ? AND v2 = ? AND v3 = ? AND v4 = ? AND v5 = ?")
79
+ .run(ptype, ...padded);
80
+ }
81
+ async removeFilteredPolicy(_sec, ptype, fieldIndex, ...fieldValues) {
82
+ const where = ["ptype = ?"];
83
+ const args = [ptype];
84
+ fieldValues.forEach((v, i) => {
85
+ if (v !== undefined && v !== "") {
86
+ where.push(`v${fieldIndex + i} = ?`);
87
+ args.push(v);
88
+ }
89
+ });
90
+ this.db.prepare(`DELETE FROM casbin_rule WHERE ${where.join(" AND ")}`).run(...args);
91
+ }
92
+ }
93
+ export function capsForRoles(roles, limits) {
94
+ const member = roles.includes("member") || roles.includes("admin");
95
+ const runCap = member ? limits.memberDailyRuns : limits.freeDailyRuns;
96
+ const tokenCap = member ? (limits.memberDailyTokenQuota ?? limits.dailyTokenQuota) : limits.dailyTokenQuota;
97
+ return { runCap: runCap && runCap > 0 ? runCap : undefined, tokenCap };
98
+ }
99
+ /** 某人格的生效上限 = 产品级 + `limits.personas.<id>` 覆盖(逐字段)。 */
100
+ export function limitsForPersona(limits, persona) {
101
+ return { ...limits, ...(limits.personas?.[persona] ?? {}) };
102
+ }
103
+ /**
104
+ * 额度按**当前会话的人格**取,不再由全局 `member` 角色决定。
105
+ * `isMember` 必须是「这个人格的账本」是否在期(admin 恒真)——
106
+ * 否则买了 A 人格会解锁 B 人格的次数。
107
+ */
108
+ export function capsForPersona(limits, persona, isMember) {
109
+ return capsForRoles(isMember ? ["member"] : ["user"], limitsForPersona(limits, persona));
110
+ }
111
+ /**
112
+ * 结算拆账(唯一算式):池先冲,冲不下的走余额。
113
+ * 已知边界:部分覆盖时 toolCalls 服务费按全额算(computeSpendCents 的第二项不随
114
+ * billable 缩小)——池 600 万 vs 单轮 ~2.3 万,跨界轮每年个位数,误差可接受,
115
+ * 真财务模型时再按 billable/total 比例化。
116
+ */
117
+ export function poolSplit(total, poolRemaining) {
118
+ const poolPart = Math.max(0, Math.min(poolRemaining, total));
119
+ return { poolPart, billable: total - poolPart };
120
+ }
121
+ /**
122
+ * 组装好的授权面:casbin enforcer + membership 动态角色 + 管理页要用的读写原语。
123
+ * 用 create() 构造(newEnforcer 是 async,构造器不能 await)。
124
+ */
125
+ export class Authz {
126
+ enf;
127
+ membership;
128
+ now;
129
+ constructor(enf, membership, now) {
130
+ this.enf = enf;
131
+ this.membership = membership;
132
+ this.now = now;
133
+ }
134
+ /**
135
+ * seed 直写表(幂等:INSERT OR IGNORE),再交给 enforcer 加载——空表才种,
136
+ * 尊重管理页后来撤销/追加的策略。种子来自 manifest(出核:core 不内置
137
+ * 业务词汇,规范 违规清单第一条);缺省空数组 = 空库零策略。
138
+ */
139
+ static async create(db, membership, now = () => new Date(), seedPolicies = []) {
140
+ const empty = db.prepare("SELECT COUNT(*) AS n FROM casbin_rule").get().n === 0;
141
+ if (empty) {
142
+ const ins = db.prepare("INSERT OR IGNORE INTO casbin_rule (ptype, v0, v1, v2, v3, v4, v5) VALUES ('p', ?, ?, ?, '', '', '')");
143
+ for (const { sub, obj, act } of seedPolicies)
144
+ ins.run(sub, obj, act);
145
+ }
146
+ const enf = await newEnforcer(newModelFromString(MODEL_TEXT), new SqliteCasbinAdapter(db));
147
+ return new Authz(enf, membership, now);
148
+ }
149
+ /** casbin 侧是否健康(加载失败由装配方降级)。装配成功恒真。 */
150
+ ready() {
151
+ return true;
152
+ }
153
+ /** 用户此刻意味着哪些主体:user ∪ member(动态)∪ 静态角色 ∪ 本人 id ∪ __admin__ 兼容。 */
154
+ async rolesFor(userId) {
155
+ const roles = new Set(["user"]);
156
+ // 粗粒度:任一产品在期 ⇒ member 角色(额度不走这个角色,见 capsForPersona)。
157
+ if (await this.membership.hasAnyActive(userId))
158
+ roles.add("member");
159
+ if (userId === "__admin__")
160
+ roles.add("admin"); // ADMIN_TOKEN 运维身份兼容(stores.ts createAdminAuth)
161
+ for (const r of await this.enf.getRolesForUser(userId))
162
+ roles.add(r);
163
+ roles.add(userId); // 个案豁免:p 行 v0 直接写用户 id
164
+ return [...roles];
165
+ }
166
+ /** 不含「本人 id」直判的纯角色视图(whoami/前端显隐用)。 */
167
+ async rolesOf(userId) {
168
+ const roles = await this.rolesFor(userId);
169
+ return roles.filter((r) => r !== userId);
170
+ }
171
+ async allowed(userId, obj, act) {
172
+ const subjects = await this.rolesFor(userId);
173
+ for (const sub of subjects) {
174
+ if (await this.enf.enforce(sub, obj, act))
175
+ return true;
176
+ }
177
+ return false;
178
+ }
179
+ /** 封号判定独立于 casbin(身份闸),这里只把 account:ban 的管理动作交给策略。 */
180
+ async canBan(userId) {
181
+ return this.allowed(userId, "account", "ban");
182
+ }
183
+ async listPolicies() {
184
+ return (await this.enf.getPolicy()).map(([sub, obj, act]) => ({ sub, obj, act }));
185
+ }
186
+ async addPolicy(sub, obj, act) {
187
+ await this.enf.addPolicy(sub, obj, act);
188
+ }
189
+ async removePolicy(sub, obj, act) {
190
+ await this.enf.removePolicy(sub, obj, act);
191
+ }
192
+ async listAssignments() {
193
+ return (await this.enf.getGroupingPolicy()).map(([userId, role]) => ({ userId, role }));
194
+ }
195
+ async assignRole(userId, role) {
196
+ await this.enf.addRoleForUser(userId, role);
197
+ }
198
+ async revokeRole(userId, role) {
199
+ await this.enf.deleteRoleForUser(userId, role);
200
+ }
201
+ }
202
+ /**
203
+ * casbin 加载失败的降级面:ready()=false 让业务数据走 fail-closed(503);
204
+ * 角色恒为 ["user"] 让依赖角色的展示面(whoami/feedback 优先级)fail-open 到最小
205
+ * 口径——它不抛错、不阻断与授权无关的通道。管理面被 ready() 检查挡在 503 后。
206
+ */
207
+ export class UnavailableAuthz {
208
+ ready() {
209
+ return false;
210
+ }
211
+ async rolesFor(userId) {
212
+ return ["user", userId];
213
+ }
214
+ async rolesOf() {
215
+ return ["user"];
216
+ }
217
+ async allowed() {
218
+ return false;
219
+ }
220
+ async listPolicies() {
221
+ return [];
222
+ }
223
+ async addPolicy() {
224
+ throw new Error("authz unavailable");
225
+ }
226
+ async removePolicy() {
227
+ throw new Error("authz unavailable");
228
+ }
229
+ async listAssignments() {
230
+ return [];
231
+ }
232
+ async assignRole() {
233
+ throw new Error("authz unavailable");
234
+ }
235
+ async revokeRole() {
236
+ throw new Error("authz unavailable");
237
+ }
238
+ }
@@ -0,0 +1,33 @@
1
+ import type { AgentSessionEvent } from "@earendil-works/pi-coding-agent";
2
+ import type { ChatEvent, TokenUsage } from "@njuptlzf/agent-chat-protocol";
3
+ export declare function emptyUsage(): TokenUsage;
4
+ /**
5
+ * 模型报错的用户文案(2026-11-04):pi 的 errorMessage 是原始串(如
6
+ * `429: {"message":"inference exceeds tpm/rpm limit",...}`),直接下发会把
7
+ * 上游 JSON 露进气泡。这里折叠成一句人话 + 保留状态码数字便于口头报障。
8
+ * **failover 匹配不读这条文案**(见 server.ts 的 rawModelError)——它直接从
9
+ * pi 原始事件取 errorMessage 做正则,用户文案怎么改都不影响切换逻辑。
10
+ */
11
+ export declare function friendlyModelError(raw: string | undefined): string;
12
+ export interface EventMapper {
13
+ map(event: AgentSessionEvent): ChatEvent[];
14
+ /** Usage accumulated across every assistant message seen so far. */
15
+ totalUsage(): TokenUsage;
16
+ }
17
+ /**
18
+ * Translate pi session events into the stable wire protocol.
19
+ * Stateful (message ids, usage totals), so create one mapper per run.
20
+ */
21
+ export declare function createEventMapper(): EventMapper;
22
+ export interface RunAccounting {
23
+ /** Feed each outgoing protocol event; counts completed tool rounds. */
24
+ observe(ev: ChatEvent): void;
25
+ toolRounds(): number;
26
+ /** True once a completed tool round hit the configured cap. */
27
+ limitHit(): boolean;
28
+ }
29
+ /**
30
+ * Bounds one run's agentic loop: pi has no native turn cap, so the server
31
+ * counts tool rounds on the wire and aborts when the cap is hit.
32
+ */
33
+ export declare function createRunAccounting(maxToolRounds: number | undefined): RunAccounting;