How does Ruby manage fiber scheduling state transitions in cooperative concurrency?

Fibers transition between running, suspended, and ready states under a user-level scheduler.

Fibers maintain execution state in VM-managed stacks. State transitions occur explicitly via Fiber.yield or implicitly via scheduler hooks. The scheduler maintains queues of runnable fibers. Unlike threads, fibers do not preempt; they must yield control, making execution deterministic and lightweight.