Merge pull request #145 from johnxie/pr/tutorial-depth-batch-2

docs: deepen tutorial chapters batch 2 (copilot-cli through llama-factory)

Author: johnxie

tutorials/README.md

@@ -17,11 +17,16 @@ Use this guide to navigate all tutorial tracks, understand structure rules, and
 <<<<<<< HEAD
 | Tutorial directories | 188 |
 | Tutorial markdown files | 1705 |
-| Tutorial markdown lines | 632,794 |
+| Tutorial markdown lines | 738,367 |
 =======
+<<<<<<< HEAD
 | Tutorial directories | 188 |
 | Tutorial markdown files | 1705 |
-| Tutorial markdown lines | 632,794 |
+| Tutorial markdown lines | 738,367 |
+=======
+| Tutorial directories | 188 |
+| Tutorial markdown files | 1705 |
+| Tutorial markdown lines | 738,367 |
 
 ## Source Verification Snapshot
 
@@ -38,6 +43,7 @@ Repository-source verification run against tutorial index references (GitHub API
 - JSON: [../discoverability/tutorial-source-verification.json](../discoverability/tutorial-source-verification.json)
 - Script: [../scripts/verify_tutorial_sources.py](../scripts/verify_tutorial_sources.py)
 >>>>>>> origin/main
+>>>>>>> origin/main
 
 ## Content Structure Patterns
 

tutorials/copilot-cli-tutorial/01-getting-started.md

@@ -8,6 +8,9 @@ parent: CopilotKit Tutorial
 
 # Chapter 1: Getting Started with CopilotKit
 
+Welcome to **Chapter 1: Getting Started with CopilotKit**. In this part of **CopilotKit Tutorial: Building AI Copilots for React Applications**, you will build an intuitive mental model first, then move into concrete implementation details and practical production tradeoffs.
+
+
 > Set up CopilotKit in your React application and create your first AI copilot with basic functionality.
 
 ## Overview
@@ -653,4 +656,51 @@ Now that you have a basic copilot running, let's explore how to make your app co
 
 **Ready for Chapter 2?** [Reading App Context](02-app-context.md)
 
-*Generated for [Awesome Code Docs](https://github.com/johnxie/awesome-code-docs)*
+*Generated for [Awesome Code Docs](https://github.com/johnxie/awesome-code-docs)*
+
+## What Problem Does This Solve?
+
+Most teams struggle here because the hard part is not writing more code, but deciding clear boundaries for `text`, `className`, `todo` so behavior stays predictable as complexity grows.
+
+In practical terms, this chapter helps you avoid three common failures:
+
+- coupling core logic too tightly to one implementation path
+- missing the handoff boundaries between setup, execution, and validation
+- shipping changes without clear rollback or observability strategy
+
+After working through this chapter, you should be able to reason about `Chapter 1: Getting Started with CopilotKit` as an operating subsystem inside **CopilotKit Tutorial: Building AI Copilots for React Applications**, with explicit contracts for inputs, state transitions, and outputs.
+
+Use the implementation notes around `copilotkit`, `react`, `note` as your checklist when adapting these patterns to your own repository.
+
+## How it Works Under the Hood
+
+Under the hood, `Chapter 1: Getting Started with CopilotKit` usually follows a repeatable control path:
+
+1. **Context bootstrap**: initialize runtime config and prerequisites for `text`.
+2. **Input normalization**: shape incoming data so `className` receives stable contracts.
+3. **Core execution**: run the main logic branch and propagate intermediate state through `todo`.
+4. **Policy and safety checks**: enforce limits, auth scopes, and failure boundaries.
+5. **Output composition**: return canonical result payloads for downstream consumers.
+6. **Operational telemetry**: emit logs/metrics needed for debugging and performance tuning.
+
+When debugging, walk this sequence in order and confirm each stage has explicit success/failure conditions.
+
+## Source Walkthrough
+
+Use the following upstream sources to verify implementation details while reading this chapter:
+
+- [View Repo](https://github.com/CopilotKit/CopilotKit)
+  Why it matters: authoritative reference on `View Repo` (github.com).
+- [Awesome Code Docs](https://github.com/johnxie/awesome-code-docs)
+  Why it matters: authoritative reference on `Awesome Code Docs` (github.com).
+
+Suggested trace strategy:
+- search upstream code for `text` and `className` to map concrete implementation paths
+- compare docs claims against actual runtime/config code before reusing patterns in production
+
+## Chapter Connections
+
+- [Tutorial Index](index.md)
+- [Next Chapter: Chapter 2: Reading App Context - Making Your App State Visible to AI](02-app-context.md)
+- [Main Catalog](../../README.md#-tutorial-catalog)
+- [A-Z Tutorial Directory](../../discoverability/tutorial-directory.md)