review(round3): use production flag description; pin printInitCatalog description columns

TestSetInitUsage now registers --force with the actual production description
("Overwrite an existing .mdsmith.yml instead of leaving it unchanged") so
the PrintDefaults pin matches what a real user sees, not an arbitrary stub.

TestPrintInitCatalog adds description/summary assertions ("Open Knowledge
Format bundle config", "Curated no-llm-tells word-lists") so removing the
description column from printInitCatalog's format string would break the test.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013KgrSLVGA3ioVKvpNkK9ar

Author: claude

cmd/mdsmith/init_unit_test.go

@@ -25,15 +25,17 @@ func TestPrintInitCatalog(t *testing.T) {
 	assert.Contains(t, out, "Starters (mdsmith init --starter <name>):")
 	assert.Contains(t, out, "Packs (mdsmith init --add <name>):")
 	assert.Contains(t, out, "okf")
+	assert.Contains(t, out, "Open Knowledge Format bundle config")
 	assert.Contains(t, out, "wordlists")
+	assert.Contains(t, out, "Curated no-llm-tells word-lists")
 }
 
 // --- setInitUsage ---
 
 func TestSetInitUsage(t *testing.T) {
 	var buf bytes.Buffer
 	fs := flag.NewFlagSet("init", flag.ContinueOnError)
-	fs.BoolVar(new(bool), "force", false, "overwrite existing .mdsmith.yml")
+	fs.BoolVar(new(bool), "force", false, "Overwrite an existing .mdsmith.yml instead of leaving it unchanged")
 	setInitUsage(fs, &buf)
 	fs.Usage()
 	out := buf.String()
@@ -43,7 +45,7 @@ func TestSetInitUsage(t *testing.T) {
 	assert.Contains(t, out, "--force")
 	assert.Contains(t, out, "--list")
 	// Pins that fs.PrintDefaults() ran: description only appears via PrintDefaults, not the static header.
-	assert.Contains(t, out, "overwrite existing .mdsmith.yml")
+	assert.Contains(t, out, "Overwrite an existing .mdsmith.yml instead of leaving it unchanged")
 }
 
 // --- runInit ---