Skip to content

[PR] Minor fix: Revert the v6 pin for parity tests along with the fastpath-v6 rollback (master self-red fix) | 小修:parity 测试的 v6 钉随 fastpath-v6 回滚一起回退(master 自红修复) - #5862

Merged
ranxianglei merged 1 commit into
masterfrom
2026-11-07_master-parity-pin-hygiene
Nov 7, 2026

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

小修:把 parity 测试的两条 v6 钉退回 pre-v6 判决(master 自红修复)

现象:master HEAD 起 tests/msgid-rule-parity.test.ts 恒红 2 条(per-slot screening: one hole voids the WHOLE list (v6 F2) 与 pf-channel end-to-end handshake: v6 F1 fixed tail window)。

机制链:#5826 的提交 33b2f82dc(ci-check,11-07 12:21)在「#5652 fastpath-v6 已合入 master」的前提下把这两条判决重新钉到 v6 F1/F2;随后 revert PR #5854(merge bebc239f2)又把 fastpath-v6 代码整体撤掉。代码没了、钉还在 → 断言 v6 行为的两条必然失败。纯 master 复现验证过(detached worktree @ fb18e7e4c 同 2 条红),与任何未合并分支无关。

修法选择:本文件在 bc44f77b0(#5826 原始 parity 提交)与 33b2f82dc 之间的差异恰好只有这两组钉的调整(diff 已核对:仅 import 行、LONG_LIST/OVER_CAP 常量、两个测试块),所以直接恢复该文件到 bc44f77b0 状态 = 精确地只回退那两处判决,不丢其他内容。恢复后语义与现存代码一致:坏槽骑 %3F、尾部窗口按学到的 K 切片、无 16384 上限。

证据:tsc --noEmit 干净;node --import tsx --test tests/msgid-rule-parity.test.ts → 5 pass / 0 fail。

合并后请顺手把 #5842 rebase 一次(它当前 head 继承了同样的两红)。

…stpath-v6 code was reverted, #5854)

#5826 commit 33b2f82 re-pinned two msgid-rule-parity rows to the v6 F1/F2
rulings «after master merge»; revert #5854 then removed the fastpath-v6
code (#5652), leaving those pins asserting behavior that no longer exists —
master failed the same two rows on pure fb18e7e (verified via detached
worktree). This restores tests/msgid-rule-parity.test.ts to its bc44f77
state, i.e. exactly undoes the 33b2f82 hunks: PF_SLOT_UNKNOWN import back
to pf-channel.js, per-slot "?" rides-again semantics, K-sliced tail window,
and the removed OVER_CAP row (v6 MAX_IDS 16384 no longer applies).
@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-11-07_master-parity-pin-hygiene (613d290)

Latest build — install this exact version

npm install -g billion-context@0.0.8466-pr.5862.9196095

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
613d290 billion-context@0.0.8466-pr.5862.9196095 build

Download artifact

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

Install instructions are refreshed on each push.

@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.1068-master.713a975 (rolling master tag).

npm install -g billion-context@0.0.1068-master.713a975  # 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.

@ranxianglei ranxianglei changed the title 小修:parity 测试的 v6 钉随 fastpath-v6 回滚一起回退(master 自红修复) [PR] Minor fix: Revert the v6 pin for parity tests along with the fastpath-v6 rollback (master self-red fix) | 小修:parity 测试的 v6 钉随 fastpath-v6 回滚一起回退(master 自红修复) Nov 7, 2026
Louie0806 added a commit to Louie0806/billion-context that referenced this pull request Nov 7, 2026
…nel wiring + ranxianglei#5862 parity hygiene + ranxianglei#5860 phantom-pressure guard

Master moved twice since the last sync (295ba58 -> 591e940 -> df0a402).

- 591e940 (folded in here): ranxianglei#5862 "master hygiene" restored the
  msgid-rule-parity pins to their pre-v6 verdicts (undoing 33b2f82,
  which had pinned behaviour that the ranxianglei#5854 revert deleted), plus the
  ranxianglei#5860 phantom-pressure guard (a7cbfd1) and the kernel 0.0.184 bump.
- df0a402 (this merge): ranxianglei#5842 identity-channel wiring - one unified
  consume seam for every client lane (opencode V2 stamped header, goose/
  qwen adapters, openai row-pin parity, decoupled cohort gate), the
  identity DETERMINATION docs, and the unused-exports gate fixes.

The merge itself was conflict-free: the only shared files are the two
generated CONFIGURATION docs plus the website config-reference/web
artifacts, all of which are regenerated from the committed seeds rather
than hand-merged.

One inherited red needed a golden refresh: tests/golden/storage-render/
*.json digest drift, pre-existing on pristine master (verified on a
detached df0a402 worktree before the merge). The metadata section digest
and its derived stateDigest/stateDigestAligned moved with a7cbfd1, which
added compress.requireUsageSampleForPressure (default true) to the config
echo written into session.metadata - but that commit did not regenerate
tests/golden/storage-render/. Regenerated all four under the documented
pinned environment (node --import tsx scripts/update-storage-render-goldens.ts);
the diff is exactly 3 lines per wire (stateDigest, stateDigestAligned,
sectionDigests.metadata) and every other section digest is byte-identical.
ranxianglei added a commit that referenced this pull request Nov 7, 2026
…ted-state shape

Master moved past this branch's base (295ba58 → df0a402: #5860 phantom-pressure
guard + kernel 0.0.184, #5862 pin hygiene, #5842 identity-channel-wiring). The new
kernel config surface changes what the golden drive persists per session, so every
merge-ref CI run reds on all four wires even though no rendering behavior moved.

Re-generated via scripts/update-storage-render-goldens.ts (its own Parity #3 pin).
Per wire only stateDigest / stateDigestAligned / sectionDigests.metadata changed —
all turns[].sha (wire bodies) byte-identical, foldAt/editedAt unchanged,
state-key set unchanged ("state-key divergence: none").

A/B proof, same machine, same env (real node_modules each, kernel dist rebuilt):
- base 295ba58 + this branch's BILI_MESSAGE_TIMESTAMPS pin   -> exit 0, all green
- master df0a402 + identical pin                              -> exactly these four
  failures; digests byte-match our PR's CI errors verbatim
  (chat f53ae7a7..., anthropic 769f3766..., responses 01c80a61..., google 2c935a3a...).
Master's last scheduled CI predates #5860, so nothing upstream has surfaced this
yet; regenerating here so the branch is green against live master. No render or
storage-contract intent behind the delta beyond what the merged upstream commits
introduced.
Louie0806 added a commit to Louie0806/billion-context that referenced this pull request Nov 7, 2026
…nel wiring + ranxianglei#5862 parity hygiene + ranxianglei#5860 phantom-pressure guard

Master moved twice since the last sync (295ba58 -> 591e940 -> df0a402).

- 591e940 (folded in here): ranxianglei#5862 "master hygiene" restored the
  msgid-rule-parity pins to their pre-v6 verdicts (undoing 33b2f82,
  which had pinned behaviour that the ranxianglei#5854 revert deleted), the ranxianglei#5860
  phantom-pressure guard (a7cbfd1), and the kernel 0.0.184 bump.
- df0a402 (this merge): ranxianglei#5842 identity-channel wiring - one unified
  consume seam for every client lane (opencode V2 stamped header, goose/
  qwen adapters, openai row-pin parity, decoupled cohort gate), the
  identity DETERMINATION docs, and the unused-exports gate fixes.

The merge itself was conflict-free: the only shared files are the two
generated CONFIGURATION docs plus the website config-reference/web
artifacts, all of which are regenerated from the committed seeds rather
than hand-merged.

Two golden refreshes ride along, both caused by a7cbfd1 and both already
red on pristine master before this merge (verified on detached worktrees at
591e940 and df0a402):

- tests/golden/storage-render/*.json - the new
  compress.requireUsageSampleForPressure (default true) lands in the config
  echo written into session.metadata, so only the metadata section digest
  and its derived stateDigest/stateDigestAligned moved. Three lines per
  wire; every other section digest is byte-identical.
- tests/golden/wire-contract/kernel.json - the same knob appears in the
  pinned acp-kernel NudgeConfig export snapshot: exactly one added line,
  "requireUsageSampleForPressure": true.

Both regenerated with the documented scripts (update-storage-render-goldens,
update-wire-contract-goldens) under the pinned suite environment.

Not fixed here (upstream behaviour, needs an owner ruling): a7cbfd1
defaults the pressure band to usage-grade readings only, but
tests/fork-nudge-trigger.test.ts and tests/silent-backend-nudge.test.ts
still assert that a local-estimate reading fires the pressure nudge. Both
are byte-identical to master and fail there too, so this merge does not
touch them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant