docs: add gitignore guidance for users who generate log files with --log-dir

Users following the getting-started guide create ralph_logs/ via --log-dir
but had no guidance on excluding them from version control. Added:
- ralph_logs/ to .gitignore
- A tip in the getting-started guide after the first --log-dir usage
- A "What files should I commit?" FAQ entry with a clear table

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: 2 people

.gitignore

@@ -5,4 +5,5 @@ dist/
 .venv/
 .claude/
 .codex/
-site/
+site/
+ralph_logs/

docs/faq.md

@@ -119,6 +119,23 @@ Each loop operates independently with its own prompt and checks.
 
 ## Configuration
 
+### What files should I commit?
+
+Ralphify creates several files and directories. Here's what belongs in version control and what doesn't:
+
+| File / directory | Commit? | Why |
+|---|---|---|
+| `ralph.toml` | **Yes** | Loop configuration — shared across your team |
+| `PROMPT.md` | **Yes** | The prompt is the core of your loop |
+| `.ralph/` | **Yes** | Checks, contexts, and instructions — project config your team should share |
+| `ralph_logs/` | **No** | Iteration output logs — large, machine-specific, regenerated every run |
+
+Add `ralph_logs/` to your `.gitignore`:
+
+```bash
+echo "ralph_logs/" >> .gitignore
+```
+
 ### Should I commit the `.ralph/` directory?
 
 Yes. It contains your checks, contexts, and instructions — this is project configuration that your team should share:

docs/getting-started.md

@@ -100,6 +100,13 @@ ls ralph_logs/
 cat ralph_logs/001_*.log
 ```
 
+!!! tip "Add `ralph_logs/` to `.gitignore`"
+    Log files are useful for debugging but shouldn't be committed. Add them to your `.gitignore`:
+
+    ```bash
+    echo "ralph_logs/" >> .gitignore
+    ```
+
 If the agent produced useful work, you're ready to add guardrails.
 
 ## Step 5: Add a test check