I suspect some of the remaining instances of this log may be due to the
alarm manager polling at time T and learning of an alarm that will run
at time T + 12 (for example), the application updating the alarm time to
T + 1, the alarm manager not being updated (alarm notifier fails + alarm
manager polls too infrequently), and then the alarm looking as though it
ran late.

Only print late alarm if time discrepancy is large

…cleanup

Add tracing span creation for waitForBookmark at the DurableObjectStorage
API layer. Update ActorCacheInterface and ActorSqlite to accept SpanParent
parameter for trace context propagation.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Add Jaeger tracing for the waitForBookmark storage API.

Allow omitting name while creating dynamic workers

The comments in ser.c++ suggested that V8 would always treat objects with internal fields as host objects, not calling the `IsHostObject()` callback even when it was enabled. This turns out to be wrong: if HasCustomHostObject() returns true, then IsHostObject() will be called for *all* objects, internal fields or otherwise, and the result respected.

Prior to the introduction of `enhanced_error_serialization`, though, `HasCustomHostObject()` would only return true when `treatClassInstancesAsPlainObjects` was false. This inadvertently neutralized the bug, because all objects with internal fields are also "class instances" (i.e. their prototype is something other than `Object.prototype`). So all API objects continued to be treated as host objects.

But `enhanced_error_serialization` introduced another way that `HasCustomHostObject()` could return true, even when `treatClassInstancesAsPlainObjects` is also true. Unfortuntaley, in this case, API objects (objects with internal fields) _stopped_ being treated as host objects. Hence, all API objects started being serialized as empty objects, since the default serialization behavior for all objects is to ignore the prototype and just serialize the own properties.

The fix is to make sure we check for internal fields in `IsHostObject()`.

Ironically, the test for `DOMException` serialization in `js-rpc-test.js` managed to depend on this bug. `enhanced_error_serialization` as implemented doesn't apply to `DOMException`, since it's a custom API object. But the bug caused it to be serialized as a plain object, which ended up causing its own properties to be preserved, as they should be under `enhanced_error_serialization`. However, its _type_ was not preserved, but this was not actually tested, so the test passed by accident. I have removed this test from `js-rpc-test` and recreated it in `rpc-error-test`, where I also adjusted it to verify the type but not the own properties (leaving the latter as a TODO to fix later).

… checks

Meant to add cppcoreguidelines-pro-type-member-init since it would have saved me
spending hours from tracking down a test failure, but that would be
significantly more work.

…rialization-hostobject

add initial jsg rust integration