Add development pipeline inheritance example

docs/config.md

@@ -40,6 +40,14 @@ have no effect; `NOTARIUS_CONFIG` remains a source-discovery input.
   [LLM profile](../examples/llm-profiles/dnd-extraction.yml) and imports its
   pipeline from [a fragment](../examples/pipelines/dnd-session.yml).
 
+The complete fragment also defines `dnd-session-development`, which inherits
+the complete pipeline and profile while setting
+`structured_output_repair_attempts: 0`. Select it with
+`notarius run dnd-session-development --config /path/to/dnd-complete.config.yml`;
+it disables PromptKit structural repairs without changing configured producer
+retry budgets. When using another profile, operators can instead select
+`dnd-session` and set its `llm_profile` to that profile.
+
 Use these complete files as starting points rather than combining the
 illustrative fragments in this reference.
 

docs/roadmap/implementation.md

@@ -392,6 +392,8 @@ Prompt size: command-boundary behavior and representative error propagation.
 
 ## Stage 7 — Publish And Test The Development Pipeline Example
 
+> Completion: complete.
+
 Goal: give operators one complete, runnable demonstration without duplicating
 the full pipeline.