feat: add Aegis to ACP registry

[OneStepAt4time]

Register Aegis

Adds Aegis to the ACP registry.

agent.json

• id: aegis
• name: Aegis
• version: 0.6.7
• description: Enterprise orchestration middleware for Claude Code — REST API, MCP server, SSE, webhooks, and dashboard
• license: MIT
• distribution: npx @onestepat4time/aegis@0.6.7 mcp

Checklist

• agent.json follows schema
• icon.svg is 16x16 monochrome (currentColor)
• ACP initialize returns valid authMethods
• Package published on npm (@onestepat4time/aegis)

Closes OneStepAt4time/aegis#3018

[OneStepAt4time]

👋 Gentle ping — this PR has been open since May 10 with no CI checks triggered. I noticed other registration PRs are being merged daily (e.g. #299, #298, #297).

Is there anything we need to adjust in aegis/agent.json or the PR format to get CI running? Happy to make any changes needed.

For context: Aegis is an enterprise orchestration middleware for Claude Code — REST API, MCP, RBAC, audit trail, web dashboard. npm: @onestepat4time/aegis. We have an external tester waiting on v0.6.7 and registry listing would help with discoverability.

Thanks! 🙏

[OneStepAt4time]

👋 Gentle follow-up — pinging again since the last check on May 12 (thank you @OneStepAt4time for the initial ping). Our PR has been open since May 10 with no CI checks triggered, while other registration PRs continue to be merged regularly.

Is there something specific in our submission that needs attention? We are happy to adjust anything to move this forward.

Thanks for your time!

[OneStepAt4time]

👋 Third ping — PR has been open for 10 days now (since May 10). CI still hasn't triggered. We've noticed newer PRs (#302, #301, #300, #299) getting merged within days. Is there something specific blocking this one? Happy to make any changes needed. Thanks for your time.