Release 0.11.1

A patch release. The pagination-cap fixes, and the documentation that missed the
0.11.0 installer by a few minutes.

docs/UPGRADE.md is one of the documents the Windows installer puts on the server,
and its buildings-and-levels section was committed after 0.11.0 was tagged. So
0.11.0 shipped the page an operator reads WHILE upgrading without the guidance
about that upgrade - which matters most on an air-gapped box, where there is no
other way to reach it. The installer now also ships FLOOR-MAP.md for the same
reason the Windows runbooks ship.

No application code changed on the server side and the plugin contract stays at
0.20.0.

The version and the changelog are the release; the detail is in the entry.

CHANGELOG.md

@@ -10,6 +10,17 @@ ADR-007 and ADR-002.
 
 ## [Unreleased]
 
+## [0.11.1] - 2026-08-17
+
+A patch release: the pagination-cap fixes, plus the documentation that missed the
+0.11.0 installer. No application behaviour changed on the server and the plugin
+contract stays at 0.20.0.
+
+`docs/UPGRADE.md` is one of the documents the Windows installer puts on the box,
+and its buildings-and-levels section landed after 0.11.0 was tagged - so 0.11.0
+shipped the page an operator reads WHILE upgrading without the guidance about
+that upgrade. An air-gapped server has no other way to reach it.
+
 ### Fixed
 
 - Pickers and batch label sheets no longer stop at 100 rows. `perpage` is
@@ -25,6 +36,16 @@ ADR-007 and ADR-002.
   `PrintedPartsLabels`, `MachineForm` and `NetworkDeviceForm`. Lists that render
   a page at a time are unchanged - they page deliberately.
 
+### Changed
+
+- The installer now also ships `FLOOR-MAP.md`, the operator's page for loading
+  floor plans, placing markers and moving them when a plan changes. Same reason
+  the Windows runbooks ship: the box cannot reach the wiki.
+- The bundled `UPGRADE.md` now carries the 0.11.0 section: an existing map is
+  preserved and nothing moves on screen, and replacing a blueprint with one of
+  different dimensions moves every marker on that level, so recalibrate from
+  landmarks rather than editing the level's width and height.
+
 ## [0.11.0] - 2026-08-17
 
 The floor map became a set of drawings instead of one picture. A site can hold

docs/PROJECT-MAP.md

@@ -11,7 +11,7 @@ never by editing this file.
 
 | series | value | governed by |
 |---|---|---|
-| product `__version__` | `0.11.0` | ADR-007 |
+| product `__version__` | `0.11.1` | ADR-007 |
 | plugin contract `__contract_version__` | `0.20.0` | ADR-002 |
 
 They move independently. A contract bump is not a release.

frontend/package.json

@@ -1,6 +1,6 @@
 {
   "name": "shopdb-frontend",
-  "version": "0.11.0",
+  "version": "0.11.1",
   "private": true,
   "type": "module",
   "scripts": {

scripts/build-site.sh

@@ -95,7 +95,8 @@ python3 "$REPO/scripts/generate_sbom.py" "$REPO" -o "$OUT/sbom.cdx.json"
 echo "==> Staging docs ..."
 mkdir -p "$OUT/docs"
 for doc in openapi.json llms.txt api-inventory.json \
-           INSTALL-WINDOWS.md OPERATE-WINDOWS.md BACKUP-RESTORE.md UPGRADE.md; do
+           INSTALL-WINDOWS.md OPERATE-WINDOWS.md BACKUP-RESTORE.md UPGRADE.md \
+           FLOOR-MAP.md; do
   [ -f "$REPO/docs/$doc" ] && cp -a "$REPO/docs/$doc" "$OUT/docs/"
 done
 # Never let a missing optional doc fail the build - the loop's last test governs

shopdb/__init__.py

@@ -63,7 +63,7 @@ __contract_version__ = '0.20.0'
 # plugin-contract version above are distinct series with independent
 # bump rules. Not part of the shopdb.api contract surface, so it is
 # not re-exported there.
-__version__ = '0.11.0'
+__version__ = '0.11.1'
 
 
 def create_app(config_name: str = None) -> Flask: