agent-sh/agnix v0.52.2

on GitHub

Added

• CC-SET-030 detects local-command entries that Claude Code skips in
  managedMcpServers.

Changed

• Refresh current Claude Code, Codex CLI, OpenCode, Kiro, Cline, Cursor, Amp,
  Cursor/Copilot spec, and Copilot inventory baselines.
• Accept Codex CLI 0.153 configuration keys and synchronize CodeQL v4.37.9
  action pins.

Fixed

• XML-001 now ignores fenced code blocks indented under ordered list items.

Changed

• Claude Code 2.1.261 and ecosystem baseline refresh. Add CC-SET-030
  for local-command entries that Claude Code silently skips in
  managedMcpServers; accept Codex CLI 0.153's tui.auto_recap,
  tui.disable_paste_burst, and experimental context-management keys; and
  refresh Amp, Cline, Cursor, Kiro, OpenCode, and changed specification hashes.
• Maintenance dependencies. Keep CodeQL init/analyze together on v4.37.9
  and refresh the VS Code and docs-site npm lockfiles.
• Claude Code and Codex patch baselines. Advance Claude Code to v2.1.258
  and Codex CLI to rust-v0.152.1. Their primary notes contain only a macOS
  launch repair, remote-session message replay repair, and Guardian Node REPL
  policy fix; neither patch changes a configuration schema agnix validates.
• OpenCode release baseline. Advance OpenCode to v1.18.26; its primary
  release notes contain model-provider, replay, timing, patch metadata, Azure
  sign-in, and desktop bug fixes, with no change to a configuration surface
  agnix validates.
• Tool and specification baselines. Advance Amp to fable-5.1, Claude
  Code to v2.1.257, Codex CLI to rust-v0.152.0, Cursor to 3.18.25, and
  Gemini CLI to v0.58.0 after reviewing their current primary release notes
  and validated configuration surfaces. Refresh the Claude hooks, plugins,
  skills, and subagent documentation hashes after confirming the documented
  event, manifest, frontmatter, and matcher contracts remain covered by the
  existing rules. Claude's new clock and read-boundary preferences are not
  correctness constraints agnix currently validates; Codex's package-style MCP
  names, per-tool output limits, app-server timeout, and opt-in planning flag
  are accepted by the current lenient nested configuration handling. The Amp,
  Cursor, and Gemini markers do not change a schema agnix validates.
• Maintenance dependencies. Update uuid to 1.26.0, synchronize both
  CodeQL steps on 4.37.8, and refresh the pinned setup-java, install-action,
  and Claude Code action revisions.
• Tool release baselines. Advance Amp through amp-on-ios-and-macos, Claude
  Code to v2.1.251, Codex CLI to rust-v0.151.0, Cursor to 3.18.9, OpenCode
  to v1.18.25, and Kiro CLI to 2.20.0 after reviewing their current upstream
  notes and validated configuration surfaces. Claude Code added the
  PreModelSwitch and PostModelSwitch hook events, now accepted by the
  existing CC-HK-001 rule; the other releases do not change a schema agnix
  validates. The
  Codex research inventory now also records its shared MCP rule family and
  accepted .yml, .mcp.json, [mcp_servers.*], and managed-environment
  requirements.toml surfaces, with parity regression assertions.

Fixed

• Floating v0 tag pushes no longer trigger the release pipeline. The
  release workflow matched every v* tag, so the manually pushed floating
  action tag ran the entire pipeline with version "0": the semver verification
  guards stopped crates.io, npm, PyPI, and VS Code, but a junk GitHub release
  was created, a junk Zed update PR was opened, and a version-"0" plugin update
  reached the JetBrains marketplace (all three cleaned up the same day; the
  marketplace update was deleted via the vendor API). The trigger now matches
  only semver-shaped tags (v[0-9]*.[0-9]*.[0-9]*), which the automated
  floating-tag move never produces - and that move uses GITHUB_TOKEN, whose
  events do not start workflows anyway.

Fixed

• uses: agent-sh/agnix@v0 did not resolve. The README, configuration
  guide, and marketplace snippet all instruct agent-sh/agnix@v0, but no v0
  tag or branch has ever existed - every user who copied the documented GitHub
  Action snippet got "unable to resolve action". The repo's own CI never
  noticed because it exercises the action as uses: ./. The floating tag now
  exists (pointing at v0.52.1) and the release workflow force-moves it to each
  new release commit, so the documented ref tracks the latest release the way
  major-version action tags are expected to.

Fixed

• Homebrew tap was 34 releases behind. brew install agnix built v0.18.0
  from source because nothing told the tap about new releases: the tap's
  update-formula.yml listens for a release-published dispatch that the main
  repository never sent. The tap has been dispatched to v0.52.1 manually, the
  vestigial in-repo Formula/agnix.rb copy is synced to match, and release.yml now
  dispatches the tap directly from a new homebrew job. A separate
  release: published workflow could never have worked here: the release is
  published with the default GITHUB_TOKEN, and events created by
  GITHUB_TOKEN do not start workflow runs - which is exactly how the drift
  stayed invisible. The job reuses the existing cross-repo COMMITTER_TOKEN
  (already pushing to other repos in the zed and version-docs jobs), so no new
  secret is needed; the dispatch shape was verified live against the tap's
  update-formula.yml. Manual fallback stays
  gh workflow run update-formula.yml --repo agent-sh/homebrew-agnix -f tag=<tag>.

Changed

• CLAUDE.md/AGENTS.md no longer pin a stale version. The "Current State"
  section claimed v0.37.3 fifteen releases later; nothing in the bookkeeping
  sync touches that line, so it now points at GitHub releases instead of
  hardcoding a number that drifts.