upptime/upptime：README 來源編輯指南

upptime/upptime 的 README 將專案描述為「⬆️ GitHub Actions uptime monitor & status page by @AnandChowdhary」。本文只整理倉庫可直接核對的內容，不把 star、Fork 或宣傳語當成品質證明。README 在「[」下寫到：Upptime (https://upptime.js.org) is the open-source uptime monitor and status page, powered entirely by GitHub Actions, Issues, and Pages, made with 💚 by Anand Chowdhary.。這說明的是專案邊界，不是已完成的生產驗證。

從 README 的「⭐ How it works」與相關條目，可以先判斷它是否處理你的實際問題：Response time is recorded every 6 hours and committed to git。若需求不同，不應只因專案熱度就採用。本文保留原始專案名、命令與元件名，方便回到一手來源核對。 README 另外列出一項可核對的資訊：Every 5 minutes, a workflow visits your website to make sure it's up。這類原文條目可用來設計試跑步驟，但不能取代實際環境測試。

README 將運作方式分散在「[」等段落。可確認的線索包括：I built Upptime because, like many developers, I needed an uptime monitor and status page for my startup Pabio that was affordable, flexible, and completely under my control.。本文不把未寫出的架構、效能或安全邊界補成結論；真正的執行鏈仍要配合目錄、設定檔與版本標籤檢查。

第一次安裝應從 README 指出的入口開始。目前可核對的命令是： README 没有给出可直接复制的安装命令。 如果倉庫沒有命令，本文不會自行編造步驟，而是建議先閱讀「📈 Live Status: 🟩 All systems operational」，確認系統依賴、預設埠與首次初始化。

日常使用取決於專案文件。README 的「[」段落提到：Upptime runs scheduled checks using GitHub Actions (as often as every 5 minutes) to ping your endpoints and verify they're online. Response time data is recorded and committed to git, enabling long-term trend charts and historical insights.。設定檔、環境變數、權限與資料目錄只在來源明確時才會記錄；沒有寫出的預設值，應在測試環境驗證並保留回滾副本。 同一部分也提到：Graphs of response time are generated every day。

README 能確認的限制比宣傳頁更重要。現有來源沒有證明upptime/upptime具備固定相容矩陣、服務等級、效能基準或長期支援承諾。README 只明確寫到「I built it to be completely free if you're already using GitHub since there's no external server or subscription needed. All configuration lives in a single file, and your data is gone if you delete the repo.」。這些未知項應列入選型紀錄，不要改成肯定句。