The reusable Operations workflow's logs operation hardcodes the ai-dev-env-{environment} namespace, so operators cannot inspect application pods in other managed namespaces during incidents. Reuse the existing resource_namespace input for logs, validate it with the same Kubernetes namespace allowlist, and preserve the derived default when omitted.
Acceptance: logs can target a validated namespace such as creativetoolkits-dev; arbitrary shell input remains rejected; workflow formatting and CI pass; a live dispatch reads the Creativetoolkits API logs without an issue-specific workflow.
The reusable Operations workflow's logs operation hardcodes the ai-dev-env-{environment} namespace, so operators cannot inspect application pods in other managed namespaces during incidents. Reuse the existing resource_namespace input for logs, validate it with the same Kubernetes namespace allowlist, and preserve the derived default when omitted.
Acceptance: logs can target a validated namespace such as creativetoolkits-dev; arbitrary shell input remains rejected; workflow formatting and CI pass; a live dispatch reads the Creativetoolkits API logs without an issue-specific workflow.