Skip to content

fix(neovim): migrate Bob read-only proxy - #6

Merged
Attamusc merged 1 commit into
mainfrom
fix-bob-readonly-proxy
Aug 8, 2026
Merged

fix(neovim): migrate Bob read-only proxy#6
Attamusc merged 1 commit into
mainfrom
fix-bob-readonly-proxy

Conversation

@Attamusc

@Attamusc Attamusc commented Aug 8, 2026

Copy link
Copy Markdown
Owner

Summary

  • make an existing Bob-owned Neovim proxy user-writable before channel activation
  • preserve stable-channel selection and Bob's own proxy replacement behavior
  • enforce repair-before-use ordering in the portability contract

Why

The real macOS rollout reached Bob after Homebrew, managed-file apply, mise Node 24, and hunk-review succeeded. Bob 4 could not switch the existing nightly installation to stable because ~/.local/share/bob/nvim-bin/nvim was a user-owned mode-0555 file.

Integrated verification before PR

  • reproduced bob use stable failing at copy_nvim_proxy
  • applied the candidate repair locally
  • ran scripts/check-portability.sh successfully
  • reran the complete ./install.sh lifecycle successfully through Bob stable, Pi package reconciliation, and local-skill linking
  • verified Bob owns ~/.local/share/bob/nvim-bin/nvim at Neovim v0.12.4
  • verified full nvim --headless '+qa', Helix health, baseline commands, hunk-review v0.1.1, and all public Pi package declarations
  • verified Homebrew trust directory mode 0700
  • verified protected repository state and machine-local mise configuration remain intact

Make a legacy Bob-owned Neovim proxy user-writable before selecting the stable channel. Existing macOS installations can leave the proxy mode at 0555, which prevents Bob 4 from replacing it while switching from nightly.

Verify repair ordering in the portability contract. The candidate fix completed the full macOS install lifecycle and automated runtime smoke before publication.
@Attamusc
Attamusc merged commit 9b8f504 into main Aug 8, 2026
1 check passed
@Attamusc
Attamusc deleted the fix-bob-readonly-proxy branch August 8, 2026 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant