🧪 Add tests for mangle/synth validate.go

[theRebelliousNerd]

🎯 What: The testing gap addressed
The ValidateSpec function and all its unexported validation helpers in internal/mangle/synth/validate.go had zero test coverage.

📊 Coverage: What scenarios are now tested
A comprehensive suite of table-driven tests has been added to internal/mangle/synth/validate_test.go. The new tests cover:

• ValidateSpec and validateProgramSpec (handling empty programs, formatting errors, and option flags)
• AST-level node validations including:
  • Packages and Uses
  • Declarations and Clauses
  • Transform Statements
  • Terms and Atoms
  • Expressions (checking all valid kinds: var, name, string, bytes, number, float, apply, list, map, struct)
• Helper validators for arity and valid variable names

✨ Result: The improvement in test coverage
Statement coverage for the validate.go file has drastically improved, securing the schema validation checks used by the MangleSynth compiler against future regressions.

---

PR created automatically by Jules for task 18210714133922930454 started by @theRebelliousNerd

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Rate limit exceeded

@theRebelliousNerd has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 54 minutes and 56 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a90b2628-5ee8-4234-b1fb-e7a3a64944e6

📥 Commits

Reviewing files that changed from the base of the PR and between cc0e10f and 0bb9227.

📒 Files selected for processing (1)

• internal/mangle/synth/validate_test.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jules-18210714133922930454-c12d694a

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}