[MOCK UI TEST] Generated UI imagery for the 10 latest changelog entries

[samgutentag]

Experiment (per Sam's request): generate mock-UI product imagery for recent changelog entries and insert each image after the opening bold paragraph. This is a test run — open as draft for review.

What this is

Each image is a faithful HTML reproduction of the relevant Trunk surface (built from real trunk2 design tokens + component source via the mock-ui skill), captured to PNG and scrubbed to Acme Corp data. Not real product screenshots, not creative redesigns — reproductions for changelog illustration.

Scope

The literal "latest 10 by date" included 6 entries that live on unmerged pending/held PRs (fork-pr-uploads, testing-duration, stacked-prs, filterable-uploads, test-collections, stable-branches) — not on main, so a single PR can't touch them without prematurely publishing them. This covers the 10 latest entries that are live on main. None already had images.

The 10 images

Entry	What the mock shows
monitor-action-types	"Mark tests as" classify card + Apply-labels card
run-history-filters	Result + Quarantined segmented controls over the runs table
pass-on-retry-branch-scope	Pass-on-retry config with Branch Scope chips (main, release/*)
failure-statuses	MQ item detail: "Waiting on" PRs + "Required check failed" status
repositories-overview	Repos overview table: Tests/Flaky/Broken + sparklines + Runs/Day
linked-tickets	Test detail with an intact linked Linear ticket chip
ai-investigations-webhooks	Slack message: Trunk posting an AI investigation result
no-monitors-banner	Flaky Tests page warning banner + Monitors tab indicator
detect-broken	Threshold monitor with Detection type = Broken + red BROKEN badge
flag-as-flaky	Test status strip with Flag as Flaky + amber flagged banner

Fidelity caveats worth a look (from the build agents)

• pass-on-retry-branch-scope: Branch Scope doesn't yet exist in the pass-on-retry component in trunk2; styling was ported from the failure-count monitor's Branch Scope. Verify the feature actually renders this way.
• monitor-action-types: live UI uses two stacked action cards (not a segmented control); mock matches the real components.
• flag-as-flaky: the full who/when/why banner is a composition from real fields (markedBy/updatedAt/note); the live component renders an inline amber pill + attribution rather than a separate banner.
• no-monitors-banner: used the changelog's copy ("No detection monitors configured…") + a warn icon; live banner wording differs slightly.

How to regenerate / tweak

Source HTML mocks live at ~/TRUNK/mocks/changelog-mock-test/. Re-capture via Chrome (full-page screenshot → PIL crop on the data-capture region). Light mode; dark variants not generated.

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
trunk	🟢 Ready	View Preview	May 29, 2026, 7:27 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[samgutentag]

Verification status (2026-05-29): unknown

Could not determine rollout state from available signals. Chaining to verify-docs-against-code for content-accuracy check.

• Flag state: not applicable. This PR adds mock-UI imagery to changelog entries already live on main; it ships no feature and references no eng PR.
• Eng PR: none referenced in the PR body.
• Flag: none.
• Signals: no trunk-io/<repo>#NNN eng refs and no TRUNK-XXXX Linear ticket in the body, so there is no rollout state to read. This is the [MOCK UI TEST] experiment PR (parked per Sam's notes); verifying only, not merging or expanding.

No verdict label applied (unknown). The changelog category label is set because the diff touches changelog/ and assets/changelog/. No Linear ticket in the PR body, so no Linear comment posted.

[samgutentag]

Code verification (2026-05-29): no claim candidates found.

This PR adds mock-UI PNG assets and inserts 10 markdown image embeds (alt text plus asset paths) into changelog entries already live on main. There are no factual technical claims to verify against source (no field names, numeric limits, API paths, branch patterns, CLI flags, or env vars). No draft change, no label.

Note: the PR body flags four fidelity caveats from the mock-build agents (pass-on-retry Branch Scope not yet in the trunk2 component, monitor-action-types card layout, flag-as-flaky banner composition, no-monitors banner wording). Those are image-accuracy questions about whether the mocks match the live UI, not docs-text claims, so they fall outside this skill's scope. Worth a human eyeball before these images ship.

[samgutentag]

Verification status (May 31, 2026): unknown

Could not determine rollout state from available signals.

• Eng PR: none referenced in PR body
• Flag: none
• Flag state: not applicable (no eng PR, no product feature)
• Signals: no trunk-io/repo#NNN eng refs and no TRUNK-XXXX Linear ticket. This is the [MOCK UI TEST] experiment PR; it ships no feature and references no eng PR. No rollout state to verify. Verdict unchanged.

No verdict label applied. No further action needed on rollout verification.

---

Generated by Claude Code

[samgutentag]

Docs Verify Sweep · June 1, 2026 · ❓ unknown

Could not determine feature status — no linked eng PR or feature flag found, or signals were unclear. Manual review required.

Unchanged from previous sweep (May 31, 2026).

---

Generated by Claude Code

[samgutentag]

closed, use /ui-capture skill instead, no reason to mock uis and generate any form of confusion down the line