feat(dev): preserve active Workflow generations

[ctgowrie]

Why

A local Workflow turn can outlive a successful dev rebuild. Its retries and queued deliveries must keep using the tool, instrumentation, and compiled-artifact generation selected when that turn started, including after the parent dev process restarts.

What changed

• Moves the local Workflow World into the parent dev server and routes deliveries through the generation-aware worker transport.
• Resolves new turns to the latest promoted generation, then pins each run to that generation for retries and continuation.
• Retains referenced workers and runtime artifacts, restores nonterminal generations after restart, and prunes them once no active run or request owns them.
• Preserves cancellation, client-disconnect, lease-release, and shutdown ordering across HTTP, WebSocket, and Workflow delivery paths.

This is Stage 5, stacked on #766.

Validation

• Full unit suite: 4,699 passed, 1 skipped
• Full integration suite: 448 passed
• Full scenario suite: 318 passed, 15 skipped
• Focused dev-server lifecycle scenarios: 8 passed
• Build, formatting, lint, workspace typecheck, and invariant guard passed
• Real linked notes app boot, health/runtime-artifact probes, typecheck, and clean shutdown passed

The existing vendored gray-matter direct-eval warning remains unchanged and is outside this stage.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
eve-docs	Ready	Preview, Comment, Open in v0	Jul 14, 2026 12:27pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
eve-docs-1644	Skipped	Open in v0	Jul 14, 2026 12:27pm
eve-docs-4759	Skipped	Open in v0	Jul 14, 2026 12:27pm