A configuration or secret change now restarts the portal

Changing a portal setting or secret and running helm upgrade (or memex-local up) now rolls the portal pods, one at a time and gracefully, so the setting you changed is the one the portal runs with. Before, the release reported "deployed" and the rendered ConfigMap and Secret carried the new value, but the running pods — which read configuration only at start — kept the old one until something else happened to restart them. That is how an open-registration key delivered to memex.meshweaver.cloud still answered 401 for an hour after the deploy. An upgrade that changes nothing still restarts nothing.