fix: reverse Toolbox header orientation

README.md

@@ -1,7 +1,7 @@
 # add·ideas Toolbox Portal
 
 `toolbox-portal` is the static launcher and release assembler for the add·ideas
-browser toolbox. Version `0.2.1` reads one same-origin catalogue, shows each app
+browser toolbox. Version `0.2.2` reads one same-origin catalogue, shows each app
 as a full-page launch tile, and keeps personal pins, drag-and-drop ordering,
 visibility, and appearance in the current browser. Pinned tools have their own
 section; search, category, and clickable tag filters stay close to the tool
@@ -30,7 +30,7 @@ npm run build
 npm run dev
 ```
 
-The package lock resolves the `^0.2.1` SDK ranges to the published `0.2.1`
+The package lock resolves the `^0.2.2` SDK ranges to the published `0.2.2`
 packages. A sibling SDK checkout is only needed when intentionally developing
 the SDK and portal together.
 
@@ -68,7 +68,7 @@ privacy and executable-code warning. Light, dark, and system modes are supported
 ## Production deployment behind Traefik
 
 The committed `compose.yaml` is the shortest production path. Its release
-container downloads the immutable Toolbox 0.4.1 ZIP during the image build,
+container downloads the immutable Toolbox 0.4.2 ZIP during the image build,
 verifies SHA-256 before extracting it, and then copies only the verified static
 files into the pinned unprivileged nginx image. Node.js and a local portal
 assembly are not required on the deployment host.
@@ -119,8 +119,8 @@ The app release should also publish a matching `.sha256` sidecar. The manifest
 must declare the pinned reverse-DNS id and version. Application and portal
 versions are independent.
 
-`release/toolbox.lock.json` is the reviewed v0.4.1 lock. Its URLs and checksums
-pin the published PDF Tools 0.4.1, XSLT Tools 0.4.1, and OneNote Tools 0.3.1
+`release/toolbox.lock.json` is the reviewed v0.4.2 lock. Its URLs and checksums
+pin the published PDF Tools 0.4.2, XSLT Tools 0.4.2, and OneNote Tools 0.3.2
 release bytes. Use
 `release/toolbox.lock.example.json` as the template for a future release and
 verify every downloaded asset before committing updated values. Artifacts may be:
@@ -142,7 +142,7 @@ npm run assemble -- \
   --lock release/toolbox.lock.json \
   --portal-dist dist \
   --output build/toolbox \
-  --archive build/add-ideas-toolbox-0.4.1.zip
+  --archive build/add-ideas-toolbox-0.4.2.zip
 ```
 
 Existing output is refused. Pass `--force` only when replacing those exact
@@ -162,8 +162,8 @@ build/toolbox/
     ├── xslt/
     └── onenote/
 
-build/add-ideas-toolbox-0.4.1.zip
-build/add-ideas-toolbox-0.4.1.zip.sha256
+build/add-ideas-toolbox-0.4.2.zip
+build/add-ideas-toolbox-0.4.2.zip.sha256
 ```
 
 The assembler verifies SHA-256 before opening an artifact, validates every app
@@ -184,7 +184,7 @@ directory separately:
 ```sh
 npm run package:static -- \
   --input build/toolbox \
-  --output artifacts/add-ideas-toolbox-0.4.1.zip
+  --output artifacts/add-ideas-toolbox-0.4.2.zip
 ```
 
 This also emits a `.sha256` sidecar.
@@ -201,9 +201,9 @@ normal local XML/XSLT transformations do not require that permission.
 
 ```sh
 podman build -f Containerfile \
-  -t git.add-ideas.de/zemion/toolbox:0.4.1 .
+  -t git.add-ideas.de/zemion/toolbox:0.4.2 .
 podman run --rm -p 8080:8080 \
-  git.add-ideas.de/zemion/toolbox:0.4.1
+  git.add-ideas.de/zemion/toolbox:0.4.2
 ```
 
 For a direct-port local deployment after assembly, use the separate example:
@@ -220,7 +220,7 @@ docker login git.add-ideas.de
 docker buildx build \
   --platform linux/amd64,linux/arm64 \
   --file Containerfile.release \
-  --tag git.add-ideas.de/zemion/toolbox:0.4.1 \
+  --tag git.add-ideas.de/zemion/toolbox:0.4.2 \
   --tag git.add-ideas.de/zemion/toolbox:0.4 \
   --push .
 ```
@@ -246,8 +246,8 @@ permission to push code, releases, and container packages.
    all three apps, switch between them, and confirm the encoded `toolbox`
    context.
 5. Verify the distribution with
-   `(cd build && sha256sum -c add-ideas-toolbox-0.4.1.zip.sha256)`.
-6. Commit the reviewed lock, tag the toolbox release (for example `v0.4.1`), and
+   `(cd build && sha256sum -c add-ideas-toolbox-0.4.2.zip.sha256)`.
+6. Commit the reviewed lock, tag the toolbox release (for example `v0.4.2`), and
    push the branch and tag to Gitea.
 7. In Gitea, open **Releases → New release**, select the tag, and upload the
    static ZIP plus its `.sha256` file. Do not use a mutable “latest” URL in a