Add config option to include whole files for context if they fit in the prompt

[wesm]

This may produce better reviews in some codebases

[turian]

So the most important thing here is not just the changed files get put in context but also important unrelated files.

If you ask the coding agent with its context to choose what those important unrelated files are, this is a good idea because it actually knows from its coding what is relevant.

If this process is onerous for different workflows, you can instead use augment context engine API to inject good related context. The proposed workflow would be that you send your current prompt (code + diff) WITHOUT the whole file to augment context engine API search endpoint and then include its entire source files into the prompt. A very interesting and appealing intermediate variation is JUST to augment your existing prompt with the resuts of context engine API search endpoint WITHOUT whole files.

It should be incredibly rare that the prompt length is exceeded. That would actually suggest bad practice and maybe dovetails with your idea to discourage bad practice.

Also, skip lockfile updates by default.