bounded parsing for safety

[MichaelMure]

Confidence Score: 3/5

Fix the oversized-edit allocation path before merging; it can exhaust memory before returning the new limit error.

Findings

1.   Oversized edits exhaust memory ▶
2.  Command entries escape the ceiling ▶

Summary

Adds 16 MiB, entry/header, and item limits to parsing and edits. File loads now emit entries while parsing and share an entry budget across includes.

• Uses smaller offsets and avoids retaining file pieces during loads.
• Adds limit, include-error-order, and memory tests; removes stored benchmark output.
• Oversized edits still allocate before rejection. The load documentation also overstates the limit for command entries.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A["File bytes"] --> B["Byte limit"]
  B --> C["parseFile: entry and item limits"]
  C --> D["Editable File"]
  D --> E["Build replacement text and output"]
  E --> F["parseFile checks edited output"]
  F -->|Accepted| G["Replace File contents"]
  F -->|ErrLoadLimit| H["Keep original contents"]
  I["Env.Load"] --> J["parseEntries with shared budget"]
  J --> K["Emit entry, then follow include"]
  K -->|Included file| J
  K -->|Continue parent| J

Loading

_{Reviews (1) · Last reviewed commit: "bounded parsing for safety" · Reviewed by Greptile}

[greptile-apps]

MichaelMure has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.