8839075805
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>
57 lines
2.3 KiB
TypeScript
57 lines
2.3 KiB
TypeScript
export default interface MjsonwpCommands {
|
|
/**
|
|
* Mjsonwp Protocol Command
|
|
*
|
|
* No description available, please see reference link.
|
|
* @ref https://github.com/appium/appium-base-driver/blob/master/docs/mjsonwp/protocol-methods.md#mobile-json-wire-protocol-endpoints
|
|
* @deprecated In Appium 2.0, this method is marked as deprecated and currently has no available alternatives.
|
|
*
|
|
*/
|
|
getPageIndex(): Promise<string>;
|
|
/**
|
|
* Mjsonwp Protocol Command
|
|
*
|
|
* No description available, please see reference link.
|
|
* @ref https://github.com/SeleniumHQ/mobile-spec/blob/master/spec-draft.md#device-modes
|
|
* @deprecated For Appium Android automation, use `driver.execute('mobile: getConnectivity', { ... })` instead
|
|
*
|
|
*/
|
|
getNetworkConnection(): Promise<number>;
|
|
/**
|
|
* Mjsonwp Protocol Command
|
|
*
|
|
* No description available, please see reference link.
|
|
* @ref https://github.com/SeleniumHQ/mobile-spec/blob/master/spec-draft.md#device-modes
|
|
* @deprecated For Appium Android automation, use `driver.execute('mobile: setConnectivity', { ... })` instead
|
|
*
|
|
*/
|
|
setNetworkConnection(type: number): Promise<void>;
|
|
/**
|
|
* Mjsonwp Protocol Command
|
|
*
|
|
* No description available, please see reference link.
|
|
* @ref https://github.com/SeleniumHQ/mobile-spec/blob/master/spec-draft.md#touch-gestures
|
|
* @deprecated For Appium, use `driver.performActions(...)` instead
|
|
*
|
|
*/
|
|
touchPerform(actions: object[]): Promise<void>;
|
|
/**
|
|
* Mjsonwp Protocol Command
|
|
*
|
|
* No description available, please see reference link.
|
|
* @ref https://github.com/SeleniumHQ/mobile-spec/blob/master/spec-draft.md#touch-gestures
|
|
* @deprecated For Appium, use `driver.performActions(...)` instead
|
|
*
|
|
*/
|
|
multiTouchPerform(actions: object[], elementId?: object[]): Promise<void>;
|
|
/**
|
|
* Mjsonwp Protocol Command
|
|
*
|
|
* No description available, please see reference link.
|
|
* @ref https://github.com/appium/appium-base-driver/blob/master/docs/mjsonwp/protocol-methods.md#mobile-json-wire-protocol-endpoints
|
|
* @deprecated For Appium, use `driver.executeAsyncScript(...)` instead
|
|
*
|
|
*/
|
|
receiveAsyncResponse(status: string, value: string): Promise<void>;
|
|
}
|
|
//# sourceMappingURL=mjsonwp.d.ts.map
|