Document direct Notebook page export

README.md

@@ -214,9 +214,23 @@ That flow:
 - makes the resulting pack consumable by the learner workbench with
   GroundRecall review and graph context intact
 
+If you want just the Notebook page artifact without building a full pack, use
+the direct export wrapper:
+
+```bash
+didactopus notebook-page-groundrecall \
+  /path/to/groundrecall-store \
+  channel-capacity \
+  /tmp/notebook-page-export
+```
+
+That command writes both `groundrecall_query_bundle.json` and
+`notebook_page.json` into the output directory.
+
 The fuller bridge workflow is documented in:
 
 - `docs/groundrecall-bridge.md`
+- `docs/evo-edu-notebook-pipeline.md`
 
 ## Didactopus As Pedagogy Support
 

docs/evo-edu-notebook-pipeline.md

@@ -180,6 +180,17 @@ For important notebook concepts, export:
 
 - `groundrecall_query_bundle.json`
 
+If you only need the page-ready artifact for a concept, `Didactopus` now also
+has a direct wrapper that writes both the query bundle and `notebook_page.json`
+into one output directory:
+
+```bash
+didactopus notebook-page-groundrecall \
+  /path/to/groundrecall-store \
+  natural-selection \
+  /tmp/notebook-page-export
+```
+
 This becomes the handoff object for learner-facing or page-facing pack flows.
 
 Expected result:

docs/groundrecall-bridge.md

@@ -96,3 +96,12 @@ Run the plain `doclift` bundle conversion without GroundRecall:
 ```bash
 didactopus doclift-bundle /tmp/doclift-bundle /tmp/didactopus-pack --course-title "Example Course"
 ```
+
+Build just the Notebook page artifact from a GroundRecall concept:
+
+```bash
+didactopus notebook-page-groundrecall \
+  /path/to/groundrecall-store \
+  channel-capacity \
+  /tmp/notebook-page-export
+```