Updates API client to align with changes in the ros2_medkit gateway

[bburda]

Pull Request

Summary

This pull request updates the sovd_web_ui API client to align with changes in the ros2_medkit gateway, implementing SOVD-compliant API contracts. The changes migrate from the old operations API to a new executions model, and add support for new entity types (Apps, Functions, and Faults).

Changes:

• Migrated operations API from direct invocation to SOVD-compliant executions model (POST /{entity}/operations/{op}/executions)
• Added support for Apps (ROS 2 nodes), Functions (capability groupings), and Faults (diagnostic trouble codes) as new entity types
• Updated type definitions to include Execution, App, Function, Fault, and related interfaces
• Added virtual folders for faults and apps in the entity tree
• Created FaultsPanel component for displaying and clearing faults
• Updated UI components to handle execution status instead of goal status

---

Issue

Link the related issue (required):

• closes Update API client for ros2_medkit changes #13

---

Type

• Bug fix
• New feature
• Breaking change
• Documentation only

---

Testing

How was this tested / how should reviewers verify it?

---

Checklist

• Breaking changes are clearly described (and announced in docs / changelog if needed)
• Linting passes (npm run lint)
• Build succeeds (npm run build)
• Docs were updated if behavior or public API changed

[bburda]

I plan to do further improvements in #14

[Copilot]

Pull request overview

This pull request updates the sovd_web_ui API client to align with changes in the ros2_medkit gateway, implementing SOVD-compliant API contracts. The changes migrate from the old operations API to a new executions model, and add support for new entity types (Apps, Functions, and Faults).

Changes:

• Migrated operations API from direct invocation to SOVD-compliant executions model (POST /{entity}/operations/{op}/executions)
• Added support for Apps (ROS 2 nodes), Functions (capability groupings), and Faults (diagnostic trouble codes) as new entity types
• Updated type definitions to include Execution, App, Function, Fault, and related interfaces
• Added virtual folders for faults and apps in the entity tree
• Created FaultsPanel component for displaying and clearing faults
• Updated UI components to handle execution status instead of goal status

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
src/lib/types.ts	Added Execution, App, Function, Fault types and related interfaces; updated VirtualFolderData to support new entity types
src/lib/sovd-api.ts	Migrated to executions API; added Apps, Functions, and Faults API methods; added server capabilities and SSE fault stream support
src/lib/store.ts	Replaced activeGoals with activeExecutions; added faults state management; updated entity tree to include faults and apps virtual folders
src/components/OperationsPanel.tsx	Updated to use createExecution instead of invokeOperation; changed execution tracking from goal IDs to execution IDs
src/components/OperationResponse.tsx	Simplified to display execution status and ID (removed detailed result/error display)
src/components/ActionStatusPanel.tsx	Updated to track executions instead of goals; renamed from goal_id to executionId throughout
src/components/FaultsPanel.tsx	New component for displaying and managing faults for components and apps
src/components/EntityTreeNode.tsx	Added icons for fault, app, and apps folder node types
src/components/EntityDetailPanel.tsx	Added FaultsPanel integration for fault virtual folders
src/components/ConfigurationPanel.tsx	Added entityType prop (currently unused)

Comments suppressed due to low confidence (1)

src/components/OperationResponse.tsx:59

• The OperationResponseDisplay component no longer displays the result or error fields from the CreateExecutionResponse. For service calls, result may contain important response data, and for failed executions, the error field should be displayed. The original implementation showed these fields, but they were removed in the refactoring. These fields should be conditionally displayed when present.

export function OperationResponseDisplay({ response }: OperationResponseProps) {
    const isSuccess = response.status === 'succeeded';
    const statusConfig = getStatusConfig(response.status);
    const StatusIcon = statusConfig.icon;

    return (
        <div
            className={`rounded-lg border ${isSuccess ? 'border-green-500/30 bg-green-500/5' : 'border-muted bg-muted/5'}`}
        >
            {/* Header */}
            <div className="flex items-center gap-3 px-3 py-2 border-b border-inherit">
                <StatusIcon
                    className={`w-4 h-4 ${statusConfig.color} ${response.status === 'running' ? 'animate-spin' : ''}`}
                />
                <div className="flex items-center gap-2 flex-1">
                    <Badge variant={statusConfig.variant}>{response.status}</Badge>
                </div>
            </div>

            {/* Body */}
            <div className="p-3 space-y-2 text-sm">
                {/* Execution ID */}
                <div className="flex items-center gap-2">
                    <Hash className="w-3.5 h-3.5 text-muted-foreground" />
                    <span className="text-muted-foreground text-xs">Execution ID:</span>
                    <code className="bg-muted px-1.5 py-0.5 rounded text-xs font-mono">{response.id}</code>
                </div>
            </div>
        </div>
    );
}