chore(docs): sweep stale visual-baseline references + queue gate-hardening convoy #135
No reviewers
Labels
No labels
agent-context-drift
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: rstillwell/deckhearth#135
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/sweep-visual-baseline-doc-drift"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
PR #58 (`83a358b`, 2026-06-02) committed the first Linux visual baseline, resolving the `seed-visual-baselines-on-linux` convoy. But the cleanup sweep across the docs that referenced it as "queued / not yet done" never landed. Three files still describe the world as if PR #58 hadn't happened, which makes onboarding any agent (human or AI) into the visual-diff pipeline confusing — they read "no baseline yet" + a Docker-recipe seeding instruction, when the baseline has been on `main` for 10 days.
Surfaced organically while investigating whether `seed-visual-baselines-on-linux` still had work to do. The answer is "no, but the post-resolution sweep does."
What
Pure doc / comment changes. Zero code behavior delta.
What this PR does not do
Test plan
Related
Made with Cursor
The latest updates on your projects. Learn more about Vercel for GitHub.
Pipeline Health
Build + CI gates
Build runs on Vercel; this CI runs lint and schema-map drift only (no duplicate build).
Role reports
See individual comments above for details. This rollup updates automatically.
Visual Diff
Screenshots and diffs uploaded as artifacts: view run
If intentional changes: update snapshots locally with
npx playwright test --project=visual --update-snapshotsand commit.