Repository navigation
[PR] probe: master + #3658 full-CI run - #3679
Closed
ranxianglei wants to merge 17 commits into
Closed
ranxianglei wants to merge 17 commits into
ranxianglei wants to merge 17 commits into
Conversation
…3640) Three real-world defect classes shared one root: fold identity keyed coverage to content hashes, so id re-mints without content loss were read as destruction. - shape tier in planReconciliation: loose word-evidence pairing for prose cells (wordbag equal + simhash hamming <= 8 + role/length guards), flanked k-th discipline for evidence-less cells (image families, #3588) — claims require BOTH flanks verified on the wire - residual census: unmatched class-carrying ids classify as transformed (near-dup evidence exists) vs absent-everywhere (content truly off the wire) - verdict classifier: transform churn and wire-suffix-continuation truncation (host compaction/windowing, #2695) never accrue the collapse streak; one info latch each per session - episode witness: wire order frozen at episode start; a foreign conversation can never become the truncation baseline mid-episode - total collapse now latches foldEpochConfirmPending and pauses folding (verbatim passthrough, snapshot kept) until realignment or explicit user epoch confirmation, replacing the destroyed-escalation misdiagnosis; detection intact (#2903 tests) - unresolved summary anchors clamp ahead of the newest user turn instead of the array tail (#3640 "model answers stale summaries") - single genuine edits below the mass bar still report drift honestly Tests: tests/fold-anchor-doctrine.test.ts 6/6; families green (fold-drift 7, fold-reconcile 66, positional 24, issue2915 15, and the 1908/1987/2033/2601/1595/1820/1569/images-archive/refold set).
… change (#3644) CI-fix additive commit: the kernel-guard job enforces that any change under kernel/src/** carries a kernel/package.json version bump (Kernel Boundary rule 2, AGENTS.md). The placement fix in kernel/src/prune.ts landed without it, so kernel-guard failed and the test matrix was skipped.
…3644 kernel version bump) The a9fe72f kernel bump moved kernel/package.json to 0.0.131 but left the file:./kernel resolution in package-lock.json at 0.0.130, so the lock-sync job (npm install --package-lock-only && git diff --exit-code) drifted red and gated the test matrix. Regenerate the lock record so it matches.
…on (#3644) The docstring named 'status panel' as a consumer, but only the preflight fold gate reads epochConfirmPending in this PR. Narrow the note so it does not promise an unimplemented panel integration.
…ta keys (#3644) #3644 persists four new session-metadata latches (foldEpisodeOrder, foldEpochConfirmPending, foldShapeChurnNoted, foldTruncationNoted), so the pinned persisted-state digest drifts in exactly one section: metadata. Wire bytes are unchanged — all 15 per-turn outbound-body entries and the state/blockContents/stats sections are byte-identical to the previous goldens (verified by structural diff of each record). Regenerated with scripts/update-storage-render-goldens.ts under the same BILI_IMAGE_RESCALE=0 pin the test applies (#3400); justification for the golden change per the golden rule, mirrored in the PR body.
…pt (#3400 parity) The test pins the legacy wire shape before driving but the regen script did not — regenerating without the pin writes goldens whose per-turn wire digests differ from what the test drives under CI, red-ing the suite on the next run. Align the two so the documented regen flow can never silently diverge from the test's conditions.
…review) - document the doctrine ladder (shape tier / census verdicts / episode witness / epoch-confirm gate / unresolved-anchor placement), the honesty boundary (strict wordbag equality — bulk suffix re-stamps are NOT claimed by design), and zero-migration storage independence - EN + zh-CN mirrors, cross-linked from the header and Related lists - tests: harden the #3640 fixture so every reshaped cell is shape-tier- only (deleting the tier now escalates — the no-escalation assertion has teeth), pin byShape > 0 on the first pass, and add adversarial honesty-gate coverage (role flip / length padding / word reversal are wordbag-equal but must not be claimed)
One logical conversation, one set of core ids, in all four dialects. - kernel/src/wire/identity.ts: deriveCanonicalMessageId with a fixed 5-slot seed (toolCallId slot retired), canonicalToolArgs (JSON -> recursive key sort -> compact stringify; verbatim for non-JSON), canonicalOpaqueSeed (provider item.id/status stripped), shared [image] marker for image cells. - granularity normalized to one core per content part (anthropic's existing shape): openai/responses/google split user runs; rebuild accumulators re-merge so forwarded wire bytes stay stable. - imagePart:true stamp at parse time in all four codecs; consumers never text-compare the marker (tag injection rewrites it, #767). - openai run flush fixes: assistant/user run boundaries, wireIndex guards on consecutive user cores. - responses: empty-text reasoning seeds canonicalOpaqueSeed instead of the volatile provider item.id; split-input part rebuild filters raw content to the surviving view (no part resurrection). - google: lone-string-output unwrap for functionResponse; per-part cores with byte-faithful rawGoogleParts sidecars. - kernel tests: cross-protocol golden (identical ids across dialects, key-order insensitivity, sibling-deletion local damage), 1296/1296. - src goldens re-pinned (id churn from canonical tool seeds only).
…gle unwrap assertion (#3642 follow-ups) Review of #3658 found two must-fix items; both fixed here. 1. Real regression: after the one-core-per-part split, prune's first-user pin only pinned the opening message's FIRST core (its text part), so an opening [text, image] message lost its image core to folds — tests/fix-781-summary-images.test.ts (responses variant) failed with "0 !== 1" surviving images. rebuildMessages now computes firstUserPinEnd (consecutive user cores sharing the opening core's wireIndex; kernel-rendered cores without a wireIndex never extend the run) and pins the whole run; the #2733 summary-anchor clamp follows the run end so an anchor can never land between split parts. Run length 1 keeps the legacy shape byte-for-byte. Two new state-prune tests. 2. Stale assertion: wire-google.test.ts still expected the pre-unwrap tool-result shape '{"output":"a.ts\nb.ts"}' — updated to the new plain 'a.ts\nb.ts' (this was the static-gates red on head 4165380). Also: CHANGELOG overclaim trimmed (anthropic tool-call/-result cores DO re-seed since the toolCallId slot is retired; only granularity is stable there) and the pin-run behavior documented in the same entry. kernel: version 0.0.131 → 0.0.132 (src/prune.ts), lock regenerated.
…review) The per-part user split accumulates unknown parts seen AFTER a text core on lastTextCore.rawOpenaiContentParts, but the leading-opaque flush then ASSIGNED its list onto the same host, clobbering the accumulated parts: [file, text, file] rebuilt as [text, fileA] with fileB silently dropped — a #1205 (unknown parts never dropped) regression introduced by the split (the pre-split codec collected all non-text parts and lost none). Prepend instead of assign so both groups survive in relative order. Adds the [file, text, file] round-trip regression test to media-payload.
…fter the kernel version bump)
Conflict resolution: kernel 0.0.132 (higher wins), root+kernel locks regenerated, CHANGELOG union-merged. Probe branch only — not for merge.
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4345-pr.3679.601cba3This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3679.tgz
npm install -g packageInstall instructions are refreshed on each push. |
…runs reuse stale event payload)
…id-churn canary (full-CI shard-3 reds, #3658 follow-up) - kernel/src/wire/openai.ts: user-branch guard extended to !Array.isArray(content) — a lone content-part object (some clients) threw 'm.content is not iterable' (#2824 corpus). Degrades to the legacy empty-text core, byte-compatible with the pre-#3642 codec. kernel 0.0.132 -> 0.0.133, both locks regenerated. - tests/golden/storage-render/chat.json: regenerated via scripts/update-storage-render-goldens.ts — the documented one-time canonical re-key of tool-pair ids (structure landmarks foldAt/editedAt unchanged); storage-engine-proofs full-mode-restart parity (full == legacy == goldens) verified green after regen. - tests/identity-proof.test.ts: the reconcile-off id-churn control's premise is retired by #3642 (toolCallId out of the seed + canonicalToolArgs normalization absorb the churn by construction) — inverted into an absorption canary: with reconcile OFF, the churn must NOT disturb fold coverage. Guards against id-sensitivity leaking back into the canonical seeds. - kernel/tests/media-payload.test.ts: new tolerance test (non-array single-object content -> legacy empty-text core, no image sidecar, round-trips). Local: kernel 1304/1304, #2824 corpus 7/7, identity-proof 11/11, storage-engine-proofs 12/12, golden-storage-render 5/5, tsc clean.
…ignature (#2824 class visibility) The catch in buildIncomingImageIndex returned an empty index with zero signal — that is exactly how the #3642 single-object-content TypeError hid: image recovery silently off for every session carrying the shape, no error, no log line. Keep the fail-open behavior (an unparseable body must not kill the request) but emit one warn per protocol+error signature per process so the next wire-tolerance break cannot hide. Test: proxy-bomb body -> empty index + the #2824 visibility warn.
Owner
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ai: zhipuai-lb/glm-5.3
这不是功能 PR,是 full-CI 探针分支,不要合并。
内容 = 最新 master(1f0397b)+ #3658 分支头(acc2aea,含 review 修复 6663f89/3c940c58/acc2aea4)的合并。目的:在「master + 本 PR」的合成头上跑一遍全量 CI 矩阵(12 腿测试 + static gates + e2e 车道),验证 #3658 与 master 最近 70 个合并(含 #3580/#3584/#3540 等)的交互面。
已知状态:dispatch 跑在 acc2aea 上有 4 个测试红(shard 3:storage-render golden chat、identity-proof control、#2824 corpus、storage-engine full-mode restart golden)——本地已复现 3/4,归因进行中,详见 #3658。本探针用于确认这些红是否在与 master 合并后仍然存在/有无新增。
冲突解决:kernel 取高版本 0.0.132,两个 lock 重新生成,CHANGELOG 双取。
Ref #3658
kernel-change: probe merge only — carries #3658's already-owner-declared kernel changes (canonical core identity 0.0.132); this branch adds no kernel edits beyond version/lock conflict resolution.