Add xsfire-camp ACP agent entry

[haegyung]

Summary

• Add new ACP agent manifest for xsfire-camp.
• Add xsfire-camp/agent.json under the new directory.
• Point distribution archives to the latest published release v0.9.16.
• Include all required platform binaries:
  • darwin-aarch64
  • darwin-x86_64
  • linux-aarch64
  • linux-x86_64
  • windows-aarch64
  • windows-x86_64

Validation

• Verified agent.json against repository format and field requirements.
• Confirmed release assets exist at:
  • https://github.com/theprometheusxyz/xsfire-camp/releases/tag/v0.9.16

[haegyung]

I added xsfire-camp/icon.svg to this PR and re-pushed as commit 067fdbf. I also re-ran local validations: .github/workflows/build_registry.py passed and verify_agents.py --agent xsfire-camp --auth-check passed. The CI run is still marked action_required with no check jobs attached, so it looks like GitHub Actions approval is still needed for this fork PR workflow to execute fully. No review comments were found on this PR.

[haegyung]

Refreshed the xsfire-camp registry entry to v0.9.17 on the PR head (commit 9e73971). Re-ran local validation on this updated branch:\n\n- uv run --with jsonschema .github/workflows/build_registry.py\n- python3 .github/workflows/verify_agents.py --auth-check --agent xsfire-camp\n\nBoth passed locally, and the agent now resolves against the published v0.9.17 release assets.

[haegyung]

Current PR head (9e73971) is ready and locally validated, but GitHub Actions is blocked at action_required with no attached check jobs.\n\nCould a maintainer please approve/re-run workflow run 23058333179 (Build Registry) for this fork PR?\nRun URL: https://github.com/agentclientprotocol/registry/actions/runs/23058333179\n\nOnce that run executes, this PR should have normal check results for merge review.

[haegyung]

Status update with new evidence:

• The xsfire-camp product-repo GitHub Actions matrix is now fully green, including the macOS x86_64 job: https://github.com/theprometheusxyz/xsfire-camp/pull/2/checks
• The registry entry on this PR still resolves to the published v0.9.17 release assets.

The remaining blocker still appears to be the upstream Build Registry workflow for this fork PR:
https://github.com/agentclientprotocol/registry/actions/runs/23058333179

It is still in action_required with no attached check results. Could a maintainer please approve or re-run that workflow?