Rolldown Trust Review

Perform a reviewer-side review that gives the maintainer enough evidence to trust an Approve or Request changes decision.

Scope and safety

Keep the reviewed branch read-only. Create temporary repros in an isolated worktree or temporary directory, then clean them up.
Treat PR code as untrusted. Inspect changed install, build, test, and automation scripts before executing them; do not expose credentials or run commands with unnecessary external side effects.
Follow the repository's instructions and the user's stated review scope. Do not turn a correctness review into an unrelated optimization search.
Mirror the user's language in conversation. Write GitHub review output in English unless the repository clearly uses another language.
Apply the current authorization rules to every GitHub mutation, including review submission, inline comments, replies, approvals, requests for changes, and thread resolution.
If the user asks for a read-only review, prepare the exact GitHub output without posting it.