docs(nemo-retriever): document Nemotron Parse hosted vs self-hosted contract selection

[kheiss-uwzoo]

Summary

Documents Nemotron Parse hosted Build vs self-hosted request-contract selection after library-side compatibility landed in #2398.

Hosted NVIDIA Build and self-hosted nemotron-parse-v1.2 still use different request contracts, but the library now selects the matching contract automatically. Hosted Build is a supported path.

Changes

• prerequisites-support-matrix.md — Default NVCF endpoints: annotate the nemotron-parse row and add a configuration note covering automatic model/contract selection, when to set nemotron_parse_invoke_url / nemotron_parse_model, and the mixed-endpoint rule. Uses public method="nemotron_parse" (not extract_method).
• troubleshoot.md — model/endpoint mismatch entry for the residual HTTP 400 / text-input failure when an incompatible tagged or v1.2 model is sent to Build; resolution is omit nemotron_parse_model or set nvidia/nemotron-parse.

Scope

Docs-only. Runtime contract selection is already in #2398.

Self-review

• Reflects post-Fix hosted Nemotron Parse contract #2398 supported Build path (not the old unavoidable failure mode)
• Uses method= for public API guidance added by this PR
• Page-role / link-CTA check passed (check-nrl-doc-leakage.ps1)
• Cross-links and anchors consistent

[greptile-apps]

Greptile Summary

This docs-only PR documents the hosted NVIDIA Build vs self-hosted Nemotron Parse request-contract selection that landed in #2398, and globally renames extract_method= to method= to reflect the updated public API surface.

• Global rename: extract_method=\"nemotron_parse\" → method=\"nemotron_parse\" applied consistently across eight files (docs, READMEs, Helm reference).
• New callout in prerequisites-support-matrix.md: explains that hosted Build and self-hosted nemotron-parse-v1.2 use different request contracts, that the library auto-selects the matching contract, and when to set nemotron_parse_invoke_url / nemotron_parse_model explicitly.
• New troubleshooting entry in troubleshoot.md: describes the HTTP 400 "Content cannot be a plain string" failure from a contract mismatch and provides resolution steps.

Confidence Score: 5/5

Safe to merge; all changes are documentation-only with no runtime code modified.

The rename of extract_method to method is applied uniformly across all eight changed files, cross-links and anchors are consistent, and the new callout and troubleshooting content accurately reflects the contract-selection behaviour described in #2398. Two minor prose clarity issues exist in the new callout but neither introduces incorrect guidance that would break a user's deployment.

Files Needing Attention: The new callout block in prerequisites-support-matrix.md (lines 114-123) is the only area needing a second read for prose clarity; the rest of the changes are mechanical renames.

Important Files Changed

Filename	Overview
docs/docs/extraction/prerequisites-support-matrix.md	Renames extract_method to method in table/notes, and adds a new hosted Build vs self-hosted NIM callout; one sentence uses undefined "endpoint lists" terminology that may confuse readers.
docs/docs/extraction/troubleshoot.md	Renames extract_method to method in one existing entry, and adds a new Nemotron Parse model/endpoint mismatch troubleshooting section.
docs/docs/extraction/customize-extend.md	Single-line rename of extract_method to method; consistent with the rest of the PR.
docs/docs/extraction/faq.md	Single-line rename of extract_method to method; consistent.
docs/docs/extraction/multimodal-extraction.md	Renames extract_method to method in three locations; all consistent.
docs/docs/extraction/overview.md	Renames extract_method to method in two locations; consistent.
nemo_retriever/README.md	Single-line rename of extract_method to method; consistent.
nemo_retriever/helm/README.md	Single-line rename of extract_method to method in the Helm value description; consistent.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User sets method=nemotron_parse] --> B{nemotron_parse_invoke_url set?}
    B -- No --> C[Use default hosted Build URL]
    B -- Yes --> D{Points to Build endpoint?}
    D -- Yes --> C
    D -- No --> E[Use self-hosted chat endpoint]
    C --> F{nemotron_parse_model set?}
    F -- No --> G[Auto-select nvidia/nemotron-parse]
    F -- Yes --> H{Model matches Build contract?}
    H -- Yes --> I[Use image-only tool-call contract]
    H -- No versioned v1.2 model --> J[HTTP 400 Content cannot be a plain string]
    G --> I
    E --> K{nemotron_parse_model set?}
    K -- No --> L[Auto-select nvidia/nemotron-parse-v1.2]
    K -- Yes --> M[Use specified model]
    L --> N[Use tagged text-prompt contract]
    M --> N

Loading

_{Reviews (4): Last reviewed commit: "docs(nemo-retriever): standardize extrac..." | Re-trigger Greptile}

[kheiss-uwzoo]

Holding this as draft pending Charles's engineering compat changes so we handle each nemotron-parse version properly. Will refresh the doc wording against that PR once it lands (easier to contextualize then).

[charlesbluca]

Thanks for holding this until #2398 landed. The hosted and self-hosted deployments still use different request contracts, but #2398 added library-side compatibility, making hosted Build a supported path. The inline comments identify the places that still describe the old failure mode, along with one invalid public parameter name.

The PR title and description also need to be refreshed: they currently state that hosted extraction fails and that dual-API support remains future work. They should instead describe the supported contract-selection behavior and any configuration guidance retained by this PR.

Once the docs and PR metadata reflect #2398, I did not find another content blocker in this diff; the anchors and cross-links are consistent.

[charlesbluca]

Thanks for cleaning up the touched pages, and apologies—I was not clear that I meant the remaining Nemotron Parse/general extraction-selector references across the customer-facing docs as well. These can be updated directly from extract_method to method:

• docs/docs/extraction/multimodal-extraction.md: lines 27, 30, 55, 61
• docs/docs/extraction/overview.md: lines 26, 30
• docs/docs/extraction/faq.md: line 39
• docs/docs/extraction/customize-extend.md: line 26
• nemo_retriever/README.md: line 73
• nemo_retriever/helm/README.md: line 477

One caveat: nemo_retriever/README.md:129 uses extract_method="audio"; please do not mechanically change that to method="audio". Audio uses a different API path (.extract_audio()), so that occurrence should be handled separately rather than included in this replacement.