Add expected output examples for recce-cloud upload

Add real-world CLI output examples to help users verify their CI/CD
setup is working correctly. Shows the detailed output from
recce-cloud upload command including:

- CI environment detection (platform, PR/MR number, branches, etc.)
- Authentication method used (GITHUB_TOKEN/CI_JOB_TOKEN)
- Session creation and artifact upload progress
- Success confirmation with session ID and URLs

Examples added to:
- GitHub CI setup (PR validation)
- GitHub CD setup (production baseline)
- GitLab CI setup (MR validation)
- GitLab CD setup (production baseline)

These examples help users:
- Confirm their setup is working correctly
- Understand what information is automatically detected
- Verify authentication is working
- Get session IDs and URLs for reviewing changes

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
Signed-off-by: even-wei <[email protected]>

Author: even-wei

docs/7-cicd/github/setup-cd.md

@@ -105,6 +105,28 @@ jobs:
 
 ![Recce Cloud showing updated base sessions](../../assets/images/7-cicd/verify-setup-github-cd.png){: .shadow}
 
+#### Expected Output
+
+When the upload succeeds, you'll see output like this in your workflow logs:
+
+```
+─────────────────────────── CI Environment Detection ───────────────────────────
+Platform: github-actions
+Session Type: prod
+Commit SHA: def456ab...
+Source Branch: main
+Repository: your-org/your-repo
+Info: Using GITHUB_TOKEN for platform-specific authentication
+────────────────────────── Creating/touching session ───────────────────────────
+Session ID: abc123-def456-ghi789
+Uploading manifest from path "target/manifest.json"
+Uploading catalog from path "target/catalog.json"
+Notifying upload completion...
+──────────────────────────── Uploaded Successfully ─────────────────────────────
+Uploaded dbt artifacts to Recce Cloud for session ID "abc123-def456-ghi789"
+Artifacts from: "/home/runner/work/your-repo/your-repo/target"
+```
+
 ## Next Steps
 
 **[Setup CI](./setup-ci.md)** to automatically validate PR changes against your updated base session. This completes your CI/CD pipeline by adding automated data validation for every pull request.

docs/7-cicd/github/setup-ci.md

@@ -103,6 +103,32 @@ jobs:
 
 ![Recce Cloud showing PR validation session](../../assets/images/7-cicd/verify-setup-github-ci.png){: .shadow}
 
+#### Expected Output
+
+When the upload succeeds, you'll see output like this in your workflow logs:
+
+```
+─────────────────────────── CI Environment Detection ───────────────────────────
+Platform: github-actions
+PR Number: 42
+PR URL: https://github.com/your-org/your-repo/pull/42
+Session Type: cr
+Commit SHA: abc123de...
+Base Branch: main
+Source Branch: feature/your-feature
+Repository: your-org/your-repo
+Info: Using GITHUB_TOKEN for platform-specific authentication
+────────────────────────── Creating/touching session ───────────────────────────
+Session ID: f8b0f7ca-ea59-411d-abd8-88b80b9f87ad
+Uploading manifest from path "target/manifest.json"
+Uploading catalog from path "target/catalog.json"
+Notifying upload completion...
+──────────────────────────── Uploaded Successfully ─────────────────────────────
+Uploaded dbt artifacts to Recce Cloud for session ID "f8b0f7ca-ea59-411d-abd8-88b80b9f87ad"
+Artifacts from: "/home/runner/work/your-repo/your-repo/target"
+Change request: https://github.com/your-org/your-repo/pull/42
+```
+
 #### Review PR Session
 
 To analyze the PR changes in detail:

docs/7-cicd/gitlab/setup-cd.md

@@ -191,6 +191,28 @@ To enable automatic baseline updates:
 
 ![Recce Cloud showing updated base sessions](../../assets/images/7-cicd/verify-setup-gitlab-cd.png){: .shadow}
 
+#### Expected Output
+
+When the upload succeeds, you'll see output like this in your pipeline logs:
+
+```
+─────────────────────────── CI Environment Detection ───────────────────────────
+Platform: gitlab-ci
+Session Type: prod
+Commit SHA: a1b2c3d4...
+Source Branch: main
+Repository: your-org/your-project
+Info: Using CI_JOB_TOKEN for platform-specific authentication
+────────────────────────── Creating/touching session ───────────────────────────
+Session ID: abc123-def456-ghi789
+Uploading manifest from path "target/manifest.json"
+Uploading catalog from path "target/catalog.json"
+Notifying upload completion...
+──────────────────────────── Uploaded Successfully ─────────────────────────────
+Uploaded dbt artifacts to Recce Cloud for session ID "abc123-def456-ghi789"
+Artifacts from: "/builds/your-org/your-project/target"
+```
+
 #### Verify Scheduled Runs
 
 1. Go to **CI/CD → Schedules**

docs/7-cicd/gitlab/setup-ci.md

@@ -121,6 +121,32 @@ The command automatically uses your GitLab CI environment for authentication (vi
 
 ![Recce Cloud showing MR validation session](../../assets/images/7-cicd/verify-setup-gitlab-ci.png){: .shadow}
 
+#### Expected Output
+
+When the upload succeeds, you'll see output like this in your pipeline logs:
+
+```
+─────────────────────────── CI Environment Detection ───────────────────────────
+Platform: gitlab-ci
+MR Number: 4
+MR URL: https://gitlab.com/recce/staging-jaffle-shop-snowflake/-/merge_requests/4
+Session Type: cr
+Commit SHA: c928e3d5...
+Base Branch: main
+Source Branch: feature/replace-recce-cicd-component-with-recce-cloud-cli
+Repository: recce/staging-jaffle-shop-snowflake
+Info: Using CI_JOB_TOKEN for platform-specific authentication
+────────────────────────── Creating/touching session ───────────────────────────
+Session ID: f8b0f7ca-ea59-411d-abd8-88b80b9f87ad
+Uploading manifest from path "target/manifest.json"
+Uploading catalog from path "target/catalog.json"
+Notifying upload completion...
+──────────────────────────── Uploaded Successfully ─────────────────────────────
+Uploaded dbt artifacts to Recce Cloud for session ID "f8b0f7ca-ea59-411d-abd8-88b80b9f87ad"
+Artifacts from: "/builds/recce/staging-jaffle-shop-snowflake/target"
+Change request: https://gitlab.com/recce/staging-jaffle-shop-snowflake/-/merge_requests/4
+```
+
 #### Review MR Session
 
 To analyze the MR changes in detail:
@@ -129,12 +155,6 @@ To analyze the MR changes in detail:
 - Find the MR session that was created
 - Launch Recce instance to explore data differences
 
-Or use the session launch URL from the pipeline output:
-```bash
-# Pipeline output example
-RECCE_SESSION_LAUNCH_URL: https://cloud.reccehq.com/launch/abc123
-```
-
 ## Troubleshooting
 
 ### Missing dbt files