teahubxyzandClaude Opus 5
56cebd3e29
teahub.xyz is denied by the cloud network policy, so a cloud session cannot clone, test locally or push. That is the lane's shape, not a fault: commit with tea_commit/tea_file_edit and let Gitea Actions run the tests on the runner, which does have repo access. Replaces the push-from-hb-5 advice. Adds the cloud lane itself (router.json's cloud block, paid from session credit and so absent from the ledger) and three situations rows drawn from today: read the bus before starting a card, never rebuild a card PR whose diff is empty (time#277 lost two cards that way), and queue nothing on a judge reply you cannot parse (time#211 ranked 37 candidates at 1.911 and sent three cards to the cloud lane on it). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FAqjv1aMxprhswN5gJqFkA
Teahub v1 (Green Tea)
Teahub is Git + tea (Gitea) + Time. This repository is the spine of the v1 prod instance at https://teahub.xyz, rebuilt fresh on 2026-10-14. Nothing was copied from the hb-5 era; pieces are ported only when a card needs them, and each port is a commit here.
AGENTS.md— the map for agents (where you are, how to move).docs/decisions.md— append-only decisions ledger.docs/rebuild.md— every step the rebuild needed beyond "clone + bootstrap"; the measure of portability.mcp/— Green Tea MCP, the Teahub MCP (FastMCP) against this Gitea. Every tool acts as the signed-in user.- Time (the automation layer) lives at https://github.com/teahubxyz/time, mirrored here as
teahubxyz/time.
Logins: GitHub (now), nostr (next). Prod holds no secrets beyond Gitea's own keys, the GitHub OAuth client, and the MCP's OAuth client.