dc09888c49
Request: - Run the scheduled hk-ipo-analyst refresh as of 2026-06-22T15:47:32Z. - Refresh the IPO candidate universe and network facts through the archivist before analysis. - Rebuild the analysis dataset and publish the latest broad candidate report in Simplified Chinese. Changes: - Archived the HKEX current new-listing page, new official allotment-result PDFs for 06067 and 06132, extracted text, a fresh VBKR/Jieli T0.95 market-heat snapshot, ipohk external history, and recent Yahoo price-performance responses. - Updated structured SQLite facts and CSV snapshots, including official T1 demand for 06067 and 06132 while keeping live subscription heat in ipo_market_heat. - Rebuilt data/snapshots/analysis_model_v0_dataset.csv after the archive refresh. - Rewrote reports/2026-06-22_latest_ipo_candidates_analysis.md and mirrored the same content to reports/README.md. Verification: - Ran archive_hkex_current_new_listings.py, archive_hkex_documents.py, backfill_t1_demand_from_text.py, archive_t0_5_market_heat.py, archive_price_performance.py, archive_ipohk_history.py, and build_analysis_dataset.py with as-of 2026-06-22T15:47:32Z. - Confirmed reports/README.md matches the dated report with cmp. - Ran git diff --check and git diff --cached --check. - Checked source_refs paths are repo-relative and existing. - Checked the latest 13 T0.95 live heat rows remain separate from official T1 demand rows. Next useful context: - 06067 and 06132 now have official T1 demand in the archive; 06106 and 02335 remain T1 data_gap names as of this run. - The 15:47Z VBKR/Jieli live heat values matched the earlier 13:57Z values for active candidates. - Price refresh still has provider gaps for some historical tickers, including internal D1 price data for 00901.
1 line
2.2 KiB
JSON
1 line
2.2 KiB
JSON
{"chart":{"result":[{"meta":{"currency":"HKD","symbol":"2553.HK","exchangeName":"HKG","fullExchangeName":"HKSE","instrumentType":"EQUITY","firstTradeDate":1780450200,"regularMarketTime":1782115693,"hasPrePostMarketData":false,"gmtoffset":28800,"timezone":"HKT","exchangeTimezoneName":"Asia/Hong_Kong","regularMarketPrice":44.64,"fiftyTwoWeekHigh":46.68,"fiftyTwoWeekLow":18.02,"regularMarketDayHigh":46.68,"regularMarketDayLow":42.48,"regularMarketVolume":1208600,"longName":"Beijing Shougang LanzaTech Technology Co., Ltd.","shortName":"SHOUGANG LANZA","chartPreviousClose":28.0,"priceHint":3,"currentTradingPeriod":{"pre":{"timezone":"HKT","end":1782091800,"start":1782090000,"gmtoffset":28800},"regular":{"timezone":"HKT","end":1782115800,"start":1782091800,"gmtoffset":28800},"post":{"timezone":"HKT","end":1782115800,"start":1782115800,"gmtoffset":28800}},"dataGranularity":"1d","range":"","validRanges":["1d","5d","1mo","ytd","max"]},"timestamp":[1780450200,1780536600,1780623000,1780882200,1780968600,1781055000,1781141400,1781227800,1781487000,1781573400,1781659800,1781746200,1782091800],"indicators":{"quote":[{"open":[28.0,20.219999313354492,33.0,30.100000381469727,37.0,32.0,32.0,42.2400016784668,42.220001220703125,43.0,43.20000076293945,43.0,43.20000076293945],"high":[29.979999542236328,36.5,36.380001068115234,35.70000076293945,38.15999984741211,32.959999084472656,42.31999969482422,42.65999984741211,45.0,45.439998626708984,43.900001525878906,44.79999923706055,46.68000030517578],"low":[18.020000457763672,20.1200008392334,28.1200008392334,30.100000381469727,28.65999984741211,29.100000381469727,32.0,40.70000076293945,40.31999969482422,42.52000045776367,40.560001373291016,41.540000915527344,42.47999954223633],"volume":[37023483,13295136,3118100,3030492,5707070,2016200,6147802,1169306,1306200,1220800,694400,1352000,1208600],"close":[21.059999465942383,34.2400016784668,30.34000015258789,33.939998626708984,33.0,31.5,41.41999816894531,42.220001220703125,43.58000183105469,43.540000915527344,43.0,43.20000076293945,44.63999938964844]}],"adjclose":[{"adjclose":[21.059999465942383,34.2400016784668,30.34000015258789,33.939998626708984,33.0,31.5,41.41999816894531,42.220001220703125,43.58000183105469,43.540000915527344,43.0,43.20000076293945,44.63999938964844]}]}}],"error":null}} |