chore: loose ends from theme/CI session (branch cleanup, act tooling)

[amcheste-ai-agent]

Tracking the leftovers from the 2026-07-08 session that landed #102 (alanchester theme + spaceship prompt + CI tap-trust fix). Everything blocking was merged; these are the non-blocking remainders.

1. Prune 34 stale local branches (local machine)

All 34 are verified merged: 23 are patch-equivalent to develop (git cherry shows no unique commits), the other 11 (release/v1.0.0, fix/remove-mascot-from-readme, the chore/sync-main* trio, etc.) have MERGED PRs on GitHub. They survive only because squash-merge hides ancestry from git branch -d. One-liner:

git branch -vv | grep ': gone]' | awk '{print $1}' | xargs git branch -D

2. Remove leftover colorscheme backup (local machine)

install-dotfiles.sh backed up the pre-vendoring copy to ~/.vim/colors/alanchester.vim.bak. It is byte-identical to the vendored dotfiles/vim/colors/alanchester.vim, safe to delete.

3. act is documented but not installed (repo change)

CLAUDE.md and TESTING.md instruct testing workflows locally with act (act pull_request -j lint), but act is not installed on the machine and is not in Brewfile/Brewfile.ci. Either:

• add brew "act" following the new-tool checklist (Brewfile, Brewfile.ci, smoke-test in validate.yml, README tool table), or
• update the docs if it is intentionally manual.

No action needed (for the record)

• main is behind develop — expected; it catches up at the next /publish-release.
• Homebrew CI breakage (untrusted hashicorp/tap) was fixed in feat: adopt alanchester vim theme and spaceship zsh prompt #102; if other repos share this workflow pattern, they will need the same brew trust fix.

🤖 Generated with Claude Code