Operator Integrations page + capability framework (P3 UI) #1

jules · 2026-06-09T13:09:46Z

jules commented

2026-06-09 13:09:46 +00:00

Completes the arcadia-admin operator surface for the integration registry.

Operator Integrations page (/api/v1/integrations*): scope filter, per-card scope badge, create platform/pooled credentials, credentials/usage, gate-check Test.
Client delegates to the shared @crema/integration-registry-client lib (vite alias + tsconfig).
platform.integrations capability + Data-group nav.
Includes the supporting capability-gating framework (capabilities map, route-guard, jwt helpers, apps/plan/entitlements routes).

My integration files typecheck clean.

🤖 Generated with Claude Code

Completes the arcadia-admin operator surface for the integration registry. - Operator Integrations page (`/api/v1/integrations*`): scope filter, per-card scope badge, create platform/pooled credentials, credentials/usage, gate-check Test. - Client delegates to the shared `@crema/integration-registry-client` lib (vite alias + tsconfig). - `platform.integrations` capability + Data-group nav. - Includes the supporting capability-gating framework (capabilities map, route-guard, jwt helpers, apps/plan/entitlements routes). My integration files typecheck clean. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

jules added 2 commits 2026-06-09 13:09:46 +00:00

Add operator Integrations page (integration registry console) 06490865d3

The operator surface for the integration registry: manage platform/pooled
external-API credentials across every scope and inspect cross-tenant usage
(metadata only — secrets are write-only). Talks to arcadia-llm-gateway's
/api/v1/integrations* endpoints via a gateway-pointed ArcadiaClient.

- gateway.ts: second ArcadiaClient at VITE_LLM_GATEWAY_URL, reusing the
  arcadia-app JWT (the gateway validates it via the shared Guardian secret;
  CORS already allows *.sky-ai.com + localhost — no proxy).
- lib/arcadia/integrations.ts: operator API client (any-scope create, scope
  filter, cross-tenant usage). Pure functions over an injected client —
  extraction-ready to share with arcadia-console.
- routes/integrations.tsx: scope filter + per-card scope badge, create
  platform/pooled credentials, credentials/usage, Test (surfaces the
  expiry/budget gate), enable toggle, delete.

The route/nav/capability wiring (routes.ts, app-shell, capabilities.ts) lands
with the in-flight capability framework, not here.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Wire operator Integrations page + capability-gating framework 4b817b85ff

Completes the arcadia-admin operator surface for the integration registry and
the capability/route-guard framework it depends on.

- Integration registry: route + Data-group nav entry + `platform.integrations`
  capability; the in-app client now delegates to the shared
  `@crema/integration-registry-client` lib (vite alias + tsconfig); the
  operator Integrations page (committed earlier) is now reachable.
- Capability gating: capabilities map + route-guard + jwt helpers + the
  apps/plan/entitlements routes and supporting tenants/session changes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

jules merged commit 6ab9b730f5 into main

2026-06-09 13:15:16 +00:00

jules referenced this issue from a commit

2026-06-09 13:15:17 +00:00

Merge pull request 'Operator Integrations page + capability framework (P3 UI)' (#1) from feat/integration-registry into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: CremaUIStudio/arcadia-admin#1