📋 PR Title Format

The PR title should follow the format:

type(scope): concise message (max 50 chars)

Where:

• type is one of: feat, fix, docs, refactor, perf, test, chore.
• scope is optional and describes the part of the codebase affected (e.g., auth, ui, api).
• concise message is a short description of the change (max 50 chars).

📝 Change Type

Please select the type of change this PR introduces (choose one or more):

• feat: New feature.
• fix: Bug fix.
• docs: Documentation only changes.
• refactor: A code change that neither fixes a bug nor adds a feature.
• perf: Performance improvement.
• test: Adding missing tests or correcting existing tests.
• chore: Maintenance tasks (e.g., updating dependencies).

💡 Description

Briefly describe the change, its purpose, and the problem it solves.
Before parallax could not support lora, now it can use sglang's lora.

Key Changes

1.add sglang's lora params
2.transfer params to sglang

🔗 Related Issues

List any issues this PR closes or relates to:

• Closes [Feature]: Support LoRA Adapters #146

✅ Checklist

Please ensure the following points are addressed before merging:

• I have performed a self-review of my own code.
• I have added/updated tests that prove my fix or feature works (if applicable).
• I have updated the documentation (if necessary).
• My code follows the project's style guidelines.