Update CI/CD documentation to use recce-cloud CLI

Replace GitHub Actions and GitLab CI/CD components with the new
recce-cloud CLI for simpler, more direct CI/CD integration.

Changes:
- Replace DataRecce/recce-cloud-cicd-action with recce-cloud upload command
- Replace GitLab component with direct CLI usage
- Remove RECCE_API_TOKEN requirements (auto-detects GITHUB_TOKEN/CI_JOB_TOKEN)
- Simplify authentication - no manual token setup needed
- Add platform-specific verification images for GitHub/GitLab CI/CD
- Update configuration examples to show CLI flags instead of component inputs

Benefits:
- Simpler setup without external dependencies
- Consistent approach across GitHub and GitLab
- Automatic platform and context detection
- Direct pip install + CLI execution

🤖 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

@@ -70,9 +70,10 @@ jobs:
         env:
           DBT_ENV_SECRET_KEY: ${{ secrets.DBT_ENV_SECRET_KEY }}
 
-      - name: Update Recce Cloud Base Session
-        uses: DataRecce/[email protected]
-        # This action automatically uploads artifacts to Recce Cloud
+      - name: Upload to Recce Cloud
+        run: |
+          pip install recce-cloud
+          recce-cloud upload --type prod
 ```
 
 ### 2. Artifact Preparation Options
@@ -102,7 +103,7 @@ jobs:
 - ✅ **Workflow completes** without errors in Actions tab
 - ✅ **Base session updated** in Recce Cloud
 
-![Recce Cloud showing updated base sessions](/assets/images/7-cicd/verify-setup-cd.png){: .shadow}
+![Recce Cloud showing updated base sessions](../../assets/images/7-cicd/verify-setup-github-cd.png){: .shadow}
 
 ## Next Steps
 

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

@@ -70,9 +70,10 @@ jobs:
         env:
           DBT_ENV_SECRET_KEY: ${{ secrets.DBT_ENV_SECRET_KEY }}
 
-      - name: Update Recce PR Session
-        uses: DataRecce/[email protected]
-        # This action automatically creates a PR session in Recce Cloud
+      - name: Upload to Recce Cloud
+        run: |
+          pip install recce-cloud
+          recce-cloud upload
 ```
 
 ### 2. Artifact Preparation Options
@@ -100,7 +101,7 @@ jobs:
 - ✅ **Workflow completes** without errors in Actions tab
 - ✅ **PR session updated** in Recce Cloud
 
-![Recce Cloud showing PR validation session](/assets/images/7-cicd/verify-setup-ci.png){: .shadow}
+![Recce Cloud showing PR validation session](../../assets/images/7-cicd/verify-setup-github-ci.png){: .shadow}
 
 #### Review PR Session
 

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

@@ -22,25 +22,15 @@ You need `manifest.json` and `catalog.json` files (dbt artifacts) for Recce Clou
 
 ### 1. Core Workflow
 
-GitLab's CD setup uses the same Recce Cloud component as CI, but with different trigger rules. Add to your `.gitlab-ci.yml`:
+Add to your `.gitlab-ci.yml`:
 ```yaml
-include:
-  - component: gitlab.com/recce/recce-cloud-cicd-component/[email protected]
-    inputs:
-      stage: upload
-
 stages:
   - build
   - upload
 
 variables:
   DBT_TARGET_PROD: "prod"
 
-# Disable the default component job
-recce-cloud-upload:
-  rules:
-    - when: never
-
 # Production build - runs on schedule or manual trigger
 prod-build:
   stage: build
@@ -65,11 +55,14 @@ prod-build:
       when: manual
 
 # Production Recce upload
-recce-cloud-upload-prod:
-  extends: recce-cloud-upload
-  needs:
-    - job: prod-build
-      artifacts: true
+recce-upload-prod:
+  stage: upload
+  image: python:3.11-slim
+  script:
+    - pip install recce-cloud
+    - recce-cloud upload --type prod
+  dependencies:
+    - prod-build
   rules:
     - if: $CI_PIPELINE_SOURCE == "schedule"
     - if: $CI_PIPELINE_SOURCE == "push" && $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
@@ -85,22 +78,12 @@ This configuration:
 
 ### 2. Unified CI/CD Configuration
 
-The Recce Cloud component can handle both CI (MR validation) and CD (base session updates) in a single configuration. Here's the combined approach:
+You can handle both CI (MR validation) and CD (base session updates) in a single configuration:
 ```yaml
-include:
-  - component: gitlab.com/recce/recce-cloud-cicd-component/[email protected]
-    inputs:
-      stage: upload
-
 stages:
   - build
   - upload
 
-# Disable the default component job
-recce-cloud-upload:
-  rules:
-    - when: never
-
 # MR build - runs on merge requests
 mr-build:
   stage: build
@@ -135,28 +118,34 @@ prod-build:
     - if: $CI_PIPELINE_SOURCE == "push" && $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
 
 # MR Recce upload
-recce-cloud-upload-mr:
-  extends: recce-cloud-upload
-  needs:
-    - job: mr-build
-      artifacts: true
+recce-upload-mr:
+  stage: upload
+  image: python:3.11-slim
+  script:
+    - pip install recce-cloud
+    - recce-cloud upload
+  dependencies:
+    - mr-build
   rules:
     - if: $CI_PIPELINE_SOURCE == "merge_request_event"
 
 # Production Recce upload
-recce-cloud-upload-prod:
-  extends: recce-cloud-upload
-  needs:
-    - job: prod-build
-      artifacts: true
+recce-upload-prod:
+  stage: upload
+  image: python:3.11-slim
+  script:
+    - pip install recce-cloud
+    - recce-cloud upload --type prod
+  dependencies:
+    - prod-build
   rules:
     - if: $CI_PIPELINE_SOURCE == "schedule"
     - if: $CI_PIPELINE_SOURCE == "push" && $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
 ```
 
 This unified approach:
 
-- Uses the same component for both CI and CD
+- Uses the same `recce-cloud upload` command for both CI and CD
 - Separates MR validation from production updates via `rules`
 - Maintains different dbt targets for each environment
 - Reduces configuration duplication
@@ -200,7 +189,7 @@ To enable automatic baseline updates:
 - ✅ **Pipeline completes** without errors in CI/CD → Pipelines
 - ✅ **Base session updated** in Recce Cloud
 
-![Recce Cloud showing updated base sessions](../../assets/images/7-cicd/verify-setup-cd.png){: .shadow}
+![Recce Cloud showing updated base sessions](../../assets/images/7-cicd/verify-setup-gitlab-cd.png){: .shadow}
 
 #### Verify Scheduled Runs
 
@@ -253,7 +242,7 @@ recce-cloud-upload-prod:
 
 ## Complete Example
 
-See the [complete working example](https://gitlab.com/recce/jaffle-shop-snowflake/-/blob/main/.gitlab-ci.yml) showing unified CI/CD configuration with the Recce Cloud component.
+Here's a complete working example with unified CI/CD configuration using `recce-cloud` CLI. This example can be used as a reference for your own setup.
 
 ## Next Steps
 

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

@@ -24,14 +24,9 @@ You need `manifest.json` and `catalog.json` files (dbt artifacts) for Recce Clou
 
 Add to your `.gitlab-ci.yml`:
 ```yaml
-include:
-  - component: gitlab.com/recce/recce-cloud-cicd-component/[email protected]
-    inputs:
-      stage: test
-
 stages:
   - build
-  - test
+  - upload
 
 variables:
   DBT_TARGET: "ci"
@@ -56,46 +51,47 @@ dbt-build:
     expire_in: 1 week
   rules:
     - if: $CI_PIPELINE_SOURCE == "merge_request_event"
+
+recce-upload:
+  stage: upload
+  image: python:3.11-slim
+  script:
+    - pip install recce-cloud
+    - recce-cloud upload
+  dependencies:
+    - dbt-build
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
 ```
 
-The included Recce Cloud component automatically:
+The `recce-cloud upload` command automatically:
 
+- Detects your GitLab CI environment
 - Creates a session in Recce Cloud for the merge request
 - Uploads your dbt artifacts (`manifest.json` and `catalog.json`)
-- Provides session URL for validation review
+- Links the session to your MR
+
+### 2. Configuration Options
 
-### 2. Component Configuration Options
+The `recce-cloud upload` command supports customization via flags:
 
-The component accepts optional inputs for customization:
 ```yaml
-include:
-  - component: gitlab.com/recce/recce-cloud-cicd-component/[email protected]
-    inputs:
-      stage: test                        # Pipeline stage (default: test)
-      dbt_target_path: target            # Path to dbt artifacts (default: target)
-      base_branch: main                  # Base branch for comparison (default: main)
-      gitlab_token: $CUSTOM_GITLAB_TOKEN # Custom GitLab token (default: $CI_JOB_TOKEN)
+recce-upload:
+  script:
+    - pip install recce-cloud
+    - recce-cloud upload --target-path custom-target --type cr
 ```
 
-**Default Configuration** (shown in example above):
+**Available options:**
 
-- Component uses `$CI_JOB_TOKEN` automatically (no manual token setup required)
-- Uploads from `target/` directory by default
-- Compares against `main` branch
+- `--target-path`: Path to dbt artifacts directory (default: `target`)
+- `--type`: Session type - `cr`, `prod`, or `dev` (auto-detected by default)
+- `--cr`: Override MR number (auto-detected by default)
+- `--dry-run`: Preview what would be uploaded without actually uploading
 
-**Custom Token** (optional):
+**Authentication:**
 
-If you need to use a custom GitLab token instead of the default `$CI_JOB_TOKEN`:
-
-1. Create a [Project Access Token](../gitlab-pat-guide.md) with `api` scope
-2. Add it as a [CI/CD variable](https://docs.gitlab.com/ee/ci/variables/) in your project
-3. Reference it in the component inputs:
-```yaml
-include:
-  - component: gitlab.com/recce/recce-cloud-cicd-component/[email protected]
-    inputs:
-      gitlab_token: $CUSTOM_GITLAB_TOKEN
-```
+The command automatically uses your GitLab CI environment for authentication (via `CI_JOB_TOKEN`). No additional token setup required.
 
 ### 3. Artifact Preparation Options
 
@@ -123,7 +119,7 @@ include:
 - ✅ **MR session updated** in Recce Cloud
 - ✅ **Session URL** appears in pipeline job output
 
-![Recce Cloud showing MR validation session](../../assets/images/7-cicd/verify-setup-ci.png){: .shadow}
+![Recce Cloud showing MR validation session](../../assets/images/7-cicd/verify-setup-gitlab-ci.png){: .shadow}
 
 #### Review MR Session
 
@@ -187,24 +183,18 @@ dbt-build:
 
 Here's a full working example combining dbt build and Recce validation:
 ```yaml
-include:
-  - component: gitlab.com/recce/recce-cloud-cicd-component/[email protected]
-    inputs:
-      stage: test
-
 stages:
   - build
-  - test
+  - upload
 
 variables:
   DBT_TARGET: "ci"
 
 dbt-build:
   stage: build
   image: python:3.11-slim
-  before_script:
-    - pip install -r requirements.txt
   script:
+    - pip install -r requirements.txt
     - dbt deps
     - dbt build --target $DBT_TARGET
     - dbt docs generate --target $DBT_TARGET
@@ -214,6 +204,15 @@ dbt-build:
     expire_in: 1 week
   rules:
     - if: $CI_PIPELINE_SOURCE == "merge_request_event"
-```
 
-See the [complete example project](https://gitlab.com/recce/jaffle-shop-snowflake/-/blob/main/.gitlab-ci.yml) for a full working configuration.
+recce-upload:
+  stage: upload
+  image: python:3.11-slim
+  script:
+    - pip install recce-cloud
+    - recce-cloud upload
+  dependencies:
+    - dbt-build
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
+```