fix(ci): bake the CLI telemetry token into the build that bun publish ships

[waleedlatif1]

Summary

• The published sim@2.1.15 has no reporting destination: bun publish runs prepublishOnly, which rebuilds dist after the "Build package" step, and that second build ran without SIM_CLI_TELEMETRY_* because the variables were scoped to the first step
• Variables now sit at the job level so both builds see them

Type of Change

• Bug fix

Testing

• Verified the shipped 2.1.15 tarball still contains the raw process.env.SIM_CLI_TELEMETRY_KEY reads and reports "no reporting destination"; the publish run log shows the second bun build under bun publish
• Locally, a build with the variable set inlines the token and reports "Usage reporting is on"

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 11, 2026 11:23pm UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge and correctly covers the artifact-producing publish lifecycle.

Summary

• Ensures the prepublishOnly rebuild triggered by bun publish receives the telemetry destination.
• Preserves the existing initial build while covering the artifact-producing publish lifecycle.
• Introduces no dependency, application-code, or security-boundary changes.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Job[Publishing job environment] --> Initial[Initial bun run build]
  Job --> Publish[bun publish]
  Publish --> Lifecycle[prepublishOnly]
  Lifecycle --> Rebuild[bun run build]
  Rebuild --> Artifact[Published CLI with telemetry destination]

Loading

_{Reviews (1) · Last reviewed commit: "fix(ci): bake the CLI telemetry token in..."}