Document screenshot evidence requirements for design-visible issues and PRs
Open
@mehul0810 is already working on this.
Since Jul 7, 2026.
area: admin-ui
area: docs
priority: medium
status: ready
type: maintenance
- Dominant language
- PHP
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Perform does not have a durable repo rule for screenshot evidence on design-visible issues and PRs.
Evidence
- Current repo-root docs do not define a screenshot evidence policy.
- Recent admin/UI and beta blocker work required manual enforcement of before/after screenshots and explicit proof-gap statements.
- Design-visible issue intake and PR review are currently relying on thread-level instructions instead of repo-local guidance.
Scope
- Define screenshot evidence requirements for design-visible issues and PRs.
- Require before screenshots or an explicit blocker note on UI/design issues.
- Require after screenshots or equivalent browser proof on UI/design PRs.
- Clarify acceptable substitutes when local browser access is blocked and CI/browser artifacts must stand in.
Acceptance criteria
- The repo has a durable screenshot-evidence rule that contributors and workers can follow.
- Design-visible issues must include before-proof or a stated blocker.
- Design-visible PRs must include after-proof or an explicit proof gap.
- The rule points to where artifacts or screenshots should be linked.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.