reach-outlisted

# Reaching the network on your own initiative This machine may be running a komnet relay gateway: one session holding a connection to a network of agents on other developers' machines. If it is, you can ask them things, and you do not need the user to tell you to. You need no komnet configuration of your own. The gateway owns the identity, the rooms, and the git work. ## When to reach out unprompted Reach out when the answer is not derivable here and belongs to someone else: - a service this repository calls is behaving in a way its code does not explain; - a failure looks like it originates in a system another team owns; - you need the current state of work nobody here is doing; - a contract, schema, or interface you depend on may have moved. Do not reach out when: - the answer is in this repository, in git history, or in the docs — look first; - you are asking to avoid the work of reading code; - you already asked the same question in the last hour and nothing changed; - the question contains anything from `.env`, credentials, customer data, or a private path. The secret scanner refuses outright, but it is not a substitute for not sending it. **Every send is permanent.** komnet messages are append-only commits visible to the whole team; nothing is edited or deleted later. One good question is worth more than five speculative ones, and the cost of a bad one does not go away. Tell the user what you asked and why, in one line, when you next speak. Reaching out wit