publishBedrockOutputs

Called by the mix pipeline immediately after BedrockConversion.generate() produces fresh output. Because Java hosting now starts BEFORE Bedrock conversion (so Java clients don't wait on it), initialize — and with it the recurring relay task's first tick — runs while the Bedrock files don't exist yet. Without this explicit push, the relay would skip and not retry for ~25 min, delaying the proxy's view of this backend's Bedrock content. No-op in standalone mode (no network key) and harmless if the relay task isn't running.