fix(docs): 🐛 Clarify container build usage

docs/.vitepress/config.mts

@@ -136,6 +136,10 @@ export default defineConfig({
       { text: 'Getting Started', link: '/getting-started/introduction' },
       { text: 'Guide', link: '/guides/dependency-injection' },
       { text: 'Reference', link: '/reference/' },
+      {
+        text: 'npm',
+        link: 'https://www.npmjs.com/package/@haskou/ddd-kernel',
+      },
     ],
 
     sidebar: {

docs/reference/dependency-injection.md

@@ -8,7 +8,7 @@ Most applications should configure DI through the kernel:
 const kernel = new Kernel();
 
 await kernel.dependencyInjection({
-  containerBuild: process.env.NODE_ENV === 'production',
+  containerBuild: process.env.NODE_ENV !== 'production',
 });
 ```
 

docs/reference/kernel.md

@@ -50,7 +50,7 @@ Most applications call this once during startup:
 
 ```ts
 await kernel.dependencyInjection({
-  containerBuild: process.env.NODE_ENV === 'production',
+  containerBuild: process.env.NODE_ENV !== 'production',
   overrides: [],
 });
 ```
@@ -62,6 +62,10 @@ await kernel.dependencyInjection({
 | `servicesYamlPath` | Constructor option or `config/container/services.yaml` | Container YAML path for this compile.                                                            |
 | `sourceDirectory`  | Constructor option or `src`                            | Source tree used when generating the container.                                                  |
 
+Use `containerBuild: true` while generating `services.yaml` from the source
+tree. Production runtimes should usually leave it `false` and load the YAML
+shipped with the application artifact.
+
 Prefer constructor injection in application classes. Use overrides at bootstrap
 or test setup to choose infrastructure.