Add workflow to auto-update test summary via Claude

[vishalchangrani]

Summary

• Adds a new GitHub Actions workflow (.github/workflows/update_test_summary.yml) that automatically triggers when test files (cadence/tests/*_test.cdc or test_helpers.cdc) are changed on main
• Uses anthropics/claude-code-action@v1 to analyze the full test suite, scan for TODOs, and update TODO_AND_MISSING_TESTS_SUMMARY.md
• Creates a separate PR with the updated test summary document
• Includes workflow_dispatch trigger for manual testing

Setup required

• Add ANTHROPIC_API_KEY as a repository secret (Settings > Secrets and variables > Actions)

Test plan

• Add ANTHROPIC_API_KEY secret to the repository
• Trigger the workflow manually via workflow_dispatch from the Actions tab
• Verify Claude creates a branch and opens a PR with an updated TODO_AND_MISSING_TESTS_SUMMARY.md
• Merge a PR that touches a test file and verify the workflow fires automatically

🤖 Generated with Claude Code

[vishalchangrani]

• added the ANTHROPIC_API_KEY to this project.

[Kay-Zee]

is the API key your API key? If there is a "name" or some other identifier for it, can you include it here in the PR?

Also, have you tested this? Is there a test PR you could link to if you have?

[vishalchangrani]

is the API key your API key? If there is a "name" or some other identifier for it, can you include it here in the PR?

Also, have you tested this? Is there a test PR you could link to if you have?

The Key name is Claude is
github_action_flow_credit_market and is an organization wide key (not my personal API key).

It can be viewed here https://platform.claude.com/settings/keys?search=github_action_flow_credit_market

[vishalchangrani]

is the API key your API key? If there is a "name" or some other identifier for it, can you include it here in the PR?

Also, have you tested this? Is there a test PR you could link to if you have?

I tried testing it (locally and on github) but it doesn't work. The action will only work after I merge this PR in.

From Claude.

GitHub requires the workflow YAML file to exist on the repository's default branch (main) before it can be triggered via workflow_dispatch -- whether from the Actions UI or the gh CLI. Since your workflow file only exists on the vishal/claude_test_github_action branch (pending PR #146), GitHub returns a 404. Merging locally doesn't help either, because gh workflow run triggers execution on GitHub's servers using the remote main, and branch protection prevents pushing directly to remote main. The only path forward is to get PR #146 reviewed and merged.