Repository navigation
feat: add service-backed document API - #18
Merged
Merged
Conversation
privatenumber
marked this pull request as ready for review
August 10, 2026 04:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ocrDocument()andocrDocument.pages()Problem
The document core and CLI can recognize paragraphs, tables, and lists, but Node callers still need a typed API. A one-shot wrapper would undo the shared-service behavior that protects server workloads from spawning a native process for every concurrent request.
For example, a server can receive ordinary OCR, document-page streaming, and searchable-PDF calls together. Each must wait in one FIFO queue so Vision work remains serial, cancellation is consistent, and the process is reused.
Changes
Add
documentanddocument-pagesservice operations with the existing framed unary and pull-controlled stream protocol. Node validates the recursive document payload before exposing it, including malformed candidate arrays, page metadata, and the macOS-unavailable error.Main-thread document calls now share the native service with the existing APIs; worker calls retain their existing one-shot lifecycle. The public result schema and document language rules match the CLI.