V1 Web PWA · Surface walkthrough

Studio Aja · Configuration Formats

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

walked + e2e-covered
9sections3 minread
Markdown source
On this page

Context. surface studio · domain aja · route /studio/aja/configuration-formats · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/aja/configuration-formats/page.tsx

Last walked. 2026-07-02 developer-ops lane addendum — Playwright real-dev-infra coverage now proves signed-in render, route-map contract, quick-action href order, ready format resolver form and matrix, 44 px submit target, blank-input client guard with no POST, real BVH/USDA/unrecognized detect results, fail-closed loading/unauthorized/catalog-error states, mobile no-overflow, and direct BFF 401/403/400/200 gates for catalog and detect. Spec: apps/oshun/web/e2e/studio-aja-developer-ops-lane-consoles.spec.ts.' '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 for the real @aja/motion-formats detectFormat resolver. The lane renders the extension→format support matrix from the catalog and lets the operator resolve a motion file's format from a filename or a content snippet (file extension, USDA header, glTF/FBX/C3D binary magic) — the same resolver the ingest pipeline uses.

Entry points#

  • Direct URL / bookmark — /studio/aja/configuration-formats; metadata canonical to this path
  • Studio nav — Domain-bridge studios section of /studio
  • Sibling quick-actions on this page: Quality Presets, Back to Studio (no breadcrumb panel on this route)
  • Operator surfacing — see ../../studio-overview.md

Layout regions#

page.tsx renders inside <ShellLayout active="studio">:

  • Workspace (<StudioAjaConfigurationFormatsWorkspace />, archetype: LEAF):
    • <h1> (WorkspaceHeading) "Aja Configuration Formats Workspace"
    • Summary <p data-aja-configuration-formats-summary> — inspect the format matrix and resolve a file's format via the detectFormat resolver
    • The detect form + a data-aja-cf-matrix table of the catalog's extension→format rows
  • Route Map panel (data-aja-configuration-formats-route-map): <h2>Route Map</h2> listing 5 entries from STUDIO_AJA_CONFIGURATION_FORMATS_ROUTE_MAP (primary, scenes, exports, revisions, governance)
  • Quick-action panel: two Link.quickAction anchors — Quality Presets, Back to Studio workspace index

States#

  • Loading — GETs the catalog on mount; renders <p data-aja-cf-loading> "Loading format resolver…"
  • Unauthorized — 401/403 renders data-aja-cf-unauthorized ("Access restricted." + admin-scope message, default "Aja workspace scope required to inspect motion formats.")
  • Error — non-OK / malformed / unreachable renders data-aja-cf-error ("Could not load the format resolver." + reason)
  • Ready (form) — success renders the data-aja-cf-form and the data-aja-cf-matrix table (data-aja-cf-matrix-row per extension)
  • Result — a successful POST renders data-aja-cf-result: either data-aja-cf-detected ("detected format: ") or data-aja-cf-unrecognized
  • Detect error — empty input or POST failure renders data-aja-cf-detect-error
  • Empty / Standalone PWA / offline — N/A beyond the above; shell SSR, lane is a client fetch on mount

Interactions#

Workspace lane (data-aja-cf-form)#

  • Filename or content snippet (data-aja-cf-input, input, aria-label "filename or content")
  • "Detect format" (data-aja-cf-submit, submit) — fires POST /v1/admin/aja/configuration-formats/detect with { input }

Format matrix#

  • data-aja-cf-matrix table — non-interactive extension→format rows from the catalog

Route Map panel#

  • Route entries (5 × <article>) — non-interactive path+purpose

Quick-action panel#

  • "Open Aja Quality Presets workspace" → /studio/aja/quality-presets
  • "Back to Studio workspace index" → /studio

E2E coverage#

  • apps/oshun/web/e2e/studio-aja-developer-ops-lane-consoles.spec.ts covers signed-in shell render, ready resolver form and extension matrix, blank input client guard with no POST, real .BVH extension detection, USDA content-snippet detection, unrecognized input state, route-map count, exact quick-action hrefs, 44 px submit target, loading / unauthorized / malformed-catalog fail-closed states, mobile no-overflow, and direct BFF auth/schema/happy-path gates.

Data & contracts#

  • Reads: GET /v1/admin/aja/configuration-formats on mount — catalog { formatMatrix: { extension, format }[] }
  • Writes: POST /v1/admin/aja/configuration-formats/detect — { input } → { result } (input, format, recognized)
  • Realtime: none
  • Caching: client fetch on mount with cache: 'no-store' and buildBffAuthHeaders(); SSR shell only
  • Auth/role check: BFF endpoints admin-scoped + fail-closed (401/403 → unauthorized render); route behind the signed-in + studio proxy gate

Cross-references#

Known downstream boundaries#

  • Route-map sub-routes are descriptive contracts; implementation status of those child pages is tracked separately from this leaf console.