BUG-T13: Per-Tool Latency Statistics does not show params when capture_params is false

[SoundBlaster]

Description

Fixes BUG-T13 by making the Per-Tool Latency Statistics table explicitly show when parameter capture is disabled.

Implemented changes:

• Added frontend /api/config loading so dashboard.js can read metrics.capture_params.
• Added a latency-table disabled-state hint row and disabled param toggle controls when capture_params is false.
• Updated empty-state parameter messaging to distinguish disabled capture vs. no captured patterns yet.
• Added regression assertions in tests/unit/webui/test_server.py.
• Archived task artifacts and validation report under SPECS/ARCHIVE/BUG-T13_Per-Tool_Latency_Statistics_does_not_show_params_when_capture_params_is_false/.

Validation report:

• SPECS/ARCHIVE/BUG-T13_Per-Tool_Latency_Statistics_does_not_show_params_when_capture_params_is_false/BUG-T13_Validation_Report.md

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactoring
• CI/CD improvement

Quality Gates

Before submitting, ensure all quality gates pass:

make check

Or run individually:

• make test - All tests pass with ≥90% coverage
• make lint - No linting errors
• make format - Code is properly formatted
• make typecheck - Type checking passes
• make doccheck - Documentation is synced with DocC (if docs changed)

Documentation Sync

If you modified files in docs/, ensure corresponding DocC files are also updated:

docs/ file	DocC file
docs/installation.md	mcpbridge-wrapper.docc/Installation.md
docs/cursor-setup.md	mcpbridge-wrapper.docc/CursorSetup.md
docs/claude-setup.md	mcpbridge-wrapper.docc/ClaudeCodeSetup.md
docs/codex-setup.md	mcpbridge-wrapper.docc/CodexCLISetup.md
docs/troubleshooting.md	mcpbridge-wrapper.docc/Troubleshooting.md
docs/architecture.md	mcpbridge-wrapper.docc/Architecture.md
docs/environment-variables.md	mcpbridge-wrapper.docc/EnvironmentVariables.md
README.md	mcpbridge-wrapper.docc/mcpbridge-wrapper.md

• Documentation changes are synced with DocC catalog (or N/A)

Testing

• Added/updated tests for new functionality
• All tests pass locally
• Manually tested the changes

Checklist

• Code follows the project's style guidelines
• Self-review completed
• Comments added for complex code
• Documentation updated (if needed)
• No new warnings generated
• PR title is descriptive