@@ -0,0 +1,14 @@
+---
+'@objectstack/plugin-approvals': patch
+---
+
+fix(plugin-approvals): the approval request page's highlights strip no longer shows the target object's API name
+
+Clause-②: no
+
+- **The strip draws no Object chip.** `sys_approval_request_detail` no longer lists `object_name` on its highlights strip, so a request about an announcement no longer shows `showcase_announcement` there. `object_name` holds the target object's API name, and `sys_approval_request` declares no field that holds that object's label.
+- **The page still names the target object, by its label.** The Details tab draws the `record_id` / `object_name` pointer pair as a card of the target record. The card heads the record with its object's label (`Announcement`), translated into the reader's locale and read from the object's definition when the page draws, so a relabelled object shows its new label. Where the reader may not read the target record, or the platform deleted it, the card says so and the page names no object.
+- **The object's `highlightFields` drops `object_name` too.** The page's Details tab is a bare `record:details` node, which draws the object's `highlightFields` minus the strip. A change to the strip alone would have moved `object_name` into that tab as a row showing the API name.
+- **Unchanged:** `object_name` stays a declared, required field: the approvals machinery queries on it, and it is the type half of the pointer pair. The request list views still show their Object column.
+
+A patch: one entry fewer in one platform object's field list and in its page. No export, type, accepted value, served key or stored column changes.
@@ -15,7 +15,7 @@
  *      `record:approval_decision` node, `record:details`, `sys_approval_action`
  *      as the related list, no discussion thread, and a highlights strip that
  *      leaves `record_id` to the details grid (the seat's choice on the ui
- *      seat's design input `6081889955`);
+ *      seat's design input `6081889955`) and names nothing by a machine name;
  *   3. the page passes what `os validate` judges a page by — the parse, the
  *      component-type vocabulary, the props rows and the build rules — with a
  *      control for each half that can go red;
@@ -183,6 +183,30 @@ describe('sys_approval_request detail page — the slot map', () => {
     expect(fields.current_step).toMatchObject({ type: 'text' });
   });
 
+  it('draws no Object chip: object_name, the target\'s API name, is in neither list, and the Details tab is the pointer pair\'s card', () => {
+    // `object_name` holds the target object's API name (`showcase_announcement`)
+    // and the object declares no field holding that object's label. The page
+    // names the target object on the card the console draws for the
+    // `record_id` / `object_name` pair in the Details tab, which heads the
+    // record with its object's label. The object's list moves with the strip
+    // for the reason the flow chip's does: dropped from the strip alone,
+    // `object_name` would be drawn as a row in that tab.
+    const strip = SLOTS.highlights.properties.fields as string[];
+    const declared = SysApprovalRequest.highlightFields ?? [];
+    const fields = SysApprovalRequest.fields as AnyRec;
+    expect({ strip: strip.includes('object_name'), declared: declared.includes('object_name') })
+      .toEqual({ strip: false, declared: false });
+    // The Details tab's bare `record:details` node draws the object's list
+    // minus the strip: the id half of the pair, whose type half names the
+    // target object.
+    expect(TAB_ITEMS[0].children).toEqual([{ type: 'record:details' }]);
+    expect(declared.filter((f: string) => !strip.includes(f))).toEqual(['record_id']);
+    expect(fields.record_id?.referenceVia).toBe('object_name');
+    // Control: the type half stays a declared, required field. It is dropped
+    // from the two lists, not from the object.
+    expect(fields.object_name).toMatchObject({ type: 'text', required: true });
+  });
+
   it('tabs: Details is record:details, Timeline is sys_approval_action as a related list on request_id', () => {
     expect(TAB_ITEMS.map((t) => t.label?.en)).toEqual(['Details', 'Timeline']);
     expect(TAB_ITEMS[0].children).toEqual([{ type: 'record:details' }]);
 
@@ -64,11 +64,13 @@ export const SysApprovalRequest = ObjectSchema.create({
   // [ADR-0085] The flow is named by its label, `process_label`, never by the
   // machine source `process_name` (`flow:NAME`), and the step by its label,
   // `current_step_label`, never by the node id `current_step`, as the request
-  // lists name them. The record page's highlights strip is this list minus
-  // `record_id`, and the page's bare `record:details` node draws this list
-  // minus the strip, so the two move together (`sys-approval-request.page.ts`
-  // says why).
-  highlightFields: ['process_label', 'object_name', 'record_id', 'status', 'current_step_label', 'submitter_id', 'updated_at'],
+  // lists name them. The target object is not listed: `object_name` holds its
+  // API name, and the record page names it by its label on the card the
+  // `record_id` / `object_name` pair draws. The record page's highlights strip
+  // is this list minus `record_id`, and the page's bare `record:details` node
+  // draws this list minus the strip, so the two move together
+  // (`sys-approval-request.page.ts` says why).
+  highlightFields: ['process_label', 'record_id', 'status', 'current_step_label', 'submitter_id', 'updated_at'],
 
   // Curated built-in list views — render as segmented tabs in the console.
   // Filters use {current_user_id} substitution wired by the console.
 
@@ -49,9 +49,16 @@ import type { Page } from '@objectstack/spec/ui';
  *    The approvals get serves it by the same chain: the stored label, else
  *    the snapshot's `__nodeLabel`, else the humanized node id. A request with
  *    no step at all serves neither field, and the strip draws no step chip.
- *  - The Object chip is `object_name`, the target object's API name as
- *    stored. The object declares no field that holds that object's label, so
- *    the strip has none to list in its place.
+ *  - There is no Object chip. `object_name` is the target object's API name
+ *    as stored (`showcase_announcement`), and the object declares no field
+ *    that holds that object's label. The page names the target object in the
+ *    Details tab instead: the `record_id` / `object_name` pair's card heads the
+ *    target record with its object's label, translated and read from the
+ *    object's definition when the page draws, so a relabelled object reads its
+ *    new label. Where the card cannot read the target (the reader may not
+ *    read it, or the platform deleted it), the page names no object at all.
+ *    `object_name` leaves the object's `highlightFields` too, by the rule
+ *    above, so the Details tab does not draw it as a row.
  *  - `tabs` is authored: Details (`record:details`, a bare node: see the
  *    strip above) and Timeline — `sys_approval_action` as a
  *    related list keyed on `request_id`, newest first. The `tabs` slot is
@@ -88,7 +95,7 @@ export const SysApprovalRequestDetailPage: Page = {
     highlights: {
       type: 'record:highlights',
       properties: {
-        fields: ['process_label', 'object_name', 'status', 'current_step_label', 'submitter_id', 'updated_at'],
+        fields: ['process_label', 'status', 'current_step_label', 'submitter_id', 'updated_at'],
       },
     },