feat: add code as a shortcut for harness open - #211
Draft
outofcoffee wants to merge 4 commits into
Draft
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.
Add
spinloop code, a one-word top-level shortcut forspinloop harness open.Summary
spinloop codecommand: the same launch asspinloop harness open— the same flags, Spinloop application,--envconfiguration, fleet routing, and trailing-argument forwardingopenCmd()into a sharedopenLaunchCmdbuilder in a newcmd/spinloop/code.go, soharness openandcodeare one implementation and cannot driftdocs/commands/code.md, a command-index entry, cross-links fromharness.mdand the getting-started guide, and a one-line mention in the READMEcode-commandcapability (OpenSpec change), mirroringup-commandImplementation details
codeis a shortcut, not a second command: both spellings are built by the sameopenLaunchCmd(use, short, long), so the flag set, the--spinloop/-Ohandling,--env, fleet routing, and forwarding are shared by construction. The tests pin this two ways — a parity test that feeds identical arguments to both spellings and asserts they reach the harness the same way (and fail the same way), and a root-dispatch test thatcoderoutes to the launch. Shell completion needed no changes: the surface is derived from the command tree, socodeis offered and its first slot completes Spinloops automatically.Closes #203