fix(frontend): render version_check workflow entries with icon and summary

[abcxff]

No description provided.

[abcxff]

Stack for rivet-dev/rivet

• #5368 fix(frontend): render version_check workflow entries with ic … 👈
• #5369 feat(workflow-engine): add getVersion primitive for workflow …
• main

Get stack: forklift get 5368
Push local edits: forklift submit
Merge when ready: forklift merge 5368

_{change oprtsksx}

[claude]

Review

Small, focused fix that fills in the gap left by transform-workflow-history.ts already emitting "version_check" entries (via WorkflowVersionCheckEntry) with no corresponding icon/summary rendering. Before this change those nodes silently fell through to the generic checkmark icon and an empty summary. The three edits (icon, summary, story) are consistent with the existing pattern for every other entry kind in these files.

Minor: stale duplicate type in workflow-visualizer.tsx

workflow-visualizer.tsx declares its own local MetaExtendedEntryType (around lines 37-47) instead of importing the one from xyflow-nodes.tsx, and it was not updated to include "version_check" in this PR:

type MetaExtendedEntryType =
	| "step"
	| "loop"
	| "sleep"
	| "message"
	| "rollback_checkpoint"
	| "join"
	| "race"
	| "try"
	| "removed"
	| "input"
	| "output";

This is used to cast selectedNode.entryType before indexing TYPE_COLORS and calling TypeIcon (both of which do handle version_check correctly now, since they use the real, imported type). Because the local union is a subset of the imported one, TS structurally allows the cast without complaint, so nothing breaks at runtime. But the type is now misleading/incomplete, and this kind of duplication is exactly what caused this PR to be needed in the first place: a variant added in one place, forgotten in another. Worth either adding "version_check" here too or importing MetaExtendedEntryType from xyflow-nodes.tsx instead of re-declaring it locally.

Nit: latest field unused in the summary

VersionCheckEntry carries both resolved and latest, but the summary only surfaces resolved (v${resolved}). If resolved !== latest is a meaningful state, such as an actor running an outdated version, it might be worth surfacing that in the summary or icon color rather than only in the raw-data inspector. Not a blocker, just a possible follow-up.

Everything else looks good

• faTag is already used elsewhere in the codebase, so the new icon import is valid and consistent.
• The new Ladle story follows the exact pattern of the sibling per-node-type stories already in this file.
• No test coverage concerns beyond the story, since this is pure presentational mapping logic with no branching worth unit testing.

No security or performance concerns. This is presentation-only code operating on already-validated data.