Rackpad 1.9.0-beta.6

This candidate follows beta.5 with Discovery freshness and
audit-history navigation fixes. It does not add an integration or change stored
inventory, authentication, retention or deployment defaults.

Changes to test

• Discovery refreshes schedules and discovered hosts when entering the page,
  returning focus or visibility, and every 30 seconds while visible (#230).
  Unsaved inspector edits survive refreshed snapshots. Responses overtaken by
  navigation, lab/session changes or local mutations are discarded.
• Audit history counts distinct actors among the loaded results. Administrators
  can load older lab-scoped history beyond the former 500-row window, filter by
  exact action and search stored events with Unicode-aware matching (#237).
  Pagination uses timestamp/ID ordering, including events with equal timestamps.
  Refresh starts again at the newest matching page; a failed older-page request
  retains the loaded rows and can be retried with Load more.
• Audit counts describe the loaded matching results. They are not all-time totals.
  Global listing remains admin-only. Entity-specific reads still require current
  permission for every captured lab; unscoped history remains admin-only.

Upgrade and rollback

Schema is 62. This batch adds no migration or data rewrite. Download a backup
and retain a consistent pre-upgrade database, configuration and encryption key
with the matching previous image. Use that complete pair for rollback.

Both candidate and published-image smoke jobs pin the actual beta.5 image
ghcr.io/kobii-git/rackpad@sha256:5ed4b1ad6481e2d9113740fa176caeb029bfa74cc665309490af64ca4487ae02
(revision fa6bb21bcfbd60eb7a5ed50b43f1b43e064fff52, schema 62), alongside the
historical baselines. Its AMD64 and ARM64 image labels were verified before this
preparation. The next candidate must pass actual 62-to-62 upgrade, restart and
paired rollback on both architectures; inspecting predecessor metadata does not
execute those candidate checks.

Acceptance and publication

Local regressions use disposable databases and synthetic discovery/HTTP fixtures.
They cover automatic due-schedule dispatch, fresh page/focus/poll snapshots,
unsaved edits, pagination and filters, Unicode search, failed-page retry,
delayed filter/lab responses, current grants and keyboard/accessibility behavior.
The original cable create/delete-history fix is separately published and
reporter-confirmed in #211; its new UI follow-ups remain in #237.

Before publication, require the full MCP-enabled browser and Chromium/Firefox
acceptance gates, screenshot determinism, storage compatibility, Net-SNMP and
Linux container-storage checks, exact committed-tree CodeQL approval, hosted
quality/security and both candidate architectures. Preserve existing real-service
notification, Kuma/Glances and Home Assistant checks. Merge, tag and publication
require separate approval; this note does not claim any candidate image exists.

After a fixed image is published, confirm the Discovery result on the reporter's
installation and record audit-page acceptance. A synthetic passing schedule test
does not prove the cause of every reported scheduling failure. Native Proxmox,
physical-provider accuracy and existing mailbox/subscriber confirmations remain
separate acceptance work in #221.