v2.2.1

A compatibility patch: a bwrap mount-ordering fix, an AUR build fix for
LTO-enabled Arch systems, and a launch warning for opencode 2.x.

Fixed

• Private home no longer fails when a command's binary lives under a
  directory that is also being bound (#138, thanks @IgorEmerick, #139).
  With ai-memory and the Claude Code installer symlink both in
  ~/.local/bin, binding the whole directory and then the symlink made
  bwrap follow a dangling symlink while creating the mount point and abort.
  Command paths that sit under another collected path are now skipped —
  they are visible through the parent bind anyway, and the result is
  independent of path order.

• AUR source package builds again with lto in makepkg.conf (#140,
  thanks @nnorakk for the pinpoint report). Arch's default enables LTO
  globally, and ring's C/assembly cannot be consumed as GCC-LTO objects at
  link time. The PKGBUILD now opts out with options=('!debug' '!lto');
  already published to the AUR as 2.2.0-2 and carried forward.

Added

• Launch warning when opencode runs without --standalone (#137,
  thanks @naranma). opencode 2.x is a client of a shared background server that cannot
  persist across a one-shot jail with a tmpfs home; if startup hangs at
  "Starting background server...", add --standalone to the command. Also
  documented in the README's Troubleshooting section.

Checksums (SHA256)

ef8f765bc00ebda47748464a8034eb288d402120aa33364f2dd8dda6878ebbdc  ai-jail-linux-x86_64.tar.gz
3fc1645ee03effecba8e76c407272c443442abdac78830f5f16f3adf71912819  ai-jail-macos-aarch64.tar.gz

Install

brew tap akitaonrails/tap && brew install ai-jail
yay -S ai-jail-bin
cargo install --locked ai-jail