keybased.sock not found on macOS Big Sur 11.4 (MBP 15", 2018)

▶ INFO ignoring error getting keybase status: There were multiple errors: dial unix /Users/juvor/Library/Group Containers/keybase/Library/Caches/Keybase/keybased.sock: connect: no such file or directory; dial unix /Users/juvor/Library/Caches/Keybase/keybased.sock: connect: no such file or directory
▶ INFO ignoring error getting keybase local network stats: There were multiple errors: dial unix /Users/juvor/Library/Group Containers/keybase/Library/Caches/Keybase/keybased.sock: connect: no such file or directory; dial unix /Users/juvor/Library/Caches/Keybase/keybased.sock: connect: no such file or directory
▶ INFO ignoring error getting keybase remote network stats: There were multiple errors: dial unix /Users/juvor/Library/Group Containers/keybase/Library/Caches/Keybase/keybased.sock: connect: no such file or directory; dial unix /Users/juvor/Library/Caches/Keybase/keybased.sock: connect: no such file or directory
▶ INFO ignoring UI logs: There were multiple errors: dial unix /Users/juvor/Library/Group Containers/keybase/Library/Caches/Keybase/keybased.sock: connect: no such file or directory; dial unix /Users/juvor/Library/Caches/Keybase/keybased.sock: connect: no such file or directory

my log id: 14b2cea1eb30d66006d8ca1c

Start by investigating the macOS Big Sur handling of the keybased.sock connection paths shown in the report, using log ID 14b2cea1eb30d66006d8ca1c for context. Reproduce the missing-socket errors and trace which component should create or locate the socket; done means the reported status and network-stat errors no longer occur on the affected setup.