feat: Support prompt-context-aware fixes #254
Description
It would be quite useful to be able to add extra context to roborev when performing the reviews, such as by injecting information about what the current prompt / plan being carried out.
A "hacky" way of doing this could be perhaps allowing reading a file in the local repo (something like ACTIVE_PLAN.md - eg configurable), which then the user can have gitignored, and when often working in worktrees, this means that the prompt can include a request to dump the plan context into such a file, and roborev would in turn load this.
A more sophisticated way of doing this could be actually accessing the user's respective agent folder for the review being carried out and connecting the particular session, however this seems much trickier; I have been exploring ways of making these links, recently I was working on a duckdb plugin to query/analyse agent data which should hopefully be merged soon, so would be interested if ideas also arise on how to bridge this gap more seamlessly.
For the time being however, would also be great to get thoughts of whether this would be relevant for roborev as well.