Document completed LLM and reference expansion

docs/troubleshooting.md

@@ -107,10 +107,10 @@ go run ./cmd/notarius run dnd-session \
 Symptoms include:
 
 - `reference slot "..." is not declared`
-- `reference slot "..." is declared by multiple selected lanes`
+- `reference slot "..." is declared by multiple selected targets`
 - `required reference slot "..." is not bound`
-- `--reference must use slot=path or lane.slot=path`
-- `--without-reference must use slot or lane.slot`
+- `--reference must use slot=path`
+- `--without-reference must use a reference selector without =path`
 - `read "...": no such file`
 - `must be UTF-8 text`
 - `media type "..." is not accepted`
@@ -118,17 +118,24 @@ Symptoms include:
 
 Fix:
 
-- Confirm the selected extractor declares the slot. The implemented
-  `dnd/spells` extractor declares optional `roster` and `glossary` slots.
-- Use `lane.slot=path` when more than one selected lane declares the same slot.
-- Use `--without-reference slot` to remove optional config bindings; do not pass
-  an empty `--reference slot=`.
+- Confirm the selected chunker, extractor, or normalizer declares the slot. The
+  implemented `dnd/spells` extractor declares optional `roster` and `glossary`
+  slots.
+- Use a specific selector when more than one selected target declares the same
+  slot. Examples include `chunk.context=./context.txt`,
+  `spells.extract.context=./extract-context.txt`, and
+  `spells.normalize.context=./normalize-context.txt`.
+- `lane.slot=path` is valid only when exactly one selected extractor or
+  normalizer in that lane declares the slot. If both do, use
+  `lane.extract.slot=path` or `lane.normalize.slot=path`.
+- Use `--without-reference selector` to remove optional config bindings; do not
+  pass an empty `--reference selector=`.
 - Check whether a path came from config or CLI. Config paths are relative to
   the config file. CLI reference paths are relative to the current working
   directory.
 - Ensure the file is readable UTF-8 text and within any byte limit declared by
-  the extractor.
-- If the extractor narrows accepted media types, use a file extension that
+  the declaring module.
+- If the declaring module narrows accepted media types, use a file extension that
   infers an accepted type such as `text/markdown` or `application/json`.
   Unknown extensions infer `application/octet-stream`.
 - If diagnostics are retained, inspect `resolved-pipeline.json`,