Sync Repo-docs-GOVOPLAN-MODULE-ROADMAP from project files

Repo-docs-GOVOPLAN-MODULE-ROADMAP.-.md

@@ -1,4 +1,4 @@
-<!-- codex-wiki-sync:020dc3ac356481be6057a6dd -->
+<!-- codex-wiki-sync:71874b81589b85397915353e -->
 
 > Mirrored from `/mnt/DATA/git/govoplan-core/docs/GOVOPLAN_MODULE_ROADMAP.md`.
 > Origin: `repository`.
@@ -66,7 +66,7 @@ This page maps current module and integration ideas to existing GovOPlaN reposit
 
 ## Release Tooling Note
 
-`scripts/push-release-tag.sh` currently covers the released full-product set only:
+`scripts/push-release-tag.sh` covers the released full-product package set:
 
 - `govoplan-access`
 - `govoplan-admin`
@@ -78,4 +78,6 @@ This page maps current module and integration ideas to existing GovOPlaN reposit
 - `govoplan-campaign`
 - `govoplan-core`
 
-It does not currently include the wider module backlog repositories such as addresses, appointments, calendar, connectors, DMS, forms, IDM, reporting, templates, workflow, XOE/V, XRechnung, or proposed datasources/dataflow/projects modules. Extend the release script deliberately before treating those modules as part of the tagged product release train.
+It also includes existing roadmap/scaffold module repositories such as addresses, appointments, calendar, connectors, DMS, forms, IDM, reporting, templates, workflow, XOE/V, and XRechnung as tag-only repositories. Tag-only repositories are committed, tagged, and pushed with the same release tag, but they are not added to `requirements-release.txt` or `webui/package.release.json` until they contain installable package metadata.
+
+Proposed modules without repositories, such as `govoplan-datasources`, `govoplan-dataflow`, and possibly `govoplan-projects`, cannot be included until their repositories are created.