You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an optional nationwide China Weather reconciliation pipeline to complement existing CMA alerts, expanding weather ID deduplication and documenting the new fallback behaviour and configuration.
New Features:
Introduce a China Weather reconciliation service that polls compact national activity warning indexes and dispatches normalized details through the existing weather event pipeline when enabled.
Add a configurable weather_alarm_fallback runtime option, with bounded polling interval, request timeout, and detail concurrency for the reconciliation loop.
Implement a 24-hour bounded deduplication cache for weather event IDs to consistently suppress duplicate alerts across WebSocket and HTTP sources.
Enhancements:
Harden China Weather detail URL handling with strict validation to reject unsafe paths and malformed identifiers before network access.
Documentation:
Document the optional China Weather nationwide activity warning reconciliation source, its configuration, and its relationship to existing CMA FAN Studio alerts in the README.
Record the new reconciliation feature and extended weather ID dedup cache in the changelog.
Tests:
Add comprehensive unit tests for China Weather reconciliation primitives, configuration clamping, deduplication behaviour, URL safety checks, runtime loop control, and integration with the existing weather parser and runtime.
Summary by CodeRabbit
新功能
新增中国天气网全国活动预警回退对账（默认关闭）：定时轮询、增量详情抓取、事件 ID 有界去重与派发。
实现一个可选的全国范围 China Weather 活动预警对账任务，周期性读取公共紧凑索引，以第一次成功快照作为基线，只为新出现的官方 ID 获取详情，重建与 FAN 兼容的事件 ID，复用现有的 china_weather_fanstudio 解析和发送流水线，避免 FAN WebSocket 与 HTTP 之间的重复推送，在不影响 WebSocket 的情况下处理 HTTP 错误，并且不引入新的第三方依赖或城市级逻辑。
Add an optional nationwide China Weather reconciliation pipeline that polls a compact warning index, normalizes detail payloads into FAN-compatible weather events, and feeds them into the existing china_weather_fanstudio flow with robust deduplication and safety checks.
Sequence diagram for China Weather reconciliation polling and dispatch
sequenceDiagram
participant Runtime as DisasterServiceRuntimeService
participant Reconciler as ChinaWeatherReconciler
participant HTTP as aiohttp_ClientSession
participant Parser as WeatherAlarmParser
participant Pipeline as DisasterEventPipeline
Runtime->>Runtime: start_scheduled_http_fetch()
Runtime->>Runtime: _run_china_weather_loop(fallback_config)
Runtime->>HTTP: ClientSession(timeout, headers)
loop every poll_interval_seconds while service.running
Runtime->>HTTP: fetch_text(_CHINA_WEATHER_INDEX_URL)
HTTP-->>Runtime: index_script
Runtime->>Reconciler: reconcile(index_script, fetch_detail, _dispatch_china_weather_payload)
Reconciler->>HTTP: fetch_detail(detail_path)
HTTP-->>Reconciler: detail_script
Reconciler->>Reconciler: parse_warning_detail(detail_script, reference)
Reconciler->>Runtime: _dispatch_china_weather_payload(payload)
Runtime->>Parser: parse_event("china_weather_fanstudio", json.dumps(payload))
Parser-->>Runtime: event
Runtime->>Pipeline: _handle_disaster_event(event)
end
Loading
File-Level Changes
Change
Details
Files
Wire an optional China Weather reconciliation polling loop into the disaster runtime, gated by configuration and existing source enablement.
Import aiohttp and new China Weather reconciliation primitives into the disaster runtime service.
Resolve WeatherFallbackConfig from the top-level service config with bounded poll interval, timeout, and concurrency.
Start a named China Weather HTTP task only when the fallback is enabled and the china_weather_fanstudio source is active.
Implement _run_china_weather_loop to maintain an aiohttp session, poll the public China Weather index at configured intervals, and invoke the reconciler with index script, detail fetcher, and dispatch callback.
Add _dispatch_china_weather_payload to parse reconciled payloads via the china_weather_fanstudio parser and feed them once into the existing disaster event pipeline.
Define constants for the China Weather index URL, detail base URL, and required HTTP headers (User-Agent and Referer).
core/app/runtime/disaster_service_runtime.py
Introduce pure China Weather reconciliation services with index/detail parsing, event ID reconstruction, deduplication, and safe detail-path validation.
Create WeatherFallbackConfig, WarningReference, WarningSnapshotTracker, BoundedTTLSet, ReconciliationCycleResult, and ChinaWeatherReconciler in a new china_weather_reconciliation module.
Implement resolve_fallback_config to read weather_alarm_fallback, clamp numeric bounds, and expose an immutable config dataclass.
Parse compact index scripts into WarningReference lists, rejecting malformed payloads or rows and supporting empty snapshots.
Parse detail scripts into FAN-compatible payloads, including type/level code normalization, severity color mapping, headline/title/content extraction, coordinates, and transport metadata.
Validate and normalize warning identifiers to FAN-style event IDs, enforcing timestamp shape and basic sanity checks.
Implement WarningSnapshotTracker to warm on a valid index and subsequently emit only new identifiers while bounding stored snapshot size.
Implement BoundedTTLSet to track processed event IDs with TTL-based expiry and capacity enforcement.
Implement ChinaWeatherReconciler.reconcile to identify new references, fetch/parse details with bounded concurrency, call the downstream dispatch once per reference, and report new/consumed/failed identifiers, treating detail failures as retryable and dispatch returns/exceptions as at-most-once consumption.
Implement validate_detail_path to strictly accept only safe, unencoded relative file names and reject URLs, traversal, nested paths, backslashes, queries, fragments, and disallowed characters.
Extend the weather parser’s deduplication to a bounded TTL set shared with HTTP reconciliation, keeping existing china_weather_fanstudio parsing behavior.
Replace the WeatherAlarmParser deque-based cache with BoundedTTLSet configured for 24h TTL and 4096 max entries.
Use the new cache’s add and membership semantics to filter duplicate event IDs across both FAN WebSocket and HTTP reconciliation streams.
Update inline comments to reflect cache semantics (from queue to cache).
core/parsers/weather_parser.py
Expose the reconciliation primitives via a weather services package for reuse by runtime and parser.
Add a new core.services.weather package with an init exporting BoundedTTLSet, ChinaWeatherReconciler, WeatherFallbackConfig and related helpers.
Adjust imports in runtime and parser to consume types from core.services.weather instead of local definitions.
Document the optional China Weather fallback source and configuration in README and changelog.
Update README data-source table to mention the optional China Weather reconciliation for CMA warnings.
Add a new subsection describing weather_alarm_fallback semantics, including enablement conditions, baseline behavior, polling interval, timeout, concurrency, and deduplication strategy with a JSON config example.
Clarify CMA latency expectations when the optional reconciliation source is enabled.
Add an Unreleased section to CHANGELOG highlighting the new fallback feature and dedup cache expansion plus related tests.
README.md CHANGELOG.md
Add comprehensive unit tests for China Weather reconciliation logic, runtime integration, and dedup behavior.
Introduce tests for fallback config defaulting and clamping, weather parser cache contract, and dedup retention behavior.
Test index parsing for malformed rows, wrapper validation, and empty snapshots; detail parsing for wrapper checks, trailing data, codes, identifier matching, and event ID reconstruction.
Test WarningSnapshotTracker warm-start semantics and bounded snapshot behavior, and BoundedTTLSet expiry/cap logic.
Test ChinaWeatherReconciler async behavior across baseline, new warning dispatch, detail failure isolation and retry, at-most-once consumption when dispatch raises or returns None, invalid index handling, and unsafe detail-path rejection.
Add runtime-level async tests that exercise the polling loop’s aiohttp contract, cancellation propagation, parse/dispatch behavior when parse_event returns None, and scheduled task selection with enabled/disabled fallback and existing Wolfx tasks.
Verify HTTP headers/constants for the China Weather client via tests.
Implement an optional nationwide China Weather activity warning reconciliation task that periodically reads the public compact index, uses the first successful snapshot as a baseline, only fetches details for newly appeared official IDs, reconstructs FAN-compatible event IDs, reuses the existing china_weather_fanstudio parsing and sending pipeline, avoids duplicate pushes between FAN WebSocket and HTTP, handles HTTP errors without impacting WebSocket, and introduces no new third-party dependencies or city-specific logic.
Extend the weather warning event ID de-duplication mechanism to use a bounded TTL cache with sufficient capacity (e.g., 24h TTL, up to 4096 entries) so FAN and HTTP compensation share the same logical event IDs and can be cross-transport de-duplicated.
Update documentation and add tests to describe and validate the new nationwide weather alarm reconciliation feature, its configuration bounds, failure handling, URL safety, runtime integration, and de-duplication behavior.
✅
Possibly linked issues
[Feature] 为 FAN 气象预警增加全国活动预警对账补偿 #143: PR adds the optional China Weather reconciliation task, ID caching, config, and docs exactly as the issue specifies.
Tips and commands
Interacting with Sourcery
Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a title at any time. You can also comment @sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment @sourcery-ai summary on the pull request to
(re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull
request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment @sourcery-ai review to trigger a new review!
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces an optional, low-frequency China Weather national active warning reconciliation fallback (weather_alarm_fallback) to supplement the real-time FAN Studio stream. It adds the configuration schema, implements the core reconciliation and parsing logic with a bounded TTL cache for deduplication, integrates the polling loop into the disaster service runtime, and includes comprehensive unit tests. The review feedback highlights two important optimization opportunities: first, removing the detail semaphore restriction around the downstream dispatch call to prevent performance bottlenecks, and second, optimizing the BoundedTTLSet._purge_expired method to break early from the ordered dictionary traversal once a non-expired entry is encountered.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
对账测试通过 importlib.util.spec_from_file_location 和一些合成包来构建自定义的模块导入图；这相当复杂，而且在未来目录结构变化时可能比较脆弱——建议重构为直接通过公共包 API 进行测试，或者尽可能使用更简单的假对象 / stub。
给 AI Agent 的提示
Please address the comments from this code review:
## Overall Comments- In `ChinaWeatherReconciler._process_reference`, the same `detail_semaphore` is used to guard both network fetch and downstream dispatch; if the intent is only to cap HTTP concurrency, consider not wrapping the dispatch in the semaphore so you don’t unnecessarily serialize the event pipeline.
- The reconciliation tests build a custom module import graph using `importlib.util.spec_from_file_location` and synthetic packages; this is quite intricate and may be brittle against future layout changes—consider refactoring to exercise the public package API directly or using simpler fakes/stubs where possible.
## Individual Comments### Comment 1
<locationpath="tests/test_china_weather_reconciliation.py"line_range="631-271" />
<code_context>
+ async def test_unsafe_detail_paths_are_rejected_before_fetch(self) -> None:
</code_context>
<issue_to_address>
**suggestion (testing):** Add direct unit tests for validate_detail_path to cover all path validation rules.
The async reconciler test verifies that obviously unsafe paths are blocked, but `validate_detail_path` enforces additional rules that aren’t directly tested:
- Rejecting leading/trailing whitespace
- Handling URL-encoded components (e.g. `%2e%2e%2fencoded.html`)
- Empty string and non-string inputs
- Single-dot and double-dot names (`"."`, "..")
Because `validate_detail_path` is exported from `core.services.weather` and acts as a security-critical guard, please add targeted unit tests that call it directly and assert both allowed and rejected cases, so future changes to the path rules are captured explicitly rather than inferred via reconciler behavior.
Suggested implementation:
```pythonasyncdeftest_unsafe_detail_paths_are_rejected_before_fetch(self) -> None:
deftest_validate_detail_path_accepts_safe_paths(self) -> None:
safe_paths = (
"a.html",
"b.json",
"index.html",
)
for path in safe_paths:
# Should not raise for safe, normalized paths
validate_detail_path(path)
deftest_validate_detail_path_rejects_unsafe_and_malformed_paths(self) -> None:
unsafe_paths = (
# Existing unsafe patterns"https://evil.example/a.html",
"//evil.example/a.html",
"/absolute.html",
"../traversal.html",
"nested/a.html",
"nested\\a.html",
"a.html?query=1",
# Leading/trailing whitespace" leading.html",
"trailing.html ",
"\ta.html",
"\na.html",
# URL-encoded components"%2e%2e%2fencoded.html", # "../encoded.html""%2E%2E%2Fencoded.html",
# Empty and non-path-ish inputs"",
"",
# Single-dot and double-dot names".",
"..",
)
for path in unsafe_paths:
withself.assertRaises(ValueError):
validate_detail_path(path)
```1. Ensure `validate_detail_path` is imported at the top of `tests/test_china_weather_reconciliation.py`, e.g.:
`from core.services.weather import validate_detail_path`.
2. If `validate_detail_path` signals invalid paths using a different exception type (e.g. `RuntimeError` or a custom exception) or by returning a boolean instead of raising, adjust the `assertRaises(ValueError)` block accordingly:
- If it returns `False` for invalid paths, change the loop to `self.assertFalse(validate_detail_path(path))`.
- If it returns the normalized path for valid inputs, you may want to assert equality for some of the safe cases, e.g. `self.assertEqual(path, validate_detail_path(path))`.
3. If your test class uses any specific mixins or helpers for validation-related tests, you can move these new test methods into that class or adapt naming/structure to match existing conventions.
</issue_to_address>
帮我变得更有用！请在每条评论上点 👍 或 👎，我会根据你的反馈改进后续评审。
Original comment in English
Hey - I've found 1 issue, and left some high level feedback:
In ChinaWeatherReconciler._process_reference, the same detail_semaphore is used to guard both network fetch and downstream dispatch; if the intent is only to cap HTTP concurrency, consider not wrapping the dispatch in the semaphore so you don’t unnecessarily serialize the event pipeline.
The reconciliation tests build a custom module import graph using importlib.util.spec_from_file_location and synthetic packages; this is quite intricate and may be brittle against future layout changes—consider refactoring to exercise the public package API directly or using simpler fakes/stubs where possible.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments- In `ChinaWeatherReconciler._process_reference`, the same `detail_semaphore` is used to guard both network fetch and downstream dispatch; if the intent is only to cap HTTP concurrency, consider not wrapping the dispatch in the semaphore so you don’t unnecessarily serialize the event pipeline.
- The reconciliation tests build a custom module import graph using `importlib.util.spec_from_file_location` and synthetic packages; this is quite intricate and may be brittle against future layout changes—consider refactoring to exercise the public package API directly or using simpler fakes/stubs where possible.
## Individual Comments### Comment 1
<locationpath="tests/test_china_weather_reconciliation.py"line_range="631-271" />
<code_context>
+ async def test_unsafe_detail_paths_are_rejected_before_fetch(self) -> None:
</code_context>
<issue_to_address>
**suggestion (testing):** Add direct unit tests for validate_detail_path to cover all path validation rules.
The async reconciler test verifies that obviously unsafe paths are blocked, but `validate_detail_path` enforces additional rules that aren’t directly tested:
- Rejecting leading/trailing whitespace
- Handling URL-encoded components (e.g. `%2e%2e%2fencoded.html`)
- Empty string and non-string inputs
- Single-dot and double-dot names (`"."`, "..")
Because `validate_detail_path` is exported from `core.services.weather` and acts as a security-critical guard, please add targeted unit tests that call it directly and assert both allowed and rejected cases, so future changes to the path rules are captured explicitly rather than inferred via reconciler behavior.
Suggested implementation:
```pythonasyncdeftest_unsafe_detail_paths_are_rejected_before_fetch(self) -> None:
deftest_validate_detail_path_accepts_safe_paths(self) -> None:
safe_paths = (
"a.html",
"b.json",
"index.html",
)
for path in safe_paths:
# Should not raise for safe, normalized paths
validate_detail_path(path)
deftest_validate_detail_path_rejects_unsafe_and_malformed_paths(self) -> None:
unsafe_paths = (
# Existing unsafe patterns"https://evil.example/a.html",
"//evil.example/a.html",
"/absolute.html",
"../traversal.html",
"nested/a.html",
"nested\\a.html",
"a.html?query=1",
# Leading/trailing whitespace" leading.html",
"trailing.html ",
"\ta.html",
"\na.html",
# URL-encoded components"%2e%2e%2fencoded.html", # "../encoded.html""%2E%2E%2Fencoded.html",
# Empty and non-path-ish inputs"",
"",
# Single-dot and double-dot names".",
"..",
)
for path in unsafe_paths:
withself.assertRaises(ValueError):
validate_detail_path(path)
```1. Ensure `validate_detail_path` is imported at the top of `tests/test_china_weather_reconciliation.py`, e.g.:
`from core.services.weather import validate_detail_path`.
2. If `validate_detail_path` signals invalid paths using a different exception type (e.g. `RuntimeError` or a custom exception) or by returning a boolean instead of raising, adjust the `assertRaises(ValueError)` block accordingly:
- If it returns `False` for invalid paths, change the loop to `self.assertFalse(validate_detail_path(path))`.
- If it returns the normalized path for valid inputs, you may want to assert equality for some of the safe cases, e.g. `self.assertEqual(path, validate_detail_path(path))`.
3. If your test class uses any specific mixins or helpers for validation-related tests, you can move these new test methods into that class or adapt naming/structure to match existing conventions.
</issue_to_address>
Sourcery is free for open source - if you like our reviews please consider sharing them ✨
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
The pull request is currently not up to standards according to Codacy analysis. The most significant concern is a potential logic flaw in the weather parser's deduplication mechanism, where a mismatch between internal IDs and payload IDs could cause redundant alerts.
Additionally, several files exhibit high complexity or excessive length, notably in the runtime loop and the weather warning parser. While the feature implementation aligns with the requirement to provide an optional, bounded reconciliation service for China Weather alerts, refactoring is recommended for the main polling loop and the data parsing logic to ensure long-term maintainability.
Test suggestions
Verify that the first reconciliation cycle establishes a baseline and does not trigger alerts.
Verify that the BoundedTTLSet correctly expires old entries and respects the entry limit.
Verify that validate_detail_path rejects absolute paths, directory traversal (../), and URL parameters.
Verify that normalize_weather_warning_code corrects conflicting codes based on semantic text analysis.
Verify that the fallback configuration correctly clamps out-of-bounds numeric values for interval, timeout, and concurrency.
Verify that detail fetch failures are retried in the next cycle while dispatch failures follow 'at-most-once' semantics.
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@core/parsers/weather_parser.py`:
- Around line 20-40: 更新 _extract_issue_time，使用严格正则从事件 ID 中解析官方下划线格式和 FAN
连字符格式的时间段（如 310000-20260713100000-11B0102）。仅接受完整有效的时间字段，解析失败或格式不匹配时继续返回
effective_time，确保缺失 effective 时仍能使用 ID 中的发布时间。
In `@core/services/weather/china_weather_reconciliation.py`:
- Around line 290-295: 限制新增记录的处理规模，避免在 asyncio.gather 中为 new_references
的每条记录一次性创建任务。更新包含 _process_reference 的处理流程，使用固定数量 worker
或有界队列（或在进入处理前拒绝超过容量的快照），确保并发与待处理任务数量有明确上限，而不要仅依赖 detail_concurrency 或
max_entries。
In `@README.md`:
- Around line 557-564: 将 README.md 中 weather_alarm_fallback 配置示例包装在最外层 JSON
对象的大括号内，使用户复制整个代码块时得到有效 JSON；保留现有配置键和值不变。
In `@tests/test_china_weather_reconciliation.py`:
- Around line 475-482: Update the missing_type_code and unsupported_level_code
payloads in test_parse_warning_detail_rejects_missing_or_unsupported_codes to
include the matching identifier expected by REF_A, while preserving each
payload’s intended invalid condition so the tests reach the missing TYPECODE and
unsupported LEVELCODE branches respectively.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
Push a commit to this branch (recommended)
Create a new PR with the fixes
ℹ️ Review info⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 904c10e3-e307-46b5-99f2-2cef2d18ad76
📥 Commits
Reviewing files that changed from the base of the PR and between 564c330 and 87836bd.
[warning] 29-29: Do not make http calls without encryption
Context: "http://www.weather.com.cn/alarm/"
Note: [CWE-319] Cleartext Transmission of Sensitive Information.
(requests-http)
[info] 271-271: use jsonify instead of json.dumps for JSON output
Context: json.dumps(payload, ensure_ascii=False)
Note: [CWE-116] Improper Encoding or Escaping of Output.
(use-jsonify)
tests/test_china_weather_reconciliation.py
[info] 136-136: use jsonify instead of json.dumps for JSON output
Context: json.dumps({'count': str(len(rows)), 'data': rows})
Note: [CWE-116] Improper Encoding or Escaping of Output.
(use-jsonify)
[info] 140-149: use jsonify instead of json.dumps for JSON output
Context: json.dumps(
{
"ISSUETIME": "2026-07-13 10:10:00",
"head": reference.title,
"ISSUECONTENT": "Expect severe weather.",
"TYPECODE": "01",
"LEVELCODE": "02",
"identifier": reference.identifier,
}
)
Note: [CWE-116] Improper Encoding or Escaping of Output.
(use-jsonify)
tests/test_disaster_service_runtime.py
[warning] 188-188: Do not make http calls without encryption
Context: "http://www.weather.com.cn/alarm/"
Note: [CWE-319] Cleartext Transmission of Sensitive Information.
(requests-http)
[warning] 276-276: Do not make http calls without encryption
Context: "http://www.weather.com.cn/alarm/"
Note: [CWE-319] Cleartext Transmission of Sensitive Information.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
📝 描述 / Description
FAN Studio 气象 WebSocket 当前只提供单条最新快照；多个地区在同一采集周期内连续发布预警时，中间事件可能在进入 AstrBot 前被覆盖。
本 PR 增加一个默认关闭、全国通用的中国天气网活动预警对账源。它不替换 FAN 实时流，也不针对上海或任何单一地区写特殊规则。
Closes #143
🛠️ 改动点 / Modifications
新增中国天气网紧凑活动预警索引与详情解析，按官方标识、灾种和等级重建 FAN 兼容事件 ID。
首次成功快照仅建立基线；后续只抓取新官方 ID 的详情。
继续复用
china_weather_fanstudio的解析、过滤、展示、统计和发送链。新增 24 小时、最多 4096 条的气象事件 ID 缓存，抑制 FAN 与 HTTP 到达顺序造成的重复推送。
详情校验、下载或解析失败会隔离并在下一轮重试；一旦进入现有发送链，本层按最多一次语义处理，避免部分发送后的重复。
严格限制详情路径，拒绝协议、主机、绝对路径、目录穿越、查询参数、片段和编码路径。
新增默认关闭的
weather_alarm_fallback配置，轮询、超时和并发均有上下界。保留既有 Wolfx 任务和 FAN WebSocket 行为；未启用配置时不创建对账任务。
这不是一个破坏性变更 / This is NOT a breaking change.
📸 运行截图或测试结果 / Screenshots or Test Results
额外验证：
_conf_schema.json可正常解析。✅ 检查清单 / Checklist
aiohttp。Summary by Sourcery
添加一个可选的全国级“中国天气”对账管线，用于补充现有的 CMA 预警，扩展天气 ID 去重能力，并记录新的回退行为和配置。
新特性：
weather_alarm_fallback，为对账循环设置受限的轮询间隔、请求超时和详情并发度。增强：
文档：
测试：
Original summary in English
Summary by Sourcery
Add an optional nationwide China Weather reconciliation pipeline to complement existing CMA alerts, expanding weather ID deduplication and documenting the new fallback behaviour and configuration.
New Features:
weather_alarm_fallbackruntime option, with bounded polling interval, request timeout, and detail concurrency for the reconciliation loop.Enhancements:
Documentation:
Tests:
Summary by CodeRabbit