Reuse shared UI

Reuse the repository-local @stormtrust/ui package in a compatible frontend. The package uses Vue; reusing its visual contract does not require migrating a separate application runtime.

Start the workshop with make app-dev APP=ui. Review Start Here, then the relevant component or pattern. Check whether it is a stable export or an experimental story.
Select the smallest export from the UI package reference. Use replay exports for replay behavior and map exports for the map engine. Keep map rendering behind its shared interface.
Declare the dependency in the consuming package's existing manifest. The website demonstrates "@stormtrust/ui": "file:../ui" in org/apps/www/package.json. Paths are relative to the package owner; an app using the root manifest needs a root-relative package reference. Update the owning lockfile using scripts/apps/pnpm.sh.
Integrate the exported component and styles. For documentation surfaces, choose the whole StDocsShell or its independently exported pieces. Preserve keyboard behavior, focus, evidence labels, and light/dark states. Keep illustrative weather and property fixtures labeled as demonstrations.
Verify the changed UI and its consumers. For a website integration, run:
```
make app-verify APP=ui
make app-verify APP=www
node scripts/ci/catalog.mjs check
```
Use the change selector to identify additional consumers. Inspect the actual consumer journey as well as the Storybook example before following the shared release process.

Shared asset changes

Follow the asset release contract. Publish a new immutable version and update consumers deliberately. A UI package version, immutable asset URL, and Worker deployment identify different things.