Update CI documentation to reference socket-registry workflows

Add references to socket-registry's centralized CI workflow and clarify that package-specific validation tools are unique to socket-registry

Author: jdalton

CLAUDE.md

@@ -88,11 +88,12 @@ Programmatic access to Socket.dev's security analysis capabilities.
   - ❌ WRONG: `it('works', ...)`
 
 ### CI Testing Infrastructure
-- **Reusable workflows**: Use `.github/workflows/_reusable-test.yml`
+- **🚨 MANDATORY**: Use `SocketDev/socket-registry/.github/workflows/ci.yml@main` for consistent CI across Socket projects
+- **Reusable workflows**: Socket-registry provides centralized, reusable workflows for lint/type-check/test/coverage
 - **Matrix testing**: Test across Node.js versions (20, 22, 24) and platforms
 - **Custom test runner**: `scripts/test.mjs` provides glob expansion
 - **Memory configuration**: Automatic heap size adjustment for CI (8GB) vs local (4GB)
-- **Documentation**: See `docs/CI_TESTING.md`
+- **Documentation**: See `docs/CI_TESTING.md` and `socket-registry/docs/CI_TESTING_TOOLS.md`
 
 ## 🔒 SECURITY & SAFETY
 

docs/CI_TESTING.md

@@ -2,44 +2,52 @@
 
 ## Overview
 
-This project uses a comprehensive CI testing solution inspired by socket-registry's testing infrastructure. The solution provides:
+This project uses socket-registry's centralized CI testing infrastructure. The solution provides:
 
+- **🚨 MANDATORY**: Use `SocketDev/socket-registry/.github/workflows/ci.yml@main` for consistent CI
 - **Multi-platform testing**: Linux, Windows, and macOS support
 - **Multi-version Node.js matrix**: Test across Node.js 20, 22, and 24
 - **Flexible configuration**: Customizable test scripts, timeouts, and artifact uploads
 - **Memory optimization**: Configured heap sizes for CI and local environments
 - **Cross-platform compatibility**: Handles Windows and POSIX path differences
 
+**For socket-registry-specific package testing tools**, see `socket-registry/docs/CI_TESTING_TOOLS.md` and `socket-registry/docs/PACKAGE_TESTING_GUIDE.md`. These tools (`validate:packages`, `validate:ci`) are specific to socket-registry's package override structure.
+
 ## Workflow Structure
 
-### Reusable Test Workflow
+### Centralized CI Workflow
 
-Located at `.github/workflows/_reusable-test.yml`, this workflow provides a flexible testing foundation that can be customized per project.
+**🚨 MANDATORY**: Use `SocketDev/socket-registry/.github/workflows/ci.yml@main` for consistent CI across all Socket projects.
 
 **Key Features:**
 - Matrix testing across Node.js versions and operating systems
-- Configurable setup scripts for build steps
+- Parallel execution of lint, type-check, test, and coverage
+- Configurable scripts for project-specific requirements
 - Artifact upload support for coverage reports
 - Debug mode for verbose logging
 - Timeout protection for long-running tests
 
 ### Main Test Workflow
 
-Located at `.github/workflows/test.yml`, this workflow calls the reusable workflow with project-specific configuration:
+Located at `.github/workflows/test.yml`, this workflow calls socket-registry's reusable CI workflow:
 
 ```yaml
 jobs:
   test:
-    uses: ./.github/workflows/_reusable-test.yml
+    uses: SocketDev/socket-registry/.github/workflows/ci.yml@main
     with:
       setup-script: 'pnpm run build'
       node-versions: '[20, 22, 24]'
       os-versions: '["ubuntu-latest", "windows-latest"]'
       test-script: 'pnpm run test-ci'
+      lint-script: 'pnpm run check:lint'
+      type-check-script: 'pnpm run check:tsc'
       timeout-minutes: 10
       upload-artifacts: false
 ```
 
+**Note**: For projects still using local reusable workflows (`.github/workflows/_reusable-test.yml`), migrate to socket-registry's centralized workflow.
+
 ## Configuration Options
 
 ### Input Parameters
@@ -232,13 +240,15 @@ pnpm run test:run
 
 ## Integration with socket-registry
 
-This testing solution is aligned with socket-registry patterns:
-- Reusable workflow structure
-- Memory optimization strategies
-- Cross-platform compatibility
-- Test coordination utilities
+This project uses socket-registry's centralized CI infrastructure:
+- **CI Workflow**: `SocketDev/socket-registry/.github/workflows/ci.yml@main`
+- **Memory optimization strategies**: Aligned with socket-registry patterns
+- **Cross-platform compatibility**: Follows socket-registry guidelines
+- **Test coordination utilities**: Shared utilities from socket-registry
+
+**Socket-registry-specific tools**: The `validate:packages` and `validate:ci` scripts in socket-registry are specific to its package override structure and not applicable to SDK projects. See `socket-registry/docs/CI_TESTING_TOOLS.md` and `socket-registry/docs/PACKAGE_TESTING_GUIDE.md` for details.
 
-For consistency across Socket projects, follow the patterns established in socket-registry and documented here.
+For consistency across Socket projects, follow the patterns established in socket-registry/CLAUDE.md and documented here.
 
 ## Future Enhancements