Gap
The CLI, the Inspector, and the editor extension all serve the person who goes looking for the review record. Nothing surfaces the record where reviewers already live: inside the pull request. A digest of a revision's review state (observations, assessments, outstanding items) posted as a PR comment or check would close that loop.
Constraints known up front
- Publication must be an explicit, selected act — a digest shares a deliberately chosen slice of the record, never an implicit sync of the store.
- The digest is advisory: it informs the PR conversation; it must not gate merges.
Status
Design-gap placeholder — needs a real design pass (what the digest contains, where it posts, how selection is expressed) before any implementation. Filed so the gap is tracked, not to start work.
Gap
The CLI, the Inspector, and the editor extension all serve the person who goes looking for the review record. Nothing surfaces the record where reviewers already live: inside the pull request. A digest of a revision's review state (observations, assessments, outstanding items) posted as a PR comment or check would close that loop.
Constraints known up front
Status
Design-gap placeholder — needs a real design pass (what the digest contains, where it posts, how selection is expressed) before any implementation. Filed so the gap is tracked, not to start work.