Let a typed employee name find the employee

Reported from the floor: somebody types the employee's whole name into the
notification or recognition picker and presses Enter instead of clicking the
suggestion, and the entry does not pull from the employee database.

Two causes, one symptom.

The search matched the WHOLE query against first name or last name, so "Dana
Reyes" found nobody - no single column holds that string. Typing a full name is
what a person does before pressing Enter, and it was the one thing guaranteed to
return an empty list. A multi-word query is now treated as a full name: every
word must appear somewhere in the name, in either column, so "Reyes Dana" works
too, and "Dana Reyes" does not also return Sam Reyes. A single word still
searches broadly, and an SSO still resolves. Both directory backends changed,
the self-hosted tables and the external HR database.

With no suggestion to click, the form then turned the typed text into
`NAME:<text>` - a label linked to nothing. On screen that chip is identical to a
real selection; the difference only shows up later as no photo, no directory
link, and a recognition the person it is about cannot be found by. Both pickers
(the notifications form and the shared EmployeeSearch component) now look a
typed name up before deciding it is free text, through one helper.

An exact full-name match wins over a longer partial one, because somebody typing
"Dana Reyes" means that person and not "Dana Reyes-Smith". A genuinely ambiguous
name is NOT guessed at - the candidates are shown and the operator picks, which
is exactly when picking wrong matters most. A directory that cannot be reached
reports failure rather than silently producing a label.

Eleven tests. The search rules verified by planting the single-term query back.

One note for whoever reads the spec: the failure-branch test uses a thenable
that rejects rather than a mock returning a rejected promise. The runner
collects such a promise as an unhandled error even when the code under test
catches it, and fails the very test that proves the catch works.

Scope: product

plugins/computers/frontend/views/PCForm.vue

@@ -143,6 +143,10 @@
               v-model="form.locationid"
               class="form-control"
             >
+              <!-- Blank means "no location of its own", which is a real state:
+                   the PC then follows whatever it is attached to. The hint
+                   below says where that currently resolves to, so leaving the
+                   box empty is an informed choice rather than a missing one. -->
               <option value="">Select location...</option>
               <option
                 v-for="l in locations"
@@ -152,6 +156,12 @@
                 {{ l.locationname }}
               </option>
             </select>
+            <small v-if="!form.locationid && inheritedLocation" class="input-hint">
+              No location of its own. It currently shows
+              <strong>{{ inheritedLocation.locationname }}</strong>, inherited
+              from {{ inheritedLocation.inheritedfrom }}. Pick one here only to
+              override that.
+            </small>
           </div>
         </div>
 
@@ -400,6 +410,11 @@ const customFieldsRef = ref(null)
 const printerPickerRef = ref(null)
 const currentAssetId = ref(null)
 
+// What this PC resolves to today when it owns no location, captured at load.
+// Read-only: the form must never post it back as the record's own, which is
+// exactly what binding the location select to the merged `locationid` did.
+const inheritedLocation = ref(null)
+
 // PC Number (assetnumber) defaults to the serial number while the user hasn't
 // typed their own. Editable; only auto-fills on a new PC.
 const manualPcNumber = ref(false)
@@ -554,6 +569,7 @@ onMounted(async () => {
 
       const primaryComm = pc.communications?.find(c => c.isprimary) || pc.communications?.[0]
 
+      inheritedLocation.value = pc.inheritedlocation || null
       form.value = {
         machinenumber: pc.assetnumber || '',
         alias: pc.name && pc.name.toUpperCase() !== 'NONE' ? pc.name : '',
@@ -565,7 +581,11 @@ onMounted(async () => {
         statusid: pc.statusid || '',
         vendorid: ext.vendorid || '',
         modelnumberid: ext.modelnumberid || '',
-        locationid: pc.locationid || '',
+        // The OWN location, not the resolved one. Binding to `locationid`
+        // meant the form pre-selected a location this PC had inherited from a
+        // machine, and saving wrote it back as the PC's own - so an edit that
+        // never touched location silently stopped the PC following its parent.
+        locationid: pc.ownlocationid || '',
         osid: ext.osid || '',
         loggedinuser: ext.loggedinuser || '',
         azuredeviceid: ext.azuredeviceid || '',
@@ -576,9 +596,9 @@ onMounted(async () => {
           portoverride: a.portoverride ?? null
         })),
         notes: pc.notes || '',
-        mapx: pc.mapx ?? null,
-        mapy: pc.mapy ?? null,
-        levelid: pc.levelid ?? null,
+        mapx: pc.ownmapx ?? null,
+        mapy: pc.ownmapy ?? null,
+        levelid: pc.ownlevelid ?? null,
         ipaddress: primaryComm?.ipaddress || ''
       }