From 39ed2118d7ce5a84a7b5625919c2c117fddd3e66 Mon Sep 17 00:00:00 2001 From: Pigbibi <20649888+Pigbibi@users.noreply.github.com> Date: Wed, 3 Jun 2026 19:44:49 +0800 Subject: [PATCH] Use renamed crypto live pool pipeline checkout --- README.md | 4 ++-- README.zh-CN.md | 4 ++-- docs/operator_runbook.md | 2 +- tests/test_trend_pool_loading.py | 9 +++++++++ trend_pool_support.py | 4 ++-- 5 files changed, 16 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 546ba1d..d507642 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ BinancePlatform is a QuantStrategyLab Binance crypto execution platform. It executes runtime-enabled crypto strategies through Binance-facing workflows and self-hosted orchestration. -It is an execution layer, not a strategy research repository. Strategy logic comes from `CryptoStrategies`; snapshot and validation artifacts come from `CryptoSnapshotPipelines` when a profile requires them. +It is an execution layer, not a strategy research repository. Strategy logic comes from `CryptoStrategies`; live-pool and validation artifacts come from `CryptoLivePoolPipelines` when a profile requires them. ## Runtime boundary @@ -19,7 +19,7 @@ It is an execution layer, not a strategy research repository. Strategy logic com ## Direct vs snapshot-backed profiles -Direct runtime profiles can usually run from market history or portfolio state. Snapshot-backed profiles need a current artifact bundle from the matching snapshot pipeline before this platform should execute them. The platform should not invent strategy eligibility; it should consume the status and artifacts published by the strategy and snapshot repositories. +Direct runtime profiles can usually run from market history or portfolio state. Snapshot-backed profiles need a current artifact bundle from the matching live-pool pipeline before this platform should execute them. The platform should not invent strategy eligibility; it should consume the status and artifacts published by the strategy and live-pool repositories. ## Deploy safely diff --git a/README.zh-CN.md b/README.zh-CN.md index 2cd76ba..e6a1ed7 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -8,7 +8,7 @@ BinancePlatform 是 QuantStrategyLab 的Binance 加密货币执行平台。通过面向 Binance 的 workflow 和 self-hosted 编排执行 runtime-enabled 加密货币策略。 -它属于执行层，不是策略研究仓库。策略逻辑来自 `CryptoStrategies`；如果 profile 依赖 snapshot，验证和产物来自 `CryptoSnapshotPipelines`。 +它属于执行层，不是策略研究仓库。策略逻辑来自 `CryptoStrategies`；如果 profile 依赖 live-pool，验证和产物来自 `CryptoLivePoolPipelines`。 ## 运行边界 @@ -19,7 +19,7 @@ BinancePlatform 是 QuantStrategyLab 的Binance 加密货币执行平台。通 ## 普通 profile 与 snapshot-backed profile -普通 runtime profile 通常可以直接基于 market history 或 portfolio state 执行。Snapshot-backed profile 需要先从对应 snapshot pipeline 获取当前 artifact bundle，平台才应该执行。平台不应该自行判断策略资格，而应消费策略仓和 snapshot 仓发布的状态与产物。 +普通 runtime profile 通常可以直接基于 market history 或 portfolio state 执行。Snapshot-backed profile 需要先从对应 live-pool pipeline 获取当前 artifact bundle，平台才应该执行。平台不应该自行判断策略资格，而应消费策略仓和 live-pool 仓发布的状态与产物。 ## 安全部署顺序 diff --git a/docs/operator_runbook.md b/docs/operator_runbook.md index 77d1c47..f88fa44 100644 --- a/docs/operator_runbook.md +++ b/docs/operator_runbook.md @@ -93,7 +93,7 @@ Degraded mode: Interpretation: - `last_known_good` means fresh upstream validation failed, but a previously accepted upstream payload is still available in state -- `local_file` means upstream live access failed and the runtime fell back to a validated local file from the configured `STRATEGY_ARTIFACT_FILE`, the repo-local artifact, or a compatible `CryptoSnapshotPipelines` checkout +- `local_file` means upstream live access failed and the runtime fell back to a validated local file from the configured `STRATEGY_ARTIFACT_FILE`, the repo-local artifact, or a compatible `CryptoLivePoolPipelines` checkout - `static` is emergency-only and should be treated as lowest-confidence operation ## Strategy Artifact Settings diff --git a/tests/test_trend_pool_loading.py b/tests/test_trend_pool_loading.py index 4272a26..214d213 100644 --- a/tests/test_trend_pool_loading.py +++ b/tests/test_trend_pool_loading.py @@ -149,6 +149,15 @@ def test_validate_trend_pool_payload_preserves_ordered_symbols_in_symbol_map(sel self.assertEqual(list(result["symbol_map"]), payload["symbols"]) self.assertEqual(list(result["payload"]["symbol_map"]), payload["symbols"]) + def test_default_live_pool_candidates_include_renamed_repo_checkout(self): + default_path = Path("/tmp/live_pool_legacy.json") + + candidates = main.tp_get_default_live_pool_candidates(default_path) + candidate_text = [str(path) for path in candidates] + + self.assertEqual(candidates[0], default_path) + self.assertTrue(any("CryptoLivePoolPipelines" in value for value in candidate_text)) + def test_strategy_artifact_env_aliases_override_legacy_trend_pool_settings(self): with patch.dict( os.environ, diff --git a/trend_pool_support.py b/trend_pool_support.py index bc4360b..fb61b4e 100644 --- a/trend_pool_support.py +++ b/trend_pool_support.py @@ -247,8 +247,8 @@ def get_default_live_pool_candidates(default_live_pool_legacy_path): Path("/home/ubuntu"), } repo_names = ( - "CryptoSnapshotPipelines", - "crypto-snapshot-pipelines", + "CryptoLivePoolPipelines", + "crypto-live-pool-pipelines", "CryptoLeaderRotation", "crypto-leader-rotation", )