Repository navigation
docs: default version bump to patch in AGENTS.md - #2
Merged
Merged
Conversation
softmaxe
added a commit
that referenced
this pull request
Oct 15, 2026
## Summary Maintenance pass looking for unnecessary tests and code that is hard to maintain long-term. The repo is already lean (the demo was removed in #5), so the changes are small: - **raycast/** — each of the five scripts carried the same 20-line binary lookup (an `if/elif` chain plus a `for` loop over candidates). It is replaced with `path+=(...)` + `whence -p ferry`, so each script drops from 39 to 24 lines. Scripts stay self-contained so the README's "copy the five files" / "copy a script for Space 6+" workflow still works. Lookup order is unchanged: `FERRY_BINARY` → inherited `PATH` → `/opt/homebrew/bin` → `/usr/local/bin` → `~/.local/bin` → `build/` next to `raycast/`. The missing-binary message and exit status 127 are unchanged. - **src/ferry.m** — `g_verbose` was a file-scope global used only inside `main`; it is now a local. - **tests/follow.m** — names the fullscreen space type (`SPACE_TYPE_FULLSCREEN`) instead of using the literal `4` twice, matching `ferry.m`. ## Reviewed and kept - `tests/cli.sh`: each case covers a distinct argument-parsing branch (non-numeric, zero, overflow, missing value, unknown option, extra index). None are redundant. - `tests/follow.m`: manual-only, but it is the only test of real move and Follow behavior (the issue #2 regression). - `macho_find_symbol` and the focus code mirror yabai and stay as they are, per AGENTS.md "upstream first". ## Test plan - Ran a Raycast script under zsh with stub binaries for each lookup case: nothing found (exit 127 + message), `build/` fallback, `~/.local/bin` beating `build/`, `PATH` beating fallbacks, `FERRY_BINARY` winning, a missing `FERRY_BINARY` erroring, and invocation from another cwd. All match the old order. - The `.m` changes could not be compiled locally (Linux container). CI builds them on macOS 26 with `-Werror`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01P1i79aMaG5M7eTyaXZuVS9 --- _Generated by [Claude Code](https://claude.ai/code/session_01P1i79aMaG5M7eTyaXZuVS9)_ Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When the owner asks to update or bump the version without naming one, agents bump the patch.
Evidence
This changes only the docs; there is no code or test to run.
merge-and-release.mdstep 1)After: "update the version" →
VERSION0.0.1 → 0.0.2, whatever the commit typesMerge Danger
Door: two-way
Blast Radius: agent-only
Affects only how agents choose a version number when the owner gives none. An explicitly named version still wins.