Fix 100MB false positive, add missing cobra usage error patterns

client.go: read one extra byte after LimitReader to distinguish
  'exactly 100MB response' from 'truncated at 100MB' — no false positive

errors.go: add 'requires ' (MinimumNArgs) and 'invalid argument'
  (ValidArgsFunction) to isCobraUsageError patterns

Author: ilyazub

pkg/api/client.go

@@ -64,8 +64,12 @@ func (c *Client) doGet(endpoint string, params map[string]string) ([]byte, error
 	if err != nil {
 		return nil, &clierrors.NetworkError{Message: "Failed to read response: " + err.Error()}
 	}
+	// Detect truncation: try reading one more byte; if it succeeds the body exceeded the limit.
 	if len(body) == maxBytes {
-		return nil, &clierrors.ApiError{Message: "Response exceeded 100 MB limit"}
+		var extra [1]byte
+		if n, _ := resp.Body.Read(extra[:]); n > 0 {
+			return nil, &clierrors.ApiError{Message: "Response exceeded 100 MB limit"}
+		}
 	}
 
 	if resp.StatusCode != http.StatusOK {

pkg/errors/errors.go

@@ -60,8 +60,10 @@ func errorCode(err error) string {
 func isCobraUsageError(err error) bool {
 	msg := err.Error()
 	return strings.HasPrefix(msg, "accepts ") ||
+		strings.HasPrefix(msg, "requires ") ||
 		strings.HasPrefix(msg, "unknown command") ||
-		strings.HasPrefix(msg, "required flag")
+		strings.HasPrefix(msg, "required flag") ||
+		strings.HasPrefix(msg, "invalid argument")
 }
 
 // PrintError writes a structured JSON error to stderr.