Update to Kora

{
  "description": "Use when routing a user to the Platform web UI or naming current app navigation, routes, settings sections, tabs, buttons, or product surfaces.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 307
    },
    {
      "relative_path": "assets/kora-mark.png",
      "size_in_bytes": 24826
    }
  ],
  "name": "kora-product-ui",
  "skill_md_contents": "---\nname: kora-product-ui\ndescription: \"Use when routing a user to the Platform web UI or naming current app navigation, routes, settings sections, tabs, buttons, or product surfaces.\"\n---\n\n# Kora Product UI\n\nUse this skill before naming a Kora web-app destination. Do not invent\nsettings, menus, tabs, buttons, or routes. If a surface is not listed here,\nsay you do not see a current web UI destination for it.\n\nThis skill owns product destinations and visible UI labels. It does not own\nworkflow source authoring, release/deployment command choreography, runtime IO\ncontracts, or extension package authoring.\n\n## Link Rules\n\n- Use relative Markdown links for Platform UI routes, such as\n  `[release detail](/app/releases/<releaseId>)`.\n- Do not format UI routes as code when they should be clickable.\n- Include query parameters only when they select a real section, tab, focus, or\n  environment.\n- Route managed runtime artifact inspection and downloads through Platform UI\n  surfaces. Do not point users to object-store buckets, storage keys, filesystem\n  paths, or signed storage URLs.\n\n## Shell\n\nThe app lives under `/app` and uses a left rail.\n\n| Surface | Route | What it owns |\n| --- | --- | --- |\n| Home | `/app` | Workspace overview, recent health, deployments, runs, events, and links into Releases, Activity, and Environments. |\n| Actions | `/app/inbox` | Human work queue and action completion. |\n| Deployed workflows | `/app/processes` | Live workflows currently deployed to environments. |\n| Releases | `/app/releases` | Immutable release artifacts, release inventory, source import, and deployment targets. |\n| Environments | `/app/environments` | Environment inventory, detail, live deployment status, and environment lifecycle. |\n| Activity | `/app/activity` | Runs, events, failures, and focused activity by person, agent, capability, or workflow. |\n| Settings | `/app/settings?section=workspace` | Workspace, billing, AI usage, access, extensions, variables, secrets, models, artifacts, audit, utilization, plan, and reset sections. |\n\nWorkspace and account switching live at the bottom of the rail. Profile is\n`/app/profile`, not a Settings section.\n\n## Home\n\nUse `/app` for broad workspace orientation. The page summarizes release and\ndeployment health, recent runs/events, workspace participants, and quick links\nto release inventory, runtime activity, and deployment targets.\n\n## Actions\n\n| Surface | Route | Visible behavior |\n| --- | --- | --- |\n| Actions list | `/app/inbox` | Pending human actions with owner, capability, due/release, and context columns. |\n| Action detail | `/app/tasks/:taskId` | Action overview, guidance, input data, schema-driven completion fields, history, `Open run`, and sometimes `Abort run`. |\n\nUse Actions for human tasks awaiting input or completion. Use Activity for run\nhistory and runtime events.\n\n## Deployed Workflows\n\n| Surface | Route | Visible behavior |\n| --- | --- | --- |\n| Deployed workflow list | `/app/processes` | Live deployed workflows by environment, release, last deploy time, last run, and run state. |\n| Environment filter | `/app/processes?environment=<environmentKey>` | Narrows the deployed workflow table to one environment. |\n| Live workflow detail | `/app/workflows/:name?environment=<environmentKey>&releaseId=<releaseId>` | Live workflow graph and release-backed workflow metadata. |\n\nWorkflow rows open the live workflow detail. The list and detail surfaces can\nstart a workflow when a live environment and release are available. Starting a\nworkflow opens a `Start workflow` dialog; successful starts navigate to\n`/app/activity/runs/:runId` with workflow and environment focus.\n\n## Releases\n\nReleases are top-level. They are not under Deployed workflows or Settings.\nCreating a release produces an immutable artifact from source. Deploying that\nrelease to an environment is a separate action.\n\n| Surface | Route | Visible behavior |\n| --- | --- | --- |\n| Release list | `/app/releases` | Release revisions, creation metadata, validation/readiness status, action menu, and source import. |\n| Release detail | `/app/releases/:releaseId` | Defaults to Workflows. The left rail switches to release sections. |\n| Release workflow detail | `/app/releases/:releaseId?section=workflows&workflow=<workflowName>` | Release workflow graph, source files, assets, and `Start workflow` when deployable context exists. |\n| Release triggers | `/app/releases/:releaseId?section=triggers` | Immutable trigger bindings by extension, event, target message, and source path. |\n| Release item detail | `/app/releases/:releaseId?section=<section>&item=<itemName>` | Detail for modeled people, agents, roles, assignments, capabilities, operations, or decisions. |\n| Release deployments | `/app/releases/:releaseId?section=deployments` | Current deployments and deployment targets for the release. |\n\nRelease sections:\n\n| Group | Sections |\n| --- | --- |\n| Process | Workflows, Triggers, Decisions, Operations |\n| Participants | People, Agents |\n| Responsibilities | Roles, Assignments, Capabilities |\n| Runtime | Deployments |\n\nThe Triggers section is an inspection surface. It does not show raw selector,\nprovider payload, or provider provisioning configuration.\n\nVisible release actions include `Import release`, `Create release from source`\ninside the import dialog, opening a release detail, `Deploy to environment...`\nfrom the release list, `Deploy this release...` or `Replace with this\nrelease...` from release deployment targets, the deploy dialog's `Deploy to\nenvironment` confirmation, starting a workflow from a release workflow, and\nreturning to an older release by deploying that release again.\n\n## Environments\n\n| Surface | Route | Visible behavior |\n| --- | --- | --- |\n| Environment list | `/app/environments` | Environment inventory and `Add environment`. |\n| Environment detail | `/app/environments/:environmentKey` | Deployment history, links to releases and deployed workflows, undeploy controls, and per-deployment trigger route/stream health disclosed from the Triggers column. |\n\nVisible actions include `Add environment`, `View`, `View workflows` when live,\n`Rename`, `Archive`, and `Undeploy` from a live deployment row on the\nenvironment detail page. Environment management is owner/admin gated.\n\nUse Environments for environment lifecycle and live deployment status. Use\nSettings -> `Environment variables` for runtime configuration values.\n\n## Activity\n\n| Surface | Route | Visible behavior |\n| --- | --- | --- |\n| Runs tab | `/app/activity` | Default tab. Workflow execution history by environment and release. |\n| Events tab | `/app/activity?tab=all` | Runtime events. |\n| People tab | `/app/activity?tab=people` | Focus activity for one modeled person. |\n| Agents tab | `/app/activity?tab=agents` | Focus activity for one modeled agent. |\n| Capabilities tab | `/app/activity?tab=capabilities` | Focus activity for one capability. |\n| Workflows tab | `/app/activity?tab=workflows` | Focus activity for one workflow. |\n| Failures tab | `/app/activity?tab=failures` | Failed runs and events needing review. |\n| Activity run detail | `/app/activity/runs/:runId` | Execution graph, timeline, step details, run metadata, artifacts, and abort controls when allowed. |\n| Run detail from Actions | `/app/runs/:runId` | Same run detail view. The action detail `Open run` button uses this path. |\n\nActivity supports query filters such as `environment`, `range`, `focusType`,\n`focusValue`, run status/search/sort/pagination filters, and task filters.\nWhen linking, include only the filters needed to land the user in the right\ncontext.\n\nRun detail links back to release, release workflow, environment, and release\ndeployment surfaces. When a run started from a managed trigger and the trigger\nlabel is known, `Started by` links to the release Triggers section. Use the run\ndetail page for runtime event timelines, execution graph inspection, step-level\ndetails, and run artifacts.\n\n## Settings\n\nSettings is the owner for workspace and instance configuration. The canonical\ngeneral route is `/app/settings?section=workspace`.\n\n### Canonical surface ownership\n\nRoute a user decision to exactly one product surface. A second page is valid\nonly when it serves a different user, answers a different operational question,\nand has a distinct data contract. Similar data, a different permission, or an\noperator-oriented label is not enough. Extend the canonical surface or delete\nthe duplicate; do not preserve overlapping pages, reports, or navigation as a\ncompromise.\n\n| Group | Section | Route | What it owns |\n| --- | --- | --- | --- |\n| Workspace | General | `/app/settings?section=workspace` | Workspace/org display settings. |\n| Workspace | Billing | `/app/settings?section=billing` | Hosted subscription status, member-seat usage, Checkout, and billing portal. Owner gated and absent outside hosted billing compositions. |\n| Workspace | AI usage | `/app/settings?section=ai-usage` | Organization Chat and workflow-agent request/token consumption over a visible selectable time range, with surface totals, trend, and Kora catalog model breakdown. It does not show money or purchase controls. |\n| Workspace | Members & access | `/app/settings?section=members` | Human members, invites, role changes, invite links, and removals. |\n| Workspace | API keys | `/app/settings?section=api-keys` | Organization-scoped API credentials. New tokens are shown only once. |\n| Workspace | Extensions | `/app/settings?section=extensions` | Installed extension packages, setup, management, permissions, schedules, and package install flows. |\n| Workspace | Environment variables | `/app/settings?section=environment-variables` | Runtime variable inventory, create/edit/delete, and environment filters. |\n| Workspace | Secrets | `/app/settings?section=secrets` | Org and environment-scoped secret storage, create/edit/delete, and environment filters. |\n| Workspace | Models | `/app/settings?section=models` | Organization model access, optional compatible endpoints, and Chat/workflow defaults. API keys are write-only; compact badges identify defaults; removal is blocked when a live deployment depends on the model. |\n| Workspace | Artifacts | `/app/settings?section=artifacts` | Runtime artifact inventory, upload, preview/detail, download, archive, restore, and purge. Owner/admin gated. |\n| Workspace | Audit | `/app/settings?section=audit` | Audit/event review, filtering, pagination, and event detail. Owner/admin gated. |\n| Instance | Utilization | `/app/settings?section=utilization` | Platform users, activity, sessions, active chat turns, runs in progress, and upgrade readiness. Platform-admin gated. |\n| Instance | Plan | `/app/settings?section=license` | Plan/license status and account management link. Platform-admin gated. |\n| Danger zone | Reset | `/app/settings?section=danger` | Owner-only `Reset organization workspace`. Clears release history, source storage, environment-scoped configuration, and workspaces. |\n| Account | Profile | `/app/profile` | User account profile. Not an embedded Settings section. |\n\nSettings actions:\n\n- Members & access: `Invite`, role changes for non-owner members, `Remove`,\n  `Copy link` for created invites, and `Cancel` for pending invites.\n- API keys: `Create key`, `Copy`, and `Revoke`.\n- Extensions: `Add extension`, `Refresh`, setup, manage, enable/disable,\n  delete install, save permissions, run declared settings buttons, and open\n  external action windows.\n- Environment variables: `Add variable`, edit, delete, search/filter, and\n  environment selection in create/edit dialogs.\n- Secrets: `Add secret`, edit, delete, search/filter, and environment selection\n  in create/edit dialogs.\n- Models: `Add model`, set/edit/clear the Chat or workflow default, edit model\n  access, and remove model. The first model becomes both defaults when neither\n  has been chosen.\n- Artifacts: upload, refresh, preview/detail, download, archive, restore,\n  purge, and pagination.\n- Audit: filtering by category/source/action/resource and selecting an event\n  for detail.\n\nDo not confuse access members with release-modeled people. Access members live\nin Settings -> `Members & access`; modeled people live inside a release detail.\n\n## Extension Setup Links\n\nFor any extension install, setup, connection, permission, schedule, or\nmanagement issue, use this exact Markdown link:\n\n```md\n[install and configure the extension](/app/settings?section=extensions)\n```\n\n## Artifact Surfaces\n\nUse Platform UI routes for managed runtime artifacts:\n\n- Run artifacts: `/app/activity/runs/:runId`, in the run detail artifact\n  and step/detail surfaces.\n- Task input artifacts: `/app/tasks/:taskId`, in the action detail input\n  section.\n- Organization artifact inventory: `/app/settings?section=artifacts`.\n\nStart-workflow dialogs can upload supported `x-kora-type: file` inputs before\nstarting a run. Runtime artifact references in task input data render as\nartifact cards. Link to the appropriate UI surface, not to raw object storage.\n"
}