/cls/telegraph route broken due to upstream API returning 404

### Routes ```routes /cls/telegraph/:category? ``` ### Full routes ```fullroutes /cls/telegraph/:category? ``` ### Related documentation https://rsshub-doc.pages.dev/finance.html#cai-jing-wang ### What is expected? The /cls/telegraph route should return the latest RSS feed. ### What is actually happening? Requests to /cls/telegraph fail with 503 from RSSHub. RSSHub logs show that the upstream API returns 404 Not Found. Testing from a Windows machine / different network confirms the endpoint is no longer available. ### Deployment information Self-hosted ### Deployment information (for self-hosted) Ubuntu 22.04, Docker version 24.0 ### Additional info ```shell RSSHub log: warn: Request https://www.cls.cn/nodeapi/updateTelegraphList?appName=CailianpressWeb&category=&hasFirstVipArticle=1&os=web&sv=7.7.5&sign=a238a5f06453a6fe1e3c33e8f835c19e with error 404 remaining retry attempts: 2 error: Error in /cls/telegraph: FetchError: [GET] "https://www.cls.cn/nodeapi/updateTelegraphList?appName=CailianpressWeb&category=&hasFirstVipArticle=1&os=web&sv=7.7.5&sign=a238a5f06453a6fe1e3c33e8f835c19e": 404 Not Found info: --> GET /cls/telegraph 503 1s Powershell log (same endpoint from different Windows PC): PS C:\Users\User> Invoke-WebRequest -Uri "https://www.cls.cn/nodeapi/updateTelegraphList?appName=CailianpressWeb&category=&hasFirstVipArticle=1&os=web&sv=7.7.5&sign=a238a5f06453a6fe1e3c33e8f835c19e" -UseBasicParsing Invoke-WebRequest: 很抱歉，当前没有启用javascript，网站无法正常访问。请开启以便继续访问。关于我们网站声明联系方式用户反馈网站地图帮助首页电报话题盯盘VIPFM投研下载页面找不到了返回首页关于我们|网站声明|联系方式|用户反馈|网站地图|友情链接|举报电话：021-54679377转617举报邮箱：editor@cls.cn财联社 ©2018-2026上海界面财联社科技股份有限公司 版权所有沪ICP备14040942号-9沪公网安备31010402006047号互联网新闻信息服务许可证：31120170007沪金信备 [2021] 2号{"props":{"pageProps":{}},"page":"/404","query":{},"buildId":"iSsoUz_IeNoamqtJ52Mny","nextExport":true,"autoExport":true,"isFallback":false,"scriptLoader":[]} ``` ### This is not a duplicated issue - [x] I have searched [existing issues](https://github.com/DIYgod/RSSHub/issues) to ensure this bug has not already been reported