20:"$Sreact.view_transition" 21:I[9754,["/_next/static/chunks/2t36f5p4pjzlb.js","/_next/static/chunks/1gyqeidjm5eoa.js","/_next/static/chunks/0_fjnxc4tt_l_.js","/_next/static/chunks/1ymt1shyhmu-4.js","/_next/static/chunks/3kv2zf0i7s2wc.js","/_next/static/chunks/1vs_3g_g75zmk.js","/_next/static/chunks/2g4dh802s8oz3.js","/_next/static/chunks/1bc3f0shukf1j.js","/_next/static/chunks/192kgs9v_t14j.js","/_next/static/chunks/0z6pw0v5c_lx5.js","/_next/static/chunks/08r60e6icmtkc.js","/_next/static/chunks/3trx6c0i7_x-3.js","/_next/static/chunks/40sro5bzp9bi_.js","/_next/static/chunks/1wgf3tk38y6cf.js"],"ProjectDetail"] 22:T352f, zubo · 定时抓取组播与酒店源

zuboGitHub Actions · Python

定时抓取组播与
酒店源，轻量自动化

一条从定时触发、逐级净化到订阅链接的管道：zubo 通过 GitHub Actions 周期性抓取组播源与酒店源，多阶段处理之后产出可订阅的链接。

定时触发

由 GitHub Actions 以定时机制周期触发整条流水线，无需人工介入。
IP 抓取

从组播源与酒店源定时抓取候选端点，作为后续净化的原始输入。
频道检测

对抓取到的 IP 逐项进行频道检测，筛掉不可用的输入。
映射

将可用频道映射为可识别的标识，供结果整理与输出使用。
订阅

整合各阶段结果，最终产出可供订阅使用与维护的频道集合。

单向管线 · 阶段高度随净化逐级递进

适合需要自动化维护 IPTV 源的用户；也适合使用 GitHub Actions 的开发者与偏好 Docker 部署的人。

查看 Docker / 运行 GitHub 仓库

STAGE

IP 抓取

从组播源与酒店源定时抓取候选端点，作为后续净化的原始输入。

STAGE

频道检测

对抓取到的 IP 逐项进行频道检测，筛掉不可用的输入。

STAGE

映射

将可用频道映射为可识别的标识，供结果整理与输出使用。

OUTPUT

订阅输出

整合各阶段结果，最终产出可供订阅使用与维护的频道集合。

组播源

Multicast

逐级检测后收录

酒店源

Hotel IPTV

支持 Docker 版升级

MAPPING

逐个对应

每个通过检测的频道被映射为可识别的标识，便于后续订阅整理与增减。

PERIODIC

定期续更

以定时机制周期触发抓取与检测，让源集合保持新鲜，避免陈旧失效。

DEPLOY

Docker 部署

以 Docker 版本运行，避免断流问题，并自带可视化管理能力。

PANEL

可视面板

通过面板增减频道、添加映射，并生成可供使用的订阅链接。

NOTE

基于文档

以上说明以 README 为依据，实际频道可用性与抓取效果未经逐项验证。

NOTE

状态提醒

受网络与源自身状态影响，抓取可能耗时较长，Docker 镜像也需要自行拉取。

23:T3615, zubo · Scheduled IPTV source scraper

zuboGitHub Actions · Python

Scheduled scraping for multicast & hotel IPTV

A pipeline from timer trigger to subscription — zubo periodically scrapes multicast and hotel IPTV sources on GitHub Actions, refining them stage by stage into subscribable output.

schedule

A timer on GitHub Actions kicks off the whole pipeline periodically, with no manual intervention.
IP scrape

Periodically harvests candidate endpoints from multicast and hotel sources as raw input for the stages ahead.
channel check

Each scraped IP is tested as a channel, dropping entries that fail to resolve into a usable stream.
mapping

Surviving channels are mapped to recognizable identifiers, ready to be organized into a clean result.
subscribe

Stage results are consolidated into a maintained channel set that can be consumed and refreshed.

Single-direction pipeline · each stage narrows the stream toward a usable output

Built for users who need automated IPTV updates, developers on GitHub Actions, and anyone who prefers Docker deployment.

View Docker / Run GitHub repository

STAGE

IP scraping

Periodically harvests candidate endpoints from multicast and hotel sources as raw input for the stages ahead.

STAGE

Channel detection

Each scraped IP is tested as a channel, dropping entries that fail to resolve into a usable stream.

STAGE

Mapping

Surviving channels are mapped to recognizable identifiers, ready to be organized into a clean result.

OUTPUT

Subscription output

Stage results are consolidated into a maintained channel set that can be consumed and refreshed.

Multicast sources

组播

detected before inclusion

Hotel IPTV sources

酒店源

Docker upgrade available

MAPPING

One-to-one

Every channel that passes detection is matched to an identifier, so additions and removals stay coherent.

PERIODIC

Refreshed on schedule

A timer re-runs scraping and detection, keeping the source set fresh instead of letting it go stale.

DEPLOY

Docker deployment

Run the Docker edition to avoid stream interruptions, with management built in.

PANEL

Web panel

Add or remove channels, attach mappings, and generate subscription links from the panel.

NOTE

Based on the README

This describes the documentation; channel availability and real scraping results are not independently verified.

NOTE

Status reminders

Network and upstream conditions can make scraping slow, and Docker images have to be pulled yourself.

a:[["$","$20",null,{"enter":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-enter","default":"none"},"exit":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-exit","default":"none"},"update":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-update","default":"none"},"default":"none","children":["$","$L21","cmt2zh0pm00ta627110ksg963:zh-CN:beautified",{"project":{"id":"cmt2zh0pm00ta627110ksg963","slug":"kakaxi-1-zubo","name":"zubo","description":"GitHub Actions 定时抓取 IPTV 源","authorName":"kakaxi-1","authorVerification":{"verified":false,"verifiedAt":null},"category":"development_tools","subcategory":"developer_resources","experienceUrl":null,"qualityScore":21,"featured":false,"officialSite":null,"views":{"original":{"available":true},"official":{"available":false,"reason":"disabled_by_policy"},"beautified":{"available":true,"reason":null},"defaultView":"beautified"},"beautifiedView":{"revisionId":"cmt2zh0qa00tm6271x5gfmese","kind":"artifact","artifact":{"schemaVersion":"localized-static-html-v4","kind":"static_html","locales":["zh-CN","en"],"defaultLocale":"zh-CN","documents":{"zh-CN":"$22","en":"$23"},"designDirections":{"schemaVersion":"dodot-design-directions-v1","directions":[{"id":"pipeline-graph","name":"时源流水线图","projectMetaphor":"把 zubo 理解为一条从定时器触发、逐级净化到订阅链接的管道：Input(IP抓取) → 频道检测 → 映射 → 订阅输出。标志视觉是节点-边构成的有向流水线图。","signatureVisual":"横向有向管线图：四枚节点(定时触发→IP抓取→频道检测→映射→订阅)以细连接线串起，节点用轻量描边圆/圆角块，连线末端有流动指示(短划线)，表达'定时周期性'与'多阶段净化'。","heroGeometry":"横贯首屏中线的一组5节点流水线，节点沿X轴均布，连线带朝右的短划流动；节点高度随阶段作用递增，示意逐级收窄/净化","sectionSequence":["hero-pipeline","stages","sources","mapping","operate","caveats"],"surfaceModel":"分层雾面玻璃面板：流水线节点浮于低对比背景上，节点内浅色填充、细描边分隔不同阶段，连线穿过面板边界不受裁切约束","palette":"低饱和冷灰基底，单点深蓝【主色】+琥珀【用于'周期/定时'触发节点】，黑白色阶为主，仅以琥珀微光标注一次调度起点","typography":"中文思源黑体/系统无衬线做正文，等宽(Consolas/Mono)用于阶段名与端点URL标签，标题用大号精练无衬线","desktopComposition":"左上锚定品牌与标语，中区为横贯流水线图(标志视觉)，右置一个真实CTA('查看Docker/运行');阶段顺序以下方分栏卡片展开","mobileTransformation":"流水线由横向5节点重构为纵向瀑布：各节点自上而下依次排列，连线变为竖向短划，每个阶段可触发展开其说明与证据","mediaStrategy":"不使用媒体区。用纯证据驱动的管线图与数据表格承载信息，无本地素材，不伪造截图","forbiddenPatterns":["不出现三卡指标墙","不出现浏览器/终端/仪表盘外壳","不出现营销Hero+大标语占据全屏","不出现发光网格或粒子背景","不出现伪造的产品界面截图"],"compositionFingerprint":"pipeline-nodes-five-flow-directional-place-overlap"},{"id":"source-antennas","name":"源之天线网","projectMetaphor":"把 zubo 想象成一张持续收束外部流源的天线网：许多外部'源'被定期捕捉、汇入一道、再分发为可订阅的订单。标志视觉是放射状的天线-汇聚图。","signatureVisual":"放射天线图：若干外部'源'节点沿画面外缘散布，斜线——指向中心枢纽'zubo';中心枢纽再向下连一条订阅出口线，表达'抓取→收束→出货'。","heroGeometry":"以中心枢纽为圆心的放射状构图，外围源节点环绕、细放射线向圆心收束，圆心下延出一条订阅出口直线","sectionSequence":["hero-collect","sources","channels","schedule","deploy","output"],"surfaceModel":"连续同色系画布上用细线层级做连接(无面板堆叠)，源与枢纽仅靠线条密度与节点大小区分，弱化卡片","palette":"墨蓝画布、放射线按距枢纽远近渐变灰度，枢纽与出口用单一青绿点缀，强调汇聚与单一出口","typography":"标题用超大字重无衬线、紧凑字距营造收束感，正文沿用系统无衬线，出口URL用等宽字体","desktopComposition":"首屏以放射天线为绝对主视觉且两侧留白，来源清单与目的地说明分置放射图两侧，调度信息以时间轴形式沉于底部","mobileTransformation":"放射状压缩为垂直汇聚：外源自上而下逐条向下收拢成一条主线汇入枢纽，终点出口高亮，节点间距与桌面完全不同以适配窄屏","mediaStrategy":"不用媒体区。以放射与汇聚的矢量关系图承担标志视觉，无本地素材，不伪造界面","forbiddenPatterns":["不出现功能卡片墙","不出现浏览器/仪表盘外壳","不出现三指标格","不出现渐变光晕或粒子替身","不出现伪造的订阅/频道表格截图"],"compositionFingerprint":"radial-antenna-converge-single-outlet-line-density"},{"id":"signal-log-book","name":"周期工单账本","projectMetaphor":"把 zubo 视作一份定期运转的抓取工单账本：每次调度回次记录'本次捕捉到的源、通过的频道、映射结果'，像日志/记账那样按时间推进。标志视觉是时间线账目。","signatureVisual":"纵向时间账本：以每次调度回次(Event N)为行的记账式时间线，每行左侧时间戳、中列各阶段状态刻度、右侧结果(订阅链接/频道数)，表达周期性增量记录","heroGeometry":"首屏为一条斜向延伸的记账时间轴，若干调度回次以刻度排布，最新回次停在首屏右缘作为当前状态","sectionSequence":["hero-ledger","runs","stages","sources","mapping","caveats"],"surfaceModel":"纸张式扁平层次：以细表线与间隔行构成账目质感，无厚重阴影与多层玻璃，靠行距与刻度建立秩序","palette":"暖米白纸底、墨黑文字、单色红在'失败/需注意'回次作警示点缀，整体克制","typography":"时间戳与纪律用等宽字体制造账本感，标题用窄字距无衬线，正文系统衬线或无衬线的克制组合","desktopComposition":"首屏左侧放标语与说明、右侧为纵向账本时间轴占据主要版面，最新回次状态最亮，来源与映射以账目式分节延续","mobileTransformation":"账本时间轴由每行信息改为一屏一回次的纵向卡片式分页：时间戳、阶段刻度、结果纵向堆叠，全程保留'账册'的纵向滚动连贯性","mediaStrategy":"不用媒体区。以记账时间轴承载全部信息，无本地素材，不伪造执行日志或截图","forbiddenPatterns":["不出现三卡指标墙","不出现终端/仪表盘/表格外壳式的伪造界面","不出现营销Hero标语占屏","不出现发光网格或粒子","不伪造真实运行日志或状态面板"],"compositionFingerprint":"ledger-timeline-vertical-run-rows-tick-status"}],"selectedDirectionId":"pipeline-graph","selectionRationale":"选『pipeline-graph 时源流水线图』。拟定的材料事实(多阶段处理：IP抓取→频道检测→映射，加周期性触发与订阅链接输出)最直接对应一条有向处理管线，pipeline-graph 的节点-边构图能逐项承载这些已验证阶段，并可用'流动短划'表达定时周期性这一核心机制；sources方向强调源汇聚但弱化了具体的多阶段处理次序，log-book方向长于记录但较弱于机制本身的可读性。pipeline-graph 在项目机制契合、证据契合与标志视觉代表性上最优，且antiTemplateContext为空，不构成重复风险。mobileTransformation把横向管线纵向化以满足390px重构图，physical difference 充分。"},"designBrief":{"schemaVersion":"dodot-design-brief-v1","selectedDirectionId":"pipeline-graph","projectMetaphor":"把 zubo 理解为一条从定时器触发、逐级净化到订阅链接的管道：Input(IP抓取) → 频道检测 → 映射 → 订阅输出。标志视觉是节点-边构成的有向流水线图。","signatureVisual":"横向有向管线图：四枚节点(定时触发→IP抓取→频道检测→映射→订阅)以细连接线串起，节点用轻量描边圆/圆角块，连线末端有流动指示(短划线)，表达'定时周期性'与'多阶段净化'。","compositionFingerprint":"pipeline-nodes-five-flow-directional-place-overlap","heroGeometry":"横贯首屏中线的一组5节点流水线，节点沿X轴均布，连线带朝右的短划流动；节点高度随阶段作用递增，示意逐级收窄/净化","sectionSequence":["hero-pipeline","stages","sources","mapping","operate","caveats"],"surfaceModel":"分层雾面玻璃面板：流水线节点浮于低对比背景上，节点内浅色填充、细描边分隔不同阶段，连线穿过面板边界不受裁切约束","palette":"低饱和冷灰基底，单点深蓝【主色】+琥珀【用于'周期/定时'触发节点】，黑白色阶为主，仅以琥珀微光标注一次调度起点","typography":"中文思源黑体/系统无衬线做正文，等宽(Consolas/Mono)用于阶段名与端点URL标签，标题用大号精练无衬线","desktopComposition":"左上锚定品牌与标语，中区为横贯流水线图(标志视觉)，右置一个真实CTA('查看Docker/运行');阶段顺序以下方分栏卡片展开","mobileTransformation":"流水线由横向5节点重构为纵向瀑布：各节点自上而下依次排列，连线变为竖向短划，每个阶段可触发展开其说明与证据","mediaStrategy":"不使用媒体区。用纯证据驱动的管线图与数据表格承载信息，无本地素材，不伪造截图","evidencePlan":["hero：标语『定时抓取组播与酒店源，轻量自动化』，CTA点出 Docker 部署与 GitHub Actions 脚本","stages：逐一呈现 IP抓取→频道检测→映射→订阅的多阶段处理(证据来自README)","sources：区分组播源与酒店源两类来源，引述README标题","operate：Docker部署+可视面板增减频道与添加映射+生成订阅链接；caveats 引述README为未验证的局限"],"localeContract":{"zh-CN":"slogan：定时抓取组播与酒店源，轻量自动化；oneLine：GitHub Actions 定时抓取 IPTV 源；overview/highlights/caveats 取自 summary.zh-CN 原文","en":"slogan：Scheduled scraping for multicast and hotel IPTV；oneLine：GitHub Actions scheduled IPTV source scraper；overview/highlights/caveats 取自 summary.en 原文"},"forbiddenPatterns":["不出现三卡指标墙","不出现浏览器/终端/仪表盘外壳","不出现营销Hero+大标语占据全屏","不出现发光网格或粒子背景","不出现伪造的产品界面/运行日志截图","不出现与 antiTemplateContext 重复的组合指纹、标志视觉或章节顺序"]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"approved","summary":"zh-CN 与 en 两版均忠实实现了所选 pipeline-graph 方向的标志视觉：真实存在于源码的5节点单向流动管线(SVG 短划动效+箭头+琥珀触发节点)，章节顺序与 brief.sectionSequence 完全一致(hero-pipeline→stages→sources→mapping→operate→caveats)。所有文案均可回溯至 material.json 的 summary/readme 证据(组播与酒店源、Docker 部署、可视面板增减频道与添加映射、生成订阅链接、多阶段 IP 抓取/频道检测/映射、定时更新、基于 README 的局限)。手机上于 560px 断点将横向管线重构为可展开的纵向瀑布(

逐阶段展开、竖向虚线连接)，是结构性重构而非简单缩放；双语言义等价且自然。未回退到三卡指标墙/浏览器与终端外壳/营销大字屏/发光网格粒子/伪造产品截图或无依据设备壳，无假控件。QA 报告(4 viewport 全 passed，fakeControlCount=0，mobile scrollWidth390=clientWidth390 无溢出)与源码审查一致，status 判定为 approved。","checks":{"projectFit":{"passed":true,"evidence":"设计方向正确选定 pipeline-graph，页面 data-dodot-section 序列为 hero-pipeline、stages、sources、mapping、operate、caveats，与 design-brief.sectionSequence 逐项一致；标志视觉为横向5节点管线(定时触发→IP抓取→频道检测→映射→订阅)，hero 标题直接使用 summary.zh-CN slogan『定时抓取组播与酒店源，轻量自动化』；6个章节落在 material 的 sections 4-7 范围内。"},"evidenceBound":{"passed":true,"evidence":"所有论述均有材料依据：组播源/酒店源两类来源对应 summary 与 readme 标题；Docker 部署、可视面板增减频道与添加映射、生成订阅链接对应 summary claim 2；多阶段处理(IP抓取/频道检测/映射)对应 claim 3；定时更新对应 claim 1；caveats 明示『基于文档/README 未见验证』对应 summary caveats 原文；brand 标注『GitHub Actions · Python』匹配 fact primary_language=Python；CTA 指向真实仓库 https://github.com/kakaxi-1/zubo。未出现无据指标(stars/forks 未编)。"},"signatureVisual":{"passed":true,"evidence":"zh-CN.html 与 en.html 的 .pipe-svg 中真实存在5节点有向管线：4枚圆形节点+1枚映射·订阅圆角矩形，以带 marker 箭头的短划虚线连接，触发节点(定时触发)为琥珀色、其余为深蓝，节点 cx/cy 分层(148/76)示意逐级收窄净化，与 brief.heroGeometry/signatureVisual 匹配；svg 带 role=img+aria-label，属可控纯矢量 data-viz，非伪造截图或设备壳。"},"mobileTransformation":{"passed":true,"evidence":"@media(max-width:560px) 下 .pipe-svg{display:none} 而 .waterfall{display:block}，横向管线被重构为纵向瀑布：5阶段自上而下排列、连线换为竖向虚线(.wf-connector span 竖向 dashed)，每阶段以原生

可触发展开说明与证据，与 brief.mobileTransformation『重构为纵向瀑布、可触发展开』相符；QA mobile scrollWidth390=clientWidth390 无横向溢出，确为结构性重构而非等比缩放。"},"localeParity":{"passed":true,"evidence":"zh-CN 与 en 两文件结构完全对齐(6章节、5个 h2、同序 data-dodot-section、同名 SVG 管线与瀑布)，英文为自然完整翻译而非生硬直译：slogan/overview/highlights/caveats 取自 summary.en 原文，段落语义等价且流畅；en 的 sources 表格以组播/酒店源作双语术语配对属合理处理；QA 两语言各 viewport 均 passed。"},"antiTemplate":{"passed":true,"evidence":"未回退到禁用模式：无三卡指标墙(各章节为双列卡片而非三项指标)，无浏览器/终端/仪表盘外壳(信息由纯 SVG 管线与数据表承载)，无营销 Hero 大标语占屏(h1Top 桌面162px 非全屏，h1 即摘要 slogan 且有证据支撑)，无发光网格或粒子背景(扁平淡灰 #eef0f2)，无伪造产品/运行日志截图，无设备外壳；compositionFingerprint 采用五节点有向管线，antiTemplateContext 为空故无重复指纹/视觉/章节顺序冲突。"},"noFakeUi":{"passed":true,"evidence":"瀑布阶段用原生

实现真实可展开控件，非假控件；SVG 管线为带 aria-label 的结构示意而非伪造界面；CTA()为真实链接；QA 报告各 viewport fakeControlCount=0、emptyLinkCount=0、brokenImageCount=0，与源码审查一致。"}},"issues":[{"code":"brief-minor-wording","severity":"warning","locale":"all","description":"design-brief 的 signatureVisual 行写为『四枚节点』但随后列举实为5个(定时触发→IP抓取→频道检测→映射→订阅)，页面实际实现了5节点管线，符合 heroGeometry 的『5节点』而非 4 枚，属 brief 内部措辞小瑕疵，不影响成品正确性，仅记录供上游校对。","repairInstruction":"无需修改页面；可在后续修订 brief 时将 signatureVisual 的节点计数统一为5枚以消除表述歧义。"}]},"repairEvidence":[{"attempt":1,"before":{"qaPassed":true,"designReviewApproved":false,"qaEvidence":{"zh-CN":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":5,"sectionCount":6,"textLength":803,"cjkCount":458,"latinLetterCount":184,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":2304,"h1Top":162.75,"bottomInset":80.46875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"bea0e30364e6edb932afcc750653a9ac3bb6255a5e3dc32d78fac57802d6f5d1","middle":"2e03e3ea2a3f130689288346c333b5461d5e0715c13e9309f9fcf9fdc36c1aaa","bottom":"622f1fe99d224806415704bad6df9dcb18ed93129d081f9d355e609df46617b7"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":5,"sectionCount":6,"textLength":803,"cjkCount":458,"latinLetterCount":184,"scrollWidth":390,"clientWidth":390,"scrollHeight":3225,"h1Top":74.75,"bottomInset":80.21875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"95824617f7f651a0ea7492e44dbf816f28e5054b49b7b98192aba494aa51df91","middle":"af62e172dbfc19e3aee587b0f23a2964fea562ceda292fcae83788e6ce90d42c","bottom":"22334a6ad8fcec7b786570cb0847630dcfe5af7371a0e1a36985b4831d38d1fa"},"consoleErrors":[],"networkRequests":[]}],"en":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":5,"sectionCount":6,"textLength":2002,"cjkCount":5,"latinLetterCount":1629,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":2419,"h1Top":162.75,"bottomInset":80.015625,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"6d8ec8f78fa9cef8e41741ba0e6a85870dfae90bd46104dc52e812fc0674c6c4","middle":"c43de067adea141e5ed46b939e7b3dd3822fcd0c8125b23eed8792b040bf7656","bottom":"a2d52ec6453ff15dd6c838bdbdd4a5aa916d9aa5a8e7aaf07eceff41a3a3a0af"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":5,"sectionCount":6,"textLength":2002,"cjkCount":5,"latinLetterCount":1629,"scrollWidth":390,"clientWidth":390,"scrollHeight":3590,"h1Top":74.75,"bottomInset":79.90625,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"c155f69a6c76e39a078bc66c74be8802eec8beff6c1c1122a75ef016037ab159","middle":"cbb1a51278b972cd045e570f8e61f3e1c93f4e37af1cd9cfb47c0ad62a0f35b8","bottom":"a17994cb341471c8a5adc7ea8e1b62f4d890f4bc9c88b2d88fb8adf0b9b6e87d"},"consoleErrors":[],"networkRequests":[]}]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"revise","summary":"页面忠实采用了 design-brief 选定的 pipeline-graph 方向：首屏横贯5节点有向流水线标志视觉真实存在且由材料证据承载，章节顺序与 heroGeometry 吻合，双语章节等价自然，未回退到通用 Hero/三卡墙/设备壳/渐变网格。唯一致命缺陷在手机 CSS：横向流水线 SVG 仅随宽度等比缩小(viewBox 恒定、无媒体查询重排节点)，并未如 brief 要求重构为纵向瀑布，|mobileTransformation| 不通过，故整体为 revise。","checks":{"projectFit":{"passed":true,"evidence":"选定方向 pipeline-graph；hero 实现横贯5节点管线(定时触发→IP抓取→频道检测→映射→订阅制SVG)，节点由r52/圆r60/矩形递增示意逐级净化，与 heroGeometry 一致；sectionSequence 依次为 hero-pipeline/stages/sources/mapping/operate/caveats，与 brief 一致。"},"evidenceBound":{"passed":true,"evidence":"slogan、oneLine 逐字取自 summary.zh-CN；多阶段处理(IP抓取/频道检测/映射/订阅)、两类来源(组播/酒店)、Docker可视面板与订阅链接均有材料(README facts)依据；CTA 指向真实仓库 https://github.com/kakaxi-1/zubo；未出现无据指标(stars/forks 未编）。"},"signatureVisual":{"passed":true,"evidence":"hero 内 .pipeline 容器中的

定时抓取组播与
酒店源，轻量自动化

多阶段处理

IP 抓取

频道检测

映射

订阅输出

两类来源

映射与记录

逐个对应

定期续更

如何运行

Docker 部署

可视面板

注意与局限

基于文档

状态提醒

Scheduled scraping for multicast & hotel IPTV

Multi-stage processing

IP scraping

Channel detection

Mapping

Subscription output

Two kinds of sources

Mapping & upkeep

One-to-one

Refreshed on schedule

Getting it running

Docker deployment

Web panel

Notes & caveats

Based on the README

Status reminders