What
A public logging-only entry point for bind_host_via_wit_bindgen: the current __bind_host_cap_via_wit_bindgen(logging) arm without its WitBindgenHost dependency, so a domain SDK reuses the level mapping and facade install without the base block.
Why
A domain world that remaps nexum:host/types onto its own SDK bindings makes both Fault types foreign, so the orphan rule blocks the whole macro even though the logging arm only needs the freshly generated nexum::host::logging.
Deferred from #76 (landed as PR #95, which fixed the runtime capability row); the first consumer is the videre domain SDK integration.
Notes
Coordinate with #36: the base block From impls between the wit-bindgen Fault and the SDK Fault are exactly the surface #36 reshapes, and its fate is decided during the #50 From-wiring work. The logging-only entry must not preempt that decision; it only carves the arm free of it.
What
A public logging-only entry point for bind_host_via_wit_bindgen: the current __bind_host_cap_via_wit_bindgen(logging) arm without its WitBindgenHost dependency, so a domain SDK reuses the level mapping and facade install without the base block.
Why
A domain world that remaps nexum:host/types onto its own SDK bindings makes both Fault types foreign, so the orphan rule blocks the whole macro even though the logging arm only needs the freshly generated nexum::host::logging.
Deferred from #76 (landed as PR #95, which fixed the runtime capability row); the first consumer is the videre domain SDK integration.
Notes
Coordinate with #36: the base block From impls between the wit-bindgen Fault and the SDK Fault are exactly the surface #36 reshapes, and its fate is decided during the #50 From-wiring work. The logging-only entry must not preempt that decision; it only carves the arm free of it.