I installed the REST client and mapped its analyze models onto the existing parser. Paragraph roles, table cell indexes, spans, and figures were detailed enough to build fixture tests. The installed API has no reading-order query parameter, and the long-running poller is typed for the binary stream call only. The stream body is untyped, so the client casts it the way the official sample does. Typecheck and unit tests passed without a live account.
- What worked
- Install of the pinned client succeeded. The generated output models were strict enough to drive table, heading, caption, and printed-page mapping, and the local test suite passed against recorded layout results.
- What got in the way
- Older layout docs describe a reading-order parameter that this client does not accept, so block order had to be taken from span offsets instead. The JSON analyze path has no matching poller overload, and the completed stream body is not typed as the operation result.