Another little “gotcha” so far, which rolls into another issue I have duct tape holding together right now:
agents need settings.json ( or equivalent; context configuration ) but not Meteor itself.
However Meteor is what loads Meteor.settings by magic, and cannot be done manually. But obeying that convention would be radical overkill to import just to get a JSON object.
And/then, client and server builds draw upon Meteor.settings from within Meteor would have no problem, while the agents break.
Leads over to probably removing dependence on Meteor.settings and doing a separate configuration JSON, or loading the same settings file, but accessing it without Meteor.settings