prepare 0.2.27: CLI and window fixes, release tooling, deps

[hewigovens]

Groundwork for the 0.2.27 release (the version bump + release notes land on the release commit, not here).

CLI & windows

• Route jayjay <repo> to the running instance, resolved from its bundle via a single ps -A call (no more LaunchServices guessing between a stale /Applications release and the running build).
• Silently refresh the installed ~/.local/bin/jayjay symlink to the current build on launch.
• Open a window when jayjay <repo> runs while the app is running with no window (previously it just activated an empty app).
• Self-contained debug build (ENABLE_DEBUG_DYLIB=NO) so the CLI-launched build no longer crashes on a missing JayJay.debug.dylib.

UI

• Strip command failed: / Error: wrappers so command errors (e.g. resolve-conflict failures) read as plain sentences.

Release tooling

• One-command version bumps: just set-version <version> <build> writes every source of truth; just release runs a check-version guard that aborts on drift.
• Render the Homebrew cask from dist/jayjay.rb.template (single source of truth) — fixes the zap bundle id, adds the binary stanza (CLI on PATH for brew users) and auto_updates.

Deps

• Pin tree-sitter 0.26.9, similar 3.1.1, tree-sitter-swift 0.7.3.

Verified: cargo build/clippy/test --workspace, just build, just test-app, just lint all green.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1358966394

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid duplicating the main repo window

When the requested repo is already loaded in the SwiftUI WindowGroup but that window has not registered a representedURL yet (for example while it is still loading, or when it is showing RepoInitErrorView and never reaches RepoContentView.onAppear), this lookup misses the existing main window. Since mainWindowPath was removed, a repeated CLI/recent-repo open for the same path now falls through and creates a second host window instead of fronting the existing one; keep an explicit main-window path or assign the represented URL as soon as the root repo window is selected.

Useful? React with 👍 / 👎.