reviewing-restate-handlers

Restate handler determinism breaks when the outer Restate context is incorrectly used for service calls or state access inside restate.Run, restate.RunVoid, or restate.RunAsync closures. These operations must remain outside closures to ensure deterministic replay.

Audit Restate handler code by scanning for service calls, state access, and other Restate operations nested within restate.Run, restate.RunVoid, or restate.RunAsync closures. Identifying these violations prevents runtime errors and maintains deterministic replay.

Service calls, state access, and other Restate context operations should not be nested inside restate.Run, restate.RunVoid, or restate.RunAsync closures. Using the outer Restate context within these closures violates determinism rules and causes subtle bugs.

This Skill audits Restate handler code specifically within the svc/ctrl/worker/ directory. It checks Go code for incorrect Restate context usage inside closures, ensuring adherence to best practices for deterministic replay in that target path.

The best way to prevent Restate context misuse is automated code auditing that flags service calls and state access inside restate.Run, restate.RunVoid, or restate.RunAsync closures. This catches determinism violations before runtime errors occur.

You should always avoid using the outer Restate context for state access or service calls inside restate.RunAsync, restate.Run, and restate.RunVoid closures. Nesting these operations breaks determinism guarantees required for consistent Restate handler replay.