Fix/scl language support

[WorkRCS]

Description

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactoring (no functional changes)
• Documentation update
• CI / Build / Tooling

How Has This Been Tested?

• make test passes locally
• Manual testing (describe below)

Checklist

• My code follows the project's coding style (go fmt, go vet)
• I have performed a self-review of my code
• I have added tests that prove my fix is effective or my feature works
• New and existing unit tests pass locally with my changes
• I have updated the documentation accordingly (if applicable)
• I have signed the CLA
• I did not use AI/LLM to create this PR, or I disclosed the tool/model below and reviewed its output; I did not attribute commits to AI and will answer maintainer questions and review comments myself without AI/LLM.

Related Issues

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

✅ OpenCodeReview: Review complete: 0 finding(s) across 2 selected item(s).

[wu21-web]

Why do need a standalone test? This is already covered by tests, you just need to append them to the test index.

[wu21-web]

Ditto

[wu21-web]

Stale site docs & CLA. @WorkRCS

[wu21-web]

There is definitely a exclude pattern because SCL follows the parallel structure, like this:

├── src/
│   └── com/scl/components/
│       ├── Button.java
│       └── Modal.java
└── src/test/  (or test/)
    └── com/scl/components/
        ├── ButtonTest.java
        └── ModalTest.java