Gap
The contextual panel's Code Review render target is a scaffolded stub that was never wired to its data. apps/vscode/src/contextual-panel/webview/main.ts:38 renders only the header plus the placeholder "This builder's pending comments and files-to-review will appear here (#1037)", and no contextual-panel/* file reads the review queue at all (no reference to ReviewQueueStore / pending-comments anywhere in the directory — verified by grep on main, 2026-08-26).
Surfaced during pir-1552 dev-approval testing: the owner authored 6 review comments against a builder diff, the queue path worked (all 6 correctly persisted to the worktree's .codev/pending-comments.json with real prose), but the panel's "Code Review · " surface showed only the stub where he expected the queued comments. The queue currently surfaces only via the #1037 status-bar "Submit Review (N)" button and the inline diff threads.
This is the #1049 pattern working as designed — the panel merged with per-mode placeholder bodies, each body owned by a participating feature issue — except the Code Review body had no tracked participating issue (#1037 predates the panel and is closed). This issue is that tracker.
What to build
Wire the Code Review body to render the shown builder's pending review-comment queue. Follow the pattern #1553 established for the Attention body (see codev/reviews/1553-contextual-panel-wire-the-atte.md and the arch.md contextual-panel paragraph):
Constraints
Provenance
Reported by the pir-1552 builder (in-code confirmation), during the owner's live dev-approval session reviewing a builder diff; filed by main as the tracked participating issue the surface was missing.
Gap
The contextual panel's Code Review render target is a scaffolded stub that was never wired to its data.
apps/vscode/src/contextual-panel/webview/main.ts:38renders only the header plus the placeholder "This builder's pending comments and files-to-review will appear here (#1037)", and nocontextual-panel/*file reads the review queue at all (no reference toReviewQueueStore/ pending-comments anywhere in the directory — verified by grep on main, 2026-08-26).Surfaced during pir-1552 dev-approval testing: the owner authored 6 review comments against a builder diff, the queue path worked (all 6 correctly persisted to the worktree's
.codev/pending-comments.jsonwith real prose), but the panel's "Code Review · " surface showed only the stub where he expected the queued comments. The queue currently surfaces only via the #1037 status-bar "Submit Review (N)" button and the inline diff threads.This is the #1049 pattern working as designed — the panel merged with per-mode placeholder bodies, each body owned by a participating feature issue — except the Code Review body had no tracked participating issue (#1037 predates the panel and is closed). This issue is that tracker.
What to build
Wire the Code Review body to render the shown builder's pending review-comment queue. Follow the pattern #1553 established for the Attention body (see
codev/reviews/1553-contextual-panel-wire-the-atte.mdand the arch.md contextual-panel paragraph):vscodeimport); decide during planning whether it is extension-local or belongs beside the other cross-client helpers — note the queue is extension-local state (a worktree file), unlike the overview wire, so extension-local is the likely answer.RenderMessagealongside the descriptor only whenkind === 'code-review'(resolver andModeDescriptorstay pure), and re-posts on queue change only while a Code Review surface is showing.Constraints
review-queue/feedback.ts,comments/builder-review.ts); 1552 was explicitly fenced out ofcontextual-panel/*and this issue is why that fence stays.#1037citation should be replaced by the real body when wired.Provenance
Reported by the pir-1552 builder (in-code confirmation), during the owner's live dev-approval session reviewing a builder diff; filed by main as the tracked participating issue the surface was missing.