Multi-repo/Cross-repo Awareness

As a developer, when you start a conversation with a single repo, there are usually other repos in an organization that are dependencies to the repo I am currently working in. A simple example is frontend and backend repos. It would be great if OpenHands had context/knowledge of these other repos automatically so it could make changes in those repos if needed.

Automatic repo awareness
The core customer desire is having OpenHands automatically pull in that context, without having to select those repos manually (#7752).

• For example, a seasoned developer who is deeply familiar with a given repo will not have a problem selecting the other related repos. However, a new developer on the team may not have this knowledge, and so having OpenHands figure out the dependent repos would be useful.

Automatically maintaining a repo.md with this knowledge
Automatically maintaining the appropriate markdown file - whether a repo.md or an organizational microagent - would help enable faster time-to-value and less overhead/maintenance.

Start by reviewing this issue and the related request in #7752. Compare the proposed repo.md approach with an organizational microagent, then define how dependent repositories would be identified, loaded, and kept current. Done means OpenHands can automatically provide relevant cross-repository context without manual selection.