Fixing Zsh Compinit Errors After Accidental Brew Update with Non-Brew User

[jimmcslim]

Output of brew config

brewer@Mac zsh % brew config
HOMEBREW_VERSION: 4.4.8
ORIGIN: https://github.com/Homebrew/brew
HEAD: e78a0adb4f260913fffdc956cc8c20fb54109feb
Last commit: 2 days ago
Branch: stable
Core tap JSON: 27 Nov 21:50 UTC
Core cask tap JSON: 27 Nov 21:51 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 3.3.6 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.6/bin/ruby
CPU: dodeca-core 64-bit arm_blizzard_avalanche
Clang: 16.0.0 build 1600
Git: 2.39.5 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.1.1-arm64
CLT: 16.1.0.0.1.1729049160
Xcode: N/A
Rosetta 2: false

Output of brew doctor

Your system is ready to brew.

Description of issue

I have three users on my Mac...

admin: the initial setup account, type Admin
jim: my every day account, type Standard
brewer: the account through which I installed Homebrew, type Admin

So, if I want to install software through brew I su brewer and brew install, brew update, brew upgrade, etc my way to victory.

This has worked just fine for quite a while.

However at some recent point in time, I think I accidentally ran brew update or brew upgrade as my jim user. And ever since then opening my shell as jim has resulted in the dreaded compinit errors...

zsh compinit: insecure directories and files, run compaudit for list.
Ignore insecure directories and files and continue [y] or abort compinit [n]?

If I abort and then later run compaudit, I get...

There are insecure directories and files:
/opt/homebrew/share/zsh/site-functions
/opt/homebrew/share/zsh
/opt/homebrew/share/zsh/site-functions/_brew
/opt/homebrew/share/zsh/site-functions/_bun
/opt/homebrew/share/zsh/site-functions/_deno
/opt/homebrew/share/zsh/site-functions/_gh
/opt/homebrew/share/zsh/site-functions/_google_cloud_sdk
/opt/homebrew/share/zsh/site-functions/_just
/opt/homebrew/share/zsh/site-functions/_k9s
/opt/homebrew/share/zsh/site-functions/_kubectl
/opt/homebrew/share/zsh/site-functions/_kubectx
/opt/homebrew/share/zsh/site-functions/_kubens
/opt/homebrew/share/zsh/site-functions/_lsd
/opt/homebrew/share/zsh/site-functions/_pipx
/opt/homebrew/share/zsh/site-functions/_rclone
/opt/homebrew/share/zsh/site-functions/_ruff
/opt/homebrew/share/zsh/site-functions/_rye
/opt/homebrew/share/zsh/site-functions/_starship
/opt/homebrew/share/zsh/site-functions/_uv
/opt/homebrew/share/zsh/site-functions/_uvx

And looking at permissions of /opt/homebrew/share/zsh...

❯ ls -la
total 0
drwxr-xr-x   3 brewer  admin    96  5 Jul  2023 .
drwxr-xr-x  50 brewer  admin  1600 27 Nov 14:48 ..
drwxr-xr-x  20 brewer  admin   640 28 Nov 07:51 site-functions

They seem reasonable to me. But reading up on zsh and completions it suggests that if completions are not owned by root or the current user, or if they are but they are group or world writable, then this fails the zsh completions security checks. If that is the case... then why haven't I always had this issue with completions?

Does anyone have a reliable way of getting completions to work in my installation scenario?