Buildings and levels for the floor map, and make every identifier searchable

The map was one picture of one floor. A second floor was added, the blueprint
changed size, and machines moved, so a position now records WHICH DRAWING its
coordinates belong to.

Buildings and levels (ADR-017). Each level owns its blueprint per theme and its
own native pixel size; assets.mapx/mapy are pixels of assets.levelid, not of the
site. A position whose level is unknown renders "level unknown" and is never
drawn on the default level, because a marker on the wrong floor plan looks
entirely correct while pointing at the wrong place.

Repositioning in bulk: filter by unplaced, needs-review or level, search, place,
confirm. Landmark recalibration solves the transform PER AXIS from landmark
pairs and never from image dimensions - the canvas grew taller without
rescaling, so a dimension-derived scale would stretch Y by 1.57 and be wrong
everywhere. It defaults to a dry run, reports what would land off the drawing,
snapshots before applying, and clears mapverifiedat because a transform is a
guess awaiting review. Snapshots restore, including the level and the review
state, and a restore snapshots first so an undo is undoable.

Search: gaugelabreference was matched only for measuring tools and
maintenancereference was matched nowhere at all, for any asset type, while
Settings happily offers both identifiers on machines and PCs. A tag an operator
is told to record has to be findable or it is a write-only field. USB devices
and printed items were unreachable from search entirely - neither is an asset,
so the generic asset search could not see them and no searcher existed; they
now match on serial, asset tag, label, bin code and gage-lab tag, honouring
isactive, with Settings toggles and result labels to match.

The retired-application rule was half a rule: GET /api/knowledgebase hid
articles whose topic application is retired while global search still returned
them and printed the retired application as the subject. A filter is only real
if every path that reaches the row applies it.

Contract to 0.20.0 (additive): Asset gained levelid and mapverifiedat, Location
gained levelid, and resolve_asset_position returns the levelid belonging to
whichever source supplied the coordinates. The five plugins that write a map
position are re-pinned. The install-list text format gained levelid as a NINTH
field, appended, because the shipped Pascal installer reads fields 0-7 by index.

That installer still compiles in one drawing's dimensions and bundles one
blueprint, so its map is accurate for the default level only; /api/maplevels is
deliberately unauthenticated so it can read both at runtime once rebuilt.
Recorded in PRINTER-INSTALLER.md section 6 along with the other known gaps.

Migration 7d33 converts an existing single-map site into one building and one
default level carrying the old map_* settings, then assigns every placed asset
and location to it. Nothing moves on screen. Old settings rows are kept so a
rollback still finds them. Verified end to end on MySQL 5.6 from a
production-shaped database.

frontend/src/components/LocationMapTooltip.vue

@@ -12,7 +12,15 @@
         @wheel.prevent="onWheel"
       >
         <div class="map-tooltip-content">
-          <div class="map-preview" ref="mapPreview">
+          <div v-if="levelUnknown" class="map-level-unknown">
+            <strong>Level unknown</strong>
+            <span>
+              This asset has a position ({{ props.left }}, {{ props.top }}) but no
+              level, so there is no drawing to show it on. Set its level on the
+              asset, or place it in the map editor.
+            </span>
+          </div>
+          <div v-else class="map-preview" ref="mapPreview">
             <div
               class="map-transform"
               :style="transformStyle"
@@ -43,7 +51,7 @@
 <script setup>
 import { ref, computed, nextTick, watch } from 'vue'
 import { currentTheme } from '../stores/theme'
-import { loadMapConfig, blueprintUrlFor, state as mapConfig } from '../composables/mapConfig'
+import { loadMapConfig, blueprintUrlFor, dimensionsFor, hasLevel, levelName, state as mapConfig } from '../composables/mapConfig'
 
 // Fetch this facility's blueprint + dimensions once; computeds below react
 // when it loads.
@@ -52,7 +60,11 @@ loadMapConfig()
 const props = defineProps({
   left: { type: Number, default: null },
   top: { type: Number, default: null },
-  machineName: { type: String, default: '' }
+  machineName: { type: String, default: '' },
+  // Which drawing left/top are pixels of (ADR-017). A position without one
+  // cannot be rendered: the same coordinates land somewhere different on every
+  // level, so this shows what is missing instead of guessing the default.
+  levelid: { type: Number, default: null },
 })
 
 const visible = ref(false)
@@ -67,18 +79,29 @@ const hasPosition = computed(() => {
   return props.left !== null && props.top !== null
 })
 
-const blueprintUrl = computed(() => {
-  // Reading currentTheme keeps this reactive to theme changes.
-  return blueprintUrlFor(currentTheme.value)
+// A position we cannot place: coordinates but no level, or a level this instance
+// does not know. Rendering the default blueprint here would look correct and be
+// wrong, so the tooltip says so instead.
+const levelUnknown = computed(() => {
+  return hasPosition.value && !hasLevel(props.levelid)
 })
 
-// Calculate marker position as percentage of the facility blueprint size
+const levelLabel = computed(() => levelName(props.levelid))
+
+const blueprintUrl = computed(() => {
+  // Reading currentTheme keeps this reactive to theme changes.
+  return blueprintUrlFor(currentTheme.value, props.levelid)
+})
+
+// Marker position as a percentage of THIS LEVEL's native size. Percentages of
+// the wrong level's dimensions is precisely how a marker ends up plausibly
+// placed and wrong.
 const markerX = computed(() => {
-  return (props.left / mapConfig.width) * 100
+  return (props.left / dimensionsFor(props.levelid).width) * 100
 })
 
 const markerY = computed(() => {
-  return (props.top / mapConfig.height) * 100
+  return (props.top / dimensionsFor(props.levelid).height) * 100
 })
 
 // Marker style with counter-scale to maintain constant size
@@ -197,6 +220,20 @@ watch(currentTheme, () => {
 .location-tooltip-wrapper:hover {
   color: var(--primary, #1976d2);
 }
+
+.map-level-unknown {
+  display: flex;
+  flex-direction: column;
+  gap: 0.35rem;
+  padding: 0.75rem;
+  max-width: 18rem;
+  font-size: 0.8rem;
+  color: var(--text-light);
+}
+
+.map-level-unknown strong {
+  color: var(--warning);
+}
 </style>
 
 <style>