Repository navigation
Report oversized native records with accurate resource-limit recovery - #46
Merged
Merged
Conversation
added 8 commits
October 5, 2026 22:13
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
1 participant
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.
A native JSONL record over the fixed 1 MiB framing limit was reported as malformed protocol with advice to reinstall a supported harness. The runner had stopped at a resource boundary before establishing the record's JSON validity.
Both Bun and Rust now report
HARNESS_FAILED/22 with the closedrecord-byte-limitdiagnostic and artifact/summary recovery advice. Doctor JSON, native dry runs and receipts exposemaxRecordBytesseparately from aggregate/capture limits. Native budget objects require that fixed cap in the current schema; non-native reports may omit the budget object. The cap is unchanged, and raising--native-output-bytesdoes not raise it. No automatic retry or lifecycle weakening is introduced.Shared controls accept exactly 1 MiB and reject one byte over with normal and larger aggregate budgets, preserving incomplete terminal state and cleanup. Mandatory compiled Rust integration controls run in ordinary Unix admission. Positive and missing-cap schema controls prevent either product from silently losing the diagnostic.
Validation: independent review approved final head
0461be34c01e137d0a6e7bbe216eb531ecc48072. Full Bun production validation passed 746 tests with three existing skips; focused Rust tests, strict Clippy, typecheck, schemas and architecture passed. Final combined budget/record controls passed eight tests with 176 assertions against Bun source, a fresh compiled Bun CLI and a Rust binary rebuilt from identical production source. Final head0461be34 passes all 15 checks. Full Linux/macOS logs confirm mandatory compiled Rust record controls and Bun boundary cases executed. IMP-089 retains earlier PATH/disk failures, the artifact-mismatch experiment and corrected receipts. The attempted full local combined Rust suite exhausted disk; it is not claimed passing.Addresses #23. No new Python, provider calls, release or deployment. This does not add a larger-record setting or claim to reproduce the unavailable live payload.