Harden container entrypoint for one-click deployments

[MontrealAI]

Summary

• expand the Docker entrypoint so config files are loaded, identity inputs validated, and runtime toggles mapped into the container command while still supporting other CLI operations
• add documentation for one-click docker usage, ship a sample node.env template, and expose service ports from the container image
• surface monitor cadence controls through Helm values and propagate the new environment variables into the deployment manifest

Testing

• npm test

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restore export of variables loaded via CONFIG_PATH

The new load_config_file function sources the file but no longer wraps it in set -a/set +a. Variables defined in a node.env file are therefore not exported to the child node process when the file is loaded via CONFIG_PATH. This regresses the documented one-click docker run flow where the env file holds values like RPC_URL, NODE_LABEL, contract addresses, etc.—they are visible to the shell for validation but disappear from process.env, causing the runtime to fall back to defaults or fail schema validation. The previous version exported these values, so configuration files now silently stop working. Reintroduce automatic exporting (or explicitly export required variables) before invoking the Node CLI.

Useful? React with 👍 / 👎.