fix(skills): notebook JSON escaping + report overwrite guidance (terra telemetry)#241
Closed
gewenyu99 wants to merge 1 commit into
Closed
fix(skills): notebook JSON escaping + report overwrite guidance (terra telemetry)#241gewenyu99 wants to merge 1 commit into
gewenyu99 wants to merge 1 commit into
Conversation
…telemetry Wizard remark telemetry from the gpt-5.6-terra rollout (2026-07-15) shows two recurring frictions in the report/notebook step, ~10 mentions in the first hour, all recovered but each burning retries: - notebooks-create payloads failing to parse because the report markdown was pasted into the JSON literal unescaped. The notebook skill now spells out the escaping contract (newlines, quotes, backslashes → one single-line string), says to Read the finished report first, names the exact tool so no tool search is needed, and forbids trimming the report to dodge a parse failure. - the report task erroring on re-runs because harnesses refuse to overwrite a file that wasn't read. The report skill now distinguishes the fresh-write case from the replace-a-leftover case. Generated-By: PostHog Code Task-Id: 843d9848-d7ad-4bab-96d2-a78e0411251f
🧙 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
Results will be posted here when complete. |
Collaborator
Author
|
Superseded: notebook JSON-escaping reshaped as the integration-v2 notebook microskill, and dashboard split into dashboard+insight microskills (experiment/orchestrator). Closing this prompt-patch shape. |
gewenyu99
added a commit
that referenced
this pull request
Jul 15, 2026
Read-then-replace when posthog-setup-report.md already exists (harnesses refuse to overwrite an unread file) — the salvaged half of the closed #241. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
What
Two prompt fixes in the
integration-v2report step, driven by wizard remark telemetry from the gpt-5.6-terra rollout (2026-07-15, ~10 remarks in the first hour of external traffic):skills/integration-v2/notebook— agents repeatedly failednotebooks-createcalls by pasting raw multi-line report markdown into the JSON payload ("repeated notebooks-create JSON parsing failures"). The skill now:Readthe finishedposthog-setup-report.mdfirst (and not before the report step wrote it)notebooks-createviaposthog_exec) so no tool-search round-trip is needed — one run wasted a lookup on a scope-gated alias surfaced first\n/\"/\\, one single-line string, and fix-the-escaping-don't-trim-the-report on rejectionskills/integration-v2/report— remarks disagreed about read-before-write because the correct behavior differs: fresh runs must write directly (a read errors on the missing file), re-runs mustReadfirst (harnesses refuse to overwrite an unread file). The skill now states both cases.Why now
All terra runs still succeeded — these loops cost retries, tokens, and ~seconds of wall-clock per run, not outcomes. But they're the top remark cluster by far (notebook escaping alone is 10+ mentions) and the fix is decoupled from the wizard release cycle.
Notes
npm testpasses (121/121).npm run buildis broken on theexperiment/orchestratortip before this change:agents/integration-v2/build.md(and possibly siblings) still declareflow: "posthog-integration"after the rename in 23276d8. Not addressed here to avoid colliding with in-flight rename work — flagging for whoever owns it.Created with PostHog Code