Review comment

Handle $ARGUMENTS.

Plate v2 on next, Plite included, is the reference. It has already worked through most jobs that Slate and Plate main PRs take on, and its decisions record what it picked, what it rejected and why. The review brings that evidence to the PR, proves every failure on the PR's head, and hands back a comment draft. The comment is public text, so it stays a draft until the owner says to post it.

It covers a PR in ianstormtaylor/slate or a udecode/plate PR whose baseRefName is main. A PR based on next, and any repair of a PR, go to the Babysit playbook. Like Babysit's review-only path, the run keeps no plan, page or decision log. Its run directory, docs/plans/artifacts/<date>-<repo>-<number>-review/, is ignored by git and holds the diff, the probes and the draft.

Steps

1. Read the PR. Run gh pr view <n> --repo <repo> --json title,author,body,baseRefName,headRefOid,files,comments,reviews,closingIssuesReferences, save gh pr diff to the run directory, run gh pr checks, and read each linked issue with gh issue view. Read every changed source file in full. The body's claims, its stated limits included, are claims to test. Done when you can name in one line the job the PR changes, such as "replace the document from outside the editor", and you hold the head SHA.

2. Gather the Plate v2 evidence. Search with rg --hidden, as AGENTS.md's Source authority says. For each lane, record what v2 decided, what it rejected and why, with the path:

   • Mentions: the PR and each linked issue, written as <repo>#<n> or <owner>/<repo>/(issues|pull)/<n>, anywhere in the repository; the bare number in docs/editor-issue-harvester/slate/ for a Slate issue; and pnpm kb slate#<n> or pnpm kb plate#<n> for the tests tagged with the issue.
   • Doctrine: VISION.md, then docs/vision/plite.md for a Slate PR or docs/vision/plate.md for a Plate PR.
   • Decisions and subjects: the job's words in docs/plans/topics/ and docs/editor-behavior/markdown-editing-spec.md. Read each match's verdict paragraph and its alternatives table.
   • Code and docs: v2's owner of the same job in packages/plitejs or packages/platejs, its tests, and the page in content/docs that teaches it.

   Done when every lane has an answer or a recorded miss, and you can say in one sentence what v2 does for this job. When v2 has nothing on the job, the comment says so instead of borrowing a nearby decision.