Module dto 

HTTP boundary DTO types for mesh-admin introspection.

These types own the HTTP JSON wire contract. Domain types (NodePayload, NodeProperties, FailureInfo) stay clean of HTTP serialization concerns; conversion happens at the boundary via From / TryFrom impls defined here.

Invariants

• HB-1 (typed-internal, string-external): NodeRef, ActorAddr, ProcAddr, and SystemTime are encoded as canonical strings in the DTO types.
• HB-2 (round-trip): NodePayload → NodePayloadDto → NodePayload is lossless for values representable in the wire format. Timestamps are formatted at millisecond precision (humantime::format_rfc3339_millis), matching the established HTTP contract; sub-millisecond precision is truncated at the boundary.
• HB-3 (schema-honesty): Schema/OpenAPI are generated from these DTO types, so the published schema reflects the actual wire format.

Structs

ActiveHandlerDto

One handler with in-flight invocations, at the HTTP boundary.

ExecutionDto

An actor’s in-flight handler execution at the HTTP boundary.

FailureInfoDto

Structured failure information for failed actors.

InboundOrderingDto

Mesh-admin presentation of inbound ordering state.

NodePayloadDto

Uniform response for any node in the mesh topology.

OrderingSessionSnapshotDto

Per-session reorder-buffer snapshot at the HTTP boundary.

ProcDebugStatsDto

Proc-level debug/operational stats (DTO mirror of ProcDebugStats).

ProcessMemoryStatsDto

Memory stats of the hosting OS process (DTO mirror of ProcessMemoryStats).

Enums

NodePropertiesDto

Node-specific metadata. Externally-tagged enum — the JSON key is the variant name (Root, Host, Proc, Actor, Error).