Review a WordPress Design System contribution

Establish the review boundary

1. Define the changed public surface and observable behaviour.
2. Scan the complete diff once, then classify it as:
   • Internal: no public contract or observable behaviour changes.
   • Public: adds, removes, renames, or changes supported behaviour.
3. Read Working with WordPress Design System packages and the applicable package source guidance.
4. Apply the public guide's evidence precedence: the diff is the proposed post-change state, target source is its baseline, and MCP is supplementary current-design context.

Review proportionally

For an internal change, verify contract preservation and focused coverage, then skip the public-only work below. For a public change: