fix: pure JSON schema output, byte-safe takeouts, context-aware 404 hints#88
Merged
Conversation
…ints - schema get -o json no longer prints the markdown heading, so output pipes straight to jq (#72) - takeouts download writes bytes via os.Stdout.Write, matching the other download commands; takeout files may be binary (#55) - 404/409 hints now know which command failed (rootCmd.ExecuteC): a 404 from `list` produces no hint instead of "use the list subcommand", and other commands get the real path, e.g. "Use `syllable tools list`". Name-keyed commands steer users to the NAME/EMAIL column instead of blaming an ID (#73, hint half of #69) - conversation-config help and AGENTS.md now say "bridge phrases" and cross-reference the Console's Voices → Phrases page; the old text mischaracterized bridges as transfer/handoff phrases (#82) Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
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.
Three small UX/correctness fixes from the v1.5.1 QA batch, plus a discoverability fix.
What changed
schema get -o jsonis now pure JSON — the markdown# Headingis suppressed under--output json, sosyllable schema get AgentCreate -o json | jq .works. Table output keeps the heading. Closes schema get <name> -o json ignores the output flag (markdown heading prefix) #72.takeouts downloadwrites bytes —fmt.Print(string(data))→os.Stdout.Write(data), matchingdirectory downloadandpronunciations get-csv(the other two commands named in the issue were already fixed). Takeout files may be binary. Closes Switch existing CSV/binary download commands to os.Stdout.Write #55.Execute()now uses Cobra'sExecuteC()to learn which command failed:listcommand produces no hint (the API's own detail, e.g. "No pronunciation dictionary found for this organization", says it all — no more wild goose chase);Use `syllable tools list` to find valid IDs;get <tool-name>,update <user-email>) steer users to the NAME/EMAIL column instead of blaming an ID — the hint half of tools get: help example uses numeric ID but command requires a name #69 (the accept-IDs half lands separately).Closes 404 hint 'Use the list subcommand to find valid IDs' fires even when the user is calling list #73.
conversation-confighelp and AGENTS.md now say "bridge phrases" and cross-reference the Console's Voices → Phrases page. The old AGENTS.md text mischaracterized bridges as transfer/handoff phrases, which is likely why Doesn't support bridge phrases #82 was filed against a feature the CLI already has.Tests
TestSchemaGetJSONOutputPure— json output parses; table keeps headingTestTakeoutsDownloadBytes— byte-exact round-trip of invalid-UTF-8 payloadTestHint404ContextAware/TestHintForErrorThreadsCommand— list-no-hint, name-keyed, id-keyed, nil-command casesgo test ./...green locally; smoke-testedschema get | jqand help output.🤖 Generated with Claude Code