Question: should cli include a raw authenticated API command alongside spec-generated commands?
Possible shape:
- arbitrary method/path calls
- request body input
- optional custom headers
Value: this would provide a fallback for unsupported endpoints, debugging, and day-zero access to new API surface, while keeping spec-generated commands as the primary interface.
The main architecture question is whether this fits the intended CLI model, or whether the generated command surface should remain the only supported access pattern.
If this direction makes sense, I can propose a minimal design.
Question: should cli include a raw authenticated API command alongside spec-generated commands?
Possible shape:
Value: this would provide a fallback for unsupported endpoints, debugging, and day-zero access to new API surface, while keeping spec-generated commands as the primary interface.
The main architecture question is whether this fits the intended CLI model, or whether the generated command surface should remain the only supported access pattern.
If this direction makes sense, I can propose a minimal design.