♻️ Remove Claude integration leftovers

.codex/config.toml

@@ -0,0 +1,3 @@
+[mcp_servers.playwright]
+args = ["@playwright/mcp@latest"]
+command = "npx"

.github/workflows/release-ember-client.yml

@@ -70,29 +70,31 @@ jobs:
           echo "version=$NEW_VERSION" >> $GITHUB_OUTPUT
           echo "tag=ember/v$NEW_VERSION" >> $GITHUB_OUTPUT
 
-      - name: Generate changelog with Claude
-        id: changelog
-        uses: anthropics/claude-code-action@v1
+      - name: Generate changelog
+        uses: openai/codex-action@v1
         with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          openai-api-key: ${{ secrets.OPENAI_API_KEY }}
+          sandbox: workspace-write
+          safety-strategy: drop-sudo
           prompt: |
             Generate release notes for the Vizzly Ember SDK v${{ steps.version.outputs.version }}.
 
             Context:
             - Client location: `clients/ember/`
             - Previous tag: `ember/v${{ steps.current_version.outputs.version }}`
             - New version: `${{ steps.version.outputs.version }}`
-            - This is a monorepo with multiple clients and a CLI
+            - This is a monorepo with multiple clients and a CLI.
 
             Instructions:
-            1. Use git commands (via Bash tool) to get commits since last ember/* tag
-            2. Analyze which commits are relevant to `clients/ember/`
-            3. Read the code changes if needed to understand impact
-            4. Generate user-friendly release notes with categories: Added, Changed, Fixed
-            5. Focus on user-facing changes only
-            6. If no relevant changes, output: "No changes to Ember SDK in this release"
+            1. Use git commands to inspect commits and changed files since the previous Ember tag.
+            2. Analyze which changes are relevant to `clients/ember/`.
+            3. Read relevant code changes when commit messages are not enough.
+            4. Generate user-friendly release notes with categories: Added, Changed, Fixed.
+            5. Focus on user-facing changes only.
+            6. If there are no relevant changes, output: "No changes to Ember SDK in this release".
+            7. Save the changelog to `clients/ember/CHANGELOG-RELEASE.md`.
 
-            Save the changelog to `clients/ember/CHANGELOG-RELEASE.md` with this format:
+            Use this format:
 
             ## What's Changed
 
@@ -106,7 +108,6 @@ jobs:
             - Bug fixes
 
             **Full Changelog**: https://github.com/vizzly-testing/cli/compare/ember/v${{ steps.current_version.outputs.version }}...ember/v${{ steps.version.outputs.version }}
-          claude_args: '--allowed-tools "Bash(git:*),Write"'
 
       - name: Install dependencies
         working-directory: ./clients/ember

.github/workflows/release-ruby-client.yml

@@ -72,29 +72,31 @@ jobs:
           echo "version=$NEW_VERSION" >> $GITHUB_OUTPUT
           echo "tag=ruby/v$NEW_VERSION" >> $GITHUB_OUTPUT
 
-      - name: Generate changelog with Claude
-        id: changelog
-        uses: anthropics/claude-code-action@v1
+      - name: Generate changelog
+        uses: openai/codex-action@v1
         with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          openai-api-key: ${{ secrets.OPENAI_API_KEY }}
+          sandbox: workspace-write
+          safety-strategy: drop-sudo
           prompt: |
             Generate release notes for the Vizzly Ruby Client SDK v${{ steps.new_version.outputs.version }}.
 
             Context:
             - Client location: `clients/ruby/`
             - Previous tag: `ruby/v${{ steps.current_version.outputs.version }}`
             - New version: `${{ steps.new_version.outputs.version }}`
-            - This is a monorepo with multiple clients and a CLI
+            - This is a monorepo with multiple clients and a CLI.
 
             Instructions:
-            1. Use git commands (via Bash tool) to get commits since last ruby/* tag
-            2. Analyze which commits are relevant to `clients/ruby/`
-            3. Read the code changes if needed to understand impact
-            4. Generate user-friendly release notes with categories: Added, Changed, Fixed
-            5. Focus on user-facing changes only
-            6. If no relevant changes, output: "No changes to Ruby client in this release"
+            1. Use git commands to inspect commits and changed files since the previous Ruby tag.
+            2. Analyze which changes are relevant to `clients/ruby/`.
+            3. Read relevant code changes when commit messages are not enough.
+            4. Generate user-friendly release notes with categories: Added, Changed, Fixed.
+            5. Focus on user-facing changes only.
+            6. If there are no relevant changes, output: "No changes to Ruby client in this release".
+            7. Save the changelog to `clients/ruby/CHANGELOG-RELEASE.md`.
 
-            Save the changelog to `clients/ruby/CHANGELOG-RELEASE.md` with this format:
+            Use this format:
 
             ## What's Changed
 
@@ -108,7 +110,6 @@ jobs:
             - Bug fixes
 
             **Full Changelog**: https://github.com/vizzly-testing/vizzly-cli/compare/ruby/v${{ steps.current_version.outputs.version }}...ruby/v${{ steps.new_version.outputs.version }}
-          claude_args: '--allowed-tools "Bash(git:*)"'
 
       - name: Update version in gemspec
         working-directory: ./clients/ruby

.github/workflows/release-static-site-client.yml

@@ -61,29 +61,31 @@ jobs:
           echo "version=$NEW_VERSION" >> $GITHUB_OUTPUT
           echo "tag=static-site/v$NEW_VERSION" >> $GITHUB_OUTPUT
 
-      - name: Generate changelog with Claude
-        id: changelog
-        uses: anthropics/claude-code-action@v1
+      - name: Generate changelog
+        uses: openai/codex-action@v1
         with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          openai-api-key: ${{ secrets.OPENAI_API_KEY }}
+          sandbox: workspace-write
+          safety-strategy: drop-sudo
           prompt: |
             Generate release notes for the Vizzly Static Site Plugin v${{ steps.version.outputs.version }}.
 
             Context:
             - Client location: `clients/static-site/`
             - Previous tag: `static-site/v${{ steps.current_version.outputs.version }}`
             - New version: `${{ steps.version.outputs.version }}`
-            - This is a monorepo with multiple clients and a CLI
+            - This is a monorepo with multiple clients and a CLI.
 
             Instructions:
-            1. Use git commands (via Bash tool) to get commits since last static-site/* tag
-            2. Analyze which commits are relevant to `clients/static-site/`
-            3. Read the code changes if needed to understand impact
-            4. Generate user-friendly release notes with categories: Added, Changed, Fixed
-            5. Focus on user-facing changes only
-            6. If no relevant changes, output: "No changes to Static Site plugin in this release"
+            1. Use git commands to inspect commits and changed files since the previous Static Site tag.
+            2. Analyze which changes are relevant to `clients/static-site/`.
+            3. Read relevant code changes when commit messages are not enough.
+            4. Generate user-friendly release notes with categories: Added, Changed, Fixed.
+            5. Focus on user-facing changes only.
+            6. If there are no relevant changes, output: "No changes to Static Site plugin in this release".
+            7. Save the changelog to `clients/static-site/CHANGELOG-RELEASE.md`.
 
-            Save the changelog to `clients/static-site/CHANGELOG-RELEASE.md` with this format:
+            Use this format:
 
             ## What's Changed
 
@@ -97,7 +99,6 @@ jobs:
             - Bug fixes
 
             **Full Changelog**: https://github.com/vizzly-testing/cli/compare/static-site/v${{ steps.current_version.outputs.version }}...static-site/v${{ steps.version.outputs.version }}
-          claude_args: '--allowed-tools "Bash(git:*),Write"'
 
       - name: Install dependencies
         working-directory: ./clients/static-site

.github/workflows/release-storybook-client.yml

@@ -62,29 +62,31 @@ jobs:
           echo "version=$NEW_VERSION" >> $GITHUB_OUTPUT
           echo "tag=storybook/v$NEW_VERSION" >> $GITHUB_OUTPUT
 
-      - name: Generate changelog with Claude
-        id: changelog
-        uses: anthropics/claude-code-action@v1
+      - name: Generate changelog
+        uses: openai/codex-action@v1
         with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          openai-api-key: ${{ secrets.OPENAI_API_KEY }}
+          sandbox: workspace-write
+          safety-strategy: drop-sudo
           prompt: |
             Generate release notes for the Vizzly Storybook Plugin v${{ steps.version.outputs.version }}.
 
             Context:
             - Client location: `clients/storybook/`
             - Previous tag: `storybook/v${{ steps.current_version.outputs.version }}`
             - New version: `${{ steps.version.outputs.version }}`
-            - This is a monorepo with multiple clients and a CLI
+            - This is a monorepo with multiple clients and a CLI.
 
             Instructions:
-            1. Use git commands (via Bash tool) to get commits since last storybook/* tag
-            2. Analyze which commits are relevant to `clients/storybook/`
-            3. Read the code changes if needed to understand impact
-            4. Generate user-friendly release notes with categories: Added, Changed, Fixed
-            5. Focus on user-facing changes only
-            6. If no relevant changes, output: "No changes to Storybook plugin in this release"
+            1. Use git commands to inspect commits and changed files since the previous Storybook tag.
+            2. Analyze which changes are relevant to `clients/storybook/`.
+            3. Read relevant code changes when commit messages are not enough.
+            4. Generate user-friendly release notes with categories: Added, Changed, Fixed.
+            5. Focus on user-facing changes only.
+            6. If there are no relevant changes, output: "No changes to Storybook plugin in this release".
+            7. Save the changelog to `clients/storybook/CHANGELOG-RELEASE.md`.
 
-            Save the changelog to `clients/storybook/CHANGELOG-RELEASE.md` with this format:
+            Use this format:
 
             ## What's Changed
 
@@ -98,7 +100,6 @@ jobs:
             - Bug fixes
 
             **Full Changelog**: https://github.com/vizzly-testing/cli/compare/storybook/v${{ steps.current_version.outputs.version }}...storybook/v${{ steps.version.outputs.version }}
-          claude_args: '--allowed-tools "Bash(git:*),Write"'
 
       - name: Install dependencies
         working-directory: ./clients/storybook

.github/workflows/release-swift-client.yml

@@ -74,29 +74,31 @@ jobs:
           echo "version=$NEW_VERSION" >> $GITHUB_OUTPUT
           echo "tag=swift/v$NEW_VERSION" >> $GITHUB_OUTPUT
 
-      - name: Generate changelog with Claude
-        id: changelog
-        uses: anthropics/claude-code-action@v1
+      - name: Generate changelog
+        uses: openai/codex-action@v1
         with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          openai-api-key: ${{ secrets.OPENAI_API_KEY }}
+          sandbox: workspace-write
+          safety-strategy: drop-sudo
           prompt: |
             Generate release notes for the Vizzly Swift SDK v${{ steps.new_version.outputs.version }}.
 
             Context:
             - Client location: `clients/swift/`
             - Previous tag: `swift/v${{ steps.current_version.outputs.version }}`
             - New version: `${{ steps.new_version.outputs.version }}`
-            - This is a monorepo with multiple clients and a CLI
+            - This is a monorepo with multiple clients and a CLI.
 
             Instructions:
-            1. Use git commands (via Bash tool) to get commits since last swift/* tag
-            2. Analyze which commits are relevant to `clients/swift/`
-            3. Read the code changes if needed to understand impact
-            4. Generate user-friendly release notes with categories: Added, Changed, Fixed
-            5. Focus on user-facing changes only
-            6. If no relevant changes, output: "No changes to Swift client in this release"
+            1. Use git commands to inspect commits and changed files since the previous Swift tag.
+            2. Analyze which changes are relevant to `clients/swift/`.
+            3. Read relevant code changes when commit messages are not enough.
+            4. Generate user-friendly release notes with categories: Added, Changed, Fixed.
+            5. Focus on user-facing changes only.
+            6. If there are no relevant changes, output: "No changes to Swift client in this release".
+            7. Save the changelog to `clients/swift/CHANGELOG-RELEASE.md`.
 
-            Save the changelog to `clients/swift/CHANGELOG-RELEASE.md` with this format:
+            Use this format:
 
             ## What's Changed
 
@@ -110,7 +112,6 @@ jobs:
             - Bug fixes
 
             **Full Changelog**: https://github.com/vizzly-testing/cli/compare/swift/v${{ steps.current_version.outputs.version }}...swift/v${{ steps.new_version.outputs.version }}
-          claude_args: '--allowed-tools "Bash(git:*)"'
 
       - name: Update CHANGELOG.md
         working-directory: ./clients/swift