[viethqb]

Re-shoots the screenshots that Wave 2 (#29) and Wave 2b (#30) listed as stale, on the shared demo stack rebuilt from platform main at 4755bdcf (B6 #728 on top of B7 #727, B4 #726 and Wave 2). egret and frontend were rebuilt from that commit; renderer was not (no change under renderer/ since its image was built). Main was checked live before shooting: the audit log opens on Changes and denials, the audit API returns actorEmail, the bundle carries Disable user and Waiting for first sign-in, and a Docker engine shows its containers.

All shots: 1440x900 (or the height the shot script sets), light theme, one admin session, every PNG viewed.

Re-shot (25)

• Control Plane, B7 (control-plane/access-control/users.md, audit-log.md, access-control/index.md): admin/cp-audit-log (opens on Changes and denials, actor email), admin/cp-user-detail, admin/cp-users-bulk, control-plane-access-overview (Recent changes by email)
• Workspace settings, B7 (members.md, roles-and-permissions.md): admin/ws-members (with a Waiting for first sign-in row and Withdraw), admin/ws-add-member, admin/ws-roles (the data_api_invoker note, 9 permissions (7 inherited)), admin/ws-roles-expanded
• Engines, B6 (query-engines/engine-detail.md): admin/cp-engine-catalogs, admin/cp-engine-workspaces (a temporary Docker engine docs-trino, deleted afterwards)
• Alerts and reports, B4 (alerts-and-reports/index.md, create-an-alert.md): alerts/alerts-list (seven alerts, two Data API alerts, with Success / Error / Not triggered), alerts/detail (Error when one destination fails, each failed destination named)
• Charts, Wave 2 (row.md, progress.md, gauge.md, number.md, table.md, the-chart-editor.md): charts/row-data (largest bar on top), charts/progress-data, charts/gauge-display, charts/scalar-display, charts/table-data (display names in the header), charts/editor-export (10,000 rows)
• Dashboards, Wave 2 (export-and-reports.md): dashboards/card-export (10,000 rows)
• Datasets, Wave 2 (usage-and-preview.md, datasets-and-metrics/index.md): sql-datasets/ds-usage (per-type icons), sql-datasets/ds-preview (display names), sql-datasets/datasets-row-menu (Duplicate)
• Data API, Wave 2 (publishing.md, parameters.md, access.md): data-api/endpoint-versions (badge beside the note), data-api/endpoint-params (constraint labels), data-api/endpoint-access (no revoke note on endpoint-only grants)

Text changed because a re-shot image contradicts it

• access-control/users.md: the cp-user-detail caption said "two platform roles"; the page lists only directly granted roles (KI-260) and Farid Haddad's direct role is security_auditor (his data_steward comes through data-stewards).
• data-api/endpoints/publishing.md: the endpoint-versions caption said the badge sits "over its note" (the fixed KI); it is beside it now.
• workspace-settings/roles-and-permissions.md: the ws-roles caption counted "two custom roles" (the stack has three); the quoted banner now has its second sentence about data_api_invoker.

Shot-script changes

• scripts/screenshots.mjs resets the viewport to 1440x900 before each shot: a shot that sets a taller viewport no longer leaks it into the next one (it did, and charts came out 1000 px tall).
• scripts/shots/{alerts,charts,dashboards,data-api,sql-datasets}.mjs take DOCS_WS (default default) for the workspace the Explore objects live in. This pass used DOCS_WS=docs-sandbox, so these shots show the Docs sandbox workspace, like the admin shots.

Still stale, and why

• Governance: admin/gov-overview, admin/gov-table-lineage, admin/gov-tag-exposure (and the rest of the gov-* set): they need the docs-trino tables in demo_warehouse.analytics, the view, grants, rules and tags of scripts/shots/admin-demo-data.md step 3; not rebuilt in this pass.
• admin/cp-engines: kept. A re-shot list shows only docs-trino; the caption names the external engine trino-demo-ext, which is not registered on the stack. The kept image already has the Endpoint column.
• admin/cp-engine-logs: no longer referenced by any page (Docker engines have no Logs); left in place.
• ops/get-started/sign-in and sign-in-break-glass: re-shot and identical, so not committed. The error message is not on a screenshot.
• Re-shot and dropped as unchanged: data-api/endpoints-list, admin/cp-users, sql-datasets/datasets-trash. sql-datasets/sqllab-truncated was not re-shot: in Docs sandbox (two connections) SQL Lab opens with no database selected.

Seed data created on the demo stack

All in the docs-sandbox workspace (Docs sandbox), from the docs repo's scripts/seed-* shapes run against that workspace: the connections trino-demo and trino-sandbox (both trino-demo:8080), the datasets, metrics, charts, folders and dashboards of seed-sql-datasets, seed-charts-deep, seed-dashboards, seed-sql-charts-lists and seed-admin (sandbox part), the Data API service accounts, clients and endpoints of seed-data-api, the alerts, Data API alerts and reports of seed-alerts (run once with --run), workspace SMTP pointed at Mailpit, and a pending SSO pre-registration nina.park@egret.local (ws_viewer). Admin is a ws_admin member of Docs sandbox (the alert owner picker shows a raw user id for an owner who is not a member). Platform-wide, from seed-admin.mjs under their documented names (the pages name them): users alice.nguyen … hiro.tanaka@egret.local (grace.lee disabled), groups finance-analysts, marketing, data-stewards, executives, roles finance_reporter, marketing_analyst, security_auditor, and the catalog tpch_bench. Other workspaces of seed-admin.mjs, secrets, storage, tags and access requests were not created. Nothing with the b4-, b6-, b7- or docs-w2b- prefix was changed; b7_reporter and the b7- users appear in some shots read-only.

The build passes for en and vi with DOCUSAURUS_NO_PERSISTENT_CACHE=1 npm run build.

🤖 Generated with Claude Code