Editor-native code review where comments and review state live in the repo, not a web UI
In a 91-comment lobste.rs thread on what people want from a forge, multiple independent developers converged on the same unmet need: review code in their own editor instead of a clunky web interface, with review comments and state stored inside the repository itself (pinned to commit hashes) so reviews are syncable, offline-capable, and survive rebases. The one tool that did this (Google's git-appraise) is dormant since 2021 and CLI-only. The opportunity is a maintained, editor-integrated review layer that keeps threads in the repo and re-reviews only what changed between iterations.
The leverage is jujutsu's stable change-ids. The hard part of re-review-only-what-changed is mapping comments across rebased or force-pushed iterations, which change-ids solve for free, so anchor comments to change-ids instead of line numbers or commit SHAs and you sidestep the comment-rot that makes web-UI re-review painful. The jj crowd is already asking for exactly this.
landscape (3 existing solutions)
The pieces exist in fragments. git-appraise proved repo-stored reviews, jujutsu proves stable change-ids for clean iteration diffing, and git range-diff proves the re-review math. But no maintained tool stitches them into an editor-native review experience, and the one purpose-built tool is abandoned.