fix(runtime): stop treating JSON bytes as hard token limit #467
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/model-input-false-hard-limit"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Production 0.1.325 rejects legitimate Peter and Odo requests because serialized JSON byte counts are treated as tokens and hard-capped at 131072. Remove the false final admission gate while retaining compaction pressure and provider context limits; no history or effect pairs are truncated. Both working and summary calls can recover. Resource/cost boundary requires a future provider-aware token mechanism, not a byte=token comparison. Local typecheck/build and 2587 tests passed, 1 skipped; independent review PASS with P2 cost-boundary note. Existing operator work must not be replayed.
PI-REVIEW-RECEIPT
State: PASS
Head:
8bccc2d77ca8Summary: PASS: No blocking findings. The change removes coverage for an important oversized-tool-result failure path.
Findings: 1
Top findings:
PI-REVIEW-RECEIPT
State: PASS
Head:
8a7eef392b40Summary: PASS: No blocking findings. The change leaves a non-blocking gap in compaction recovery coverage.
Findings: 1
Top findings: