Repository navigation
fix(integration-v2): let publish_handoff create the report notebook - #423
Merged
Merged
Conversation
New wizards create the notebook inside publish_handoff. Older wizards fall back to the MCP tool the catalog lists. A missing notebook never fails the report task. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a wizard branch:
Add Results will be posted here when complete. |
edwinyjlim
approved these changes
Oct 12, 2026
edwinyjlim
left a comment
Member
There was a problem hiding this comment.
i think we need to apply these changes to the audit programs too
Add the not-updated branch, give the true no-retry reason (the wizard already retried), restore an escaped-quote example, carve the report notebook out of the MCP skill, and say publish_handoff runs once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 12, 2026
gewenyu99
marked this pull request as ready for review
October 12, 2026 18:01
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.
Problem
The integration-v2
reportagent requires a notebook mirror throughnotebooks-create-markdown, which the MCP only lists whenrevamped-py-notebooksis on, so for most orgs the agent marks the required task failed after the report was already delivered.Changes
reportsucceeds oncepublish_handoffgoes through; the notebook is best effort and never fails the task (integration-v2 and metrics).publish_handoff. When the result names no notebook (older wizards), the agent picks the MCP tool the catalog lists:notebooks-create-markdown, ornotebooks-createwith one markdown-notebook node. Same for the legacyintegrationconclude step.[NOTEBOOK_URL]line, since a markdown link is not picked up.Replaces #376, whose branch predates the history rewrite.
Test plan
npm testnpm run buildpublish_handoff, no MCP notebook callreportdoneRelease order
Release #423 first. It is safe alone, because older wizards get no notebook note from
publish_handoffand take the MCP fallback. PostHog/wizard#1437 must not reach users before #423 is served, or orgs with the flag on get two notebooks per run.Sources
vincent/handoff-notebook(linked PR)services/mcp/tests/unit/tool-filtering.test.ts🤖 Generated with Claude Code