Repository navigation
docs: clarify released server setup for VS Code - #994
Merged
Merged
Conversation
Contributor
Documentation PreviewYour documentation changes have been deployed to: This preview will be available until the PR is closed. |
This branch was successfully deployed
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.
The Docker quickstart pointed to an image repository that returns
manifest unknown. Point to the publishedterraphim-aiimage and document its required explicit role configuration and haystack dependencies instead of presenting an incomplete launch command.The guide records a bounded check using the released VS Code extension 0.1.4 in VS Code 1.126.0 and a digest-pinned public server image: real role switching saved
concern → cost → concern, and search fallback savedsupplierthrough both autocomplete commands. It distinguishes native API checks from visible UI qualification.Validation: independently reviewed documentation, parsed JSON examples matched the actual successful configuration, actual saved output readback, and
git diff --check. No package, runtime, dependency or release changes.