Module admin 

Zenoh admin-space access (issue #14): browse @/** — the middleware’s own introspection — from the same un-namespaced session the convention tooling already holds (a namespaced session’s admin selector would be rewritten and match nothing, RFC 09 §5).

Admin key layouts vary between zenoh versions (report §3.1’s caveat), so this module stays a thin, honest transport: keys + JSON values, no hardcoded schema. routers extracts the few fields every 1.x layout carries, and leaves the rest visible in raw.

Structs

AdminEntry

One admin-space entry.

CoverageRow

RouterInfo

A router (or peer) as the admin space reports it.

StorageInfo

One configured storage, as the admin space reports it.

Enums

Coverage

How a declared state family relates to the configured storages.

Functions

admin_get

GET an admin selector (default @/**). Fans to every node (target All, consolidation None — several routers may answer).

routers

Enumerate routers/peers from @/*/router (and the fields every layout carries).

state_coverage

Judge every declared state family against the configured storages (issue #14): the family’s wire selector vs each storage’s key expression, by key algebra (includes ⇒ covered, intersects ⇒ partial). Pure.

storage_from_admin_entry

Extract a storage from one admin entry, tolerantly: the key shape is @/<zid>/router/…/storage_manager/storages/<name>[…], the value a config document whose key_expr field names what it captures. Pure — the version-variance lives here, unit-tested.

storages

Enumerate configured storages across the mesh (issue #14). Zero routers (peer mesh, admin disabled) is an empty vec, never an error.