Problem
To check if AegisFlow is running correctly today, you have to curl /health, curl /admin/v1/providers, and maybe check the dashboard. Three commands for something that should be one.
Acceptance criteria
Files to touch
cmd/aegisctl/status.go (new, or extend main.go if there is already a stub)
cmd/aegisctl/main.go to wire the subcommand
cmd/aegisctl/status_test.go (new)
How to test locally
# Start AegisFlow
./bin/aegisflow --config configs/demo.yaml
# In another terminal
./bin/aegisctl status
# Expected: a short table with all components green
./bin/aegisctl status --json
# Expected: JSON with the same fields
Notes
Look at how the existing admin API endpoints are structured in internal/admin/admin.go. You should not need any new admin endpoints for this, just new client code that calls the existing ones.
Problem
To check if AegisFlow is running correctly today, you have to curl
/health, curl/admin/v1/providers, and maybe check the dashboard. Three commands for something that should be one.Acceptance criteria
aegisctl status--jsonflag for machine-readable outputFiles to touch
cmd/aegisctl/status.go(new, or extendmain.goif there is already a stub)cmd/aegisctl/main.goto wire the subcommandcmd/aegisctl/status_test.go(new)How to test locally
Notes
Look at how the existing admin API endpoints are structured in
internal/admin/admin.go. You should not need any new admin endpoints for this, just new client code that calls the existing ones.