feat: make examples cumulative with carry-forward chain and capstone

Add three new sections to all 14 examples:
- "Carry Forward": what output feeds into later examples (01-10)
- "The Cumulative Path": alternative prompt building on previous output (02-10)
- "Now Try It Yourself": personalized template with transferable pattern (all)
- "Building On" callout connecting back to previous examples (02-10)

Add Example 14: Build Your Personal Agent - capstone that guides reader
through writing their own CLAUDE.md, creating a personal skill, connecting
a messaging channel, setting up automation, and testing end-to-end.

Update README with cumulative path diagram, two usage modes, and example 14.
Update GETTING-STARTED.md with cross-references to relevant examples.

17 files changed, 703+ lines added. The examples now form a coherent
learning path from "see what it can do" to "build your own agent."

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

examples/02-shell-and-files/prompt.md

@@ -5,6 +5,8 @@ same task. Shell output becomes input to the next step automatically.
 
 **OpenClaw equivalent:** `exec` tool with PTY support + read/write/edit file tools.
 
+> **Building on Example 01.** You produced `research-output.md` with raw research data. This example shows how Claude organizes files and runs shell commands. In the Cumulative Path below, you turn that raw research into a structured report directory.
+
 ---
 
 ## The Prompt
@@ -76,3 +78,57 @@ The permission system controls what shell commands are allowed. In the
 `settings.json` in this repo, `rm -rf` and a handful of other destructive
 patterns are blocked by the `pre-tool-use.sh` hook before execution reaches
 the shell. See `examples/09-security-hooks/` for details.
+
+---
+
+## Carry Forward
+
+You now know how to create directories, write files, verify structure, and read back content. Every example from here uses this foundation:
+
+- **Example 03** writes enriched research files with source attribution
+- **Example 05** writes memory files that persist across sessions
+- **Example 10** writes pipeline output and execution logs
+
+---
+
+## The Cumulative Path
+
+> If you ran Example 01, you have `research-output.md`. This prompt turns
+> it into a structured report.
+
+```
+Read research-output.md. Create a directory called 'pipeline-output/research-report/'
+and organize the research into three files:
+
+1. README.md - topic overview, date researched, number of items found
+2. findings.md - the research content reformatted with proper headings,
+   one section per item
+3. sources.md - all URLs and references extracted into a clean list
+
+Then run 'find pipeline-output/research-report/ -type f' to verify all
+three files exist. Show me the contents of README.md.
+```
+
+After running this, your raw research is organized into a report that agents can work with in later examples.
+
+---
+
+## Now Try It Yourself
+
+Replace the demo scaffold with a project structure you actually need:
+
+```
+Create a directory called '[your-project-name]/' with:
+1. [file 1 with specific content]
+2. [file 2 with specific content]
+3. [file 3 with specific content]
+
+Verify the structure and show me [the most important file].
+```
+
+**The pattern you just learned:** describe the directory structure + file contents + verification step. Claude creates it all in one pass and confirms.
+
+Ideas worth trying:
+- A blog post draft with frontmatter and image placeholders
+- A report template with sections matching your company format
+- A project kickoff folder with charter, timeline, and stakeholder list