V1 Web PWA · Surface walkthrough

Studio · Yemaya · CLI

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/cli · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/yemaya/cli/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#

Aggregator workspace that composes the CLI-adjacent Yemaya lanes — Developer SDKs, the Documentation Playground, and Pipeline Configuration — under a single Yemaya CLI capability summary. It owns no /v1 fetch of its own; each embedded lane is its own admin-scoped console with independent data and states.

Entry points#

  • Breadcrumb chain on this page: Studio › Yemaya Documentation Playground › CLI.
  • Reachable from sibling Yemaya routes that quick-action to /studio/yemaya/cli.
  • Direct URL / bookmark (signed-in + studio entitlement).

Layout regions#

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

  • Breadcrumbs panel: Studio › Yemaya Documentation Playground › CLI.
  • Workspace panel (StudioYemayaCliWorkspace, data-yemaya-cli-workspace):
    • <h1> (WorkspaceHeading) "Yemaya CLI Workspace".
    • Summary paragraph (data-yemaya-cli-summary).
    • Capability Summary (data-yemaya-cli-capability-summary, <h2>): four informational cards — Typed Command Operations, SDK and Docs Lane, Automation Configuration, Security and Parity.
    • Developer SDKs Lane (data-yemaya-cli-sdk-lane, <h2>): embedded StudioYemayaDeveloperSdksWorkspace.
    • Documentation Playground Lane (data-yemaya-cli-docs-lane, <h2>): embedded StudioYemayaDocumentationPlaygroundWorkspace.
    • Pipeline Configuration Lane (data-yemaya-cli-pipeline-configuration-lane, <h2>): embedded StudioYemayaPipelineConfigurationWorkspace.
  • Route Map panel (data-yemaya-cli-route-map): <h2> "Route Map" + six entries from STUDIO_YEMAYA_CLI_ROUTE_MAP.
  • Quick-action panel: four quickAction links.

States#

The page renders the capability cards + three embedded lanes unconditionally; each lane owns its own Loading / Unauthorized (admin-scope 401/403) / Error / Ready / Result states.

  • Developer SDKs Lane — states owned by /studio/yemaya/developer-sdks.
  • Documentation Playground Lane — states owned by /studio/yemaya/documentation-playground.
  • Pipeline Configuration Lane — states owned by /studio/yemaya/pipeline-configuration.

Interactions#

Capability cards#

data-yemaya-cli-capability — four informational <article> cards (Typed Command Operations, SDK and Docs Lane, Automation Configuration, Security and Parity); not interactive.

Embedded lanes#

Route map#

data-yemaya-cli-route-map — six non-interactive entries:

  • /studio/yemaya/cli — primary workspace
  • /studio/yemaya/cli/commands/[commandId]
  • /studio/yemaya/cli/profiles/[profileId]
  • /studio/yemaya/cli/integrations/[integrationId]
  • /studio/yemaya/cli/parity/[parityId]
  • /studio/yemaya/cli/governance/[policyId]

Quick actions#

  • "Open Yemaya Developer SDKs workspace" → /studio/yemaya/developer-sdks.
  • "Open Yemaya Documentation Playground workspace" → /studio/yemaya/documentation-playground.
  • "Open Yemaya Pipeline Configuration workspace" → /studio/yemaya/pipeline-configuration.
  • "Back to Studio workspace index" → /studio.

Data & contracts#

  • Reads: none at this aggregator boundary; each embedded lane issues its own GET /v1/admin/yemaya/... on mount.
  • Writes: none at this boundary; each embedded lane owns its own POST verb.
  • Realtime: none.
  • Caching: aggregator owns no fetch; embedded lanes fetch on mount with cache: 'no-store'.
  • Auth/role check: each embedded lane is admin-scoped and fail-closed; signed-in + studio entitlement enforced by the proxy/middleware.

Cross-references#

Open questions / known gaps#

  • The route-map dynamic children (commands / profiles / integrations / parity / governance) are sitemap-only — confirm whether any are backed by page.tsx files yet.