chore: disable all CI workflows on fork

[agentx-workflow]

Summary

Removes all CI workflows from this fork to save GitHub Actions minutes.

Deleted workflows:

• build-helper.yml
• bump-version.yml
• codeql.yml
• copilot-setup-steps.yml
• deploy-docsite.yml
• merge-gatekeeper.yml
• publish-release.yml
• testdriver-build.yml
• testdriver.yml

Reason

This is a fork and doesn't need its own CI running. The upstream repo handles CI.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[reagentx-workflow]

Review Summary

This PR successfully removes 9 GitHub Actions workflow files from the fork to save Actions minutes. The approach is sound and the implementation is clean.

✅ What's Good

1. Complete removal: All 936 lines of workflow configuration deleted across 9 files
2. Clean commits: Each workflow removed in a separate, well-named commit
3. Clear documentation: PR description lists all deleted workflows
4. Correct rationale: Makes sense for a fork that doesn't need its own CI infrastructure

📋 Observations

Removed workflows:

• build-helper.yml (208 lines) - Multi-platform build, signing, and S3 upload
• bump-version.yml (89 lines) - Version management automation
• codeql.yml (137 lines) - Security scanning
• copilot-setup-steps.yml (63 lines) - Copilot environment setup
• deploy-docsite.yml (83 lines) - Documentation deployment
• merge-gatekeeper.yml (32 lines) - PR merge requirements
• publish-release.yml (100 lines) - Release publishing to S3/Snap/WinGet
• testdriver-build.yml (83 lines) - TestDriver.ai build
• testdriver.yml (141 lines) - TestDriver.ai automation

💡 Recommendations

1. Consider keeping copilot-setup-steps.yml - This lightweight workflow (63 lines) just caches dependencies and doesn't consume many Actions minutes. It could be useful if GitHub Copilot agents work on this fork.

2. Consider a minimal CI - You might want a very basic workflow that just runs npm ci && npm run build on PRs to catch obvious breakage. This would use minimal minutes but provide quick feedback.

3. Document in CLAUDE.md - Consider adding a note to CLAUDE.md that this fork has no CI, so agents should test changes locally before pushing.

🔒 Security & Quality

• ✅ No security issues
• ✅ No bugs introduced (only deletions)
• ✅ No breaking changes to codebase functionality
• ℹ️ Loss of CodeQL security scanning (acceptable for a fork)
• ℹ️ Loss of automated testing (TestDriver.ai workflows)

Test Coverage

N/A - This PR only removes files, no new functionality to test.

Verdict

APPROVE ✅ - This is a clean, well-executed change that achieves its stated goal. The recommendations above are optional enhancements, not blockers.