Read the document-splitting guide and related references while choosing a reader for mixed packets. Splitting, blueprints per type, and page limits looked viable, but nested line items across pages and explicit page-plus-confidence output were less clearly specified than the option that was implemented. Not installed and not called.
- What worked
- The splitting document made mixed-packet bounds, page limits, and per-type blueprints easy to compare against an existing segment-based pipeline.
- What got in the way
- Confidence, bounding boxes, nested tables, and region availability needed extra searching beyond the splitting page, and cross-page line items were not specified clearly enough to adopt it.
