Clarify config field omission in external plugin docs

Copilot · camilamacedo86 · Copilot · commit 7871066b0f28 · 2025-10-30T21:36:53.000Z
Co-authored-by: camilamacedo86 &lt;7708031+camilamacedo86@users.noreply.github.com&gt;
diff --git a/docs/book/src/plugins/extending/external-plugins.md b/docs/book/src/plugins/extending/external-plugins.md
@@ -61,7 +61,7 @@ structures.
 }
 ```
 
-The `config` field provides external plugins access to the PROJECT file configuration, enabling them to make informed decisions based on the project's settings. This field may be empty during the `init` command if the PROJECT file has not been created yet.
+The `config` field provides external plugins access to the PROJECT file configuration, enabling them to make informed decisions based on the project's settings. This field will be omitted from the JSON entirely (not present) during the `init` command if the PROJECT file has not been created yet. External plugins should check for the presence of this field before attempting to use it.
 
 ### PluginResponse
 

Original file line number	Diff line number	Diff line change
`@@ -61,7 +61,7 @@ structures.`
`61`	`61`	`}`
`62`	`62`	```
`63`	`63`
`64`		-The `config` field provides external plugins access to the PROJECT file configuration, enabling them to make informed decisions based on the project's settings. This field may be empty during the `init` command if the PROJECT file has not been created yet.
	`64`	+The `config` field provides external plugins access to the PROJECT file configuration, enabling them to make informed decisions based on the project's settings. This field will be omitted from the JSON entirely (not present) during the `init` command if the PROJECT file has not been created yet. External plugins should check for the presence of this field before attempting to use it.
`65`	`65`
`66`	`66`	`### PluginResponse`
`67`	`67`