# wip-client

Presentation-independent stateful runtime for Web Interface Protocol (WIP) clients.

`wip-client` manages endpoint- and security-context-isolated Known Space, object and Interface Descriptor observations, bounded request ownership, supersession, out-of-order response suppression, validator recovery, and operation call contexts. It produces and consumes framework-neutral `wip-http` messages but performs no network I/O and contains no UI types.

```toml
[dependencies]
wip-client = "0.1.0"
```

Applications provide the HTTP adapter and presentation layer, send each prepared request exactly as owned by the runtime, then return the corresponding response for completion.

Interface acquisition and call APIs use `wip_protocol::InterfaceReference { scope, name }` directly. Interface caches and Object membership compare the complete structured value, so equal names in different scopes remain distinct. Interface observations retain the optional `scope_ref`, and calls copy it into `InterfaceTarget` unchanged. Scope-identity recovery is not implemented by this mechanical migration.

See the [API documentation](https://docs.rs/wip-client) for session, acquisition, cache, and call APIs.

Licensed under either of Apache-2.0 or MIT at your option.