Repository context includes more than the file currently being edited. It covers architecture, module boundaries, dependencies, configuration, tests, ownership, contribution rules, commit history, open work, and reasons behind earlier design choices.
Coding agents need relevant repository context to avoid locally plausible changes that conflict with wider behavior or future plans. Context should be retrieved for the specific task and linked to authoritative files or records so assumptions can be checked before code is changed.
