Skip to content

[PR] Fix #5618 usage wall: remote-URL / file-ref media becomes foldable, its re-access handles ride the summary - #5629

Merged
ranxianglei merged 3 commits into
masterfrom
2026-11-04_ref-recoverable-media
Nov 4, 2026
Merged

ranxianglei merged 3 commits into
masterfrom
2026-11-04_ref-recoverable-media

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

kernel-change: #5618 usage-wall root fix — splits hasUnrecoverableMediaPayload's media class so ref-based media (remote URL / file id / fileUri) becomes foldable with its re-access handle mechanically recorded in the stored summary. Owner approved in-thread (「根本上解决吧」, #5618). Host side cannot solve this: the pin lives in kernel fold/advertise/ref gates (four sites, all consuming the same predicate).

What & why

In image-heavy dsh workflows every message carrying a remote-URL image or a DeepSeek Files API file ref was permanently pinned: BLOCKED ref (never citable), never advertised as compressible, carved out of every fold, and turn integrity withdrew the turns around it. Folds kept pace with growth (~50K each) but the context floor climbed to ~70% of the window and never came down (log evidence in #5618: input=566495/792576 at 72%, 19× "No compressible ranges remain").

The fix splits the class with a conservative enumeration: a media message is FOLDABLE iff it exposes at least one extractable re-access handle (non-data: URL, file id, fileUri). Folding then loses nothing recoverable — the handle rides the stored summary verbatim, and decompress restores the original message losslessly regardless.

Behavior changes (old → new)

  1. Ref-based media (openai image_url non-data: singular/plural, {type:"file"} parts, anthropic url-source images incl. tool_result-embedded, responses input_image non-data:, google fileData.fileUri): OLD = permanently pinned (BLOCKED ref, never advertised, excluded from every fold with warning, partners withdrawn by turn integrity → the Context compression isn't working — it's stuck at 70% dsh. | 上下文压缩不掉 维持在 70 % dsh #5618 floor). NEW = foldable like text, numeric ref, handle appended verbatim to the block summary in a deterministic MEDIA REFS section.
  2. Summary content: blocks folding ref-based media carry a trailing MEDIA REFS section — deterministic bytes per fold set (cache-stable); idempotent under re-apply; carried forward through merges/distillations (consumed-block carry) and refolds (per-block carry). Byte-identical summaries for ref-free sessions (section only appears when refs exist).
  3. Prompt surface: howToCompressRules / tier2DistillRules / tier3CondenseRules extended additively to preserve the section at every tier (golden tests/golden/wire-contract/kernel.json regenerated — justification: Context compression isn't working — it's stuck at 70% dsh. | 上下文压缩不掉 维持在 70 % dsh #5618 root fix, three fields additive, COMPRESS_PHILOSOPHY unchanged). Mechanical append does NOT rely on model compliance: on the OpenAI wire the URL string of an image part is fed to the vision encoder and may be invisible to the summarizer.
  4. Excluded-media warning text reworded (now fires only for truly refless shapes).
  5. Cosmetic: one pre-existing stray leading space normalized on the tier-2 Open-objectives bullet (touched while inserting the sibling line).

Unchanged by design: control-plane structured system message pinning (#3992/#4166); unknown/opaque shapes keep pinning (conservative enumeration — no evidence their payloads are re-acquirable); archivable inline media (#2607); videoMetadata-only Google parts (no fetchable field — still pinned); document blocks in tool_results (no established ref semantics — still pinned).

Legacy sessions

No migration code: pre-fix BLOCKED refs on now-foldable media migrate to fresh numbers through the existing #3805 deferred-render path (ref minted now, carrier tag render deferred to the next fold boundary — prefix-cache safe).

Tests (targeted local; full-suite verdict = CI)

Residuals (tracked in-thread, not blocking)

Part of #5618

kernel version 0.0.179 → 0.0.180

… stored summary (#5620)

The #5620 usage wall: in image-heavy workflows every message carrying
remote-URL images / DeepSeek Files API file refs was permanently pinned
by hasUnrecoverableMediaPayload, turn integrity pinned its partners, and
the context floor climbed to ~70% of the window while folds kept pace
with growth but could never lower it.

Split the class (conservative enumeration):
- new kernel/src/media-refs.ts: extractMediaRefs pulls known re-access
  handles (non-data: URLs, file ids, fileUris) from all five wire
  sidecar families; hasRefRecoverableMediaPayload = at least one handle;
  unknown opaque shapes keep pinning until their semantics are known
- hasUnrecoverableMediaPayload media branches now return
  !hasRefRecoverableMediaPayload(msg); control-plane structured system
  branches (#3992/#4166) and refless shapes are untouched
- apply path appends a deterministic MEDIA REFS section to the stored
  block summary (applySingleRange union incl. consumed-block carry;
  applyRefolds per-block carry), so handles survive folds/merges/
  distillations mechanically — never model discretion (on the wire a
  URL part is often invisible to the summarizer); decompress restores
  the original losslessly either way
- compression-rules: MEDIA REFS preservation added to T1/T2/T3 rules;
  golden regenerated (justification: #5620 root fix, three prompt fields
  extended additively, COMPRESS_PHILOSOPHY unchanged)
- cosmetic: normalize one stray leading space on the tier-2
  Open-objectives bullet (pre-existing, touched while inserting the
  sibling line)

Legacy sessions self-heal without migration code: pre-#5620 BLOCKED refs
on now-foldable media migrate to fresh numbers via the existing #3805
deferred-render path (carrier render deferred to next fold boundary).

kernel version 0.0.179 -> 0.0.180
@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-11-04_ref-recoverable-media (2b23fca)

Latest build — install this exact version

npm install -g billion-context@0.0.8064-pr.5629.904d4e5

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Recent builds (commit → version)

commit version build
2b23fca billion-context@0.0.8064-pr.5629.904d4e5 build
5104bd5 billion-context@0.0.8058-pr.5629.eaa5ba0 build
d126087 billion-context@0.0.8057-pr.5629.5943ffa build

Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr5629.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei ranxianglei changed the title Fix #5618 usage wall: remote-URL / file-ref media becomes foldable, its re-access handles ride the summary [PR] Fix #5618 usage wall: remote-URL / file-ref media becomes foldable, its re-access handles ride the summary Nov 4, 2026
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

查重: 不重复 — 按失败签名搜了 open+closed 的 issue/PR(#5618、usage wall、ref-recoverable media):本 PR 是 #5618 唯一在途修复。搜索还命中 #4629(正文含 "5618"),但其内容是 #4600 的 codex forged-summary ledger,机制无关。

标签: bug + dsh + scope/kernel + p1 — 图片密集的 dsh 工作流里上下文地板钉在窗口 ~70% 只升不降 = 上下文失控增长类,按 owner 2026-10-19 修订一律 p1。

审查已开始:分支 2026-11-04_ref-recoverable-media @ d126087,单 commit,base c29b118 是当前 master 的祖先(rebase 干净);diff 14 文件 +822/−79,全部在 kernel/ + golden + lockfile,无 host 侧改动。CI 现状:static-gates 在 windows-22 与 ubuntu-24 双红,其余 gate(kernel-guard/lock-sync/version-guard/config-surface-guard/build-artifact 等)全绿,test 分片仍在跑。正按 #4599 协议排查 static-gates,完整八问结论随后补上。

@ranxianglei ranxianglei added bug Something isn't working dsh p1 scope/kernel labels Nov 4, 2026
…rule line

static-gates was red on both legs: surface-config.test.ts ("default
builders are byte-stable against checked-in fixtures") compares
buildCompress{,Text,Hybrid}SystemPrompt() against kernel/tests/fixtures/,
and the #5620 prompt change added one line ("Media re-access handles -
...") to all three default prompts without regenerating those fixtures.

Regenerated all three from the current builders; each fixture diffs by
exactly that one added line - no other drift. Local: kernel suite
1576/1576, pi-subagents 263/263, build + thin-install smoke OK,
wire-contract golden 23/23.
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

Review 完成:代码通过,CI 红已定位并修复(独立小修 commit 5104bd5e2 已推到 PR 分支),等 owner 合入(kernel 变更 = 人工合并档)。

CI 红根因与修复:static-gates 双腿(windows/22、ubuntu/24)红在 kernel/tests/surface-config.test.ts —— 本 PR 给三个默认压缩提示词各加了一行「Media re-access handles」规则,但 kernel/tests/fixtures/ 的三份字节稳定 fixture 没跟着重新生成。已在 PR 分支补独立标注 commit 5104bd5e2(重新生成三份 fixture,逐份 diff 恰好只有那一行,无其他漂移)。本地全量验证:typecheck ✓、kernel 套件 1576/1576 ✓、pi-subagents 263/263 ✓、build ✓、thin-install 冒烟 ✓、wire-contract golden 23/23 ✓、verif-subset-guard(compress.ts 在守护清单内)2/2 ✓。非继承性失败(master 侧该测试此前是绿的,红由本 PR 自己的提示词改动引起)。

结构化八问

  1. 是什么问题:ref-based 媒体(远程 URL 图片、DeepSeek Files 文件引用、Google fileData URI 等)被永久钉死为不可折叠——图片密集会话里每条都成永久锚点,上下文地板一路涨到窗口 ~70% 降不下来(Context compression isn't working — it's stuck at 70% dsh. | 上下文压缩不掉 维持在 70 % dsh #5618 的 usage wall)。
  2. 什么原因导致的:hasUnrecoverableMediaPayload 把「bili 本地没有存这些字节」等同于「不可恢复」。但远程 URL / file id 本身就是再访问句柄——只要句柄活下来,折叠并不销毁任何不可恢复的东西。混淆发生在单一判定函数,四个下游门(ref 分配、advertise、unit-projection 排除、refold)全部继承了这个误判。
  3. 影响范围与严重程度:dsh 及其他车道的图片密集/文件密集工作流;p1(核心能力对这类会话实际停摆——压缩形同虚设,会话只能等窗口爆掉)。修复后该类消息可折叠,只有真正无句柄的媒体保持钉死。
  4. 怎么修复的:在唯一判定点按「有无可提取再访问句柄」拆分类别;句柄在 apply 时机械地追加进存储摘要的确定性 MEDIA REFS 段(不依赖模型自觉——OpenAI 线上 URL 串对摘要器本就不可见),merge/distill/refold 全程携带且幂等(替换模型手写的孪生段);三级提示词各加一条保留规则;保守枚举——未知不透明形状照旧钉死(判据:仅凭存活文本能否重新拿到 payload,无证据即钉)。
  5. 是否有回归问题:逐项审过触碰路径的既有行为——控制面结构化 system 钉死([PR] kernel: keep mid-conversation anthropic system messages verbatim (#3991) #3992/kernel: carrier self-identification + openai/responses mid-stream system verbatim sidecar (fixes #4159 family) | kernel: 载体自标识 + openai/responses 中途 system verbatim sidecar (治 #4159 家族) #4166)未动;可归档内联媒体(建议:compress.stripImages 默认开启——否则带图消息不可压缩会形成只升不降的输入地板撑爆上下文 #2607)未动(data-URL 正则两处逐字一致,parity 不变量保住);未知形状/tool_result 内 document/anthropic wire silently drops unknown top-level blocks (incl. PDF document) when rebuilding history #3410 未知块仍硬钉(新增负向测试钉住双向);BLOCKED 机制本身未变、只变成员(已披露);无 ref 的折叠摘要字节与原实现完全一致(appendMediaRefsSection 空输入原样返回);wire 形状不变(段落藏在摘要文本内);plugin/proxy 两模式走同一 kernel 路径。未发现回归。已披露的行为变更:① ref-based 媒体 OLD=永久钉死 NEW=可折叠+句柄随摘要;② excluded-media 警告改措辞(现在只对真·无句柄触发);③ 提示词每级多一行(压缩子请求前缀一次性重付,客户端历史前缀不受影响)。
  6. 是否破坏缓存:不影响客户端前缀缓存——摘要在折叠时一次写入、字节确定性(稳定顺序+去重+幂等追加);legacy 会话里旧的 BLOCKED ref 经既有 [cache][kernel] Ref migration during durable carrier replacement rewrites sent history, causing a prefix cache seam | [cache][kernel] durable 载体替换时 ref 迁移改写已发送历史,导致前缀缓存接缝 #3805 延迟渲染路径迁移成新号,不复用编号。
  7. 是否改了设计方向:没有转向——在既有 fold/pin/ref 机器上加一个「可恢复性」维度;机械追加强化了信任模型(服务端负责句柄存活,模型只负责正文)。
  8. 是否引入了新的配置:无。

测试有效性:新回归文件 8 个测试全有牙(五族 wire 提取矩阵含负例、幂等/陈旧孪生替换、apply e2e 断言段落落位、merge 双源句柄逐字存活、legacy BLOCKED→新号迁移);carrier-advertise-validate 与 issue3410 按 #3617 双向门禁纪律翻转并补负行。两个非阻塞观察:refold 路径的携带只被间接覆盖(trio 幂等测试+merge 测试覆盖同一机制,可接受);参数化 data URL(如带 charset)会被正则判成「引用」而非内联——属过度保留方向(摘要变大、不丢句柄),且与 host 归档通道同形,是既有形状不是本 PR 引入,不建议在此 PR 动。

收工判定:代码与行为审查通过,diff 干净(14 个文件全部服务于本修复,fixture 小修独立成 commit),CI 预期在新 head 5104bd5e2 上转绿(kernel 变更属人工合并档,请 owner 自行合入:#5629 )。PR 正文自决的残留项(host 侧 URL 渲染、#5618 次发现项)范围切割正确,不阻塞。

@ranxianglei ranxianglei left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review 结论:可合并(已实测,非纸面推断)

本地全量验证(head 5104bd5e,干净 worktree):

  • kernel 套件 1576/1576 pass(含新文件 issue5620-ref-recoverable-media.test.ts 与翻转后的 media-payload 正反例)
  • 宿主侧受影响套件(wire-contract golden + media/protected 家族)49/49 pass,golden kernel.json 差异确认只增不改(COMPRESS_PHILOSOPHY 原样)
  • root typecheck rc=0

根因链路复核(master @ 5dee4850,即 #5621 合入后现状)成立:

  1. src/acp-status.ts:278 的 PRESSURE NOTE 门槛仍是 maxPending < nudgeGrowthTokens——媒体墙会话因为被钉住的回合永远挂着一条 viable range,该条件结构性永不满足,所以日志里看到 72% 用量却没有任何解释;
  2. 本 PR 对 kernel/src/protected.ts 谓词的拆分(有可提取句柄的非 data: URL / file id / fileUri ⇒ 可折叠,句柄机械写进摘要的 MEDIA REFS 段;data: 内联字节、未知形状 {type:"mystery"}、document 块、videoMetadata-only 仍钉死)与日志症状一一对应;负例 pin 齐全,BLOCKED-ref 存量迁移走既有 #3805 deferred-render 通道。

两条观察(均不阻塞):

  1. compress.ts applySingleRange 中 collectFoldMediaRefs→appendMediaRefsSection 发生在 validateSummaryLength 之后——一次折叠若含几十条长签名 URL,存储摘要会临时超过 maxSummaryLength,直到下次 T2 tier merge 重蒸馏才收敛(merge 同样携带句柄,最终有界)。行为可接受,后续可选做软上限/告警。
  2. 残余风险(PR body 已披露、owner 已知情批准 option A):句柄是"重新取图的门牌",不是字节本身;过期签名 URL 或临时代理重启后模型侧取不到(decompress 无损恢复不受影响)。dsh 浏览器截图恰恰经常走本地代理 URL——正是 #5618 那类会话,知悉即可,不构成回滚理由。

合并顺序提示: 与 #5619(MEDIA FLOOR)共享 hasUnrecoverableMediaPayload——两者都合入后 #5619 的报告语义自动收窄为"真·无法再取的质量",互补不冲突,先后随意。分支当前基于 c29b118d、落后 master 一个 #5621(mitm-lane,文件不相交),合并前顺手 sync 一下更稳。

@ranxianglei ranxianglei left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review 结论:可合并(已实测,非纸面推断)

本地全量验证(head 5104bd5e,干净 worktree):

  • kernel 套件 1576/1576 pass(含新文件 issue5620-ref-recoverable-media.test.ts 与翻转后的 media-payload 正反例)
  • 宿主侧受影响套件(wire-contract golden + media/protected 家族)49/49 pass,golden kernel.json 差异确认只增不改(COMPRESS_PHILOSOPHY 原样)
  • root typecheck rc=0

根因链路复核(master @ 5dee4850,即 #5621 合入后现状)成立:

  1. src/acp-status.ts:278 的 PRESSURE NOTE 门槛仍是 maxPending < nudgeGrowthTokens——媒体墙会话因为被钉住的回合永远挂着一条 viable range,该条件结构性永不满足,所以日志里看到 72% 用量却没有任何解释;
  2. 本 PR 对 kernel/src/protected.ts 谓词的拆分(有可提取句柄的非 data: URL / file id / fileUri ⇒ 可折叠,句柄机械写进摘要的 MEDIA REFS 段;data: 内联字节、未知形状 {type:"mystery"}、document 块、videoMetadata-only 仍钉死)与日志症状一一对应;负例 pin 齐全,BLOCKED-ref 存量迁移走既有 #3805 deferred-render 通道。

两条观察(均不阻塞):

  1. compress.ts applySingleRange 中 collectFoldMediaRefs→appendMediaRefsSection 发生在 validateSummaryLength 之后——一次折叠若含几十条长签名 URL,存储摘要会临时超过 maxSummaryLength,直到下次 T2 tier merge 重蒸馏才收敛(merge 同样携带句柄,最终有界)。行为可接受,后续可选做软上限/告警。
  2. 残余风险(PR body 已披露、owner 已知情批准 option A):句柄是"重新取图的门牌",不是字节本身;过期签名 URL 或临时代理重启后模型侧取不到(decompress 无损恢复不受影响)。dsh 浏览器截图恰恰经常走本地代理 URL——正是 #5618 那类会话,知悉即可,不构成回滚理由。

合并顺序提示: 与 #5619(MEDIA FLOOR)共享 hasUnrecoverableMediaPayload——两者都合入后 #5619 的报告语义自动收窄为"真·无法再取的质量",互补不冲突,先后随意。分支当前基于 c29b118d、落后 master 一个 #5621(mitm-lane,文件不相交),合并前顺手 sync 一下更稳。

@ranxianglei ranxianglei left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

补充实测(修正上面"先后随意"的说法):两个 PR 有顺序耦合。 我把 #5619 的新测试文件原样叠加到本 PR head 上跑:3 pass / 3 fail——它的阳性用例按旧谓词写(远程 URL=不可恢复),本 PR 翻转谓词后这些消息变成可折叠,MEDIA FLOOR 不触发。建议合并顺序:#5619 先、#5629 后;若 #5629 先落地,#5619 需 rebase 并把阳性行改钉无句柄形状(opaque/document/videoMetadata),且其 REMOTE_IMAGE_TOKENS 计量在稳态下近似死代码(被识别的远程图家族都变成可折叠了),语义需要重定。

…t lines

#5620 added 'Media re-access handles' lines to the three default compression prompts (howToCompressRules / tier2DistillRules / tier3CondenseRules in kernel/src/compression-rules.ts). Those prompts ride every outbound turn body and feed the persisted session state, so the committed tests/golden/storage-render/*.json snapshots drift on their derived digests (per-turn sha/shaCiteNorm/bytes + state/stats/metadata/nudge). The PR regenerated tests/golden/wire-contract/kernel.json and the kernel fixtures but missed this downstream suite (golden-storage-render.test.ts + storage-engine-proofs.test.ts share these goldens), reding 8 subtests across ubuntu/windows x node 22/24.

Regenerated via scripts/update-storage-render-goldens.ts. Diff is purely digest/byte-count deltas: each wire body grows a UNIFORM +359 bytes (the constant-size prompt addition), zero decreases; blockContents, fold positions (foldAt 9 / editedAt 12) and message structure are byte-identical. No behavioral regression.
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

CI 已修好并推送到 PR 分支 2026-11-04_ref-recoverable-media(新 head 2b23fcae9)。6 个红 job 全部来自同一根因;本地已复现同样失败 → 重生成 → 复查 diff → 再跑 17/17 绿。

是什么问题:6 个红的 test job(ubuntu/windows × node22/24 的不同 shard)其实只有 2 个测试文件、共 8 个子测试(chat/anthropic/responses/google 各一):

  • tests/golden-storage-render.test.ts(4 个 "…match committed snapshot")
  • tests/storage-engine-proofs.test.ts(4 个 "full-mode restart …== committed goldens")
    两者比对的是同一套快照 tests/golden/storage-render/*.json。

什么原因:本 PR(#5620)给三个默认压缩 prompt(howToCompressRules/tier2DistillRules/tier3CondenseRules,kernel/src/compression-rules.ts)各加了一行 "Media re-access handles"。这些 prompt 会注入每一轮出站 body 并进入会话持久化状态,于是快照里记录的派生值(每轮 wire body 的 sha/bytes + state/stats/metadata/nudge 摘要)整体漂移。作者更新了 tests/golden/wire-contract/kernel.json 与 kernel fixture,但漏了下游这套 storage-render 快照。判定为本 PR 自身引入(基线 c29b118d 是绿的,加上 prompt 才红),不是继承自 master 的红;失败签名在 ubuntu/windows、node22/24 完全一致(确定性 golden 比对,非 flake)。

怎么修的:用仓库官方脚本 node --import tsx scripts/update-storage-render-goldens.ts 重新生成 4 个快照文件,单独一个 test: commit 推到 PR 分支(未夹带任何其它改动)。

回归审查(重点):逐行核了重生成 diff —— 纯派生值变化,无行为回归:

  • blockContents(折叠摘要正文)字节级不变;foldAt=9 / editedAt=12 不变;messageCount/directMessageIds/effectiveMessageIds/directBlockIds 全部不变;
  • 每轮 wire body 的 bytes 统一 +359(正是那几行新增 prompt 的恒定字节量)、零减少 —— 典型"加了一段固定文本"的特征,而非逻辑改动;
  • 结论:不影响折叠行为、消息结构或媒体处理路径。

是否破坏缓存:不涉及。改的是测试快照文件,不是运行时代码;前缀缓存/重试/去重等策略零改动。

是否改了设计方向 / 是否引入新配置:均无。我没有改动任何运行时代码,也未新增配置。"ref-based media 可折叠 + prompt 加行"这一行为变更是 PR 作者本就已做的,我只把下游测试快照对齐到它,没有引入任何新的行为漂移。

收工判定:本地定向验证通过(复现同签名失败 → 重生成 → diff 复查确认无害 → 两文件 17/17 绿)。CI 会在新 head 2b23fcae9 上自动重跑;因是确定性 golden 比对,本地绿即各平台绿。

一点提醒(非阻塞):该 PR 当前 behind master(基线之后 master 又合了约 30 个提交)。我按"只修红 CI、最小机械改动"没有 rebase —— rebase 属合并就绪范畴,且可能引入新的快照漂移/冲突,超出本次范围;已核实 master 侧并未改动这两个测试文件或这套快照,故不会产生合并冲突。是否 rebase 留给你定夺。

@ranxianglei
ranxianglei merged commit 23a826d into master Nov 4, 2026
51 checks passed
@github-actions

github-actions Bot commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.1028-master.23a826d (rolling master tag).

npm install -g billion-context@0.0.1028-master.23a826d  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working dsh p1 scope/kernel

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant