Skip to content

feature/Call-site-returns-results · L-260918-4bbf1f — and the skill names each extra - #27

Merged
lchoquel merged 3 commits into
devfrom
feature/Call-site-returns-results
Sep 20, 2026
Merged

lchoquel merged 3 commits into
devfrom
feature/Call-site-returns-results

Conversation

@lchoquel

@lchoquel lchoquel commented Sep 19, 2026

Copy link
Copy Markdown
Member

Step 9 of the pipelex-integrate template now has the generated module return the narrowed output beside the run's whole RunResults — TypeScript a { output, results } type, Python a frozen dataclass of the same two fields — and the skill and its TypeScript reference gain one paragraph per extra those results carry, each pointing at @pipelex/sdk's own documentation rather than writing a helper into the user's project. /pipelex-inputs names mthds_download_artifacts for a completed run whose output references stored files, as an optional tool that is absent on the hosted console. The TypeScript SDK floor rises to 0.18.0, the release carrying that surface, in the prose, the offline drift gate and the test that pins it.

Closes L-260918-4bbf1f

🤖 Generated with Claude Code


Summary by cubic

pipelex-integrate now generates call sites that return the narrowed output beside the run's whole RunResults instead of the output alone: TypeScript gets a { output, results } type and Python gets a frozen dataclass with the same two fields. Refreshing an existing project rewrites its call site to the new shape, migrates the project's callers, and names the breaking change in its report.

  • Step 9 and the TypeScript reference describe each extra results carries and point to @pipelex/sdk's documentation instead of writing helpers into the project; the reference also notes a Server Action should return only the fields the client needs, since RunResults includes run inputs and working_memory.
  • pipelex-inputs now names mthds_download_artifacts for completed runs whose output references stored files; the tool is optional and absent from the hosted console.
  • The @pipelex/sdk floor rises to 0.18.0 in the prose, the offline drift gate, and the test that pins it.

Closes L-260918-4bbf1f

Written for commit 221ec86. Summary will update on new commits.

Review in cubic

lchoquel and others added 3 commits September 19, 2026 21:44
The module /pipelex-integrate writes now hands back the narrowed output beside the run's whole RunResults — a TypeScript type alias, a frozen Python dataclass — so the run id, the usage, the executed graph, the working memory and the references of any produced file stay reachable through .results without the module being edited or the method being run again. Step 9 and the TypeScript reference gain one paragraph per extra, each pointing at the page of the SDK's own documentation that covers it, and no helper is written into the project; the Python reference keeps to what pipelex-sdk carries today. /pipelex-inputs' closing step names mthds_download_artifacts for a completed run whose output references stored files, and its Claude manifest declares the tool. The TypeScript SDK floor rises to 0.18.0, the release carrying that surface, in the prose, the gate script's message and the test that pins it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…esh migrates the call site

The review's six findings were all confirmed. The artifact operations the new
step-9 paragraphs name are methods on the client, not barrel exports, so the
prose that listed them bare would have had an agent write an import that does
not resolve. A refresh gained the return-shape trigger: neither of the two it
had fires on one, so a project integrated before this change would have had its
pin raised to the floor and its call site left returning the output alone.
`mthds_download_artifacts` joins the optional run tools, since it is absent on
the hosted console, where stopping a completed run would be the wrong outcome,
and the step now says whose working directory it writes under.
`graph_assembly_error` is qualified to the blocking path, which is the only one
that carries it. The release-ordering constraint the floor creates is recorded
in the campaign's upstream-dependencies note, which had no trace of it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…stay on the server

A refresh that rewrites the call site to `{ output, results }` changes a
public return type, so it now migrates the project's own callers, runs the
type checker after that edit rather than only before it, and names the
breaking change in its report. The TypeScript reference gains the other half
of the Node-only boundary: `RunResults` carries the run's inputs and every
intermediate in `working_memory`, so a Server Action picks the fields the
client needs instead of returning it whole. The skill's barrel sentence now
names `artifactFilename` beside `collectArtifacts`, matching the reference
and the SDK, and the changelog credits the skill's `allowed-tools`
frontmatter for the download tool rather than the Claude manifest, which
declares the server and no tools.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0144VfCafEHp5MtpXHgzxinj
@lchoquel
lchoquel merged commit 768628f into dev Sep 20, 2026
2 checks passed
@lchoquel
lchoquel deleted the feature/Call-site-returns-results branch September 20, 2026 16:28
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