diff --git a/Repo-docs-RELEASE-DEPENDENCIES.-.md b/Repo-docs-RELEASE-DEPENDENCIES.-.md
index b3ba1d8..f969fb7 100644
--- a/Repo-docs-RELEASE-DEPENDENCIES.-.md
+++ b/Repo-docs-RELEASE-DEPENDENCIES.-.md
@@ -1,4 +1,4 @@
-<!-- codex-wiki-sync:4acb7e5950e69d802998a3db -->
+<!-- codex-wiki-sync:139ec2a4b3b9d5c798d4508c -->
 
 > Mirrored from `/mnt/DATA/git/govoplan-core/docs/RELEASE_DEPENDENCIES.md`.
 > Origin: `repository`.
@@ -46,6 +46,27 @@ govoplan-campaign git@git.add-ideas.de:add-ideas/govoplan-campaign.git v0.1.4
 govoplan-calendar git@git.add-ideas.de:add-ideas/govoplan-calendar.git v0.1.4
 ```
 
+## Runtime Module Package Changes
+
+The admin module manager can hot-enable and hot-disable packages that are
+already installed. It does not install or uninstall Python/npm packages from
+inside the running server.
+
+For runtime package changes, create an operator install plan in Admin > System >
+Modules. The plan can also be rendered from the server shell:
+
+```bash
+govoplan-module-install-plan --format shell
+# or
+python -m govoplan_core.commands.module_install_plan --format shell
+```
+
+Apply those commands from a controlled operator shell while maintenance mode is
+active. Install rows must use tagged package/git refs or registry packages, not
+local `file:` or workspace links. After package changes, run migrations and
+restart or reload the affected server/WebUI processes according to the
+deployment model.
+
 ## WebUI
 
 Local development uses `webui/package.json`, which may point at sibling module checkouts while active development is happening.