Lead bilingual READMEs with user outcomes and a coherent desktop case - #168
Merged
Conversation
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.
Explain three concrete user chores before implementation details; lead with the controlled native desktop case and keep the separate packaged example clearly labelled. Split entry paths for existing desktop users, self-contained demo users and project integrators. Preserve native Codex attribution, setup gaps and unmeasured incremental benefit. Remove the global Node badge and clarify that workspace commands do not control the native skill route. Recheck #158 and recent comments; retain an evidence-backed reply draft without posting, with one bounded onboarding checkpoint before a consolidated reply. Docs lint and local anchor checks passed. GitHub Markdown rendering was inspected as HTML; no browser screenshot or new live result is claimed. No runtime changes or community replies.