[ravarora2]

Why

Communities need to route PRs to the right reviewers, request another pass, and see which reviews need attention. A chat acknowledgment alone does not establish acceptance or approval.

What

Add an optional Review Configuration plugin with repository settings, review lanes, agent assignments, instructions, and routing rules. Separate Review Configuration and Pull requests dock icons open setup and the PR list; the list includes Submit PR.

Repositories can require ready-for-review status, passing CI, no merge conflicts, and an agent triage decision before routing. Each gate starts off. Triage admits or rejects the PR in a dedicated thread.

The table distinguishes Needs review, Reviewing, Changes requested, Looks good · not approved, and Approved. Completed outcomes are green, pending states amber, and requested changes red. Legacy Done reports remain Completed · outcome unspecified. Each lane has its own thread, status, latest-message preview, Full message link, and reminder action with an optional note.

The dock counts unseen status updates in the selected review channel. Opening Pull requests acknowledges loaded updates and clears the dock badge. Affected rows and lanes retain an Updated marker for that visit; live changes are highlighted too. Each lane shows Last updated from its latest status report or thread message, including reminders. Rows show the original submission date and latest review result date; accepting a review does not count as completing it. Older submissions without a saved creation date say Not recorded.

How

Reuse signed relay artifacts, shared agent choices, existing page navigation, and the durable outbox. Routing supports all/any rules on titles, labels, file counts, and paths. Assignments and approval policy are saved with each submission. Reminders retain the same threads and reset only the reminded lanes. Deletion preserves conversations and the GitHub PR; resubmission creates new threads with current settings.

The status tool requires a saved Reviewing report for the current request before an outcome. A skipped step returns the required call and posts a tagged correction; sequential retries reuse it. Compact requests emphasize lane instructions, reminder notes, and approval policy. Automatic approval starts off and must be explicitly enabled per lane. The tool records signed reports; it neither submits nor independently verifies GitHub approvals. Requests ask reviewers to add their authenticated GitHub account when permitted.

The original submitting device continues pending triage while the plugin is enabled. Signed current state, a Web Lock, artifact compare-and-swap, and the outbox govern sends. The dock and table share one event-driven submission reader after channel access is confirmed. Reads are bounded, startup is jittered, and failed refreshes back off. No polling is added. Seen preferences are local to the device, identity, community, and channel. A capped history read falls back to current statuses and marks review dates unavailable.

Risk

The plugin starts disabled. Review sequence enforcement belongs to the tool, not relay authorization. Two concurrent hosts can still post duplicate corrective replies. GitHub approval and reviewer assignment remain the reviewer's responsibility and require a runtime with permission. Native-app and final human acceptance remain outstanding; keep this PR draft.

Testing

The existing diff browser fixture now warms its static module graph before navigation using the shared helper. This addresses a recurring cold-load timeout in Chromium CI; assertions, timeouts, retries and case counts are unchanged. Hosted confirmation remains pending.

Local macOS validation with two workers: bin/pnpm test:browser tests/browser/diffs.spec.mjs --project=chromium --project=webkit --no-deps --repeat-each=N --reporter=json. Before (clean 1ab3cf374, N=2): 4/4 passed, 26.13s wall, 42.54s summed execution, 1.80s until first test; mean Chromium/WebKit case times 10.53/10.74s. After (same head plus only the fixture warm-up, N=10): 20/20 passed, 133.47s wall, 247.79s summed execution, 1.67s until first test; mean case times 11.47/13.30s, slowest 15.24s. Case execution includes fixture setup and warm-up; these unequal-length local runs are diagnostic, not a hosted speedup claim.

• Real browser → MCP → local relay: submit, reject a skipped Reviewing step, save Reviewing, report changes or a positive outcome, remind with a note, and require fresh acceptance. Tested approval disabled and enabled using synthetic reports; no GitHub approvals were submitted.
• Updated a UI lane while the PR page was closed: the dock count appeared, keyboard opening cleared it, and only the UI lane was marked. Returning cleared the visit markers; a live Backend update marked only that lane while the dock remained clear. Each lane showed Last updated. Reload preserved acknowledgment. Inspected light/dark, wide/narrow and enlarged layouts, including horizontal table scrolling. The isolated submission was removed afterward. All 137 review-plugin tests and TypeScript passed.
• Inspected the running table and dock in light/dark, wide/narrow, and enlarged-text layouts. Checked keyboard and pointer navigation, existing page actions, message-dialog Back/Forward, and focus. Reused CountBadge, Button, semantic text colors, FullPageSurface, PanelHeader, and the existing table scrollport.
• Earlier live runs covered admission rejection, agent triage, automatic routing with the page closed, retry recovery, deletion/resubmission, and closed-PR reminder guards. An actual agent saved Reviewing and updated the table. Actual GitHub reviewer assignment and approval remain untested.
• No repository browser cases were added or removed. State and failure matrices use colocated tests; the real browser/MCP/relay boundary was exercised in the local lab.

To try updates: choose a review channel, submit a PR, leave the PR page, and have its assigned reviewer report Reviewing followed by a result. Return through the badged icon: the dock badge clears, and Updated markers identify the changed lanes. Inspect each lane’s Last updated date. Leave and return to clear the visit markers; a later report or reminder while away should badge the PR again.

Generated with Codex