Rackpad 1.9.0-beta.4

This beta adds NUT and Redfish inventory/readings through
the existing explicit adoption, bindings and opt-in health workflow. V2 agents,
automation and provider write-back remain deferred.

NUT uses a bounded native TCP client. Configure nut://host:3493 and a read account.
STARTTLS is required by default and precedes credentials; certificate verification
is enabled by default. Unencrypted LAN transport requires the explicit Allow
unencrypted NUT transport setting. Reserved destinations remain blocked. The
only emitted operations are STARTTLS, USERNAME, PASSWORD, LIST UPS and LIST VAR.
No shutdown, instant command, configuration, LOGIN or primary/master operation can
be emitted. Sessions have a 15-second deadline, bounded ASCII frames, an 8 MiB
response budget and at most 128 UPS records. UPS status, battery charge/runtime,
load and available electrical values are normalized. On-battery/bypass regulation
is degraded; low battery and reported faults are unhealthy. Test/calibration,
unrecognized flags and unavailable/stale driver data stay unknown. Extra driver
variables are never returned or persisted as readings.

Some NUT servers allow LIST reads without validating the supplied USERNAME and
PASSWORD. A successful read therefore confirms data access, not password validity.
Use server/network access controls for that read boundary; Rackpad does not emit
LOGIN or gain a privileged monitoring session to test credentials.

Redfish discovers service-root Systems, Chassis and Managers, with explicit
capability warnings. Hardware identity, firmware and supported legacy/modern
power and thermal resources are read using GET only. Links and pagination stay
on the configured origin and Redfish resource paths; cycles, partial continuation
pages and ambiguous readings reject the collection. Advertised sample timestamps
are preserved. Missing/non-active resources stay unknown. Reads are bounded to
200 followed-resource requests plus the service-root GET, and 20 pages per collection within one 15-second deadline.
Older iDRAC support depends on firmware and account capabilities; this beta
does not assert support for a particular physical server.

Schema is 62. The appended migration adds a validated connection-options
object; only NUT accepts the optional allowUnencrypted boolean. Existing
connections default to empty options and retain TLS requirements. Logical/native
recovery includes options and rejects unsupported values atomically. Rollback
requires the matching pre-upgrade schema-61 database, configuration and encryption
key; an older executable must not open the upgraded database.

Validation uses disposable data and synthetic protocol/API fixtures. A temporary
local TCP/STARTTLS fixture supplements protocol checks; real NUT/Redfish deployment
acceptance remains separate. Publication requires exact committed CodeQL approval,
full MCP/browser and screenshot gates, Net-SNMP interoperability, Linux storage/user
checks, hosted security/quality gates, and AMD64/ARM64 install, preceding-published
image upgrade, persistence/restart and paired rollback. Verify revision/digests
before availability announcements.