You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Findings triage (objectstack#4949 discipline) — restart condition 1 FIRED, and the measurement it demanded now confirms the cost ⇒ PROMOTE to pm:queue. Domain unchanged: domain:identity.
1. The trigger, and the measurement it required
The previous verdict did not promote on the merge alone — it demanded a measurement:
@objectstack/core workspace:*
@objectstack/plugin-auth workspace:* ← new; was absent when this was held
@objectstack/spec workspace:*
The third consumer the body predicted is live. Last round this exact read went the other way ("dependencies 仍只有 @objectstack/core + @objectstack/spec ⇒ 成本面今天还没有真正产生"), and that was the stated half of the reason to hold. It has now produced.
2. The cost is real, not projected
packages/plugins/plugin-auth's own dependencies on main:
and plugin-auth's exports is still "." alone — no subpath. So service-sms reaching the ~90-line fixed-window counter in rate-limit-storage.ts must import through the package root and takes the whole better-auth family with it. That is precisely the shape direction 1 (add a "./rate-limit-storage" export subpath) was recorded to answer, and this trigger selects direction 1 over direction 2 explicitly.
3. What has NOT fired, kept honest
Conditions 2 (a fourth consumer ⇒ direction 2, lift to a neutral package) and 3 (a measured cold-start / bundle / install-time regression) remain unmet. The promotion rides on condition 1 alone, so the dispatched scope is direction 1, not the 4-consumer migration.
4. Serial constraints
The identity-lane congestion flagged last round has cleared: PR #6010 merged 2026-08-07T00:03:08Z, and no currently-open PR touches packages/plugins/plugin-auth. Still re-pull origin/main at claim time.
⛔ No target:<major>: build-graph weight and packaging shape, no shipped-surface defect on the binary criterion.
Activity
claude commentedon Aug 6, 2026
发现分诊(#4949 纪律):持有 —— 保留
finding,补domain:identity(补路由前该单对任何车道不可见)过时前提检查(
origin/main9e3709a)packages/plugins/plugin-auth/src/rate-limit-storage.ts在;该包exports实测只有"."一个入口(无子路径)⇒ 正文的「只能从包根导入」成立;packages/services/service-sms/package.json在 main 上的dependencies仍只有@objectstack/core+@objectstack/spec—— 即正文点名的第三个消费方尚未落地,它随仍 open 的 PR feat(sms): 短信全局日发送配额 —— 成本总量闸 (#2814) #6042(feat(sms): 短信全局/每租户日发送配额(成本总量闸) #2814)才出现。也就是说本单描述的成本面今天还没有真正产生。域:落点是 plugin-auth 的文件与其
exports(方向 1)或把件迁出该包(方向 2)⇒ 两个方向的主改动面都在packages/plugins/plugin-auth⇒domain:identity。为什么持有而不是晋级:作者自陈「今天没有人踩到」—— 依赖不成环、构建/类型/测试全绿、实际部署里 plugin-auth 基本总在场;属架构负债而非缺陷。方向 1(加
"./rate-limit-storage"子路径)虽小,却是给一个已发布包新增公开入口;方向 2 牵动 4 个消费方。在成本面尚未真实出现(见上)时先入队,是拿一个还没发生的问题去占车道容量。重启条件(满足任一即晋级,⛔ 不无限期持有)
@objectstack/service-sms的依赖串:若它确实为 90 行计数背上better-auth全家(实测pnpm why/ 安装体积),即按方向 1 晋级 —— 这是最可能先到的那条;串行提示(晋级后适用):identity 车道近期在 plugin-auth 上很拥挤 —— 在飞 PR #6010(#5942)触
auth-manager.ts,队列里另有 #5941 / #5978 / #6039 同区域;本单若晋级,请与它们串行并重拉origin/main。本评论来自分诊座位 Routine(#5474 试点),不构成认领。
Generated by Claude Code
claude commentedon Aug 7, 2026
Findings triage (objectstack#4949 discipline) — restart condition 1 FIRED, and the measurement it demanded now confirms the cost ⇒ PROMOTE to
pm:queue. Domain unchanged:domain:identity.1. The trigger, and the measurement it required
The previous verdict did not promote on the merge alone — it demanded a measurement:
PR #6042 merged
2026-08-06T23:56:04Z. Measurement run againstorigin/main@ede5a8e:packages/services/service-sms/package.json→dependencies:The third consumer the body predicted is live. Last round this exact read went the other way ("dependencies 仍只有
@objectstack/core+@objectstack/spec⇒ 成本面今天还没有真正产生"), and that was the stated half of the reason to hold. It has now produced.2. The cost is real, not projected
packages/plugins/plugin-auth's owndependencieson main:and plugin-auth's
exportsis still"."alone — no subpath. Soservice-smsreaching the ~90-line fixed-window counter inrate-limit-storage.tsmust import through the package root and takes the wholebetter-authfamily with it. That is precisely the shape direction 1 (add a"./rate-limit-storage"export subpath) was recorded to answer, and this trigger selects direction 1 over direction 2 explicitly.3. What has NOT fired, kept honest
Conditions 2 (a fourth consumer ⇒ direction 2, lift to a neutral package) and 3 (a measured cold-start / bundle / install-time regression) remain unmet. The promotion rides on condition 1 alone, so the dispatched scope is direction 1, not the 4-consumer migration.
4. Serial constraints
The identity-lane congestion flagged last round has cleared: PR #6010 merged
2026-08-07T00:03:08Z, and no currently-open PR touchespackages/plugins/plugin-auth. Still re-pullorigin/mainat claim time.⛔ No
target:<major>: build-graph weight and packaging shape, no shipped-surface defect on the binary criterion.本评论来自分诊座位 Routine(#5474 试点),不构成认领。
Generated by Claude Code
baozhoutao commentedon Aug 7, 2026
认领(identity 车道 PM,
session_01JwwiU9bjhwy2SWj13ho8uv,第 13 轮,2026-08-07)claude/issue-6040-rate-limit-subpath;worktree:../objectstack-issue-6040;域:domain:identityexports加"./rate-limit-storage"子路径;方向 2 的触发条件未满足,⛔ 不做中立包迁移)。packages/plugins/plugin-auth/package.json(exports)+ 子路径入口文件与其测试 +packages/services/service-sms/src/sms-daily-quota.ts+packages/runtime/src/security/inbound-rate-limit.ts+packages/runtime/src/endpoint-policy.ts(均为 import 行切换)+ changeset。派发令要求 dev 机械核对上述文件面与全部在飞分支零相交。Generated by Claude Code
baozhoutao commentedon Aug 7, 2026
ACCEPT(identity 车道 PM,第 13 轮)—— PR #6197 已过审、入合并队列。
交付:plugin-auth 新增
"./rate-limit-storage"子路径 export(包本地 tsup 双入口,根导出零破坏),仓内 9 处跨包根导入全部切至子路径;隔离回归钉 5 条(仿 #4700 的./node先例:真实 import 图遍历、外部包 allowlist、按目录扫描防换名退役、空洞通过守卫、发布面断言)。实测:子路径加载 1 模块 / 零 better-auth,对照根入口 109 模块 / 2 处 better-auth,3.71KB vs 330KB —— issue 描述的成本面就此摘除。两处偏离均接受:① 消费面 9 处而非派发令写的 3 处 —— dev 实测发现
sms-plugin.ts(服务入口)等 6 处同类根导入,只切 3 处则 service-sms 的真实加载图不变、本单目标落空;扩面全部属同一改动类(import 行切换),897 条 remote 分支零相交已机械核对。② 新 exports 条目写 types-first 并顺带归一"."—— 全仓 84:1 的既有惯例,零语义变化,不必回退。验证含双向反向证明(两处还原各自变红)与check:published-files发布门禁。Generated by Claude Code
fix(tests): make plugin-auth's rate-limit isolation radius visible to…
fix(tests): make plugin-auth's rate-limit isolation radius visible to…
fix: convert the five measured comment-mask ledger rows onto the shar…