Skip to content

Surface fork, save, and run guidance to CLI-driven agents#54

Merged
rhiever merged 2 commits into
mainfrom
randy/authoring-on-ramp-parity
Jul 2, 2026
Merged

Surface fork, save, and run guidance to CLI-driven agents#54
rhiever merged 2 commits into
mainfrom
randy/authoring-on-ramp-parity

Conversation

@rhiever

@rhiever rhiever commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

What

The server now returns two additive next-step guidance strings (on template fork and on workflow save) and strengthened run guidance on template and workflow fetches. The CLI re-parses server responses through strict wire models that drop undeclared fields, so these were silently lost for CLI-driven agents. This declares and renders them.

Changes

  • Wire models: add optional next_step to the fork and save result models, and run_guidance to the template and workflow detail models. All optional with defaults, so responses from older servers still parse.
  • Rendering: the fork and save commands print next_step to stderr when present (keeping machine-readable stdout clean), and nothing when absent, mirroring how advisory authoring notes render.
  • Run guidance already reaches agents in-band on the default markdown fetch; it is now also carried on the --json fetch path via the new detail-model field.

Testing

pre-commit (lint, format, type check) and the full test suite green (841 passed). New tests assert next_step renders present-only for both commands and that run guidance surfaces in both the markdown and --json fetch paths.

Note

No version bump here; this pairs with the server REST additions and ships on the next coordinated release.

🤖 Generated with Claude Code

rhiever added 2 commits July 1, 2026 15:03
The server now returns a next_step string on template fork (always) and
workflow save (only for a hand-edited authored fork with checks), but the
CLI's strict wire models silently dropped unknown fields. Add next_step to
TemplateForkResult and WorkflowSaveResult and print it to stderr when
present, mirroring how authoring_notes and deprecation_warning already
render as advisory, non-blocking output.
The default markdown fetch path for templates get and workflows get
already streamed the server's run_guidance in-band, so add a test
confirming that. The --json fetch path is a separate story: it parses
through TemplateDetail and WorkflowDetail, which lacked run_guidance, so
the strengthened field was silently dropped. Add the field to both
models and a test asserting it now appears in --json output.
@rhiever rhiever merged commit 336f450 into main Jul 2, 2026
1 check passed
@rhiever rhiever deleted the randy/authoring-on-ramp-parity branch July 2, 2026 02:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant