TradingAgents

Commit Graph

Author	SHA1	Message	Date
陈少杰	eda9980729	feat(orchestrator): add comprehensive provider and timeout validation Add three layers of configuration validation to LLMRunner: 1. Provider × base_url matrix validation - Validates all 6 providers (anthropic, openai, google, xai, ollama, openrouter) - Uses precompiled regex patterns for efficiency - Detects mismatches before expensive graph initialization 2. Timeout configuration validation - Warns when analyst/research timeouts may be insufficient - Provides recommendations based on analyst count (1-4) - Non-blocking warnings logged at init time 3. Enhanced error classification - Distinguishes provider_mismatch from provider_auth_failed - Uses heuristic detection for auth failures - Simplified nested ternary expressions for readability Improvements: - Validation runs before cache check (prevents stale cache on config errors) - EAFP pattern for cache reading (more robust than TOCTOU) - Precompiled regex patterns (avoid recompilation overhead) - All 21 unit tests passing Documentation: - docs/architecture/orchestrator-validation.md - complete validation guide - orchestrator/examples/validation_examples.py - runnable examples Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-04-16 11:43:19 +08:00
陈少杰	0ba4e40601	Keep maintainer docs aligned with the current contract-first and provenance reality The repository state has moved well past the oldest migration drafts: backend public payloads are already contract-first in several paths, research provenance now spans runner/live/full-state logs, and the offline trace/A-B toolchain is part of the normal maintainer workflow. This doc update records what is already true on mainline versus what remains target-state, so future changes stop treating stale design notes as the current architecture.\n\nConstraint: Reflect only behavior that is already present on mainline; avoid documenting unrecovered worker-only experiments as current reality\nRejected: Collapse everything into README \| maintainer-facing migration/provenance details would become harder to keep precise and reviewable\nConfidence: high\nScope-risk: narrow\nDirective: When changing backend public fields or profiling semantics, update AGENTS.md and the linked docs in the same change set so maintainer guidance does not drift behind code again\nTested: git diff --check on updated documentation set\nNot-tested: No runtime/code-path changes in this docs-only commit	2026-04-14 15:20:39 +08:00
陈少杰	b6e57d01e3	Stabilize TradingAgents contracts so orchestration and dashboard can converge This change set introduces a versioned result contract, shared config schema/loading, provider/data adapter seams, and a no-strategy application-service skeleton so the current research graph, orchestrator layer, and dashboard backend stop drifting further apart. It also keeps the earlier MiniMax compatibility and compact-prompt work aligned with the new contract shape and extends regression coverage so degradation, fallback, and service migration remain testable during the next phases. Constraint: Must preserve existing FastAPI entrypoints and fallback behavior while introducing an application-service seam Constraint: Must not turn application service into a new strategy or learning layer Rejected: Full backend rewrite to service-only execution now \| too risky before contract and fallback paths stabilize Rejected: Leave provider/data/config logic distributed across scripts and endpoints \| continues boundary drift and weakens verification Confidence: high Scope-risk: broad Directive: Keep future application-service changes orchestration-only; move any scoring, signal fusion, or learning logic to orchestrator or tradingagents instead Tested: python -m compileall orchestrator tradingagents web_dashboard/backend Tested: python -m pytest orchestrator/tests/test_signals.py orchestrator/tests/test_llm_runner.py orchestrator/tests/test_quant_runner.py orchestrator/tests/test_contract_v1alpha1.py orchestrator/tests/test_application_service.py orchestrator/tests/test_provider_adapter.py web_dashboard/backend/tests/test_main_api.py web_dashboard/backend/tests/test_portfolio_api.py web_dashboard/backend/tests/test_api_smoke.py web_dashboard/backend/tests/test_services_migration.py -q Not-tested: live MiniMax/provider execution against external services Not-tested: full dashboard/manual websocket flow against a running frontend Not-tested: omx team runtime end-to-end in the primary workspace	2026-04-13 17:25:07 +08:00

Author

SHA1

Message

Date

陈少杰

eda9980729

feat(orchestrator): add comprehensive provider and timeout validation

Add three layers of configuration validation to LLMRunner:

1. Provider × base_url matrix validation
   - Validates all 6 providers (anthropic, openai, google, xai, ollama, openrouter)
   - Uses precompiled regex patterns for efficiency
   - Detects mismatches before expensive graph initialization

2. Timeout configuration validation
   - Warns when analyst/research timeouts may be insufficient
   - Provides recommendations based on analyst count (1-4)
   - Non-blocking warnings logged at init time

3. Enhanced error classification
   - Distinguishes provider_mismatch from provider_auth_failed
   - Uses heuristic detection for auth failures
   - Simplified nested ternary expressions for readability

Improvements:
- Validation runs before cache check (prevents stale cache on config errors)
- EAFP pattern for cache reading (more robust than TOCTOU)
- Precompiled regex patterns (avoid recompilation overhead)
- All 21 unit tests passing

Documentation:
- docs/architecture/orchestrator-validation.md - complete validation guide
- orchestrator/examples/validation_examples.py - runnable examples

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-16 11:43:19 +08:00

陈少杰

0ba4e40601

Keep maintainer docs aligned with the current contract-first and provenance reality

The repository state has moved well past the oldest migration drafts: backend public payloads are already contract-first in several paths, research provenance now spans runner/live/full-state logs, and the offline trace/A-B toolchain is part of the normal maintainer workflow. This doc update records what is already true on mainline versus what remains target-state, so future changes stop treating stale design notes as the current architecture.\n\nConstraint: Reflect only behavior that is already present on mainline; avoid documenting unrecovered worker-only experiments as current reality\nRejected: Collapse everything into README | maintainer-facing migration/provenance details would become harder to keep precise and reviewable\nConfidence: high\nScope-risk: narrow\nDirective: When changing backend public fields or profiling semantics, update AGENTS.md and the linked docs in the same change set so maintainer guidance does not drift behind code again\nTested: git diff --check on updated documentation set\nNot-tested: No runtime/code-path changes in this docs-only commit

2026-04-14 15:20:39 +08:00

陈少杰

b6e57d01e3

Stabilize TradingAgents contracts so orchestration and dashboard can converge

This change set introduces a versioned result contract, shared config schema/loading, provider/data adapter seams, and a no-strategy application-service skeleton so the current research graph, orchestrator layer, and dashboard backend stop drifting further apart. It also keeps the earlier MiniMax compatibility and compact-prompt work aligned with the new contract shape and extends regression coverage so degradation, fallback, and service migration remain testable during the next phases.

Constraint: Must preserve existing FastAPI entrypoints and fallback behavior while introducing an application-service seam
Constraint: Must not turn application service into a new strategy or learning layer
Rejected: Full backend rewrite to service-only execution now | too risky before contract and fallback paths stabilize
Rejected: Leave provider/data/config logic distributed across scripts and endpoints | continues boundary drift and weakens verification
Confidence: high
Scope-risk: broad
Directive: Keep future application-service changes orchestration-only; move any scoring, signal fusion, or learning logic to orchestrator or tradingagents instead
Tested: python -m compileall orchestrator tradingagents web_dashboard/backend
Tested: python -m pytest orchestrator/tests/test_signals.py orchestrator/tests/test_llm_runner.py orchestrator/tests/test_quant_runner.py orchestrator/tests/test_contract_v1alpha1.py orchestrator/tests/test_application_service.py orchestrator/tests/test_provider_adapter.py web_dashboard/backend/tests/test_main_api.py web_dashboard/backend/tests/test_portfolio_api.py web_dashboard/backend/tests/test_api_smoke.py web_dashboard/backend/tests/test_services_migration.py -q
Not-tested: live MiniMax/provider execution against external services
Not-tested: full dashboard/manual websocket flow against a running frontend
Not-tested: omx team runtime end-to-end in the primary workspace

2026-04-13 17:25:07 +08:00

3 Commits