I think your log shows a continued archive recovery (PITR), not a crash
recovery.
For a crash recovery (automatic recovery), you would see something like
this in the server log:
LOG: database system was interrupted; last known up at 2022-12-23
20:50:13 CET
LOG: database system was not properly shut down; automatic recovery in
progress
In your case, the server started in archive recovery mode (standby mode)
again, restored archived WAL, and recovered the cluster from it.
You must have set the recovery_target_action parameter to 'promote'
(probably via pgbackrest's --target-action parameter), because the
server started in production mode (read-write mode) after a successful
archive recovery.
The server started in standby mode again because the recovery had not
completed, so the standby.signal file had not been deleted from the data
directory.
The server knew that it was an interrupted recovery by looking at the
database cluster state in the control file ("in archive recovery"
instead of "shutdown in recovery").