chore: prepare 0.2.0 release

crates/wip-client/README.md

@@ -6,7 +6,7 @@ Presentation-independent stateful runtime for Web Interface Protocol (WIP) clien
 
 ```toml
 [dependencies]
-wip-client = "0.1.0"
+wip-client = "0.2.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.

crates/wip-host/README.md

@@ -6,11 +6,11 @@ Framework-independent Host publication and operation dispatch for the Web Interf
 
 ```toml
 [dependencies]
-wip-host = "0.1.0"
-wip-interface = "0.1.0"
+wip-host = "0.2.0"
+wip-interface = "0.2.0"
 ```
 
-Protocol publication and dispatch use `wip_protocol::InterfaceReference { scope, name }` and compare both fields exactly. The legacy `InterfaceRef` registration token remains Host-private: `protocol_reference()` maps its opaque string verbatim to the name at root scope `/`, without parsing it. Registry lookup and fetch accept structured references; non-root references do not resolve legacy registrations. Legacy responses omit `scope_ref`.
+Protocol publication and dispatch use `wip_protocol::InterfaceReference { scope, name }` and compare both fields exactly. Registration takes an explicit `Scope` and local name; `InterfaceRef::protocol_reference()` preserves those coordinates without parsing display text. Providers attach a current `ScopeObservation` inside the coherent backend boundary, and fetch returns its optional Object ref as `scope_ref`. Calls check a supplied `scope_ref` against that current binding; omission adds no identity precondition. Retire a Scope on Object deletion, replacement or movement; retained registry artifacts alone do not establish publication.
 
 Malformed interface-reference shapes fail calls as `InvalidRequest` before object resolution. A well-shaped reference outside the target path's ancestor-or-self scope fails at the membership check as `InterfaceMismatch`.
 

crates/wip-http/README.md

@@ -6,7 +6,7 @@ The crate maps the three WIP Core interactions to fixed HTTP routes and strict U
 
 ```toml
 [dependencies]
-wip-http = "0.1.0"
+wip-http = "0.2.0"
 ```
 
 ```rust

crates/wip-interface/README.md

@@ -6,7 +6,7 @@ The crate re-exports `#[interface]` and `#[derive(WipType)]`, generates Interfac
 
 ```toml
 [dependencies]
-wip-interface = "0.1.0"
+wip-interface = "0.2.0"
 ```
 
 ```rust

crates/wip-protocol/README.md

@@ -6,7 +6,7 @@ This crate defines the canonical Object and Interface Descriptor models, the thr
 
 ```toml
 [dependencies]
-wip-protocol = "0.1.0"
+wip-protocol = "0.2.0"
 ```
 
 Interface identity is an exact `InterfaceReference { scope, name }` pair.
@@ -16,7 +16,7 @@ and Object/interaction validation at response boundaries. Fetching needs no
 target Object path. Fetch responses and interface call targets carry optional
 opaque string `scope_ref` metadata, not a third identity field. Descriptors do
 not embed identity. See the repository's [migration guide](../../MIGRATION.md)
-for the breaking Rust and HTTP wire changes and deferred consumer semantics.
+for the breaking Rust and HTTP wire changes and consumer migration guidance.
 
 See the [API documentation](https://docs.rs/wip-protocol) for the complete model and validation rules.
 

crates/wip-text-view/README.md

@@ -5,6 +5,12 @@ Standalone Object and Interface signature rendering for WIP Text View, following
 `3-protocol.md`. Only `wip-protocol` and the Rust standard library are dependencies.
 No Client, Host, HTTP I/O, cache, UI framework or retrieval service is required.
 
+```toml
+[dependencies]
+wip-text-view = "0.2.0"
+wip-protocol = "0.2.0"
+```
+
 ## Single-entity API
 
 ```rust