improvement(utils): add toArray and the scalar payload coercions

[waleedlatif1]

Summary

• Adds toArray(value) to @sim/utils/object, the array counterpart to toRecord, and replaces the 10 local definitions of Array.isArray(v) ? v : [] (incidentio, smartlead, rocketlane, uptimerobot, emailbison, confluence, jsm, asana, gmail, cbinsights)
• Adds @sim/utils/coerce with toStringOrNull / toNumberOrNull / toBooleanOrNull, replacing 34 byte-identical definitions of typeof v === 'x' ? v : null that carried eleven different names: asString, getString, stringField, nullableString, toNullableString, asStringOrNull, stringOrNull, storedNullableString, getOptionalString, toStringOrNull, asEnum, plus the number and boolean equivalents. The naming sprawl was the real cost here — one concept was unfindable under eleven spellings
• Deletes 7 exported wrappers that were left as pure renames and repoints their importers, rather than leaving indirections that restart the sprawl
• No behavior change: every replaced body was byte-identical to the helper it now calls

Deliberately not done: the ~490 inline Array.isArray(v) ? v : [] expressions. Converting them produced 266 type errors, because Array.isArray narrows the element type while a shared helper can only assert it. The inline form is better wherever the source is already typed, and toArray's TSDoc says so.

Same-named helpers whose bodies differed were left alone on purpose — splunk's asNumber/asBoolean, vanta's and trello's getNumber all carry Number.isFinite or string parsing that toNumberOrNull deliberately does not.

Type of Change

• Refactor / improvement

Testing

• bun run type-check clean in apps/sim, apps/desktop, apps/realtime, packages/{utils,emcn,sim-cli,sim-setup}
• 1,704 tests across the touched areas, 257 utils tests (13 new, pinning that toNumberOrNull passes NaN/Infinity through and that toArray returns the original array on a hit and a fresh one on every miss)
• bun run lint, check:audits (47/47), test:scripts (351), block-registry and docs-manifest:check all pass
• Reviewed independently for codemod damage: every changed file re-parsed, a kind-aware normalized diff against staging (54/55 byte-identical, the one difference a Biome reflow), and per-definition call-site accounting confirming no partial rename

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 20, 2026 2:47am UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; no outstanding correctness, security, or repository-rule issue was identified.

Summary

This PR consolidates repeated untyped-payload normalization into shared @sim/utils helpers.

• Adds and tests toArray, toStringOrNull, toNumberOrNull, and toBooleanOrNull.
• Replaces byte-identical local coercion helpers across connectors, webhook providers, and tools.
• Documents when typed sources should retain inline array narrowing and when stricter local scalar helpers should remain.
• The sole previous finding is no longer outstanding because its thread was resolved after the conflicting array guidance was corrected.

_{Reviews (3) · Last reviewed commit: "docs: document toArray and the scalar pa..."}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

Review completed against the latest diff

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

No issues found across 67 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 67 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}