Mark the v1 client as legacy#2
Draft
JamesCarnley wants to merge 1 commit into
Draft
Conversation
Route architecture work to the Client v2 and EFS v2 design spines and keep this repository's setup documentation explicitly scoped to v1. Co-authored-by: GPT-5 <noreply@openai.com>
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
1 participant
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
Why
The repository still presented itself as the production client and called the
SDK a future dependency. That guidance could cause agents to retrofit the
from-scratch v2 redesign into an outdated v1 codebase before an implementation
target has been chosen.
Validation
git diff --checknpm run build(passes with the repository's existing Vite/CSS/chunk-size warnings)Agents involved