What you can look up.
What you can run.
The reference and laboratories serve different purposes. This map connects API families to their contracts and reproducible scenarios.
Reference by subsystem
Counts are calculated from the portal catalog. An entry may group related methods; the total counts documented entries and does not represent framework test coverage. Private implementation symbols are outside the usage reference.
| Family | Entries | Contract |
|---|---|---|
| Core | 58 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Lifecycle | 16 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Store | 15 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Events | 17 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Contracts | 6 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| CLI | 17 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Permissions | 16 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Synchronization | 4 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Hooks | 11 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Plugins | 7 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Timeline | 18 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Loading | 26 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Cache | 7 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Diagnostics | 24 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| SSR | 26 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| AI | 38 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Adapters | 66 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Helpers | 6 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| Integrations | 8 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
| MCP | 34 | Signature, purpose, example, and reference; parameters, errors, permissions, and cleanup. |
Browser recipes
The eight recipes run WU 4.0.0 and contain 49 checks for specific scenarios. Passing them does not certify every possible combination of these subsystems. Each run reports its results and observed cleanup.
| Recipe | What to observe |
|---|---|
| RPC | Response, timeout, and provider removal. |
| Versioned contracts | Compatible consumption and rejection of an incompatible version. |
| Capabilities and revocation | Allowed operations, denial, and use after unmount. |
| Lifecycle middleware | Priority order, continuation, and cancellation. |
| Plugins | Explicit permissions, installation, and uninstallation. |
| Timeline | Recording, navigating projections, and returning to the present. |
| Synchronization | Exchange between stores through BroadcastChannel and closure. |
| Loading and cache | Loading strategy, preloading, and resource reuse. |
Composition connects React and Vue through mounting, shared state, and events. Services and RPC connects a client to a provider through a versioned contract: requests, validation, responses, cancellation, and revocation. The guide Running the examples provides the complete walkthrough.
Apps in motion
Try windows, drag and retained state → An interactive scenario connects detach/attach, typed delivery, transitions and keep-alive. Results appear in the apps; the eight recipes above retain their independent assertions.
Server and AI examples
| Example | Environment and scope |
|---|---|
| SSR rendering | Node and the server subpath. Checks generated HTML, serialization, and failures. |
| MCP bridge | Local relay, MCP client, and browser. The recipe documents authentication, connection, and shutdown. |
| Local AI actions | Registration, schema, permissions, and pure execution. No conversation with a model is required. |
| WU CLI | Terminal. Options, defaults, effects, and exit codes. The portal builder prepares text; it does not execute the CLI binary. |
Versions and limits
The homepage and API recipes run WU 4.0.0. Earlier examples keep their pinned versions; see versions and distribution before relying on a fix not yet published on npm.
Browser recipes, app composition, and Node examples have different execution environments. Timeline rebuilds store projections; restoration does not reverse requests or external effects. An app's grants do not replace remote-service authorization.