🎨 Palette: Improve empty state message for checkpoints

.Jules/palette.md

@@ -5,3 +5,7 @@
 ## 2024-05-24 - CLI Output Scannability and Human-Readability
 **Learning:** In text-based CLI menus, using internal identifiers (like `lesson-1`) and verbose status strings (like `pending` or `completed`) makes lists hard to scan and feels too technical.
 **Action:** When displaying lists of items with states, use familiar visual symbols (like `[x]` vs `[ ]`) and human-readable titles (like "Variables") to improve scannability and create a more friendly, intuitive interface.
+
+## 2024-05-25 - Actionable Empty States in CLI
+**Learning:** Showing a generic "No [items] found" message in a CLI leaves the user at a dead-end, unsure of what to do next. Providing actionable instructions directly in the empty state helps guide them to the right command.
+**Action:** Always pair empty state messages with clear, actionable instructions or commands on how to create the missing resource to improve the user experience and avoid dead-ends.

src/python_learning_orchestrated/cli.py

@@ -223,7 +223,10 @@ def main(
         if args.checkpoint_command == "list":
             checkpoints = checkpoint_store.list_checkpoints()
             if not checkpoints:
-                output_fn("No checkpoints found.")
+                output_fn(
+                    "No checkpoints found. "
+                    "Use 'checkpoint create <name>' to create one."
+                )
                 return
             output_fn(f"Checkpoints ({len(checkpoints)}):")
             for checkpoint in checkpoints: