V1 Web PWA · Surface walkthrough

Studio · Yemaya · Asset Marketplace

A per-surface walkthrough of the V1 Web PWA studio surface: layout, states, interactions, data, and cross-references.

walked
8sections2 minread
Markdown source
On this page

Context. surface studio · domain yemaya · route /studio/yemaya/asset-marketplace · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/yemaya/asset-marketplace/page.tsx

Last walked. 2026-05-29 automated runtime walk (Playwright headless) — render, /v1 data (2xx), console/page-errors, expected content, screenshot verified; live screen-reader, touch, offline, and telemetry-delivery checks pending a manual AT pass. Evidence: WALKTHROUGH/results/runtime-sweep-2026-05-29.md; body re-derived 2026-06-03 from current source (lane-console architecture)

Purpose#

Admin lane console that validates a Yemaya asset-marketplace listing draft against the publish-readiness rules before a listing can go live — title length, kebab slug, bounded tags, asset files with exactly one main file, and pricing consistency. The validation lane is wired to the live listing-publication validator over /v1/admin/yemaya/asset-marketplace; access is admin-scoped and fail-closed.

Entry points#

  • No breadcrumb panel on this page.
  • Reachable from sibling Yemaya routes that quick-action here (e.g., plugin-marketplace, marketplace).
  • Direct URL / bookmark (signed-in + studio entitlement).

Layout regions#

page.tsx renders ShellLayout active="studio" and:

  • Workspace panel (StudioYemayaAssetMarketplaceWorkspace, data-yemaya-asset-marketplace-workspace):
    • <h1> (WorkspaceHeading) "Yemaya Asset Marketplace Workspace".
    • Summary paragraph (data-yemaya-asset-marketplace-summary).
    • Listing Validation Lane (data-yemaya-am-lane-heading, <h2>): the catalog-loaded form (data-yemaya-am-form) for a listing draft.
  • Route Map panel (data-yemaya-asset-marketplace-route-map): <h2> "Route Map" + five entries from STUDIO_YEMAYA_ASSET_MARKETPLACE_ROUTE_MAP.
  • Quick-action panel: two quickAction links.

States#

  • Loading — data-yemaya-am-loading "Loading asset-marketplace validator…" until the GET catalog resolves.
  • Unauthorized — data-yemaya-am-unauthorized "Access restricted." on a 401/403 (Yemaya admin scope required).
  • Error — data-yemaya-am-error "Could not load the asset-marketplace validator." on a non-OK / malformed catalog response.
  • Ready (form) — engine summary (data-yemaya-am-engine-summary) + the validation form render once the catalog loads.
  • Result — data-yemaya-am-result with a verdict headline (data-yemaya-am-headline) and the per-field issue list; submit-side validation surfaces in data-yemaya-am-validate-error.

Interactions#

Listing Validation Lane#

  • "Listing draft (JSON)" — <textarea data-yemaya-am-draft> (aria-label "asset listing draft json"), prefilled with a sample draft.
  • "Validate listing" — <button data-yemaya-am-submit>; submitting the form POSTs the draft to /v1/admin/yemaya/asset-marketplace/validate and renders the valid/error/warning verdict + issue rows.

Route map#

data-yemaya-asset-marketplace-route-map — five non-interactive entries:

  • /studio/yemaya/asset-marketplace — primary workspace
  • /studio/yemaya/asset-marketplace/scenes/[sceneId]
  • /studio/yemaya/asset-marketplace/exports/[exportId]
  • /studio/yemaya/asset-marketplace/revisions/[revisionId]
  • /studio/yemaya/asset-marketplace/governance/[policyId]

Quick actions#

  • "Open Yemaya XR Support workspace" → /studio/yemaya/xr-support.
  • "Back to Studio workspace index" → /studio.

Data & contracts#

  • Reads: GET /v1/admin/yemaya/asset-marketplace (catalog: summary, pricing types, max title length, max tags) on mount.
  • Writes: POST /v1/admin/yemaya/asset-marketplace/validate (listing draft → validation result).
  • Realtime: none.
  • Caching: client fetch on mount with cache: 'no-store'; buildBffAuthHeaders().
  • Auth/role check: admin-scoped, fail-closed (401/403 → unauthorized state); signed-in + studio entitlement enforced by the proxy/middleware.

Cross-references#

Open questions / known gaps#

  • The route-map dynamic children (scenes / exports / revisions / governance) are sitemap-only — confirm whether any are backed by page.tsx files yet.