nutrition docker file fix

Dockerfile

@@ -44,6 +44,23 @@ COPY nearle-gear-firebase-adminsdk-l9oha-23ca3b3609.json .
 # thing the assistant needs to come up.
 ENV ASSISTANT_API_KEY=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
 
+# Where the nutrition panel and health score come from.
+#
+# A PUBLIC URL, not a secret — it is the catalogue-intelligence service the
+# console already reads its health score card from, and the same value is in
+# .env.example. So it is a build-time default rather than a platform setting,
+# for the same reason ASSISTANT_API_KEY is: one variable, set in one place,
+# that cannot be missed on a deploy.
+#
+# It has been missed twice. Unset, `getproductbyvariant` simply omits
+# `nutrition` and `healthscore`, which is indistinguishable from a product the
+# service has not scored — so the feature ships switched off and looks broken
+# rather than absent. The startup log now names which state it is in.
+#
+# A value set on the platform still wins: `docker run -e` overrides a Dockerfile
+# ENV, so this is a default and not a lock-in.
+ENV NUTRITION_BASE=https://mcp.nearle.ai.in/api
+
 # No `.env.*` is copied in (see .dockerignore), so this only decides which rules
 # config.Load applies: production insists on a signing secret and never falls
 # back to localhost values. Every other real value comes from the platform's