chore: move code

[MasterPtato]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[MasterPtato]

• fix(pb-outbound): add back serverless token #4817
• fix(pb-envoy): hard abort ws to tunnel on ping error #4776
• fix(outbound): implement drain grace period #4775
• fix(pb): fix pool config defaults #4774
• fix(pb): remove actor sleep ts when allocated #4772
• refactor(gateway): clean up and fix lost tunnel msgs #4771
• refactor(pb): fix actor overdue alarm handling #4770
• fix: update railway docs to include graceful shutdown #4715
• fix: add wf registry command #4714
• chore: move code #4713 👈 (View in Graphite)
• fix(gas): add large txn retries for pulling signals, tighten commit interval for actors #4712
• fix: improve epoxy propose errors, add gcp logging fmt #4698
• fix: autogenerate bare protocol versions #4696
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[railway-app]

🚅 Deployed to the rivet-pr-4713 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
frontend-cloud	😴 Sleeping (View Logs)	Web	Apr 27, 2026 at 7:18 pm
kitchen-sink	❌ Build Failed (View Logs)	Web	Apr 27, 2026 at 6:04 pm
website	😴 Sleeping (View Logs)	Web	Apr 27, 2026 at 3:21 pm
mcp-hub	✅ Success (View Logs)	Web	Apr 23, 2026 at 11:50 pm
frontend-inspector	❌ Build Failed (View Logs)	Web	Apr 23, 2026 at 11:50 pm
ladle	❌ Build Failed (View Logs)	Web	Apr 23, 2026 at 11:50 pm

[claude]

PR Review: "chore: move code"

Summary

Three files changed (+5/-13). Two independent refactors: a timestamp capture fix in ping.rs and a config-computation encapsulation in ping_task.rs.

---

Correctness — ping.rs

The ping.rs change has real behavioral significance beyond what "move code" implies.

FDB transaction closures passed to .run(|tx| async move { ... }) are retried on conflict. Previously, util::timestamp::now() was called inside the closure, so each retry wrote a different timestamp to LastPingTsKey. By capturing now before the closure, the timestamp is stable across retries and correctly represents when the ping measurement was taken, not when the transaction finally committed.

Suggestion: Update the PR description or add a brief comment noting the retry-stability motivation, so future readers understand this is not a purely mechanical move.

---

Encapsulation — ping_task.rs

Moving Duration::from_millis(ctx.config().pegboard().runner_update_ping_interval_ms()) into ping_task::task() is a clean simplification. The config is already accessible via ctx, the call site loses one parameter, and behavior is identical. No concerns.

---

Convention Checks

Check	Result
Logging (tracing, no eprintln!)	Pass
Concurrency (no Mutex<HashMap>)	Pass
Error handling (anyhow + .context())	Pass
Commit message (conventional commits)	Pass
No docs/limits drift	N/A

---

CI Note

The CI failures visible on this PR (Railway deploys for kitchen-sink, frontend-inspector, ladle) appear to be pre-existing frontend issues unrelated to the Rust changes here.

---

Verdict

Changes are correct and convention-compliant. The one actionable item is clarifying the correctness motivation for the ping.rs timestamp capture in the PR description or a code comment.