V1 Web PWA · Surface walkthrough

Studio Hathor · World API

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 hathor · route /studio/hathor/world-api · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/hathor/world-api/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 that unifies the Hathor world-API lane consoles — world configuration and world version branching — under one route, fronted by a Capability Summary. It owns no /v1 fetch of its own; each embedded lane runs its own surface.

Entry points#

  • Quick-action link from /studio/hathor/world-configuration and breadcrumb parent (verify against that page's source)
  • Direct URL / bookmark — yes; alternates.canonical set to /studio/hathor/world-api
  • Studio overview — see ../../studio-overview.md

Layout regions#

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

  • Breadcrumb panel (data-hathor-world-api-breadcrumbs) — <nav> ol: Studio (link) / Hathor World Configuration (link) / World API (current)
  • Workspace <StudioHathorWorldApiWorkspace /> (data-hathor-world-api-workspace):
    • WorkspaceHeading <h1> — "Hathor World API Workspace"
    • Summary <p data-hathor-world-api-summary>
    • Capability Summary panel (data-hathor-world-api-capability-summary, <h2> "Capability Summary") listing HATHOR_WORLD_API_CAPABILITIES (data-hathor-world-api-capability)
    • Two embedded lanes, each a <section> with an <h2> and a WorkspaceSection:
      • World Configuration Lane (data-hathor-world-api-configuration-lane) → <StudioHathorWorldConfigurationWorkspace />
      • World Version Branching Lane (data-hathor-world-api-version-branching-lane) → <StudioHathorWorldVersionBranchingWorkspace />
  • Route Map panel data-hathor-world-api-route-map — <h2> "Route Map" listing the 6 STUDIO_HATHOR_WORLD_API_ROUTE_MAP entries
  • Quick-action lane — four Link.quickAction anchors: World Configuration, World Version Branching, Workbench Worlds, Back to Studio workspace index

States#

States are owned by each embedded lane; the aggregator itself has no fetch.

Interactions#

Embedded lanes#

  • Each lane's own controls — walk per the per-lane doc

Route Map panel#

  • Route entries — verify match with STUDIO_HATHOR_WORLD_API_ROUTE_MAP (6 entries)

Quick-action lane#

  • "Open Hathor World Configuration workspace" → /studio/hathor/world-configuration
  • "Open Hathor World Version Branching workspace" → /studio/hathor/world-version-branching
  • "Open Hathor Workbench Worlds workspace" → /studio/hathor/workbench-worlds
  • "Back to Studio workspace index" → /studio

Data & contracts#

  • Reads / Writes: none at the aggregator level — delegated to the two embedded lane workspaces
  • Realtime: none
  • Caching: each embedded lane manages its own fetch lifecycle
  • Auth/role check: per embedded lane; route gated signed-in + studio by the BFF proxy

Cross-references#

Open questions / known gaps#

  • Hathor is unconfirmed-v1 per WALKTHROUGH/matrix/routes.csv. Confirm whether the dedicated /studio/hathor/ routes ship at V1 or are internal-only.