Recipe in a guide

Overview

A :::recipe written here renders the same runnable step islands a recipe PAGE ships, from the same generator, hydrated by the same console against the same hardened proxy. The reader never leaves the guide they were reading.

Your first call

1. Look at a pet

   Fetch one pet. The response is captured, so the next step can chain off it.

2. Read it back

   This step’s path references step 0’s captured output — the chaining loop. Unresolved tokens stay literal, so a step you have not run yet reads as what it is instead of throwing.

A second walkthrough on the same page

Each walkthrough is its own chaining scope: ${steps.0.…} below means the first step of THIS recipe, not the first step of the page.

Create one

1. Create a pet

   E6_GUIDE_RECIPE_CANARY — a runnable step with a request body.

A stepper that is not runnable

An ordinary stepper is untouched: no island, no console scope, no button that could not work.

Set up a key

1. Create a key

   Run doctorine keys create.

2. Log in

   Run doctorine login.

3. Write about the console

   A step that only MENTIONS the island class — doctorine-recipe-step, as this sentence does — declares no request, so this stepper is still not a console scope. Docs about the console are ordinary prose.