Epic: 014-proxy-mode (v2.1)

[ichinya]

Goal

Generalize proxy mode beyond the first provider-specific experiment.

Scope

• support multi-provider proxy abstractions
• support remote deployment and stronger auth expectations
• preserve auditability and provider-specific accounting detail
• expose proxy operational state through contracts and CLI

Done When

• proxy mode is a first-class documented capability
• multiple providers can be supported behind one proxy architecture
• remote operation requirements are covered in implementation and docs

Dependencies

Blocked by

• Epic: 002-core-proxy (v0.2) #2
• Epic: 013-daemon-mode (v2.0) #7

Enables

• Epic: 020-extensibility (v3.0) #10
• Epic: 030-infrastructure (v4.0) #13

Cross-repo / version gate

• Generalized proxy mode builds on both the first proxy slice and daemonized runtime.

[ichinya]

Planning note after proxy-mode docs/roadmap sync:

• 2.1 / 014-proxy-mode now formalizes the generalized multi-mode proxy subsystem.
• It builds on #2 as the first API proxy (L7) kernel and expands to HTTP proxy / CONNECT, remote/public deployment hardening, and shared auth/accounting policy.
• Passive collectors remain a separate subsystem; they may reuse usage/storage, but should not be merged into transport proxy code.
• This epic is where multi-provider proxy abstractions become first-class and documented.