@codyswann/lisa 1.0.5 → 1.0.9

package/expo/copy-overwrite/.github/workflows/lighthouse.yml

@@ -54,6 +54,23 @@ jobs:
             bun install --frozen-lockfile
           fi
 
+      - name: 📋 Copy amplify file (if exists)
+        run: |
+          ENV="${{ inputs.target_branch }}"
+          if [ "$ENV" == "staging" ]; then
+            SOURCE_FILE="staging.aws-exports.js"
+          elif [ "$ENV" == "dev" ]; then
+            SOURCE_FILE="dev.aws-exports.js"
+          else
+            SOURCE_FILE="prod.aws-exports.js"
+          fi
+          if [ -f "$SOURCE_FILE" ]; then
+            cp "$SOURCE_FILE" aws-exports.js
+            echo "Copied $SOURCE_FILE to aws-exports.js"
+          else
+            echo "Skipping: $SOURCE_FILE does not exist"
+          fi
+
       - name: 🏗️ Build web export
         run: ${{ inputs.package_manager }} run export:web
         env:

package/expo/copy-overwrite/knip.json

@@ -55,6 +55,8 @@
   ],
   "ignoreBinaries": ["audit", "ast-grep", "maestro", "eas", "source-map-explorer"],
   "ignoreDependencies": [
+    "@react-native-community/netinfo",
+    "aws-exports",
     "@babel/core",
     "@babel/plugin-proposal-export-namespace-from",
     "@commitlint/cli",

package/nestjs/copy-overwrite/.github/workflows/deploy.yml

@@ -62,7 +62,7 @@ jobs:
     needs: [determine_environment]
     with:
       environment: ${{ needs.determine_environment.outputs.environment }}
-      release_strategy: 'semantic'
+      release_strategy: 'standard-version'
       skip_jobs: 'test:e2e,test:unit,test:integration,test'
       # require_approval: ${{ needs.determine_environment.outputs.environment == 'main' }}
       # require_signatures: ${{ needs.determine_environment.outputs.environment == 'main' }}

package/package.json

@@ -18,6 +18,9 @@
     "dev": "tsx src/index.ts",
     "test:watch": "vitest",
     "update-node-version": "tsx scripts/update-node-version.ts",
+    "cleanup:amplify-branches": "bash scripts/cleanup-amplify-branches.sh",
+    "cleanup:github-branches": "bash scripts/cleanup-github-branches.sh",
+    "setup:deploy-key": "bash scripts/setup-deploy-key.sh",
     "lint:slow": "eslint . --config eslint.slow.config.ts --quiet",
     "knip": "knip",
     "knip:fix": "knip --fix",
@@ -75,7 +78,7 @@
     "@ast-grep/cli"
   ],
   "name": "@codyswann/lisa",
-  "version": "1.0.5",
+  "version": "1.0.9",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "bin": {

package/typescript/copy-overwrite/.github/workflows/quality.yml

@@ -1041,12 +1041,58 @@ jobs:
 
       - name: 📊 SonarCloud Scan
         if: steps.check_sonar.outputs.has_token == 'true'
+        id: sonar_scan
         uses: SonarSource/sonarqube-scan-action@v6.0.0
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
         with:
           args: -Dsonar.qualitygate.wait=true
+        continue-on-error: true
+
+      - name: 🔍 Validate SonarCloud results
+        if: steps.check_sonar.outputs.has_token == 'true'
+        env:
+          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
+        run: |
+          OUTCOME="${{ steps.sonar_scan.outcome }}"
+
+          if [ "$OUTCOME" = "success" ]; then
+            echo "✅ SonarCloud scan and quality gate passed"
+            exit 0
+          fi
+
+          if [ "$OUTCOME" = "failure" ]; then
+            REPORT_FILE=".scannerwork/report-task.txt"
+
+            if [ ! -f "$REPORT_FILE" ]; then
+              echo "::error::SonarCloud scan failed and report-task.txt is missing; failing build."
+              exit 1
+            fi
+
+            # Extract serverUrl and ceTaskId from report-task.txt (key=value format)
+            SERVER_URL=$(grep -E '^serverUrl=' "$REPORT_FILE" | cut -d= -f2-)
+            CE_TASK_ID=$(grep -E '^ceTaskId=' "$REPORT_FILE" | cut -d= -f2-)
+
+            if [ -z "$SERVER_URL" ] || [ -z "$CE_TASK_ID" ]; then
+              echo "::error::Could not extract serverUrl or ceTaskId from report-task.txt; failing build."
+              exit 1
+            fi
+
+            # Query SonarCloud CE task API to get the actual error message
+            TASK_JSON=$(curl -s -u "$SONAR_TOKEN:" "$SERVER_URL/api/ce/task?id=$CE_TASK_ID")
+            ERROR_MSG=$(echo "$TASK_JSON" | jq -r '.task.errorMessage // ""')
+
+            # Only allow line-limit quota errors to pass
+            if echo "$ERROR_MSG" | grep -qi "maximum allowed lines limit"; then
+              echo "::warning::SonarCloud scan failed due to organization line-limit quota; not blocking build."
+              echo "ℹ️ Contact your SonarCloud organization admin to increase or manage line limits."
+              exit 0
+            fi
+
+            echo "::error::SonarCloud scan failed: $ERROR_MSG"
+            exit 1
+          fi
 
       - name: 📊 SonarCloud Scan Skipped
         if: steps.check_sonar.outputs.has_token != 'true'

package/all/copy-overwrite/.claude/commands/project/complete-task.md

@@ -1,59 +0,0 @@
----
-description: Complete a single task within a project using a subagent with fresh context
-argument-hint: <task-file>
----
-
-1. Read $ARGUMENTS without offset or limit
-2. Follow the instructions literally and specifically
-
-## Verification Requirements
-
-**CRITICAL**: Before marking ANY task as complete:
-
-### For JSON Tasks (`.json` files)
-
-If the task file is JSON and contains `metadata.verification`:
-
-1. **Extract verification data**:
-   ```json
-   {
-     "metadata": {
-       "verification": {
-         "type": "manual-check",
-         "command": "the command to run",
-         "expected": "description of expected output"
-       }
-     }
-   }
-   ```
-
-2. **Run the verification command** using Bash tool
-3. **Compare output to expected** - Verify the output matches the `expected` description
-4. **Only mark complete if verification passes**
-
-### For Markdown Tasks (`.md` files)
-
-If the task has a "## Verification" section with "### Proof Command":
-
-1. **Extract the Proof Command** from the markdown
-2. **Run the command** using Bash tool
-3. **Compare output to Expected Output** section
-4. **Only mark complete if verification passes**
-
-### Verification Rules
-
-1. **`manual-check` verification type** - These require actual execution, not just configuration review:
-   - If the check requires Docker and Docker is unavailable → Task is **BLOCKED**, not complete
-   - If the check requires external services → Actually test against them
-   - If the check requires running a command → Run the command and verify output
-2. **Never assume configuration is correct** - Always empirically verify by running the actual tool/service
-3. **If verification cannot be performed**:
-   - Do NOT mark the task as complete
-   - Document the blocker in findings.md
-   - Mark the task status as "blocked: <reason>"
-4. **If verification fails**:
-   - Do NOT mark the task as complete
-   - Fix the issue and re-run verification
-   - Only mark complete when verification passes
-
-The rule "Never make assumptions about whether something worked. Test it empirically to confirm" applies especially to verification tasks.