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/api/index.js

@@ -863,6 +863,63 @@ export const setupApi = {
   }
 }
 
+// Buildings and the levels within them (ADR-017). Reads are public - the
+// printer installer map draws a blueprint before anyone logs in.
+export const mapLevelsApi = {
+  list() {
+    return api.get('/maplevels')
+  },
+  get(levelid) {
+    return api.get(`/maplevels/${levelid}`)
+  },
+  createBuilding(payload) {
+    return api.post('/maplevels/buildings', payload)
+  },
+  updateBuilding(buildingid, payload) {
+    return api.patch(`/maplevels/buildings/${buildingid}`, payload)
+  },
+  create(payload) {
+    return api.post('/maplevels', payload)
+  },
+  update(levelid, payload) {
+    return api.patch(`/maplevels/${levelid}`, payload)
+  },
+  remove(levelid) {
+    return api.delete(`/maplevels/${levelid}`)
+  },
+  // Returns the image's real pixel size alongside the stored dimensions. On an
+  // empty level the server adopts them; on a populated one it refuses and says
+  // so, because changing the coordinate space moves every marker on it.
+  uploadBlueprint(levelid, theme, file) {
+    const form = new FormData()
+    form.append('file', file)
+    form.append('theme', theme)
+    return api.post(`/maplevels/${levelid}/blueprint`, form, {
+      headers: { 'Content-Type': 'multipart/form-data' },
+    })
+  },
+}
+
+// Bulk marker positions: the landmark transform, bulk placement, review state
+// and undo. Every write snapshots first.
+export const mapPositionsApi = {
+  setPositions(positions, verified = true) {
+    return api.post('/mappositions/positions', { positions, verified })
+  },
+  transform(payload) {
+    return api.post('/mappositions/transform', payload)
+  },
+  verify(assetids, unverify = false) {
+    return api.post('/mappositions/verify', { assetids, unverify })
+  },
+  snapshots() {
+    return api.get('/mappositions/snapshots')
+  },
+  restore(snapshotid) {
+    return api.post(`/mappositions/snapshots/${snapshotid}/restore`)
+  },
+}
+
 export const settingsApi = {
   list(params = {}) {
     return api.get('/settings', { params })