[Export Audit] Internal result interfaces in `src/cli.ts` exported but never imported

[github-actions]

API Surface Issue

Category

Unused export — internal result types exposed unnecessarily

Summary

• File: src/cli.ts
• Symbols: AgentImageResult, ApiProxyValidationResult, FlagValidationResult, LocalhostProcessingResult
• Issue: Four result interfaces are exported from cli.ts but are only used as return types within cli.ts itself. No other module imports them.

Evidence

# Defined and used only in cli.ts — 0 external imports:
cli.ts:182  export interface AgentImageResult { ... }
cli.ts:207  ): AgentImageResult {                         // used internally

cli.ts:267  export interface ApiProxyValidationResult { ... }
cli.ts:293  ): ApiProxyValidationResult {                 // used internally

cli.ts:735  export interface FlagValidationResult { ... }
cli.ts:709  }): FlagValidationResult {                    // used internally

cli.ts:1008 export interface LocalhostProcessingResult { ... }
cli.ts:1034 ): LocalhostProcessingResult {                // used internally

No imports of these types were found in any other src/**/*.ts file or tests/**/*.ts file.

Recommended Fix

Remove the export keyword from all four interfaces. They are private implementation details of the CLI argument-processing pipeline and do not need to be part of the module's public contract.

Impact

• Dead code risk: Medium — clutters the public API surface of the CLI's largest module
• Maintenance burden: Medium — exported interfaces imply stability guarantees for callers that don't exist

---

Detected by Export Audit workflow. Triggered by push to main on 2026-05-04

Generated by API Surface & Export Audit · ● 292.5K · ◷

• expires on Jun 3, 2026, 2:41 PM UTC

[lpcox]

Addressed by PR #2509 (fix/export-audit-unused-exports)