Rename tech communication pullback profile

Author: Pigbibi

.github/workflows/sync-cloud-run-env.yml

@@ -77,7 +77,7 @@ jobs:
             missing_vars+=("LONGPORT_APP_SECRET_SECRET_NAME")
           fi
 
-          if [ "${STRATEGY_PROFILE:-}" = "qqq_tech_enhancement" ] && [ -z "${LONGBRIDGE_FEATURE_SNAPSHOT_PATH:-}" ]; then
+          if { [ "${STRATEGY_PROFILE:-}" = "tech_communication_pullback_enhancement" ] || [ "${STRATEGY_PROFILE:-}" = "qqq_tech_enhancement" ]; } && [ -z "${LONGBRIDGE_FEATURE_SNAPSHOT_PATH:-}" ]; then
             missing_vars+=("LONGBRIDGE_FEATURE_SNAPSHOT_PATH")
           fi
 
@@ -279,7 +279,7 @@ jobs:
             missing_vars+=("LONGPORT_APP_SECRET_SECRET_NAME")
           fi
 
-          if [ "${STRATEGY_PROFILE:-}" = "qqq_tech_enhancement" ] && [ -z "${LONGBRIDGE_FEATURE_SNAPSHOT_PATH:-}" ]; then
+          if { [ "${STRATEGY_PROFILE:-}" = "tech_communication_pullback_enhancement" ] || [ "${STRATEGY_PROFILE:-}" = "qqq_tech_enhancement" ]; } && [ -z "${LONGBRIDGE_FEATURE_SNAPSHOT_PATH:-}" ]; then
             missing_vars+=("LONGBRIDGE_FEATURE_SNAPSHOT_PATH")
           fi
 

README.md

@@ -35,7 +35,7 @@ Platform execution no longer depends on `strategy/allocation.py` or hard-coded s
 | `russell_1000_multi_factor_defensive` | Russell 1000 Multi-Factor | Yes | Yes | No | No | `us_equity` | enabled feature-snapshot stock baseline |
 | `soxl_soxx_trend_income` | SOXL/SOXX Semiconductor Trend Income | Yes | Yes | Yes | Yes | `us_equity` | current LongBridge default |
 | `tqqq_growth_income` | TQQQ Growth Income | Yes | Yes | No | No | `us_equity` | current SG dry-run line |
-| `qqq_tech_enhancement` | Tech/Communication Pullback Enhancement | Yes | Yes | No | No | `us_equity` | current HK feature-snapshot line |
+| `tech_communication_pullback_enhancement` | Tech/Communication Pullback Enhancement | Yes | Yes | No | No | `us_equity` | current HK feature-snapshot line |
 
 Check the current matrix locally:
 
@@ -114,7 +114,7 @@ BOXX: $34,000.00  Cash: $10,000.00
 | `LONGPORT_APP_SECRET` | Yes | LongPort OpenAPI app secret (for token refresh); recommended to inject from the region-specific Secret Manager secret for this deployment, such as `longport-app-secret-hk` / `longport-app-secret-sg` |
 | `LONGPORT_SECRET_NAME` | No | Secret Manager secret name for LongPort token (default: `longport_token_hk`) |
 | `ACCOUNT_PREFIX` | No | Alert/log prefix for account/environment (default: `DEFAULT`) |
-| `STRATEGY_PROFILE` | No | Strategy profile selector (default: `soxl_soxx_trend_income`; enabled values include `global_etf_rotation`, `russell_1000_multi_factor_defensive`, `qqq_tech_enhancement` on HK, and `tqqq_growth_income` on SG) |
+| `STRATEGY_PROFILE` | No | Strategy profile selector (default: `soxl_soxx_trend_income`; enabled values include `global_etf_rotation`, `russell_1000_multi_factor_defensive`, `tech_communication_pullback_enhancement` on HK, and `tqqq_growth_income` on SG) |
 | `ACCOUNT_REGION` | No | Account region marker for platform-style deployment (e.g. `HK`, `SG`; defaults to `ACCOUNT_PREFIX` / `DEFAULT`) |
 | `LONGBRIDGE_DRY_RUN_ONLY` | No | Set to `true` to keep the selected deployment in dry-run mode. |
 | `NOTIFY_LANG` | No | Notification language: `en` (English, default) or `zh` (Chinese) |
@@ -138,7 +138,7 @@ Deploy the same codebase as multiple Cloud Run services (e.g. `HK` and `SG`) by
 
 - `LONGPORT_SECRET_NAME`: point to different secrets (e.g. `longport_token_hk`, `longport_token_sg`)
 - `ACCOUNT_PREFIX`: e.g. `HK`, `SG` (all Telegram/log alerts will include `[ACCOUNT_PREFIX]`)
-- `STRATEGY_PROFILE`: set per service; current live examples are `qqq_tech_enhancement` on HK and `tqqq_growth_income` on SG
+- `STRATEGY_PROFILE`: set per service; current live examples are `tech_communication_pullback_enhancement` on HK and `tqqq_growth_income` on SG
 - Current strategy domain is `us_equity`. `STRATEGY_PROFILE` now goes through a platform capability matrix plus a rollout allowlist: `eligible` means the platform can run it in theory, `enabled` means the current rollout really allows it.
 - `ACCOUNT_REGION`: explicitly mark the deployed account region (`HK` / `SG`); if unset, the app falls back to `ACCOUNT_PREFIX` or `DEFAULT`
 - `LONGBRIDGE_DRY_RUN_ONLY`: set per service when that deployment should stay dry-run
@@ -160,7 +160,7 @@ Recommended setup:
 - **GitHub Environment: `longbridge-hk`**
   - Variables: `CLOUD_RUN_REGION`, `CLOUD_RUN_SERVICE`, `ACCOUNT_PREFIX`, `ACCOUNT_REGION`, `STRATEGY_PROFILE`, `LONGPORT_SECRET_NAME`, `LONGPORT_APP_KEY_SECRET_NAME`, `LONGPORT_APP_SECRET_SECRET_NAME`
   - Optional variables: `LONGBRIDGE_FEATURE_SNAPSHOT_PATH`, `LONGBRIDGE_FEATURE_SNAPSHOT_MANIFEST_PATH`, `LONGBRIDGE_STRATEGY_CONFIG_PATH`, `LONGBRIDGE_DRY_RUN_ONLY`
-  - Current live example: `STRATEGY_PROFILE=qqq_tech_enhancement`
+  - Current live example: `STRATEGY_PROFILE=tech_communication_pullback_enhancement`
   - Recommended secret-name values: `longport-app-key-hk`, `longport-app-secret-hk`
 - **GitHub Environment: `longbridge-sg`**
   - Variables: `CLOUD_RUN_REGION`, `CLOUD_RUN_SERVICE`, `ACCOUNT_PREFIX`, `ACCOUNT_REGION`, `STRATEGY_PROFILE`, `LONGPORT_SECRET_NAME`, `LONGPORT_APP_KEY_SECRET_NAME`, `LONGPORT_APP_SECRET_SECRET_NAME`
@@ -213,7 +213,7 @@ IAM: the Cloud Run service account needs **Secret Manager Admin** (or Secret Acc
 基于 LongPort OpenAPI 和 Google Cloud Run 的量化交易系统。
 
 这个仓库通过 `QuantPlatformKit` 复用 LongPort token 处理、上下文初始化、账户快照、行情读取和下单逻辑。Cloud Run 直接部署这个仓库。
-`LongBridgePlatform` 现在可直接执行 `UsEquityStrategies` 里的全部 5 条 live `us_equity` 策略：`global_etf_rotation`、`russell_1000_multi_factor_defensive`、`soxl_soxx_trend_income`、`tqqq_growth_income` 和 `qqq_tech_enhancement`；仓库本身继续保留 LongPort 运行时、token 刷新、执行和通知流程。
+`LongBridgePlatform` 现在可直接执行 `UsEquityStrategies` 里的全部 5 条 live `us_equity` 策略：`global_etf_rotation`、`russell_1000_multi_factor_defensive`、`soxl_soxx_trend_income`、`tqqq_growth_income` 和 `tech_communication_pullback_enhancement`；仓库本身继续保留 LongPort 运行时、token 刷新、执行和通知流程。
 
 完整策略说明现在放在 [`UsEquityStrategies`](https://github.com/QuantStrategyLab/UsEquityStrategies)。下面这些章节主要保留执行侧默认值和运行时行为。
 
@@ -236,7 +236,7 @@ IAM: the Cloud Run service account needs **Secret Manager Admin** (or Secret Acc
 | `russell_1000_multi_factor_defensive` | Russell 1000 Multi-Factor | Yes | Yes | No | No | `us_equity` | 已启用的 feature-snapshot 个股基线 |
 | `soxl_soxx_trend_income` | SOXL/SOXX 半导体趋势收益 | Yes | Yes | Yes | Yes | `us_equity` | 当前 LongBridge 默认回退线 |
 | `tqqq_growth_income` | TQQQ 增长收益 | Yes | Yes | No | No | `us_equity` | 当前 SG dry-run 线路 |
-| `qqq_tech_enhancement` | 科技通信回调增强 | Yes | Yes | No | No | `us_equity` | 当前 HK feature-snapshot 线路 |
+| `tech_communication_pullback_enhancement` | 科技通信回调增强 | Yes | Yes | No | No | `us_equity` | 当前 HK feature-snapshot 线路 |
 
 本地可直接查看当前矩阵：
 
@@ -315,7 +315,7 @@ BOXX: $34,000.00  现金: $10,000.00
 | `LONGPORT_APP_SECRET` | 是 | LongPort OpenAPI 应用密钥（用于刷新 Token）；建议从当前部署对应区域的 Secret Manager 密钥注入，例如 `longport-app-secret-hk` / `longport-app-secret-sg` |
 | `LONGPORT_SECRET_NAME` | 否 | Secret Manager 中的密钥名称（默认: `longport_token_hk`） |
 | `ACCOUNT_PREFIX` | 否 | 通知/日志前缀，区分账户环境（默认: `DEFAULT`） |
-| `STRATEGY_PROFILE` | 否 | 策略档位选择（默认: `soxl_soxx_trend_income`；已启用值还包括 `global_etf_rotation`、`russell_1000_multi_factor_defensive`，当前线上 HK 用 `qqq_tech_enhancement`，SG 用 `tqqq_growth_income`） |
+| `STRATEGY_PROFILE` | 否 | 策略档位选择（默认: `soxl_soxx_trend_income`；已启用值还包括 `global_etf_rotation`、`russell_1000_multi_factor_defensive`，当前线上 HK 用 `tech_communication_pullback_enhancement`，SG 用 `tqqq_growth_income`） |
 | `ACCOUNT_REGION` | 否 | 平台化部署时的账户区域标记（如 `HK`、`SG`；默认按 `ACCOUNT_PREFIX` / `DEFAULT` 推断） |
 | `LONGBRIDGE_DRY_RUN_ONLY` | 否 | 设为 `true` 时，该部署保持 dry-run。 |
 | `NOTIFY_LANG` | 否 | 通知语言: `en`（英文，默认）或 `zh`（中文） |
@@ -339,7 +339,7 @@ Secret Manager 中需存在 `LONGPORT_SECRET_NAME` 指定的密钥（默认: `lo
 
 - `LONGPORT_SECRET_NAME`: 指向不同密钥（如 `longport_token_hk`、`longport_token_sg`）
 - `ACCOUNT_PREFIX`: 如 `HK`、`SG`（所有通知/日志将包含 `[ACCOUNT_PREFIX]`）
-- `STRATEGY_PROFILE`: 按服务分别设置；当前线上 HK 用 `qqq_tech_enhancement`，SG 用 `tqqq_growth_income`
+- `STRATEGY_PROFILE`: 按服务分别设置；当前线上 HK 用 `tech_communication_pullback_enhancement`，SG 用 `tqqq_growth_income`
 - 当前策略域是 `us_equity`。`STRATEGY_PROFILE` 现在会先经过平台能力矩阵，再经过 rollout allowlist：`eligible` 表示平台理论可跑，`enabled` 表示当前 rollout 真正放开。
 - `ACCOUNT_REGION`: 显式标记部署账户区域（`HK` / `SG`）；未设置时会回退到 `ACCOUNT_PREFIX` 或 `DEFAULT`
 - `LONGBRIDGE_DRY_RUN_ONLY`: 需要保持模拟运行时按服务单独设置
@@ -361,7 +361,7 @@ Secret Manager 中需存在 `LONGPORT_SECRET_NAME` 指定的密钥（默认: `lo
 - **GitHub Environment: `longbridge-hk`**
   - Variables: `CLOUD_RUN_REGION`、`CLOUD_RUN_SERVICE`、`ACCOUNT_PREFIX`、`ACCOUNT_REGION`、`STRATEGY_PROFILE`、`LONGPORT_SECRET_NAME`、`LONGPORT_APP_KEY_SECRET_NAME`、`LONGPORT_APP_SECRET_SECRET_NAME`
   - 可选 Variables: `LONGBRIDGE_FEATURE_SNAPSHOT_PATH`、`LONGBRIDGE_FEATURE_SNAPSHOT_MANIFEST_PATH`、`LONGBRIDGE_STRATEGY_CONFIG_PATH`、`LONGBRIDGE_DRY_RUN_ONLY`
-  - 当前线上示例：`STRATEGY_PROFILE=qqq_tech_enhancement`
+  - 当前线上示例：`STRATEGY_PROFILE=tech_communication_pullback_enhancement`
   - 建议的 secret-name 值：`longport-app-key-hk`、`longport-app-secret-hk`
 - **GitHub Environment: `longbridge-sg`**
   - Variables: `CLOUD_RUN_REGION`、`CLOUD_RUN_SERVICE`、`ACCOUNT_PREFIX`、`ACCOUNT_REGION`、`STRATEGY_PROFILE`、`LONGPORT_SECRET_NAME`、`LONGPORT_APP_KEY_SECRET_NAME`、`LONGPORT_APP_SECRET_SECRET_NAME`

decision_mapper.py

@@ -176,7 +176,7 @@ def _resolve_layout(strategy_profile: str) -> tuple[str, tuple[str, ...], tuple[
                 "investable_cash": 0.0,
             },
         )
-    if strategy_profile == "qqq_tech_enhancement":
+    if strategy_profile in {"tech_communication_pullback_enhancement", "qqq_tech_enhancement"}:
         return (
             "risk_safe_income",
             ("risk_safe",),

notifications/telegram.py

@@ -63,6 +63,7 @@
         "strategy_name_tqqq_growth_income": "TQQQ 增长收益",
         "strategy_name_global_etf_rotation": "全球 ETF 轮动",
         "strategy_name_russell_1000_multi_factor_defensive": "罗素1000多因子",
+        "strategy_name_tech_communication_pullback_enhancement": "科技通信回调增强",
         "strategy_name_qqq_tech_enhancement": "科技通信回调增强",
     },
     "en": {
@@ -113,6 +114,7 @@
         "strategy_name_tqqq_growth_income": "TQQQ Growth Income",
         "strategy_name_global_etf_rotation": "Global ETF Rotation",
         "strategy_name_russell_1000_multi_factor_defensive": "Russell 1000 Multi-Factor",
+        "strategy_name_tech_communication_pullback_enhancement": "Tech/Communication Pullback Enhancement",
         "strategy_name_qqq_tech_enhancement": "Tech/Communication Pullback Enhancement",
     },
 }

requirements.txt

@@ -1,7 +1,7 @@
 flask
 gunicorn
 quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@v0.7.13
-us-equity-strategies @ git+https://github.com/QuantStrategyLab/UsEquityStrategies.git@v0.7.17
+us-equity-strategies @ git+https://github.com/QuantStrategyLab/UsEquityStrategies.git@v0.7.20
 pandas
 requests
 pytz

research/configs/growth_pullback_tech_communication_pullback_enhancement.json

@@ -0,0 +1,44 @@
+{
+  "role": "tech_communication_pullback_enhancement",
+  "status": "research_only",
+  "strategy": "growth_pullback_systematic_v1",
+  "branch_name": "tech_communication_pullback_enhancement",
+  "name": "tech_communication_pullback_enhancement",
+  "previous_candidate_name": "cash_buffer_a__hb10__base__adv50",
+  "family": "tech_heavy_pullback",
+  "universe": "tech_heavy",
+  "normalization": "universe_cross_sectional",
+  "min_adv20_usd": 50000000.0,
+  "sector_whitelist": [
+    "Information Technology",
+    "Communication"
+  ],
+  "symbol_whitelist": [],
+  "notes": "Sector proxy only: Information Technology + Communication; no sub-industry data available",
+  "score_template": "balanced_pullback",
+  "holdings_count": 8,
+  "single_name_cap": 0.1,
+  "sector_cap": 0.4,
+  "hold_bonus": 0.1,
+  "regime": "qqq_breadth",
+  "benchmark_symbol": "QQQ",
+  "breadth_mode": "broad",
+  "breadth_symbols": [],
+  "breadth_thresholds": {
+    "soft": 0.55,
+    "hard": 0.35
+  },
+  "exposures": {
+    "risk_on": 0.8,
+    "soft_defense": 0.6,
+    "hard_defense": 0.0
+  },
+  "execution_cash_reserve_ratio": 0.0,
+  "residual_proxy": "simple_excess_return_vs_QQQ",
+  "cost_assumption_bps_one_way": 5.0,
+  "branch_role": "cash-buffered parallel branch",
+  "canonicalized_from": "growth_pullback_systematic_v1.4 cash_buffer_refinement",
+  "legacy_names": [
+    "qqq_tech_enhancement"
+  ]
+}

strategy_registry.py

@@ -28,6 +28,7 @@
         "russell_1000_multi_factor_defensive",
         "soxl_soxx_trend_income",
         "tqqq_growth_income",
+        "tech_communication_pullback_enhancement",
         "qqq_tech_enhancement",
     }
 )

tests/test_decision_mapper.py

@@ -164,7 +164,7 @@ def test_translates_weight_decision_for_tech_strategy(self):
         plan = map_strategy_decision_to_plan(
             decision,
             snapshot=snapshot,
-            strategy_profile="qqq_tech_enhancement",
+            strategy_profile="tech_communication_pullback_enhancement",
         )
 
         self.assertEqual(plan["allocation"]["target_mode"], "value")

tests/test_runtime_config_support.py

@@ -61,7 +61,7 @@ def test_platform_supported_profiles_are_filtered_by_registry(self):
                     "russell_1000_multi_factor_defensive",
                     "tqqq_growth_income",
                     "soxl_soxx_trend_income",
-                    "qqq_tech_enhancement",
+                    "tech_communication_pullback_enhancement",
                 }
             ),
         )
@@ -75,7 +75,7 @@ def test_platform_eligible_profiles_are_exposed_by_capability_matrix(self):
                     "russell_1000_multi_factor_defensive",
                     "tqqq_growth_income",
                     "soxl_soxx_trend_income",
-                    "qqq_tech_enhancement",
+                    "tech_communication_pullback_enhancement",
                 }
             ),
         )
@@ -134,7 +134,7 @@ def test_platform_profile_status_matrix_matches_current_longbridge_rollout(self)
                 "russell_1000_multi_factor_defensive",
                 "tqqq_growth_income",
                 "soxl_soxx_trend_income",
-                "qqq_tech_enhancement",
+                "tech_communication_pullback_enhancement",
             },
         )
         self.assertEqual(
@@ -160,15 +160,15 @@ def test_platform_profile_status_matrix_matches_current_longbridge_rollout(self)
         self.assertEqual(by_profile["global_etf_rotation"]["display_name"], "Global ETF Rotation")
         self.assertTrue(by_profile["global_etf_rotation"]["eligible"])
         self.assertTrue(by_profile["global_etf_rotation"]["enabled"])
-        self.assertTrue(by_profile["qqq_tech_enhancement"]["eligible"])
-        self.assertTrue(by_profile["qqq_tech_enhancement"]["enabled"])
-        self.assertEqual(by_profile["qqq_tech_enhancement"]["display_name"], "Tech/Communication Pullback Enhancement")
+        self.assertTrue(by_profile["tech_communication_pullback_enhancement"]["eligible"])
+        self.assertTrue(by_profile["tech_communication_pullback_enhancement"]["enabled"])
+        self.assertEqual(by_profile["tech_communication_pullback_enhancement"]["display_name"], "Tech/Communication Pullback Enhancement")
 
     def test_loads_feature_snapshot_env_for_tech_profile(self):
         with patch.dict(
             os.environ,
             {
-                "STRATEGY_PROFILE": "qqq_tech_enhancement",
+                "STRATEGY_PROFILE": "tech_communication_pullback_enhancement",
                 "LONGBRIDGE_FEATURE_SNAPSHOT_PATH": "gs://bucket/tech.csv",
                 "LONGBRIDGE_FEATURE_SNAPSHOT_MANIFEST_PATH": "gs://bucket/tech.csv.manifest.json",
                 "LONGBRIDGE_STRATEGY_CONFIG_PATH": "/workspace/configs/tech.json",
@@ -177,7 +177,7 @@ def test_loads_feature_snapshot_env_for_tech_profile(self):
         ):
             settings = load_platform_runtime_settings(project_id_resolver=lambda: "project-1")
 
-        self.assertEqual(settings.strategy_profile, "qqq_tech_enhancement")
+        self.assertEqual(settings.strategy_profile, "tech_communication_pullback_enhancement")
         self.assertEqual(settings.feature_snapshot_path, "gs://bucket/tech.csv")
         self.assertEqual(settings.feature_snapshot_manifest_path, "gs://bucket/tech.csv.manifest.json")
         self.assertEqual(settings.strategy_config_path, "/workspace/configs/tech.json")
@@ -216,10 +216,10 @@ def test_print_strategy_profile_status_json_matches_registry(self):
         self.assertEqual(by_profile["global_etf_rotation"]["input_mode"], "market_history")
         self.assertFalse(by_profile["global_etf_rotation"]["requires_snapshot_artifacts"])
         self.assertFalse(by_profile["global_etf_rotation"]["requires_strategy_config_path"])
-        self.assertEqual(by_profile["qqq_tech_enhancement"]["profile_group"], "snapshot_backed")
-        self.assertEqual(by_profile["qqq_tech_enhancement"]["input_mode"], "feature_snapshot")
-        self.assertTrue(by_profile["qqq_tech_enhancement"]["requires_snapshot_artifacts"])
-        self.assertTrue(by_profile["qqq_tech_enhancement"]["requires_strategy_config_path"])
+        self.assertEqual(by_profile["tech_communication_pullback_enhancement"]["profile_group"], "snapshot_backed")
+        self.assertEqual(by_profile["tech_communication_pullback_enhancement"]["input_mode"], "feature_snapshot")
+        self.assertTrue(by_profile["tech_communication_pullback_enhancement"]["requires_snapshot_artifacts"])
+        self.assertTrue(by_profile["tech_communication_pullback_enhancement"]["requires_strategy_config_path"])
         self.assertFalse(
             by_profile["russell_1000_multi_factor_defensive"]["requires_strategy_config_path"]
         )

tests/test_strategy_loader.py

@@ -103,7 +103,7 @@ def test_load_strategy_runtime_adapter_declares_hybrid_inputs(self):
     def test_load_strategy_runtime_adapter_declares_tech_snapshot_inputs(self):
         from strategy_loader import load_strategy_runtime_adapter_for_profile
 
-        adapter = load_strategy_runtime_adapter_for_profile("qqq_tech_enhancement")
+        adapter = load_strategy_runtime_adapter_for_profile("tech_communication_pullback_enhancement")
 
         self.assertEqual(
             adapter.available_inputs,