docs(spec,api): the related-list Add example and the dangling-reference example no longer name permission_set_id

Claude-Session: https://claude.ai/code/session_01MZuVPXoYeF1Pa3G4ERmTPz
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/15204-grant-by-name-spec-tsdoc.md

@@ -0,0 +1,5 @@
+---
+'@objectstack/spec': patch
+---
+
+The TSDoc on `RecordRelatedListProps.add` names its canonical example by name: "Assigned Users" on a permission set keys `sys_user_permission_set` on `permission_set` with `relationshipValueField: 'name'`, since a grant names its permission set (ADR-0131 D4). Text only; no schema changes.

content/docs/api/error-catalog.mdx

@@ -285,14 +285,14 @@ object is rejected with `400 VALIDATION_FAILED`, and the specifics ride in
 
 ```json
 {
-  "error": "Permission Set: no sys_permission_set record has id \"ps_missing\"",
+  "error": "User: no sys_user record has id \"usr_missing\"",
   "code": "VALIDATION_FAILED",
   "fields": [{
-    "field": "permission_set_id",
+    "field": "user_id",
     "code": "reference_not_found",
-    "label": "Permission Set",
-    "constraint": { "target": "sys_permission_set" },
-    "value": "ps_missing"
+    "label": "User",
+    "constraint": { "target": "sys_user" },
+    "value": "usr_missing"
   }]
 }
 ```

packages/spec/src/ui/component.zod.ts

@@ -1596,8 +1596,8 @@ export const RecordRelatedListProps = strictObject({
    * Server-side rules still apply on insert (e.g. the AI-seat cap), and their
    * errors surface in the dialog. The canonical use is "Assigned Users" on a
    * permission set (objectName=`sys_user_permission_set`,
-   * relationshipField=`permission_set_id`, picker.object=`sys_user`,
-   * linkField=`user_id`).
+   * relationshipField=`permission_set`, relationshipValueField=`name`,
+   * picker.object=`sys_user`, linkField=`user_id`).
    */
   add: strictObject({
     surface: 'this `record:related_list` `add` config',