fix(skills): give the notebook mirror a fallback when the markdown tool is absent

context/skills/integration-v2/notebook/description.md

@@ -7,10 +7,16 @@ the report reaches the user.
 
 Use the exact report markdown you composed — the same content you pass to
 `publish_handoff`, verbatim, not a summary of it. Create the notebook in a
-single `notebooks-create-markdown` call through `posthog_exec` — that exact
-tool name, no tool search — passing a `title` and the report as `markdown`.
-The title becomes the notebook's leading `# heading`, so start the `markdown`
-at the first section below it rather than repeating the title as an H1.
+single `notebooks-create-markdown` call through `posthog_exec`, passing a
+`title` and the report as `markdown`. The title becomes the notebook's leading
+`# heading`, so start the `markdown` at the first section below it rather than
+repeating the title as an H1.
+
+Some deployments expose `notebooks-create` (rich-text `content`) instead of
+`notebooks-create-markdown`. If the create call comes back `Unknown tool`, use
+`notebooks-create` and pass the same report as one markdown code block in
+`content` — don't translate it to ProseMirror, and don't spend turns searching
+for another tool. Everything below applies to whichever one you land on.
 
 The exec command is `call notebooks-create-markdown` followed by the bare JSON
 argument — no quotes around it, and the whole argument on one line with the

context/skills/integration/references/4-conclude.md

@@ -114,7 +114,7 @@ Do not invent items beyond what applies. If only the two "Always" items apply, t
 
 Then publish the report to the wizard session with a single `publish_handoff` call, passing the complete report markdown as `content`. This call is how the report reaches the user — do not write it to a file instead.
 
-Then mirror the report into a shareable PostHog notebook so the user has an in-app copy to link and comment on. Call `notebooks-create-markdown` with a `title` (e.g. `PostHog setup (wizard) – <repo_name>`) and the report verbatim as `markdown` — the title becomes the notebook's leading heading, so start the markdown at the first section below it. Take the `short_id` from the response, build the notebook URL as `<host>/project/<project_id>/notebooks/<short_id>`, and emit it on its own line so the wizard can surface it: `[NOTEBOOK_URL]` followed by that URL.
+Then mirror the report into a shareable PostHog notebook so the user has an in-app copy to link and comment on. Call `notebooks-create-markdown` with a `title` (e.g. `PostHog setup (wizard) – <repo_name>`) and the report verbatim as `markdown` — the title becomes the notebook's leading heading, so start the markdown at the first section below it. If that call comes back `Unknown tool`, the deployment exposes `notebooks-create` (rich-text `content`) instead — pass the same report as one markdown code block in `content` rather than searching for another tool. Take the `short_id` from the response, build the notebook URL as `<host>/project/<project_id>/notebooks/<short_id>`, and emit it on its own line so the wizard can surface it: `[NOTEBOOK_URL]` followed by that URL.
 
 Upon completion, update `.posthog-events.json` so it matches the events you actually implemented, then remove it with your file tools. If removal is blocked or fails in your environment, leave the file in place and move on — the wizard host cleans it up after the run. Do not retry the removal or reach for shell commands to force it.