sorbet/sorbet：README 來源編輯指南

sorbet/sorbet 的 README 將專案描述為「A fast, powerful type checker designed for Ruby」。本文只整理倉庫可直接核對的內容，不把 star、Fork 或宣傳語當成品質證明。README 在「Sorbet」下寫到：This repository contains Sorbet, a fast, powerful type checker designed for Ruby. It aims to be easy to add to existing codebases with gradual types, and fast to respond with errors and suggestions.。這說明的是專案邊界，不是已完成的生產驗證。

從 README 的「Sorbet user-facing design principles」與相關條目，可以先判斷它是否處理你的實際問題：verbosity should be compensated with more safety。若需求不同，不應只因專案熱度就採用。本文保留原始專案名、命令與元件名，方便回到一手來源核對。 README 另外列出一項可核對的資訊：Testing "Find Definition" and "Find All References"。這類原文條目可用來設計試跑步驟，但不能取代實際環境測試。

README 將運作方式分散在「Sorbet」等段落。可確認的線索包括：If you are at Stripe, you might also want to see for docs about Stripe-specific development workflows and historical Stripe context.。本文不把未寫出的架構、效能或安全邊界補成結論；真正的執行鏈仍要配合目錄、設定檔與版本標籤檢查。

第一次安裝應從 README 指出的入口開始。目前可核對的命令是： brew install rtags # Have the rtags daemon be automatically launched by macOS on demand brew services start rtags # cd into sorbet # ensure that ./compile_commands.json exists # Tell rtags to index sorbet using our compile_commands.json file rc -J . 如果倉庫沒有命令，本文不會自行編造步驟，而是建議先閱讀「Table of Contents」，確認系統依賴、預設埠與首次初始化。

日常使用取決於專案文件。README 的「Sorbet user-facing design principles」段落提到：Early in our project, we've defined some guidelines for how working with Sorbet should feel like.。設定檔、環境變數、權限與資料目錄只在來源明確時才會記錄；沒有寫出的預設值，應在測試環境驗證並保留回滾副本。 同一部分也提到：brew install bazel autoconf coreutils parallel。

README 能確認的限制比宣傳頁更重要。現有來源沒有證明sorbet/sorbet具備固定相容矩陣、服務等級、效能基準或長期支援承諾。README 只明確寫到「We're willing to write annotations, and in fact see them as beneficial; they make code more readable and predictable. We're here to help readers as much as writers.」。這些未知項應列入選型紀錄，不要改成肯定句。