fix(databases): print a fork description once, and fix doc comment placement

The forked_from row in `fork` and `databases <id>` no longer repeats the
description that the next line prints in full. Move the lineage_row doc
comment back onto lineage_row.

Author: shefeek-jinnah

src/commands/databases.rs

@@ -1793,11 +1793,7 @@ pub fn get(workspace_id: &str, id_or_name: &str, format: &str) {
                 db.default_connection_id.clone().dark_cyan()
             );
             if let Some(f) = &db.forked_from {
-                println!(
-                    "{}{}",
-                    label("forked_from:"),
-                    lineage_row(&LineageEntry::from(f.clone()), false)
-                );
+                println!("{}{}", label("forked_from:"), forked_from_row(f));
                 if let Some(d) = &f.description {
                     println!(
                         "{}{}",
@@ -2170,10 +2166,7 @@ pub fn fork(
             // snapshot); the resolved source id is the fallback for servers
             // that predate lineage.
             match &result.forked_from {
-                Some(f) => println!(
-                    "forked_from: {}",
-                    lineage_row(&LineageEntry::from(f.clone()), false)
-                ),
+                Some(f) => println!("forked_from: {}", forked_from_row(f)),
                 None => println!("forked_from: {}", db.id),
             }
             if let Some(d) = result
@@ -2321,9 +2314,6 @@ fn fetch_lineage(
     .map(LineageResponse::from)
 }
 
-/// One `id (name) — root, forked <date>, snapshot <n>, deleted` line of the
-/// lineage tree and the `forked_from:` rows. The id leads: it's the only field
-/// guaranteed present, and the handle every other databases command accepts.
 /// Longest description shown on a one-line lineage row; the full text is in
 /// `-o json`/`yaml` and on `databases <id>`.
 const DESCRIPTION_SUMMARY_CHARS: usize = 60;
@@ -2348,6 +2338,17 @@ fn indent_continuation(s: &str, width: usize) -> String {
         .join(&format!("\n{}", " ".repeat(width)))
 }
 
+/// A `forked_from:` row. The description is left off because both views that
+/// print this row give it a line of its own.
+fn forked_from_row(f: &ForkedFrom) -> String {
+    let mut entry = LineageEntry::from(f.clone());
+    entry.description = None;
+    lineage_row(&entry, false)
+}
+
+/// One `id (name) — root, forked <date>, snapshot <n>, deleted` line of the
+/// lineage tree and the `forked_from:` rows. The id leads: it's the only field
+/// guaranteed present, and the handle every other databases command accepts.
 fn lineage_row(e: &LineageEntry, root: bool) -> String {
     use crossterm::style::Stylize;
     let mut s = e.database_id.clone().dark_cyan().to_string();
@@ -4211,6 +4212,19 @@ mod tests {
         );
     }
 
+    #[test]
+    fn forked_from_row_leaves_the_description_to_its_own_line() {
+        let row = forked_from_row(&ForkedFrom {
+            database_id: "db_src".to_string(),
+            name: Some("sales".to_string()),
+            snapshot_id: Some(42),
+            forked_at: None,
+            description: Some("q3 what-if".to_string()),
+        });
+        assert!(row.contains("db_src"), "row: {row}");
+        assert!(!row.contains("q3 what-if"), "row: {row}");
+    }
+
     #[test]
     fn description_summary_keeps_one_short_line() {
         assert_eq!(description_summary("q3 what-if"), "q3 what-if");