[Docs] Correct provider setup and inference guidance - #1889
Draft
roomote-community[bot] wants to merge 1 commit into
Draft
[Docs] Correct provider setup and inference guidance#1889roomote-community[bot] wants to merge 1 commit into
roomote-community[bot] wants to merge 1 commit into
Conversation
Contributor
Author
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.
What changed
Corrected public setup guidance across inference, compute, source-control, communications, integration, and cookbook pages. The inference docs now accurately describe model seeding and deletion, credential validation, environment-based setup, provider discovery, authentication, presets, and subscription limits.
Why this change was made
Several operator-facing details had drifted from the current implementation and provider behavior. These corrections keep setup and troubleshooting guidance aligned with the shipped product.
Impact
Operators get more precise configuration and failure guidance without any runtime behavior change. The docs build and broken-link checks pass; rendered screenshot capture was unavailable because the delegated proof runtime could not start at the configured task depth.