[shiju-nv]

Summary

An integer driver setting such as Kubernetes tolerationSeconds can become a fractional JSON number during protobuf decoding and fail typed configuration parsing. This preserves whole-number values through the shared converter and the actual Kubernetes rendering path.

Related Issue

Closes #5106. Part of #5114.

Changes

• Use one fallible protobuf-to-JSON converter in all five first-party compute driver factories.
• Preserve fractional values without rounding and reject non-finite protobuf numbers.
• Add an integer toleration to the existing Kubernetes scheduling regression.

Release Notes

Per-sandbox integer driver settings retain their JSON number type. The separate gateway TOML PID-limit path is unchanged.

Testing

• Checks appropriate to the affected code and behavior pass
• Unit tests added/updated (if applicable)
• E2E tests added/updated (if applicable)

Checklist

• Follows Conventional Commits
• Commits are signed off (DCO)
• Architecture docs updated (if applicable)

[github-actions]

Label test:e2e applied for 50d3a86. Open the existing run and click Re-run all jobs to execute with the label set. The run will execute the standard E2E suite after building the required gateway, sandbox, and supervisor images once. The matching required CI gate status on this PR will flip green automatically once the run finishes.