Implements Phases 1-8 of the TFTSR implementation plan. Rust backend (Tauri 2.x, src-tauri/): - Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama - PII detection engine: 11 regex patterns with overlap resolution - SQLCipher AES-256 encrypted database with 10 versioned migrations - 28 Tauri IPC commands for triage, analysis, document, and system ops - Ollama: hardware probe, model recommendations, pull/delete with events - RCA and blameless post-mortem Markdown document generators - PDF export via printpdf - Audit log: SHA-256 hash of every external data send - Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2) Frontend (React 18 + TypeScript + Vite, src/): - 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings - 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives - 3 Zustand stores: session, settings (persisted), history - Type-safe tauriCommands.ts matching Rust backend types exactly - 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs) DevOps: - .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push - .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload Verified: - cargo check: zero errors - tsc --noEmit: zero errors - vitest run: 13/13 unit tests passing Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
88 lines
2.9 KiB
TypeScript
88 lines
2.9 KiB
TypeScript
import { HotPayload } from '../../types/hmrPayload.js';
|
|
|
|
interface FetchFunctionOptions {
|
|
cached?: boolean;
|
|
startOffset?: number;
|
|
}
|
|
type FetchResult = CachedFetchResult | ExternalFetchResult | ViteFetchResult;
|
|
interface CachedFetchResult {
|
|
/**
|
|
* If module cached in the runner, we can just confirm
|
|
* it wasn't invalidated on the server side.
|
|
*/
|
|
cache: true;
|
|
}
|
|
interface ExternalFetchResult {
|
|
/**
|
|
* The path to the externalized module starting with file://,
|
|
* by default this will be imported via a dynamic "import"
|
|
* instead of being transformed by vite and loaded with vite runner
|
|
*/
|
|
externalize: string;
|
|
/**
|
|
* Type of the module. Will be used to determine if import statement is correct.
|
|
* For example, if Vite needs to throw an error if variable is not actually exported
|
|
*/
|
|
type: 'module' | 'commonjs' | 'builtin' | 'network';
|
|
}
|
|
interface ViteFetchResult {
|
|
/**
|
|
* Code that will be evaluated by vite runner
|
|
* by default this will be wrapped in an async function
|
|
*/
|
|
code: string;
|
|
/**
|
|
* File path of the module on disk.
|
|
* This will be resolved as import.meta.url/filename
|
|
* Will be equal to `null` for virtual modules
|
|
*/
|
|
file: string | null;
|
|
/**
|
|
* Module ID in the server module graph.
|
|
*/
|
|
id: string;
|
|
/**
|
|
* Module URL used in the import.
|
|
*/
|
|
url: string;
|
|
/**
|
|
* Invalidate module on the client side.
|
|
*/
|
|
invalidate: boolean;
|
|
}
|
|
type InvokeMethods = {
|
|
fetchModule: (id: string, importer?: string, options?: FetchFunctionOptions) => Promise<FetchResult>;
|
|
};
|
|
|
|
type ModuleRunnerTransportHandlers = {
|
|
onMessage: (data: HotPayload) => void;
|
|
onDisconnection: () => void;
|
|
};
|
|
/**
|
|
* "send and connect" or "invoke" must be implemented
|
|
*/
|
|
interface ModuleRunnerTransport {
|
|
connect?(handlers: ModuleRunnerTransportHandlers): Promise<void> | void;
|
|
disconnect?(): Promise<void> | void;
|
|
send?(data: HotPayload): Promise<void> | void;
|
|
invoke?(data: HotPayload): Promise<{
|
|
result: any;
|
|
} | {
|
|
error: any;
|
|
}>;
|
|
timeout?: number;
|
|
}
|
|
interface NormalizedModuleRunnerTransport {
|
|
connect?(onMessage?: (data: HotPayload) => void): Promise<void> | void;
|
|
disconnect?(): Promise<void> | void;
|
|
send(data: HotPayload): Promise<void>;
|
|
invoke<T extends keyof InvokeMethods>(name: T, data: Parameters<InvokeMethods[T]>): Promise<ReturnType<Awaited<InvokeMethods[T]>>>;
|
|
}
|
|
declare const createWebSocketModuleRunnerTransport: (options: {
|
|
createConnection: () => WebSocket;
|
|
pingInterval?: number;
|
|
}) => Required<Pick<ModuleRunnerTransport, "connect" | "disconnect" | "send">>;
|
|
|
|
export { createWebSocketModuleRunnerTransport as c };
|
|
export type { ExternalFetchResult as E, FetchFunctionOptions as F, ModuleRunnerTransport as M, NormalizedModuleRunnerTransport as N, ViteFetchResult as V, FetchResult as a, ModuleRunnerTransportHandlers as b };
|