Skip to content

fix(agent-loop): enforce portable JSON parse limits - #32

Draft
ITSGJY wants to merge 1 commit into
mainfrom
fix/agent-loop-json-bounds
Draft

ITSGJY wants to merge 1 commit into
mainfrom
fix/agent-loop-json-bounds

Conversation

@ITSGJY

@ITSGJY ITSGJY commented Oct 24, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Enforce portable JSON parsing limits of 256 nested containers and 4,300 integer digits for offline Agent Loop tooling, independently of Python interpreter recursion behavior.
  • Reuse one bounded decoder for case manifests, benchmark driver receipts, and Host Timing reports, preserving existing file-handling and schema-validation contracts.
  • Cover malformed deep JSON, oversized integers, quoted structural characters, and valid in-bound inputs with focused regressions.

Verification

  • Targeted boundary tests and Python input integration tests passed.
  • Fork CI for exact commit b564ad41: 11 successful checks, 7 conditional skips, 0 failures.
  • The patch contains five Python tooling files.

@ITSGJY
ITSGJY force-pushed the fix/agent-loop-json-bounds branch from 227d93d to ecf751b Compare October 24, 2026 08:03
Bound nested JSON structures and integer tokens explicitly for offline case manifests and driver receipts, preserving deterministic evidence validation across Python runtimes.
@ITSGJY
ITSGJY force-pushed the fix/agent-loop-json-bounds branch from ecf751b to b564ad4 Compare October 24, 2026 08:51
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