chore: clean up packages temporal namespace env comment

Signed-off-by: anilb <epipav@gmail.com>

Author: epipav

backend/.env.dist.composed

@@ -26,7 +26,7 @@ CROWD_OPENSEARCH_NODE=http://open-search:9200
 # Temporal
 CROWD_TEMPORAL_SERVER_URL=temporal:7233
 
-# Temporal — packages namespace (separate cluster/namespace from the main one)
+# Temporal — packages namespace
 CROWD_PACKAGES_TEMPORAL_NAMESPACE=
 
 # Seach sync api

backend/.env.dist.local

@@ -150,7 +150,7 @@ CROWD_TEMPORAL_NAMESPACE=default
 CROWD_TEMPORAL_ENCRYPTION_KEY_ID=local
 CROWD_TEMPORAL_ENCRYPTION_KEY=FweBMRnGCLshER8FlSvNusQA6G3MRUKt
 
-# Temporal — packages namespace (separate cluster/namespace from the main one)
+# Temporal — packages namespace
 CROWD_PACKAGES_TEMPORAL_NAMESPACE=default
 
 # Seach sync api

docs/adr/README.md

@@ -10,7 +10,6 @@ Use the `/adr` skill in Claude Code to record new ADRs or query past decisions.
 | --- | ----- | ------ | ---- |
 | [ADR-0001](./0001-packages-database.md) | Separate physical database for the packages domain | accepted | 2026-05-26 |
 | [ADR-0002](./0002-packages-worker-architecture.md) | Single-service, multi-entry-point architecture for packages_worker | accepted | 2026-05-25 |
-| [ADR-0003](./0003-packages-worker-temporal-parent.md) | Temporal ServiceWorker as the host for packages_worker scheduled workflows | accepted | 2026-05-26 |
 
 ## Why ADRs?