Engineering is where Grok Bot setups need receipts. A good Bot can triage issues, review a PR, update docs after a merge, run a narrow CI task, or keep a software crew coordinated. Grok Ship is the big pattern here: Firstmate, crewmates, state, routines, Cursor cloud work, and human judgment on decisions and PRs. Smaller workflows matter too: commits to issues to status page, Linear IDs in PR titles, and Intercom docs after a UI change. This hub is for code work that shows its trail. Trust comes from diffs, links, and review points.