fix: fall back to --name as label when --description omitted on create

Without this, omitting --description sent no label to the API, which
treats label as required and would return a server-side error.

Also corrects the --name help text example from a qualified
default.public.my_view to just my_view — the API table_name field
expects an unqualified identifier.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: eddietejeda

src/command.rs

@@ -455,7 +455,7 @@ pub enum DatasetsCommands {
 
     /// Create a derived view from a SQL query or saved query
     Create {
-        /// SQL table name the dataset is addressable as (e.g. default.public.my_view)
+        /// SQL table name the dataset is addressable as (e.g. my_view)
         #[arg(long)]
         name: String,
 

src/datasets.rs

@@ -76,10 +76,8 @@ fn create_dataset(
     name: &str,
     source: serde_json::Value,
 ) {
-    let mut body = json!({ "table_name": name, "source": source });
-    if let Some(desc) = description {
-        body["label"] = json!(desc);
-    }
+    let label = description.unwrap_or(name);
+    let body = json!({ "table_name": name, "label": label, "source": source });
 
     let (status, resp_body) = api.post_raw("/datasets", &body);