fix(deps): move to crud-views 0.5.1 and crud-sdk 0.5.1

docs/adrs/0006-manifest-driven-admin.md

@@ -76,7 +76,7 @@ Four facts about the libraries and the app shaped the wiring:
   (`defaultUrlAdapter`, i.e. `window.location` and `history`), the same
   adapter the lists use for filter, sort and paging, so deep links and the back
   button work. Each list prefixes its own parameters with the resource name.
-- **Dependencies.** `@craftainer/crud-sdk` 0.5.0, `@craftainer/crud-views` 0.4.1,
+- **Dependencies.** `@craftainer/crud-sdk` 0.5.1, `@craftainer/crud-views` 0.5.1,
   plus `@mui/x-data-grid` and `@mui/x-charts` 9.16.0 (crud-views' peers; MIT
   tier only). The provider's query scope is the OIDC `sub` while
   signed in (stable across token refresh; `AdminPage` also remounts per `sub`)
@@ -86,8 +86,9 @@ Four facts about the libraries and the app shaped the wiring:
   carries a token over plain http to a non-loopback host; the client's base URL
   is the page's own origin, so this only bites when the app is served over http
   from a non-loopback host, and `allowInsecureHttp` is deliberately not set.
-  (Written against 0.4.0 and re-checked against 0.5.0 / 0.4.1 on upgrade.) The
-  `@craftainer/*` scope is excluded from pnpm's
+  (Written against 0.4.0 and re-checked against SDK 0.5.1 / views 0.5.1 on
+  upgrade; views 0.5 reads the key field from `resource.id_field`, which the
+  manifest already supplies.) The `@craftainer/*` scope is excluded from pnpm's
   `minimumReleaseAge` (user decision, 2026-10-24): we release these ourselves
   and consume them right away.
 - **Tests.** Unit tests cover the `/api` prefixing, discovery, the cached ETag

package.json

@@ -17,8 +17,8 @@
     "storybook:build": "storybook build"
   },
   "dependencies": {
-    "@craftainer/crud-sdk": "0.5.0",
-    "@craftainer/crud-views": "0.4.1",
+    "@craftainer/crud-sdk": "0.5.1",
+    "@craftainer/crud-views": "0.5.1",
     "@emotion/react": "11.14.0",
     "@emotion/styled": "11.14.1",
     "@fontsource-variable/fraunces": "5.3.0",