Add composed development configuration example

docs/config.md

@@ -36,7 +36,8 @@ have no effect; `NOTARIUS_CONFIG` remains a source-discovery input.
 - [Complete D&D configuration](../examples/dnd-complete.config.yml) uses
   ordered steps, all implemented D&D lanes, generated references, state
   settings, bounded LLM concurrency, and the maintained
-  [operator profile](../examples/profiles/dnd-extraction.yml).
+  [LLM profile](../examples/llm-profiles/dnd-extraction.yml) and imports its
+  pipeline from [a fragment](../examples/pipelines/dnd-session.yml).
 
 Use these complete files as starting points rather than combining the
 illustrative fragments in this reference.
@@ -116,7 +117,7 @@ promptkit:
 Set at most one of **profile_dir** and **profile_file**. Every nonempty relative
 configured filesystem path is resolved from the canonical directory of the
 file that supplies it. The complete example's
-`./profiles/dnd-extraction.yml` value therefore resolves beside that example.
+`./llm-profiles/dnd-extraction.yml` value therefore resolves beside that example.
 Use absolute paths for services and containers when their deployment layout is
 not configuration-relative.
 
@@ -124,7 +125,7 @@ An operator source is optional. For a requested ID, PromptKit checks the
 configured operator source first, then Notarius's embedded fallback profiles,
 then its own built-in catalog. A matching profile is complete: it replaces a
 lower-precedence definition rather than merging with it. The maintained
-[`dnd-extraction` operator profile](../examples/profiles/dnd-extraction.yml)
+[`dnd-extraction` LLM profile](../examples/llm-profiles/dnd-extraction.yml)
 is a secret-free deployment artifact; production, development, and local
 deployments can each provide a complete definition with that same workload ID.
 Use workload-oriented IDs for new profiles instead of model names.

docs/operations.md

@@ -115,7 +115,7 @@ precedence rules are owned by [Configuration](config.md#promptkit-profiles).
 Use a profile source owned by the service account, keep it readable only by
 the intended operator, and supply provider credentials through the service
 environment—not in the Notarius configuration or profile YAML. The maintained
-[operator profile](../examples/profiles/dnd-extraction.yml) is secret-free and
+[LLM profile](../examples/llm-profiles/dnd-extraction.yml) is secret-free and
 can be copied as a format starting point. Validate a deployment without a
 provider call or credentials:
 
@@ -128,7 +128,7 @@ may receive a 401 or 403 response.
 
 Configured PromptKit profile paths resolve from the file that supplies their
 surviving declaration. The complete example's
-`./profiles/dnd-extraction.yml` path is therefore relative to that example.
+`./llm-profiles/dnd-extraction.yml` path is therefore relative to that example.
 Use absolute paths such as `/etc/notarius/profiles/dnd-extraction.yml` for
 services and containers when that is clearer for the deployment.
 

docs/roadmap/implementation.md

@@ -607,6 +607,8 @@ have moved.
 
 ## Stage 13 — Demonstrate Imports And Development Profiles
 
+**Status:** Completed 2026-09-13.
+
 **Goal:** Supply two maintained operator examples covering simple and composed
 configuration, with a clear distinction between the two profile systems.