Put the dual-bay sibling in the triage band, and fix the gage counterpart

TWO STRIPS OF CHROME SAYING THE SAME KIND OF THING

The machine page opened with a banner - "Dual-bay machine - sibling bay: 2022" -
directly above a hero whose band said "Controlled by". Both answer "what am I
looking at", and splitting them across a banner and a band cost a strip of
vertical space to say so.

The sibling is now a chip in the band beside the controlling PC. The band takes
an `extraitems` prop rather than learning what dualpath is: the pairing is
resolved by the machines plugin, not from the relationships endpoint, so core
cannot derive it, and a dualpath-shaped prop on a core component would be the
machines plugin leaking upward. A page passes [{label, links:[{text, to}]}] and
the band renders it with its own markup, which also keeps the chips visually
identical to the ones it derives itself.

The label stays "Dual-bay sibling" rather than "Dualpath". The banner spelled
the meaning out because a dualpath pair is ONE physical machine in two bays; a
chip reading "Dualpath" would have dropped that.

THE GAGE PAGE FILTERED FOR A COUNTERPART THAT CANNOT EXIST

MeasuringToolDetail was wired counterparttype="machine" labelled "Used on".
Wrong on both counts. The import synthesizes one measuring-tool asset per
metrology PC and a 'controls' edge PC -> tool (stage_metrology), so a gage's
counterpart is a COMPUTER, exactly as on the machine page. Filtering for a
machine peer meant the band rendered nothing on every gage that has a PC.

It looked merely empty rather than wrong because this dev database holds one
measuring tool with no relationships at all, so there was nothing to be missing.
A hand-held gage genuinely has no such edge and correctly shows nothing; a
metrology station now shows the PC that drives it.

The relationships card stays. It is the only surface with Add Relationship and
the per-row delete, and it lists types the band filters out - the band is
triage, the card is management. It does now repeat what the band shows, which
is worth revisiting separately.

Verified on screen. Frontend 280 passed.

plugins/machines/frontend/views/MachineDetail.vue

@@ -20,16 +20,6 @@
     <div v-if="loading" class="loading">Loading...</div>
 
     <template v-else-if="machine">
-      <!-- Dual-bay sibling banner: a Dualpath pair is one physical machine -->
-      <div v-if="machine.dualpathpartner" class="dualpath-banner">
-        Dual-bay machine - sibling bay:
-        <router-link
-          v-if="machine.dualpathpartner.machineid"
-          :to="`/machines/${machine.dualpathpartner.machineid}`"
-        >{{ machine.dualpathpartner.assetnumber }}</router-link>
-        <span v-else>{{ machine.dualpathpartner.assetnumber }}</span>
-      </div>
-
       <!-- Hero Section -->
       <div class="hero-card">
         <div class="hero-image" v-if="machine.machine?.imageurl">
@@ -80,6 +70,7 @@
             :assetid="machine.assetid"
             counterparttype="computer"
             counterpartlabel="Controlled by"
+            :extraitems="triageextras"
           />
         </div>
       </div>
@@ -259,7 +250,7 @@
 </template>
 
 <script setup>
-import { ref, onMounted } from 'vue'
+import { ref, computed, onMounted } from 'vue'
 import { useRoute, useRouter } from 'vue-router'
 import { machinesApi } from '@/api'
 import { withBase } from '@/utils/basePath'
@@ -281,6 +272,25 @@ const { isEnabled } = useIdentifierFlags()
 
 const loading = ref(true)
 const machine = ref(null)
+
+// The dual-bay sibling, as a triage chip. It had its own banner above the hero
+// until the band existed; two strips of chrome answering two halves of the same
+// "what am I looking at" read as clutter, and the sibling belongs beside the
+// PC that drives the machine rather than above it.
+const triageextras = computed(() => {
+  const partner = machine.value?.dualpathpartner
+  if (!partner) return []
+  return [{
+    // Says what the pair MEANS, not just that a link exists: a dualpath pair is
+    // one physical machine in two bays, which is why the old banner spelled it
+    // out rather than showing a bare number.
+    label: 'Dual-bay sibling',
+    links: [{
+      text: partner.assetnumber,
+      to: partner.machineid ? `/machines/${partner.machineid}` : null
+    }]
+  }]
+})
 const { heroWarranty, warrantyDate } = useWarrantyBadge(() => machine.value?.assetid)
 
 // relationships render via the shared AssetRelationships card
@@ -334,21 +344,6 @@ async function confirmRetire() {
   font-family: 'SF Mono', 'Monaco', 'Consolas', monospace;
 }
 
-.dualpath-banner {
-  margin-bottom: 16px;
-  padding: 10px 14px;
-  border-radius: 6px;
-  background: var(--bg-card);
-  border: 1px solid var(--border);
-  border-left: 4px solid var(--primary);
-  color: var(--text);
-  font-size: 0.9rem;
-}
-
-.dualpath-banner a {
-  color: var(--link);
-  font-weight: 600;
-}
 
 .feature-tag {
   display: inline-block;