Feedback source
External user feedback (travel multi-agent workshop team).
Problem
The current single-binary distribution bundles everything: interactive shell, MCP server, LSP, brokered auth, OpenTelemetry, ARM management. For CI/CD use cases (data seeding, CRUD, queries, integration test validation), most of this is unnecessary weight and attack surface.
Proposed solution
Ship a separate lightweight, headless CI distribution with:
- Predictable exit codes (stable contract)
- JSON output mode (--output json)
- Workload-identity authentication (federated credentials, no interactive browser)
- Core commands: import, query, assert, CRUD
- No MCP, LSP, brokered authentication, or interactive UI
Implementation options (in priority order)
- Same .NET codebase with trimming/Native AOT — feature-flag the build to exclude MCP/LSP/interactive modules, use .NET publish trimming or NativeAOT for a smaller binary
- Go or Rust reimplementation of the CI-only subset — smallest possible binary, no runtime dependency
Splitting the feature set is more important than changing languages.
Relationship to other issues
Acceptance criteria
Feedback source
External user feedback (travel multi-agent workshop team).
Problem
The current single-binary distribution bundles everything: interactive shell, MCP server, LSP, brokered auth, OpenTelemetry, ARM management. For CI/CD use cases (data seeding, CRUD, queries, integration test validation), most of this is unnecessary weight and attack surface.
Proposed solution
Ship a separate lightweight, headless CI distribution with:
Implementation options (in priority order)
Splitting the feature set is more important than changing languages.
Relationship to other issues
Acceptance criteria