Update documentation for DependsOn usage examples

Author: NikolayPianikov

DIAGNOSTICS.md

@@ -316,7 +316,7 @@ example scenarios. IDs and anchors are stable; message text is localized.
 - Description: DependsOn requires a setup context name when using a setup context kind (except Members).
 - Problem: `DependsOn` was called with a setup context kind but without a context name.
 - Fix: Provide a non-empty `name` value or use `DependsOn(params string[] setupNames)` when a context is not needed. `SetupContextKind.Members` allows omitting `name`.
-- Examples: Unexpected exception during generation.
+- Examples: `DependsOn(setupName, contextKind)` without providing `name` parameter.
 
 ## Warnings
 

Pure.DI.sln

@@ -8,6 +8,7 @@ Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "solution", "solution", "{9B
 		Directory.Build.props = Directory.Build.props
 		build.sh = build.sh
 		build.cmd = build.cmd
+		DIAGNOSTICS.md = DIAGNOSTICS.md
 	EndProjectSection
 EndProject
 Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Pure.DI.IntegrationTests", "tests\Pure.DI.IntegrationTests\Pure.DI.IntegrationTests.csproj", "{9EB0FB9E-487A-48D8-8B2C-03FBA81335B1}"