@qontinui/shared-types 0.2.4 → 0.2.5

package/src/task-run/_api.ts

@@ -1,108 +1,108 @@
-/**
- * Task Run Types
- *
- * Merged type definitions from both runner (taskRun.ts) and web (task-runs.ts).
- * Runner types are used for local execution, web types for backend API communication.
- *
- * Types generated from Rust (source of truth: qontinui-schemas/rust/src/task_run.rs).
- * Do not edit by hand — regenerate via `just generate-types` (or
- * `qontinui-runner/src-tauri/scripts/generate_types.sh`).
- */
-
-// =============================================================================
-// Status Types
-// =============================================================================
-
-export type { TaskRunStatus } from "../generated/TaskRunStatus";
-export type { TaskType } from "../generated/TaskType";
-
-// =============================================================================
-// Runner Task Run (local execution)
-// =============================================================================
-
-export type { TaskRun } from "../generated/TaskRun";
-
-// =============================================================================
-// Web Backend Task Run (API responses)
-// =============================================================================
-
-export type { TaskRunBackend } from "../generated/TaskRunBackend";
-
-// =============================================================================
-// Session Types
-// =============================================================================
-
-export type { TaskRunSession } from "../generated/TaskRunSession";
-
-// =============================================================================
-// Finding Types
-// =============================================================================
-
-export type { TaskRunFindingCategory } from "../generated/TaskRunFindingCategory";
-export type { TaskRunFindingSeverity } from "../generated/TaskRunFindingSeverity";
-export type { TaskRunFindingStatus } from "../generated/TaskRunFindingStatus";
-export type { TaskRunFindingActionType } from "../generated/TaskRunFindingActionType";
-export type { TaskRunFinding } from "../generated/TaskRunFinding";
-
-// Local alias: `TaskRunFindingResponse` is a TS-only convenience synonym for
-// `TaskRunFinding` (the Rust side uses `TaskRunFinding` directly).
-import type { TaskRunFinding as _TaskRunFinding } from "../generated/TaskRunFinding";
-export type TaskRunFindingResponse = _TaskRunFinding;
-
-// =============================================================================
-// Detail Types
-// =============================================================================
-
-export type { TaskRunFindingSummary } from "../generated/TaskRunFindingSummary";
-export type { TaskRunBackendDetail } from "../generated/TaskRunBackendDetail";
-
-// =============================================================================
-// Request/Update Types
-// =============================================================================
-
-export type { TaskRunCreate } from "../generated/TaskRunCreate";
-export type { TaskRunUpdate } from "../generated/TaskRunUpdate";
-export type { TaskRunFindingCreate } from "../generated/TaskRunFindingCreate";
-export type { TaskRunFindingUpdate } from "../generated/TaskRunFindingUpdate";
-
-// =============================================================================
-// Runner-Specific Request Types
-// =============================================================================
-
-// `RunPromptResponse.data` was an inline object in the old hand-authored TS;
-// the Rust side lifted it to a named `RunPromptResponseData` struct, so we
-// re-export both.
-export type { RunPromptResponseData } from "../generated/RunPromptResponseData";
-export type { RunPromptResponse } from "../generated/RunPromptResponse";
-export type { RunPromptRequest } from "../generated/RunPromptRequest";
-export type { CreateTaskRunRequest } from "../generated/CreateTaskRunRequest";
-
-// =============================================================================
-// Filter Types
-// =============================================================================
-
-export type { TaskRunFilters } from "../generated/TaskRunFilters";
-export type { TaskRunFindingFilters } from "../generated/TaskRunFindingFilters";
-
-// =============================================================================
-// Response Types
-// =============================================================================
-
-export type { Pagination } from "../generated/Pagination";
-export type { TaskRunListResponse } from "../generated/TaskRunListResponse";
-export type { TaskRunFindingsListResponse } from "../generated/TaskRunFindingsListResponse";
-export type { FindingsSummary } from "../generated/FindingsSummary";
-
-// =============================================================================
-// Verification Result Types
-// =============================================================================
-
-export type { CheckIssueDetail } from "../generated/CheckIssueDetail";
-export type { IndividualCheckResult } from "../generated/IndividualCheckResult";
-export type { VerificationStepDetails } from "../generated/VerificationStepDetails";
-export type { StepExecutionConfig } from "../generated/StepExecutionConfig";
-export type { VerificationStepResult } from "../generated/VerificationStepResult";
-export type { GateEvaluationResult } from "../generated/GateEvaluationResult";
-export type { VerificationPhaseResult } from "../generated/VerificationPhaseResult";
-export type { VerificationResultResponse } from "../generated/VerificationResultResponse";
-export type { VerificationResultsListResponse } from "../generated/VerificationResultsListResponse";
+/**
+ * Task Run Types
+ *
+ * Merged type definitions from both runner (taskRun.ts) and web (task-runs.ts).
+ * Runner types are used for local execution, web types for backend API communication.
+ *
+ * Types generated from Rust (source of truth: qontinui-schemas/rust/src/task_run.rs).
+ * Do not edit by hand — regenerate via `just generate-types` (or
+ * `qontinui-runner/src-tauri/scripts/generate_types.sh`).
+ */
+
+// =============================================================================
+// Status Types
+// =============================================================================
+
+export type { TaskRunStatus } from "../generated/TaskRunStatus";
+export type { TaskType } from "../generated/TaskType";
+
+// =============================================================================
+// Runner Task Run (local execution)
+// =============================================================================
+
+export type { TaskRun } from "../generated/TaskRun";
+
+// =============================================================================
+// Web Backend Task Run (API responses)
+// =============================================================================
+
+export type { TaskRunBackend } from "../generated/TaskRunBackend";
+
+// =============================================================================
+// Session Types
+// =============================================================================
+
+export type { TaskRunSession } from "../generated/TaskRunSession";
+
+// =============================================================================
+// Finding Types
+// =============================================================================
+
+export type { TaskRunFindingCategory } from "../generated/TaskRunFindingCategory";
+export type { TaskRunFindingSeverity } from "../generated/TaskRunFindingSeverity";
+export type { TaskRunFindingStatus } from "../generated/TaskRunFindingStatus";
+export type { TaskRunFindingActionType } from "../generated/TaskRunFindingActionType";
+export type { TaskRunFinding } from "../generated/TaskRunFinding";
+
+// Local alias: `TaskRunFindingResponse` is a TS-only convenience synonym for
+// `TaskRunFinding` (the Rust side uses `TaskRunFinding` directly).
+import type { TaskRunFinding as _TaskRunFinding } from "../generated/TaskRunFinding";
+export type TaskRunFindingResponse = _TaskRunFinding;
+
+// =============================================================================
+// Detail Types
+// =============================================================================
+
+export type { TaskRunFindingSummary } from "../generated/TaskRunFindingSummary";
+export type { TaskRunBackendDetail } from "../generated/TaskRunBackendDetail";
+
+// =============================================================================
+// Request/Update Types
+// =============================================================================
+
+export type { TaskRunCreate } from "../generated/TaskRunCreate";
+export type { TaskRunUpdate } from "../generated/TaskRunUpdate";
+export type { TaskRunFindingCreate } from "../generated/TaskRunFindingCreate";
+export type { TaskRunFindingUpdate } from "../generated/TaskRunFindingUpdate";
+
+// =============================================================================
+// Runner-Specific Request Types
+// =============================================================================
+
+// `RunPromptResponse.data` was an inline object in the old hand-authored TS;
+// the Rust side lifted it to a named `RunPromptResponseData` struct, so we
+// re-export both.
+export type { RunPromptResponseData } from "../generated/RunPromptResponseData";
+export type { RunPromptResponse } from "../generated/RunPromptResponse";
+export type { RunPromptRequest } from "../generated/RunPromptRequest";
+export type { CreateTaskRunRequest } from "../generated/CreateTaskRunRequest";
+
+// =============================================================================
+// Filter Types
+// =============================================================================
+
+export type { TaskRunFilters } from "../generated/TaskRunFilters";
+export type { TaskRunFindingFilters } from "../generated/TaskRunFindingFilters";
+
+// =============================================================================
+// Response Types
+// =============================================================================
+
+export type { Pagination } from "../generated/Pagination";
+export type { TaskRunListResponse } from "../generated/TaskRunListResponse";
+export type { TaskRunFindingsListResponse } from "../generated/TaskRunFindingsListResponse";
+export type { FindingsSummary } from "../generated/FindingsSummary";
+
+// =============================================================================
+// Verification Result Types
+// =============================================================================
+
+export type { CheckIssueDetail } from "../generated/CheckIssueDetail";
+export type { IndividualCheckResult } from "../generated/IndividualCheckResult";
+export type { VerificationStepDetails } from "../generated/VerificationStepDetails";
+export type { StepExecutionConfig } from "../generated/StepExecutionConfig";
+export type { VerificationStepResult } from "../generated/VerificationStepResult";
+export type { GateEvaluationResult } from "../generated/GateEvaluationResult";
+export type { VerificationPhaseResult } from "../generated/VerificationPhaseResult";
+export type { VerificationResultResponse } from "../generated/VerificationResultResponse";
+export type { VerificationResultsListResponse } from "../generated/VerificationResultsListResponse";

package/src/task-run/index.ts

@@ -1 +1 @@
-export * from "./_api";
+export * from "./_api";

package/src/tauri-events/_api.ts

@@ -1,90 +1,90 @@
-/**
- * Tauri Event Payload Types
- *
- * Wire-format types for payloads emitted on Tauri event channels by the
- * runner. Use these to type the generic parameter of `listen<T>(...)` so
- * future Rust serde renames (e.g. snake_case → camelCase) and shape
- * changes break the TypeScript build instead of silently dropping events
- * at the listener guard.
- *
- * ## Adjacently-tagged envelope (`AppEvent`)
- *
- * Most runner events are variants of the `AppEvent` enum, which is
- * serialized via `#[serde(tag = "event_type", content = "data")]`. The
- * wire payload is therefore `{ event_type: "<VariantName>", data: { ... } }`
- * and consumers MUST read `event.payload.data.<field>` (NOT
- * `event.payload.<field>`). The `AppEvent` discriminated union below
- * encodes that envelope; reaching `data.<field>` after narrowing by
- * `event_type` is type-safe.
- *
- * ## Direct-payload events
- *
- * A handful of events bypass `AppEvent` and emit a payload struct
- * directly:
- *  - `terminal-output` → `TerminalOutputEvent`
- *  - `terminal-exit` → `TerminalExitEvent`
- *  - `terminal-created` → `TerminalInfo`
- *  - `finding_detected` / `finding_resolved` → wrap a `RunnerFinding`
- *    inside the `AppEvent` envelope's `data.finding` field as untyped
- *    JSON; consumers should cast `data.finding as RunnerFinding`.
- *
- * Source of truth:
- *  - `AppEvent`: `qontinui-runner/src-tauri/src/event_system/types.rs`
- *  - Terminal events: `qontinui-schemas/rust/src/terminal.rs`
- *  - `RunnerFinding`: `qontinui-runner/src-tauri/src/tauri_event_payloads.rs`
- *
- * Regenerate via `cd qontinui-runner && npm run gen-events`.
- */
-
-export type { AppEvent } from "../generated/AppEvent";
-
-// ── Terminal events (direct payloads, not wrapped in AppEvent) ──
-export type { TerminalInfo } from "../generated/TerminalInfo";
-export type { TerminalOutputEvent } from "../generated/TerminalOutputEvent";
-export type { TerminalExitEvent } from "../generated/TerminalExitEvent";
-
-// ── Runner-local finding payload (carried inside AppEvent::FindingDetected /
-//    AppEvent::FindingResolved as `data.finding`). Distinct from
-//    `qontinui_types::verification::Finding`. ──
-export type { RunnerFinding } from "../generated/RunnerFinding";
-export type { RunnerFindingCodeContext } from "../generated/RunnerFindingCodeContext";
-export type { RunnerFindingUserInput } from "../generated/RunnerFindingUserInput";
-
-// ── WS relay envelopes (runner→backend) and backend→client status events.
-//    Discriminated unions tagged on `type`. Source of truth lives in
-//    `qontinui-runner/src-tauri/src/relay_envelopes.rs`; backend-originated
-//    events mirror `qontinui-web/backend/app/services/runner/event_publisher.py`. ──
-export type { RunnerRelayMessage } from "../generated/RunnerRelayMessage";
-export type { RunnerStatusEvent } from "../generated/RunnerStatusEvent";
-export type { RunnerConnectedConnection } from "../generated/RunnerConnectedConnection";
-
-// ── Dev-only seed-finding payload (`dev:seed-finding` Tauri event from
-//    `commands/dev_findings.rs`). Sibling to the camelCase RunnerFinding
-//    fields so the TS listener can spread them straight into a Finding. ──
-export type { DevSeedFindingPayload } from "../generated/DevSeedFindingPayload";
-
-// ── Recommendation review decision payloads (`review-approved` /
-//    `review-rejected` from `commands/productivity.rs`). One struct
-//    covers both channels — only `userDecision` differs. ──
-export type { RecommendationReviewDecisionPayload } from "../generated/RecommendationReviewDecisionPayload";
-
-// ── Canvas panel payload carried inside AppEvent::CanvasUpdate's
-//    `data.panel` field. Wire-format mirror of the runner's `StoredPanel`
-//    (`mcp/canvas.rs`). The hand-written `CanvasPanel` in `../canvas/index.ts`
-//    pre-dates this generated re-export; both shapes are intentionally
-//    identical. New consumers should prefer this generated import. ──
-export type { CanvasPanel as CanvasUpdatePanel } from "../generated/CanvasPanel";
-
-// ── UI Bridge IPC envelope payloads carried on the `ui-bridge-request` and
-//    `ui-bridge-response` Tauri channels. Stage 1 of the ui-bridge-request
-//    envelope concretization (deferral note in commit ea5d9a61f). The Rust
-//    sources live in `qontinui-schemas/rust/src/app_events.rs`; the runner's
-//    React handler in `src/hooks/ui-bridge-events/types.ts` should pick the
-//    `requestId | type` fields off these to keep the envelope head in sync
-//    while leaving its rich set of optional payload fields hand-written.
-//    Stage 2 (per-payload tagged union of all 171 request_types) is deferred
-//    indefinitely — the existing AssertEqual<AllHandledTypes,
-//    UIBridgeRequestType> + per-hook never checks already enforce dispatch
-//    exhaustiveness from the right end of the pipeline. ──
-export type { UiBridgeRequestEnvelope } from "../generated/UiBridgeRequestEnvelope";
-export type { UiBridgeResponseEnvelope } from "../generated/UiBridgeResponseEnvelope";
+/**
+ * Tauri Event Payload Types
+ *
+ * Wire-format types for payloads emitted on Tauri event channels by the
+ * runner. Use these to type the generic parameter of `listen<T>(...)` so
+ * future Rust serde renames (e.g. snake_case → camelCase) and shape
+ * changes break the TypeScript build instead of silently dropping events
+ * at the listener guard.
+ *
+ * ## Adjacently-tagged envelope (`AppEvent`)
+ *
+ * Most runner events are variants of the `AppEvent` enum, which is
+ * serialized via `#[serde(tag = "event_type", content = "data")]`. The
+ * wire payload is therefore `{ event_type: "<VariantName>", data: { ... } }`
+ * and consumers MUST read `event.payload.data.<field>` (NOT
+ * `event.payload.<field>`). The `AppEvent` discriminated union below
+ * encodes that envelope; reaching `data.<field>` after narrowing by
+ * `event_type` is type-safe.
+ *
+ * ## Direct-payload events
+ *
+ * A handful of events bypass `AppEvent` and emit a payload struct
+ * directly:
+ *  - `terminal-output` → `TerminalOutputEvent`
+ *  - `terminal-exit` → `TerminalExitEvent`
+ *  - `terminal-created` → `TerminalInfo`
+ *  - `finding_detected` / `finding_resolved` → wrap a `RunnerFinding`
+ *    inside the `AppEvent` envelope's `data.finding` field as untyped
+ *    JSON; consumers should cast `data.finding as RunnerFinding`.
+ *
+ * Source of truth:
+ *  - `AppEvent`: `qontinui-runner/src-tauri/src/event_system/types.rs`
+ *  - Terminal events: `qontinui-schemas/rust/src/terminal.rs`
+ *  - `RunnerFinding`: `qontinui-runner/src-tauri/src/tauri_event_payloads.rs`
+ *
+ * Regenerate via `cd qontinui-runner && npm run gen-events`.
+ */
+
+export type { AppEvent } from "../generated/AppEvent";
+
+// ── Terminal events (direct payloads, not wrapped in AppEvent) ──
+export type { TerminalInfo } from "../generated/TerminalInfo";
+export type { TerminalOutputEvent } from "../generated/TerminalOutputEvent";
+export type { TerminalExitEvent } from "../generated/TerminalExitEvent";
+
+// ── Runner-local finding payload (carried inside AppEvent::FindingDetected /
+//    AppEvent::FindingResolved as `data.finding`). Distinct from
+//    `qontinui_types::verification::Finding`. ──
+export type { RunnerFinding } from "../generated/RunnerFinding";
+export type { RunnerFindingCodeContext } from "../generated/RunnerFindingCodeContext";
+export type { RunnerFindingUserInput } from "../generated/RunnerFindingUserInput";
+
+// ── WS relay envelopes (runner→backend) and backend→client status events.
+//    Discriminated unions tagged on `type`. Source of truth lives in
+//    `qontinui-runner/src-tauri/src/relay_envelopes.rs`; backend-originated
+//    events mirror `qontinui-web/backend/app/services/runner/event_publisher.py`. ──
+export type { RunnerRelayMessage } from "../generated/RunnerRelayMessage";
+export type { RunnerStatusEvent } from "../generated/RunnerStatusEvent";
+export type { RunnerConnectedConnection } from "../generated/RunnerConnectedConnection";
+
+// ── Dev-only seed-finding payload (`dev:seed-finding` Tauri event from
+//    `commands/dev_findings.rs`). Sibling to the camelCase RunnerFinding
+//    fields so the TS listener can spread them straight into a Finding. ──
+export type { DevSeedFindingPayload } from "../generated/DevSeedFindingPayload";
+
+// ── Recommendation review decision payloads (`review-approved` /
+//    `review-rejected` from `commands/productivity.rs`). One struct
+//    covers both channels — only `userDecision` differs. ──
+export type { RecommendationReviewDecisionPayload } from "../generated/RecommendationReviewDecisionPayload";
+
+// ── Canvas panel payload carried inside AppEvent::CanvasUpdate's
+//    `data.panel` field. Wire-format mirror of the runner's `StoredPanel`
+//    (`mcp/canvas.rs`). The hand-written `CanvasPanel` in `../canvas/index.ts`
+//    pre-dates this generated re-export; both shapes are intentionally
+//    identical. New consumers should prefer this generated import. ──
+export type { CanvasPanel as CanvasUpdatePanel } from "../generated/CanvasPanel";
+
+// ── UI Bridge IPC envelope payloads carried on the `ui-bridge-request` and
+//    `ui-bridge-response` Tauri channels. Stage 1 of the ui-bridge-request
+//    envelope concretization (deferral note in commit ea5d9a61f). The Rust
+//    sources live in `qontinui-schemas/rust/src/app_events.rs`; the runner's
+//    React handler in `src/hooks/ui-bridge-events/types.ts` should pick the
+//    `requestId | type` fields off these to keep the envelope head in sync
+//    while leaving its rich set of optional payload fields hand-written.
+//    Stage 2 (per-payload tagged union of all 171 request_types) is deferred
+//    indefinitely — the existing AssertEqual<AllHandledTypes,
+//    UIBridgeRequestType> + per-hook never checks already enforce dispatch
+//    exhaustiveness from the right end of the pipeline. ──
+export type { UiBridgeRequestEnvelope } from "../generated/UiBridgeRequestEnvelope";
+export type { UiBridgeResponseEnvelope } from "../generated/UiBridgeResponseEnvelope";

package/src/tauri-events/index.ts

@@ -1 +1 @@
-export * from "./_api";
+export * from "./_api";

package/src/tree-events/_api.ts

@@ -1,42 +1,42 @@
-/**
- * Tree Event Types
- *
- * Execution logging events emitted by qontinui during automation runs.
- * Source of truth: `qontinui-schemas/rust/src/tree_events.rs`.
- *
- * Used by:
- * - qontinui (Python library) — emits events during execution
- * - qontinui-runner (Tauri app) — receives and displays events
- * - qontinui-web (backend + frontend) — stores, forwards, and displays events
- *
- * Schema shape: workflows contain actions; actions can nest (`GO_TO_STATE`,
- * `RUN_WORKFLOW`); each event captures a node state change with rich
- * metadata.
- */
-
-// Enums
-export type { NodeType } from "../generated/NodeType";
-export type { NodeStatus } from "../generated/NodeStatus";
-export type { TreeEventType } from "../generated/TreeEventType";
-export type { ActionType } from "../generated/ActionType";
-
-// Nested metadata
-export type { MatchLocation } from "../generated/MatchLocation";
-export type { TopMatch } from "../generated/TopMatch";
-export type { RuntimeData } from "../generated/RuntimeData";
-export type { StateContext } from "../generated/StateContext";
-export type { TimingInfo } from "../generated/TimingInfo";
-export type { Outcome } from "../generated/Outcome";
-
-// Main models
-export type { NodeMetadata } from "../generated/NodeMetadata";
-export type { TreeNode } from "../generated/TreeNode";
-export type { PathElement } from "../generated/PathElement";
-export type { TreeEvent } from "../generated/TreeEvent";
-
-// Display + API response
-export type { DisplayNode } from "../generated/DisplayNode";
-export type { TreeEventCreate } from "../generated/TreeEventCreate";
-export type { TreeEventResponse } from "../generated/TreeEventResponse";
-export type { TreeEventListResponse } from "../generated/TreeEventListResponse";
-export type { ExecutionTreeResponse } from "../generated/ExecutionTreeResponse";
+/**
+ * Tree Event Types
+ *
+ * Execution logging events emitted by qontinui during automation runs.
+ * Source of truth: `qontinui-schemas/rust/src/tree_events.rs`.
+ *
+ * Used by:
+ * - qontinui (Python library) — emits events during execution
+ * - qontinui-runner (Tauri app) — receives and displays events
+ * - qontinui-web (backend + frontend) — stores, forwards, and displays events
+ *
+ * Schema shape: workflows contain actions; actions can nest (`GO_TO_STATE`,
+ * `RUN_WORKFLOW`); each event captures a node state change with rich
+ * metadata.
+ */
+
+// Enums
+export type { NodeType } from "../generated/NodeType";
+export type { NodeStatus } from "../generated/NodeStatus";
+export type { TreeEventType } from "../generated/TreeEventType";
+export type { ActionType } from "../generated/ActionType";
+
+// Nested metadata
+export type { MatchLocation } from "../generated/MatchLocation";
+export type { TopMatch } from "../generated/TopMatch";
+export type { RuntimeData } from "../generated/RuntimeData";
+export type { StateContext } from "../generated/StateContext";
+export type { TimingInfo } from "../generated/TimingInfo";
+export type { Outcome } from "../generated/Outcome";
+
+// Main models
+export type { NodeMetadata } from "../generated/NodeMetadata";
+export type { TreeNode } from "../generated/TreeNode";
+export type { PathElement } from "../generated/PathElement";
+export type { TreeEvent } from "../generated/TreeEvent";
+
+// Display + API response
+export type { DisplayNode } from "../generated/DisplayNode";
+export type { TreeEventCreate } from "../generated/TreeEventCreate";
+export type { TreeEventResponse } from "../generated/TreeEventResponse";
+export type { TreeEventListResponse } from "../generated/TreeEventListResponse";
+export type { ExecutionTreeResponse } from "../generated/ExecutionTreeResponse";

package/src/tree-events/index.ts

@@ -1 +1 @@
-export * from "./_api";
+export * from "./_api";