Hey thanks for your response,

Actually this is the crux of the problem. Runit IS starting firewalld. I've got the service directory linked like so: /etc/sv/firewalld/ ---> /etc/service/firewalld/. When I remove that link and reboot, firewalld doesn't run. When I relink it and reboot, voila it runs.

Using the original runnit service run file like so(/etc/sv/firewalld/run):
     

#!/bin/bash
     exec /usr/sbin/firewall

Results in the aforementioned lines in the log about firewalld already running:

     /var/log/firewalld:
     2023-08-14 15:04:31 FATAL ERROR: Not starting FirewallD, already running.
     2023-08-14 15:04:32 FATAL ERROR: Not starting FirewallD, already running.
     2023-08-14 15:04:33 FATAL ERROR: Not starting FirewallD, already running.
     2023-08-14 15:04:34 FATAL ERROR: Not starting FirewallD, already running.

While putting the if/then statement in to see if it's already running results in nothing logged.

Here's another piece of this annoying puzzle: In both cases running sv status firewalld shows it as "down" when it is running:

     # sv status firewalld
     run: firewalld: (pid 27290) 1s; down: log: 1s, normally up, want up
     # firewall-cmd --state
     running

Reloading the service, stopping/starting, restarting, all don't affect anything except the error messages in the log.
Using

     # sv stop firewalld
     ok: down: firewalld: 1s, normally up

Results in the error messages no longer being written.

I think I failed to mention I'm on Chimaera.
Thanks,
YB

P.S. I frickin love Devuan: any help is much appreciated and I hope to pay it forward once I get my bearings.