v0.10.0

Highlights

The secure HTTP client takes per-instance timeouts. VaultHttpClientInterface::withTimeout(int $seconds) joins withReason() and withAuthentication() as an immutable wither. The override is baked into the hardened inner Guzzle client through the shared factory, so it covers every send path — plain and authenticated — while connect_timeout deliberately stays platform-managed: the override bounds the transfer, not the TCP/TLS handshake. Consumers with long-running upstream calls (large AI image generations were the trigger) no longer die at the instance-wide TYPO3 HTTP timeout.

Automation analytics tell the truth again. TYPO3's CLI bootstrap installs a CommandLineUserAuthentication — a BackendUserAuthentication subclass — so the backend-user-first check in the access-control service stamped every CLI and messenger-worker secret read as backend. The analytics module then saw zero automated reads and flagged busy automation secrets as "Automation-stale". CLI detection now runs first, worker reads count as automated, and a latent constant-case fatal in the legacy CLI check went with it. Historic audit rows are untouched (tamper-evident chain); the flag clears as new correctly-classified reads enter the window.

Developer ergonomics. runTests.sh now defaults to the upper supported PHP bound (8.5) instead of 8.2 — local runs without -p exercise the newest platform, while CI keeps pinning its full matrix explicitly.

Compatibility

No schema changes, no breaking API changes. withTimeout() is additive; existing consumers are unaffected.