Repository navigation
feat: 分层压缩触发阈值 compress.tierNudgeTokens(T1/T2/T3 独立设置) - #2378
Conversation
Each tier's token-mass trigger in decideNudge now resolves from an
optional nudge.tierGrowthTokens.{t1,t2,t3} before falling back to the
derived defaults (T1 = growth step, T2/T3 = multiplier x growth step),
so long-task sessions can pin T1/T2/T3 independently (#2376). Count
triggers, cadence floor, first-sight bypass and pressure routing are
untouched; unset values keep byte-identical behavior including log
strings. validateConfig rejects non-positive/non-finite values.
Host-side surface for the kernel's nudge.tierGrowthTokens: config key
compress.tierNudgeTokens {t1?,t2?,t3?} parsed/validated by
parseCompressSettings, merged sub-field-wise across the three-level
hierarchy, mapped onto the kernel config by applyCompressSettings, and
exposed as three inputs in the web quick settings (blank = derived
default). Absent or empty object preserves legacy behavior exactly.
CONFIGURATION en+zh documented.
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2615-pr.2378.f646400This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2378.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Merging master into this branch absorbed #2302's own 0.0.106 bump, which erased this PR's kernel version diff against origin/master — the kernel-guard version-discipline job (SRC_CHANGED without BUMPED) would fail. Re-bump to 0.0.107 so the tierGrowthTokens change keeps its own version increment, and sync the acp-kernel >= 0.0.10x doc/comment references.
[bot] 🏷 Review 结论(结构化七问) 1. 是什么问题:功能需求(#2376)——T1/T2/T3 三层压缩提醒的 token-mass 触发阈值共用一套派生值(T1=增长步长、T2/T3=×1.5),长任务想单独调某一层时表达不了;本 PR 让三层各自可钉住独立阈值(配置 + web 快速设置)。 2. 什么原因导致的:非缺陷,是能力缺口—— 3. 怎么修复的:机制层——kernel 新增可选 4. 是否有回归问题:逐项审过既有行为——计数触发(tier2Trigger/tier3Trigger)、节奏 floor、first-sight 质量旁路、压力/紧急路由全部不受影响;wire-contract golden 15/15 未变证明 5. 是否破坏缓存:不涉及——只影响 nudge 注入时机;未设置时判定结果与旧逻辑完全一致,前缀缓存/重试/增量游标策略均不受影响。 6. 是否改了设计方向:没有。沿既有三级 compress 层级与子字段合并模式扩展,无架构转向。 7. 是否引入了新的配置:是—— review 期间发现并处理的问题:
判定:可合——待新 head |
… and T2 long-project note Per owner feedback on #2376: the quick-settings tier row now shows the current derived defaults (T1 = growth step, T2/T3 = x1.5) instead of blank placeholders, each input gets -/+ 5000 stepper buttons, only values that differ from the derived default are persisted (unchanged tiers stay out of the config), emptied fields self-heal back to the derived value, and a description line explains each tier's role including that T2/T3 count lower-tier summary tokens (default 75K at ~10:1 ratio carries ~750K raw per T2 block; raise T2 for longer projects).
[bot] 🏷 Review 后续:首轮回复后跟踪 CI,发现两处独立根因导致 CI 红,均已修复并推送(新 head 根因 1 — npm test 四条矩阵腿全挂(#1024 i18n guard) 根因 2 — docs-sync artifact drift 并发变更说明:review 期间作者 session 按 owner 反馈推了 新 head |
[bot] 🏷 CI 确认:新 head 分支最终修复链:原 2 commit → 最终判定:可合。 剩余门禁均为人工项:① PR 合并按系统规则只能由人执行;② |
|
冲突 |
[bot] 🏷 冲突已解决:master 在上次同步后又前进了约 30 个合并(含 release v0.1.188/#2377、model-decided nudge #2228/#2243、pi-subagents vendor #2384、runaway-enumeration gate #2346 等),与 PR 分支在 7 个文件冲突。已把 结构化八问:
判定不变:可合(CI 全绿后 + kernel 部分人工 review)。CI 结果出来我再确认一次。 |
[bot] 🏷 CI 确认:冲突解决后的新 head |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.145-master.b7c3d1d # this exact build
npm install -g billion-context@master # always the newest merged build
|
master independently consumed 0.0.108 (#2378); recut so the branch's kernel/src changes carry a version delta vs master (Kernel Boundary rule 2).
master independently consumed 0.0.108 (#2378); recut so the branch's kernel/src changes carry a version delta vs master (Kernel Boundary rule 2).
Closes #2376
kernel-change: decideNudge 的三层 token-mass 触发仲裁在 kernel 内,host 无法在不加 kernel 旋钮的情况下表达「每层独立阈值」——新增可选 nudge.tierGrowthTokens.{t1,t2,t3},未设置时回退到既有派生默认值(T1=增长步长,T2/T3=×multiplier),行为与日志逐字节不变。
What
Issue #2376:T1/T2/T3 nudge 目前共用一个统一数值,T1 升 T2 后长任务仍可能不够用。本 PR 让三层各自可单独钉住触发阈值:
nudge.tierGrowthTokens.{t1,t2,t3}, acp-kernel 0.0.105 → 0.0.106):decideNudge 里每层 token-mass 判定先取该层覆盖值、再回退派生默认;validateConfig 拒绝非正数/非有限值。compress.tierNudgeTokens):parseCompressSettings 解析校验(非法值整块拒绝)、三级层级按子字段合并、applyCompressSettings 映射到 kernel config。config surface
新增配置键
compress.tierNudgeTokens:object{ t1?: number, t2?: number, t3?: number },每个值 ≥1 token。为什么现有面表达不了:nudgeGrowthTokens拍平的是单一增长步长,三层阈值都从它派生(T2/T3 = ×1.5),无法只调其中一层。已考虑的方案:providers 表(按 provider 而非按层切分,不适用)、三级 compress 层级(直接沿用——本键就走 global→provider→model 三级,且是子字段级合并)。兼容:不设置或空对象 = 与旧参数完全一致(无迁移);未加新 env var(#2030 纪律,纯 config-file key)。Behavior change disclosure
新增 opt-in 旋钮,默认路径零变化:三层均未设置时,触发条件、reason 日志字符串、诊断 breakdown 全部逐字节一致(wire-contract golden pin 15/15 通过证明 defaultConfig 输出不变;既有 arbitration 测试未改动且全绿)。计数触发(tier2Trigger/tier3Trigger)、节奏 floor、first-sight bypass、压力路由均不受影响。
Verification
披露补充(review 2026-10-08)
nudgeGrowthTokens改为各层自身阈值(默认 ×1.5)——当 T2/T3 pending mass 落在[X, 1.5×X)区间时诊断行措辞会变化(旧代码把该区间标为 mass-ready,实际触发阈值是 1.5×X;新代码不再误标)。这是诊断精度修正(与既有代码注释「old fixed string lied」的意图一致),不影响任何注入决策;golden pin 覆盖的是defaultConfig输出而非运行时日志,故 15/15 通过不涵盖此项。