BUG-T14: Rows in Per-Tool Latency Statistics fold automatically immediately after unfolding

[SoundBlaster]

Description

Fixes BUG-T14 by preserving expanded rows in the Per-Tool Latency table during periodic dashboard refreshes.

What changed

• Added persistent latencyExpandedRows state in src/mcpbridge_wrapper/webui/static/dashboard.js.
• Collected and reapplied expanded latency rows after table re-render.
• Updated toggle handling to persist explicit user expand/collapse actions.
• Added regression assertions in tests/unit/webui/test_server.py for latency-row state preservation.
• Archived task artifacts and validation/report updates under SPECS/ARCHIVE/BUG-T14_Rows_in_Per-Tool_Latency_Statistics_fold_automatically_immediately_after_unfolding/.

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)

Validation evidence:

• PYTHONPATH=src pytest → 631 passed, 5 skipped
• ruff check src/ → All checks passed!
• mypy src/ → Success: no issues found in 18 source files
• PYTHONPATH=src pytest --cov → Total coverage: 91.33%

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