fix: support request-scoped rollout logging config

[xzrderek]

Summary

• Add request-scoped gatewayBaseUrl and apiKey support to the TypeScript Fireworks logging transport.
• Extend createRolloutLogger to accept an options object while preserving the existing string-name call shape.
• Keep API keys inside the transport instance rather than attaching them to log metadata.

Test plan

• npx tsc --noEmit from typescript/

Made with Cursor

---

Note

^{Cursor Bugbot is generating a summary for commit c4aa43a. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c4aa43a. Configure here.}

[cursor]

Duplicated logger configuration will drift over time

Low Severity

The logger configuration inside createRolloutLogger (level, format, console transport) is a near-exact copy of the module-level logger configuration. If either copy is updated in the future (e.g., log level, format options, additional transports), the other will silently remain stale. Extracting shared config (format, level, console transport factory) into a reusable constant or helper would eliminate this risk.

Additional Locations (1)

• typescript/logging/logger.ts#L21-L40

 

^{Reviewed by Cursor Bugbot for commit c4aa43a. Configure here.}