v1.4.47.2 added defensive PEM normalisation but the production env-var is still rejected at crypto.createPrivateKey with error:1E08010C:DECODER routines::unsupported. The base64 body itself appears corrupted along the Coolify → docker-compose → process.env path; normalising the wrapping cannot recover it.
This release adds a one-line diagnostic on the existing parse-failure branch:
APNs key did not parse as PEM: <err> [diag raw_len=… norm_len=…
escaped_newlines=… real_newlines=… begin_markers=… end_markers=…
base64_chars=… other_chars=… sha256_prefix=…]
No secret bytes leave the warning — only character-class counts, structural marker counts, and a 16-char SHA-256 prefix the operator can compare against shasum -a 256 AuthKey_*.p8 locally.
Risk
Zero. Behaviour-preserving — only the warning text gets richer on an already-failing branch.