Studio Hathor · NPC Platform Integrations

Purpose#

Admin lane console for the NPC platform capability checker. The single Live Platform Capability Matrix lane checks each target platform's supported capabilities against the NPC feature's required set, returning per-platform compatibility and the missing capabilities. Admin-scoped and fail-closed.

Entry points#

• Direct URL / bookmark — /studio/hathor/npc-platform-integrations; alternates.canonical is set.
• Quick-action from siblings — the Lore Validation Timeline lane links here; this page links to NPC-to-NPC Conversations.
• Studio overview — see ../../studio-overview.md.

Layout regions#

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

• Workspace (StudioHathorNpcPlatformIntegrationsWorkspace, data-hathor-npc-platform-integrations-workspace):
  • <h1> WorkspaceHeading — "Hathor NPC Platform Integrations Workspace"
  • Summary <p data-hathor-npc-platform-integrations-summary>
  • The embedded PlatformCapabilityLane (data-pcm-lane, <h2 data-pcm-heading>Live Platform Capability Matrix</h2>): its own fetch-on-mount catalog state, then the evaluation form + result table.
• Route Map panel (<section data-hathor-npc-platform-integrations-route-map>, <h2>Route Map</h2>): 5 entries from STUDIO_HATHOR_NPC_PLATFORM_INTEGRATIONS_ROUTE_MAP (path + purpose).
• Quick-action lane (className="quickAction" Links): NPC-to-NPC Conversations, Back to Studio workspace index.

States#

• Loading — <p data-pcm-loading> "Loading platform capability checker…".
• Unauthorized — data-pcm-unauthorized on 401/403 (admin-scope).
• Error — data-pcm-error on a non-OK catalog response or network failure.
• Ready (form) — data-pcm-form with the capabilities/platforms textarea.
• Result — data-pcm-result with data-pcm-headline (data-pcm-compatible-count) and the data-pcm-platforms table (data-pcm-platform-row carrying data-platform / data-compatible, data-pcm-missing).
• Validation error — data-pcm-evaluate-error for malformed JSON or a failed POST.

Interactions#

• data-pcm-payload (textarea, aria-label="platform capabilities json") — edit the { requiredCapabilities[], platforms[{ platformId, supportedCapabilities[] }] } JSON.
• data-pcm-submit ("Evaluate platforms") — parses the JSON and POSTs it to the evaluate endpoint; on 200 with a valid result renders the matrix.
• Route Map entries — verify against STUDIO_HATHOR_NPC_PLATFORM_INTEGRATIONS_ROUTE_MAP (5 entries).
• Quick-action links — NPC-to-NPC Conversations (/studio/hathor/npc-to-npc-conversations), Back to Studio (/studio).

Data & contracts#

• Reads: GET /v1/admin/hathor/npc-platform-integrations (the catalog body is fetched to gate the lane; the form itself supplies the evaluation input).
• Writes: POST /v1/admin/hathor/npc-platform-integrations/evaluate with the capabilities/platforms payload.
• Realtime: none.
• Caching: client fetch on mount, cache: 'no-store', buildBffAuthHeaders(), AbortController on unmount.
• Auth: admin-scoped, fail-closed (401/403 → unauthorized); route is behind the signed-in + studio proxy gate.

Cross-references#

• Parent: ../../studio-overview.md
• Component sources:
  • apps/oshun/web/src/components/studio/StudioHathorNpcPlatformIntegrationsWorkspace.tsx (wraps the PlatformCapabilityLane)
  • apps/oshun/web/src/components/studio/StudioHathorNpcPlatformIntegrationsRouteMap.ts
• Siblings: ./studio-hathor-npc-to-npc-conversations.md, ./studio-hathor-lore-validation-timeline.md

Open questions / known gaps#

• Hathor is unconfirmed-v1 per WALKTHROUGH/matrix/routes.csv; confirm whether the dedicated /studio/hathor/* admin lanes ship V1 or are internal-only.