mirror of
https://github.com/morluto/rea
synced 2026-10-28 06:46:47 -04:00
270bc38f72
Codex and Grok client TOML was parsed with smol-toml's default reader, which rejects any integer beyond JavaScript's safe Number range. Valid TOML 1.0 Int64 values such as `max_bytes = 9223372036854775807` made setup, doctor and uninstall treat the whole file as malformed. The client TOML owner now parses with `integersAsBigInt: "asNeeded"`, keeping safe integers as numbers and larger ones exact as bigint, and rejects values outside signed Int64 before any write. All TOML parses in the document owner (document read, inline string decoding and the preserving-edit check) use that reader. The inline-table writer emits bigint values, and setup and doctor accept a positive bigint `startup_timeout_sec`/`tool_timeout_sec` instead of replacing or rejecting it. Fixes #4917 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>