proDreams/revu 2.5.0 on GitHub

deep shows the model the shape of the repository. The tree was already being read — it is how the
tests and dependencies of a changed file are found — so the listing costs no extra request: one line per
directory, a few names each, manifests and lock files first, capped at a couple of thousand characters.
uv.lock appearing there is how a review knows the project uses uv, even though the file itself is never
sent; a directory with three hundred files still shows the six that matter and says how many it left out.
Secrets are the exception to being listed by name: .env, keys and credentials stay out of it, because a
listing reveals what a search does not. It belongs to deep alone, and it has its own ceiling rather than
a share of the code budget.

Other people's comments reach the model on a first review. They were being fetched
— the GitLab /notes call sits in the log with a 200 next to it — and then dropped
before the prompt: the renderer returned early unless ReVu had findings of its own,
which on a first review it never has. Found while testing on GitLab, and it was never a
GitLab problem: the same early return applied to every host, and a test had frozen that
behaviour by asserting the empty result. The two halves of the block now appear on their
own terms — ReVu's findings only on a follow-up, when there is something to verify, and
the discussion always, because a reviewer who cannot see it repeats what was settled
there. The instructions say so too, in both the criteria and the follow-up prompt.