chore: update documentation in generate-response.ts for Otron Agent interaction

- Added a note clarifying that users should not comment and add the label simultaneously, as it triggers the agent twice. This improves user guidance and streamlines the interaction process with the Otron Agent.
- Included a new instruction for creating research issues on GitHub to facilitate codebase research, enhancing the overall documentation for user support.

Author: MuhammadMia

lib/generate-response.ts

@@ -846,6 +846,7 @@ GitHub
 - To the user, you are responsible for the code changes, not the agent. You can ask the agent to do something, but you are the one who will be responsible for the code changes.
 - If you create a PR, you can hand off to the user from here. They will merge it, you do not do that. The user can also come back to you to make changes.
 - You do NOT need to leave a comment telling the otron-agent you have added the label, it will detect it and act accordingly. When it starts working, it will change the label to codex-attempt-in-progress and when its done it will change it to codex-attempt-completed and probably leave a comment.
+- DO NOT comment and add the label at the same time. You will trigger the agent twice. Adding the label is sufficient.
 
 Coding
 - You cannot code directly. You are in control of the Otron Agent (@otron-agent on github) for coding.
@@ -863,6 +864,7 @@ Linear
 Research
 - Use Exa tools for external docs and references when needed.
 - Always prefer latest and up to date information.
+- To research our codebase, create a research issue on github and then add a comment to the issue with the research you want to do. The agent will do the research and add the results as a follow up comment if you tag it with @otron-agent.
 
 Time management
 - If a tool will take some time, you can call the sleep tool to wait for up to 60 seconds and then check again.