Add CPU_SIZE and MEMORY_SIZE support to Squirro workflow

- Updated build-and-push-to-ecr.yml.template to handle CPU/Memory variables
- Added support for GitHub Variables override (same pattern as main workflow)
- Updated documentation in .squirro/README.md
- Updated setup-for-squirro.sh.template instructions

This ensures Squirro deployments can also benefit from configurable
resource allocation without hardcoding values.

Author: ppolydoras

.squirro/README.md

@@ -79,6 +79,8 @@ These are **optional overrides** for config.env values:
 - `AWS_ACCOUNT_ID` - Override the AWS account ID from config.env
 - `AWS_REGION` - Override the AWS region from config.env
 - `ECR_REPOSITORY` - Override the ECR repository name from config.env
+- `CPU_SIZE` - Override CPU allocation (e.g., "1 vCPU", "4 vCPU")
+- `MEMORY_SIZE` - Override memory allocation (e.g., "2 GB", "8 GB")
 
 ### GitHub Secrets (Repository Settings → Secrets and variables → Secrets)
 These are **sensitive** values that must be kept secret:

.squirro/setup-for-squirro.sh.template

@@ -78,6 +78,8 @@ echo "2. Configure GitHub Variables (optional overrides):"
 echo "   - AWS_ACCOUNT_ID (override config.env value)"
 echo "   - AWS_REGION (override config.env value)"
 echo "   - ECR_REPOSITORY (override config.env value)"
+echo "   - CPU_SIZE (override config.env value, e.g., '4 vCPU')"
+echo "   - MEMORY_SIZE (override config.env value, e.g., '8 GB')"
 echo ""
 echo "3. Configure GitHub Secrets (required):"
 echo "   - AWS_ACCESS_KEY_ID (for ECR push access)"

.squirro/workflows/build-and-push-to-ecr.yml.template

@@ -41,6 +41,8 @@ jobs:
         [ -n "${{ vars.AWS_REGION }}" ] && AWS_REGION="${{ vars.AWS_REGION }}"
         [ -n "${{ vars.AWS_ACCOUNT_ID }}" ] && AWS_ACCOUNT_ID="${{ vars.AWS_ACCOUNT_ID }}"
         [ -n "${{ vars.ECR_REPOSITORY }}" ] && ECR_REPOSITORY="${{ vars.ECR_REPOSITORY }}"
+        [ -n "${{ vars.CPU_SIZE }}" ] && CPU_SIZE="${{ vars.CPU_SIZE }}"
+        [ -n "${{ vars.MEMORY_SIZE }}" ] && MEMORY_SIZE="${{ vars.MEMORY_SIZE }}"
 
         # Validate required values exist (from either source)
         if [ -z "$AWS_ACCOUNT_ID" ]; then
@@ -107,17 +109,29 @@ jobs:
           export ECR_REPOSITORY="${{ vars.ECR_REPOSITORY }}"
           echo "📝 ECR_REPOSITORY overridden by GitHub Variable: $ECR_REPOSITORY"
         fi
+        if [ -n "${{ vars.CPU_SIZE }}" ]; then
+          export CPU_SIZE="${{ vars.CPU_SIZE }}"
+          echo "📝 CPU_SIZE overridden by GitHub Variable: $CPU_SIZE"
+        fi
+        if [ -n "${{ vars.MEMORY_SIZE }}" ]; then
+          export MEMORY_SIZE="${{ vars.MEMORY_SIZE }}"
+          echo "📝 MEMORY_SIZE overridden by GitHub Variable: $MEMORY_SIZE"
+        fi
 
         # Export to GITHUB_ENV for subsequent steps
         echo "AWS_REGION=$AWS_REGION" >> $GITHUB_ENV
         echo "AWS_ACCOUNT_ID=$AWS_ACCOUNT_ID" >> $GITHUB_ENV
         echo "ECR_REPOSITORY=$ECR_REPOSITORY" >> $GITHUB_ENV
         echo "ECR_REGISTRY=$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com" >> $GITHUB_ENV
+        echo "CPU_SIZE=$CPU_SIZE" >> $GITHUB_ENV
+        echo "MEMORY_SIZE=$MEMORY_SIZE" >> $GITHUB_ENV
 
         echo "📊 Final configuration:"
         echo "   AWS_REGION=$AWS_REGION"
         echo "   AWS_ACCOUNT_ID=$AWS_ACCOUNT_ID"
         echo "   ECR_REPOSITORY=$ECR_REPOSITORY"
+        echo "   CPU_SIZE=$CPU_SIZE"
+        echo "   MEMORY_SIZE=$MEMORY_SIZE"
 
     - name: Configure AWS credentials
       uses: aws-actions/configure-aws-credentials@v4

README.md

@@ -65,7 +65,7 @@ graph TB
         ValidateConfig["just validate-config<br/>📝 YAML validation"]
         CiTests["just ci-tests-with-data<br/>🔍 CI tests + data"]
         FullPipeline["just full-pipeline<br/>🏗️ Complete dev pipeline"]
-        TestIntegration["just test-integration<br/>🔧 Integration tests"]
+        TestTools["just test-tools<br/>🔧 Tool tests"]
         PrepareBuild["just prepare-build<br/>📦 Data preparation"]
         TestData["just test-data<br/>🧪 Level 1: dbt tests"]
         TestEvals["just test-evals<br/>🤖 Level 3: LLM evals"]
@@ -90,7 +90,7 @@ graph TB
     %% Workflow Relationships
     Deploy -->|"1. Validation"| CiTests
     Deploy -->|"Fallback"| ValidateConfig
-    Deploy -->|"2. Post-deployment"| TestIntegration
+    Deploy -->|"2. Post-deployment"| TestTools
     
     Test -->|"PR Testing"| FullPipeline
     Test -->|"Fallback"| ValidateConfig
@@ -102,9 +102,9 @@ graph TB
     
     FullPipeline --> PrepareBuild
     FullPipeline --> TestData
-    FullPipeline --> TestIntegration
+    FullPipeline --> TestTools
     
-    TestIntegration -->|"Uses"| Tools
+    TestTools -->|"Uses"| Tools
     TestData -->|"Tests"| Models
 
     %% Docker Build Process
@@ -120,12 +120,12 @@ graph TB
     %% 3-Tiered Testing
     subgraph "🎯 3-Tiered Testing"
         Level1["Level 1: Data Quality<br/>🧪 dbt schema tests<br/>💰 Free"]
-        Level2["Level 2: Integration<br/>🔧 MXCP tools tests<br/>💰 Free"]
+        Level2["Level 2: Integration<br/>🔧 MXCP tools & API tests<br/>💰 Free"]
         Level3["Level 3: LLM Evaluation<br/>🤖 AI behavior tests<br/>💰 Costs Apply"]
     end
 
     TestData -.->|"Implements"| Level1
-    TestIntegration -.->|"Implements"| Level2
+    TestTools -.->|"Implements"| Level2
     TestEvals -.->|"Implements"| Level3
 
     %% Styling
@@ -136,7 +136,7 @@ graph TB
     classDef testing fill:#fce4ec,stroke:#880e4f,stroke-width:2px
 
     class Deploy,Test,Release workflow
-    class ValidateConfig,CiTests,FullPipeline,TestIntegration,PrepareBuild,TestData,TestEvals justfile
+    class ValidateConfig,CiTests,FullPipeline,TestTools,PrepareBuild,TestData,TestEvals justfile
     class Dockerfile,ConfigEnv,MxcpSite,UserConfig,StartSh deployment
     class Scripts,Tools,Models project
     class Level1,Level2,Level3 testing
@@ -688,7 +688,7 @@ just dev-full              # Download data + build + test all 3 levels
 
 # Individual testing levels
 just test-data             # Level 1: dbt schema tests
-just test-integration      # Level 2: MXCP tools tests  
+just test-tools            # Level 2: MXCP tools tests  
 just test-evals           # Level 3: LLM evaluation tests (requires OPENAI_API_KEY)
 
 # CI/CD pipeline