Verify live Kitchen installs and make the public setup clear - #10
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
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.
New visitors can mistake the map command for Kitchen and expect an editor extension or automatic artifact handoffs. Lead the README with the real kitchen overview, a short silent cooking clip, the exact public install command, and a clear comparison of the two views. Document VS Code/Cursor browser use, optional hooks, troubleshooting, and unshipped or unverified integrations.
The packaged-install check now reads fresh synthetic native logs over SSE, moves one session between multiple chefs contributing to one dish, verifies native completion at the deliverable table, and observes file changes without changing the watched repo. Run it on macOS as well as Linux in CI.
Validation: