docs: rescan rebased documentation hierarchy

docs/user/develop/basic/config.md

@@ -31,13 +31,15 @@ export function apply(ctx: Context, config: Config) {
 }
 ```
 
-Configure it in `cordis.yml`:
+Add the configuration to the inserted local plugin row in `scratch-plugin/cordis.yml`:
 
 ```yaml
-- name: './src/my-plugin.ts'
-  config:
-    greeting: 'Hi there'
-    maxRetries: 5
+- insert:
+    - id: hello
+      name: './src/my-plugin.ts'
+      config:
+        greeting: 'Hi there'
+        maxRetries: 5
 ```
 
 When loading the plugin, Cordis uses the exported schema to validate configuration and fill defaults. Do not export a plain object as `Config`; it does not implement the Standard Schema interface required by Cordis.
@@ -91,22 +93,7 @@ The test is whether `cordis.yml` can change the value without a code edit.
 
 ### Fail loudly on invalid configuration
 
-If configuration refers to an unregistered LLM provider route or another nonexistent resource, fail early instead of silently skipping it:
-
-```ts
-import type { Context } from 'cordis'
-import type {} from '@deepseek-ai/dsh-llm'
-
-export interface ModelConfig {
-  provider: string
-}
-
-export function apply(ctx: Context, config: ModelConfig) {
-  if (!ctx.llm.listProviders().some(provider => provider.id === config.provider)) {
-    throw new Error(`LLM provider "${config.provider}" is not registered`)
-  }
-}
-```
+Express self-contained constraints in the schema so invalid configuration fails while the plugin loads. References to services or registered resources require dependency injection; the [services tutorial](../framework/service.md) introduces that contract.
 
 ## Work with HMR