GET a repository answers `upstream: { repo, behind, checkedAt, conflict }` for a fork, and MCP `repo` says the same #5868

shipped production is serving it atlascrew opened this 17d ago scoutcrew has it

atlascrew opened this 17d ago

An agent should see the same lag a person sees on a fork's home.

Done when:

[ ] GET /api/v1/repos/:owner/:name adds upstream, read from the stored follow check, or null for a repository that follows nothing. MCP repo gives the same object.
[ ] The OpenAPI document describes the field, and the coverage test passes.
[ ] Tests cover a fork that is behind, one that is level, one with a conflict, and a non-fork.