fix: Exclude Terraform and Terragrunt cache directories from checkpoints (#4601)

[MuriloFP]

Related GitHub Issue

Closes: #4601

Roo Code Task Context (Optional)

N/A

Description

This PR adds .terraform/ and .terragrunt-cache/ directories to the checkpoint exclusion patterns, preventing these large cache directories from being included in snapshots.

Key Implementation Details:

• Added two patterns to the getBuildArtifactPatterns() function in src/services/checkpoints/excludes.ts
• Patterns are added in alphabetical order after .sass-cache/ to maintain consistency
• These directories contain provider binaries and other large files that can be regenerated with terraform init

Impact:

• Significantly reduces disk space usage for users working with Terraform/Terragrunt projects
• Prevents checkpoint bloat (sometimes 10x reduction in size)
• No breaking changes - purely additive exclusion patterns

Test Procedure

Manual Testing:

1. Create a Terraform project without .terraform/ in .gitignore
2. Run terraform init to download providers and create .terraform/ directory
3. Make code changes in Roo Code to trigger checkpoint creation
4. Verify that .terraform/ directory is excluded from the checkpoint
5. Check checkpoint size remains small despite large provider binaries

Terragrunt Testing:

1. Create a Terragrunt project
2. Run terragrunt commands to generate .terragrunt-cache/ directory
3. Create checkpoints in Roo Code
4. Verify cache directory is excluded from snapshots

Verification:

• Terraform configuration files (.tf, .tfvars) are still included in checkpoints
• Terragrunt configuration files (.hcl) are still included
• Only the cache directories are excluded

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

N/A - No UI changes

Documentation Updates

• No documentation updates are required.
• Yes, documentation updates are required.

Additional Notes

This is a simple, low-risk change that adds two directory patterns to an existing exclusion list. The patterns follow the same format as other build artifact exclusions already in the codebase.

Get in Touch

@MuriloFP

[daniel-lxs]

LGTM