Rackpad 1.9.0-beta.7

This batch follows beta.6 with complete audit summaries, portable hardware
templates, chassis finishes and per-face rotation. Schema is 62.

Changes to test

• As an administrator, open Audit log in a lab with more than 100 entries. The
  counters cover all stored events matching the search and action filters. The
  action selector covers the complete scoped history. Scrolling loads older
  matching pages automatically; a failed request leaves loaded rows available
  and exposes Retry. Changing the lab or filters discards obsolete responses.
  Global listing and summaries remain admin-only; entity reads keep their
  existing current-grant and captured-lab rules (#241).
• In Device types, select a saved hardware template and choose Export saved
  template. On another installation, choose a local Import device type and
  Import template. The new library copy has an independent ID. Select the
  reported name from Templates to edit it. Import does not replace the open
  draft, assign defaults or update devices (#164).
• Choose a Chassis skin and Orientation on either template face. Automatic
  retains the theme; Graphite, Silver and Ivory apply fixed chassis palettes.
  Existing explicit item colors, selection and linked-port indicators remain.
  Save/reload, export/import and Preview/Apply should retain these settings.
• For an individual device, open Physical layout, choose Edit, then select
  the face, skin and orientation. Preview and Apply save a device-specific layout.
  Quarter turns also work on directly mounted equipment. Rotation changes artwork
  inside the assigned footprint; adjust rack Height (U) and Column span separately
  when changing the physical mount. Verify cabling and SVG/PNG exports, and try
  rotated drag, resize, keyboard movement and Undo/Redo in the template editor.
• Static serving and lint matching use patched glob/minimatch releases. The
  dependency gate checks cancellation, bounded pattern preprocessing and
  legitimate matching through the installed consumers.

Upgrade and rollback

There is no SQL migration, inventory rewrite, retention change or new public
route. Skins and rotation are optional metadata in existing schema-v1 face JSON;
missing values keep the previous appearance. Older binaries may discard the
optional metadata when rewriting layouts.

Before upgrading, retain a consistent database/volume snapshot, configuration,
encryption key and matching previous image. Use that complete pair for rollback.
The immediately preceding image is beta.6 at revision
8f2a32ac77db8167fecb468c6091e12720a0bbae, schema 62:
ghcr.io/kobii-git/rackpad@sha256:2ec9251b0db8d63dcaa009a465fd879c9487989ff90b00489641f7f728fce1d5.
Candidate and publication checks must exercise this actual 62-to-62 upgrade,
restart and paired rollback on AMD64 and ARM64 alongside the historical fixtures.

Reporter acceptance

The earlier Discovery and Proxmox fixes remain separate real-installation checks:

• #230: after upgrading, check Discovery on entry, after returning focus and
  after a due automatic run. Compare the displayed timestamp without a hard
  refresh. Preserve unsaved inspector edits and include the exact version and
  sanitized reproduction details for any remaining scheduling failure.
• #208: retry the Proxmox API-token connection. Check host management IPs,
  actual interfaces and permission warnings in the preview, then import twice
  and verify existing port IDs and cables survive without duplicates. The
  reporter's JSON-import confirmation does not establish API-token acceptance.
• #164 and #241: try the controls on actual templates and audit history. The
  automated synthetic cases do not replace reporter confirmation.

Publication requires the combined local/hosted quality and security gates,
independent authorization/source review, Chromium/Firefox acceptance, storage,
Net-SNMP, Linux container storage, screenshot determinism and both architecture
upgrade/restart/rollback checks. This document describes the release contract;
publication status is recorded by the tagged release and its workflow runs.