feat(agent): use configs to replace the multi-round testing functionality of scripts.

[mmltt-star]

Describe this PR

Use configs to replace the multi-round testing functionality of scripts. Meanwhile,

What changed?

Why?

Related issues

Checklist for PR

• Write a descriptive PR title following the Angular commit message format: <type>(<scope>): <subject>

  • Examples: feat(agent): add pdf tool via mcp, perf: make llm client async, fix(utils): load custom config via importlib
  • Valid types: feat, fix, docs, style, refactor, perf, test, build, ci, revert
  • The check-pr-title CI job will validate your title format
  • Bad title examples and why they fail:
    • Update README ❌ Missing type and colon
    • feat add new feature ❌ Missing colon after type
    • Feature: add new tool ❌ Invalid type (should be feat)
    • feat(Agent): add tool ❌ Scope should be lowercase
    • feat(): add tool ❌ Empty scope not allowed
    • feat(my_scope): add tool ❌ Underscores not allowed in scope
    • feat(my space): add tool ❌ Space not allowed in scope
    • feat(scope):add tool ❌ Missing space after colon
    • feat(scope): ❌ Empty subject

• Run lint and format locally:

  • uv tool run [email protected] check --fix .
  • uv tool run [email protected] format .
  • CI job lint enforces ruff default format/lint rules on all new codes.