Skip to content

Enable + validate automated visual capture end-to-end for metagraphed #3611

Description

@JSONbored

Part of #3607. Depends on #3608, #3609, #3610.

Motivation

Once self-host rendering, preview-URL discovery, and per-repo route mapping are done, the feature still needs to actually be turned on and verified against real traffic before it's trustworthy enough to rely on instead of contributor-submitted screenshots.

Requirements

  • Set GITTENSORY_REVIEW_SCREENSHOTS=true on edge-us-01 (metagraphed is already on the GITTENSORY_REVIEW_REPOS cutover allowlist — no change needed there).
  • Open a real (or deliberately test) PR against metagraphed touching apps/ui/** and confirm: the before/after table renders in the gittensory-orb comment, both desktop + mobile shots are present, the "after" shot reflects the actual PR change (not a stale/placeholder image), and a failed/pending preview degrades to the documented placeholder cards rather than a broken image or a thrown error.
  • Confirm capture failures are fully fail-safe under real self-host conditions (network timeouts to the browserless service, etc.), not just in unit tests — a broken screenshot must never block or hold an otherwise-mergeable PR (already a design invariant of buildCapture/capturePage; verify it holds in practice).
  • Monitor cost/latency impact for a week of real traffic before calling this done — Browser Rendering (or its self-host chromium equivalent) is explicitly called out in the existing code comments as the most expensive part of this pipeline.

Deliverables

  • Flag enabled on edge-us-01
  • At least one real metagraphed PR with a verified, correct before/after table
  • A documented rollback plan (flip the flag back off) if something goes wrong
  • A week of production observation with no regressions before calling this shipped

Expected outcome

Metagraphed contributors touching apps/ui/** get automated before/after visual evidence with no action required on their part — the original ask, fully live.

Effort

S — mostly verification/observation once the prerequisite sub-issues land, not new engineering.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)visualUI/web visual work — owner-led, NOT for Gittensor contributors (extensions excepted)

Projects

Status
Done

Relationships

None yet

Development

No branches or pull requests

Issue actions