Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(token-meter): drop the dead deep-compare from claim bookkeeping

Browse Source 
A defined fold claim is always freshly built and adjacent metering events
cannot repeat, so presence alone decides the claim transition; the value
comparison was unreachable and failed the per-file branch gate.
This commit is contained in:
imccyu
2026-08-06 03:20:34 +08:00
parent 59df683ef1
commit 297edd512d
1 changed files with 3 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
packages/llm/token-meter/src/usage-projection.ts
View File

@@ -94,12 +94,6 @@ interface ContextPressureState {
claim?: ShadowPriceClaim
}
/** Whether two optional shadow-price claims price the same range identically. */
const claimEquals = (left: ShadowPriceClaim | undefined, right: ShadowPriceClaim | undefined): boolean =>
left === right
|| (left !== undefined && right !== undefined
&& left.start === right.start && left.end === right.end && left.tokens === right.tokens)
/**
* Token-meter's session projection unit.
*
@@ -194,7 +188,9 @@ ProjectionDefinition<'contextPressure', ContextPressureState> = {
if (fold.deltaTokens !== 0) {
next = { ...next, surfaceTokens: next.surfaceTokens + fold.deltaTokens }
}
if (claimEquals(state.claim, fold.claim)) return next
// A defined fold.claim is always freshly built, so presence decides claim
// bookkeeping: no claim before or after this event leaves `next` as is.
if (state.claim === undefined && fold.claim === undefined) return next
const { claim: _expired, ...withoutClaim } = next
return fold.claim === undefined ? withoutClaim : { ...withoutClaim, claim: fold.claim }
},