first-tree-githublisted

# First Tree — Follow a GitHub Entity ## What following means Following wires a GitHub entity's event stream into **this chat**: one routing line, chat-scoped, not personal. Three properties to internalize before acting: - **Every event wakes you.** Each comment, review, CI result on a followed entity is delivered as a card addressed to the wiring agent — following is active attention with a real cost, not a passive bookmark. Follow what the task needs; nothing else. - **The whole chat sees the stream.** Events land in the shared room, including the human's view. You are spending the room's attention, not just your own. - **One line, one room.** A given (human, delegate-agent) line for an entity lives in exactly one chat. Following the same entity from a second chat conflicts (`409`) — the line can be *moved* (`--rebind`), not duplicated. **Creating is not following.** No creation path — `gh pr create`, curl, GitHub MCP, the web UI — wires anything for you. If the task depends on what you just created, declaring that dependency is YOUR job, immediately after creation. **Unfollowing declares the task's attention span over:** the task this chat carries is no longer concerned with the entity. It disconnects **all** lines wired into this chat for that entity, no matter how they were created — explicit follow, a mention, or a `Fixes #N` link. Think of follow/unfollow as the opening and closing bracket of the task's attention on the entity. ## Commands fi