fix: update hub-search version in README files

| `admin-ui/` | The Data Lab UI: React + TypeScript + Vite, public pages and management console |

| `examples/` | Sample MAP datasets (Turtle) to register against a running stack |

| `local/` | One-command local trial: `local-up.sh` / `local-down.sh`, a generated local-only Keycloak realm, `e2e.py` |

| `config/profile/` | piveau form/search profile — mounted but inert: profile mode is off (it breaks indexing in hub-search 5.3.1), see requirements-and-design §L.1 |

| `config/profile/` | piveau form/search profile — mounted but inert: profile mode is off (it breaks indexing in hub-search 5.3.11), see requirements-and-design §L.1 |

| `config/shapes/` | Vendored MAP SHACL shapes (staged, not enforced: the Data Lab API validates its own writes in code, direct hub writes are not validated; see requirements-and-design §L.1) |

| `keycloak/` | `dataspace` realm export: the UI, API and piveau access-control clients (Keycloak 26.4+) |

| `nginx/` | `/data-lab/*` route family for the platform Nginx |

The web UI is `admin-ui/`: one React app with the **public catalogue pages**

(faceted dataset search, catalogue and dataset pages — no sign-in) and the

**management console** at `#/admin` (catalogues, members, datasets: create and edit

through a MAP form, delete, promote staging → production). It replaces the 6G-DALI

catalogue UI that earlier drafts used.

through a MAP form, delete, promote staging → production).

## Catalogue model

See [docs/deployment.md](docs/deployment.md) for the full procedure, including

the Keycloak realm import.

On Kubernetes, the `datalab` subchart of `oop-platform-chart` in the

[helm repository](https://labs.etsi.org/rep/oop/deploy/helm) deploys the Data Lab instead of

Compose (ADR-0069); its README's *Data Lab* section shows how to turn it on.

## Build and release

Only two components are built from this repo: `data-lab-api` (`api/`) and `data-lab-admin-ui` (`admin-ui/`).

These are **not** loaded by the running stack, and the form/search profile in

`../profile/` is not active either (profile mode is off — it breaks indexing in

hub-search 5.3.1). Validation in this release is decided (requirements-and-design

hub-search 5.3.11). Validation in this release is decided (requirements-and-design

§L.1): the Data Lab API checks its own writes against the MAP rules in code, and

direct hub writes are not validated (Known Gap T1). Running these shapes in

`piveau-hub-repo`'s validation hook or behind an external validator is the planned