Fix BC_SlIP_WALL casing typo

[sbryngelson]

User description

Summary

• Fixed BC_SlIP_WALL (lowercase L) to BC_SLIP_WALL in the z-direction boundary condition handler
• The typo caused the case statement to not match the BC_SLIP_WALL constant, making the slip wall condition unreachable for this boundary direction

Test plan

• Verify 3D slip wall boundary conditions work correctly
• No golden file changes expected (fixes dead code path)

🤖 Generated with Claude Code

---

CodeAnt-AI Description

Restore slip-wall boundary condition handling for the Z-direction in 3D runs

What Changed

• Fixed a casing typo so the slip-wall boundary case now matches and executes for the z-direction
• Slip-wall boundary behavior in 3D is now applied where intended instead of being skipped
• No behavioral changes to other boundary types; existing boundary handlers remain unchanged

Impact

✅ Correct 3D slip-wall boundaries
✅ Fewer incorrect boundary treatments in z-direction
✅ More accurate simulation results when slip walls are used

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

[Copilot]

Pull request overview

Fixes an unreachable slip-wall boundary condition branch in the z-direction boundary-condition handler by correcting a constant name typo, ensuring BC_SLIP_WALL is properly matched in the relevant select case.

Changes:

• Corrected case (BC_SlIP_WALL) to case (BC_SLIP_WALL) in the z-direction boundary condition dispatch.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.05%. Comparing base (d048c4b) to head (1216c4d).
⚠️ Report is 15 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1228      +/-   ##
==========================================
- Coverage   44.07%   44.05%   -0.02%     
==========================================
  Files          70       70              
  Lines       20431    20498      +67     
  Branches     1974     1990      +16     
==========================================
+ Hits         9004     9030      +26     
- Misses      10291    10329      +38     
- Partials     1136     1139       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.