sarman/tftsr-devops_investigation
1
1
Fork 0
Code Issues 4 Pull Requests Actions 34 Packages Projects 3 Releases 6 Wiki Activity
f47ec90d05
tftsr-devops_investigation/src-tauri/Cargo.toml

70 lines
1.4 KiB
TOML
Raw Normal View History

feat: initial implementation of TFTSR IT Triage & RCA application 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>
2026-03-15 03:36:25 +00:00
[package]
feat(rebrand): rename binary to trcaa and auto-generate DB key - Rename Cargo package from 'tftsr' to 'trcaa' — installed command becomes 'trcaa' instead of 'tftsr' - Update app data directories to ~/.local/share/trcaa (Linux), ~/Library/Application Support/trcaa (macOS), %APPDATA%/trcaa (Windows) - Update bundle identifier to com.trcaa.app - Auto-generate per-installation DB encryption key on first launch and persist to <data_dir>/.dbkey (mode 0600 on Unix) — removes the hard requirement for TFTSR_DB_KEY to be set before the app will start
2026-04-05 22:50:16 +00:00
name = "trcaa"
feat(mcp): add MCP Server Support with TDD implementation Adds full Model Context Protocol (MCP) server management, enabling the AI assistant to discover and call tools from external MCP servers during triage conversations. Backend (Rust): - rmcp 1.7.0 dependency (client + stdio + Streamable HTTP transports) - Migration 018: mcp_servers, mcp_tools, mcp_resources tables with CHECK constraints for transport_type, auth_type, discovery_status - src/mcp/ module: models, store, client, adapter, discovery, commands, transport/{stdio,http} - AppState gains mcp_connections: Arc<TokioMutex<HashMap<...>>> - .setup() hook auto-discovers enabled servers at startup - 8 new Tauri commands wired into invoke_handler - execute_mcp_tool_call: PII scan + mandatory audit_log before execution - Auth values encrypted at rest via integrations::auth::encrypt_token(); scrubbed before any frontend response Frontend: - MCPServers.tsx settings page (/settings/mcp) with server list, status badges, Discover Now, Add/Edit modal, enable/disable toggle - tauriCommands.ts: McpServer, McpTool, McpServerStatus types + 8 cmds - App.tsx: Plug icon, /settings/mcp route, sidebar nav entry Tests (TDD): 15 new tests, all green - 5 migration tests (written before migration, red → green) - 5 store CRUD + encryption tests - 5 adapter sanitization + conversion tests Verification: 185/185 Rust, 94/94 Vitest, clippy -D warnings: 0
2026-05-23 21:23:48 +00:00
version = "0.3.0"
feat: initial implementation of TFTSR IT Triage & RCA application 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>
2026-03-15 03:36:25 +00:00
edition = "2021"
[lib]
name = "tftsr_lib"
crate-type = ["staticlib", "cdylib", "rlib"]
[build-dependencies]
tauri-build = { version = "2", features = [] }
[dependencies]
fix: resolve all clippy lints (uninlined format args, range::contains, push_str single chars)
2026-03-15 18:10:26 +00:00
tauri = { version = "2", features = [] }
feat: initial implementation of TFTSR IT Triage & RCA application 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>
2026-03-15 03:36:25 +00:00
tauri-plugin-stronghold = "2"
tauri-plugin-dialog = "2"
tauri-plugin-fs = "2"
tauri-plugin-shell = "2"
tauri-plugin-http = "2"
fix: use bundled-sqlcipher-vendored-openssl for portable Windows cross-compilation SQLCipher requires OpenSSL when cross-compiling for Windows with mingw-w64. bundled-sqlcipher-vendored-openssl compiles OpenSSL from source — no system OpenSSL needed for any target. Add perl to CI steps (required by OpenSSL build).
2026-03-16 00:17:36 +00:00
rusqlite = { version = "0.31", features = ["bundled-sqlcipher-vendored-openssl"] }
feat: initial implementation of TFTSR IT Triage & RCA application 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>
2026-03-15 03:36:25 +00:00
serde = { version = "1", features = ["derive"] }
serde_json = "1"
tokio = { version = "1", features = ["full"] }
feat: support GenAI datastore file uploads and fix paste image upload - Add use_datastore_upload field to ProviderConfig for enabling datastore uploads - Add upload_file_to_datastore and upload_file_to_datastore_any commands - Add upload_log_file_by_content and upload_image_attachment_by_content commands for drag-and-drop without file paths - Add multipart/form-data support for file uploads to GenAI datastore - Add support for image/bmp MIME type in image validation - Add x-generic-api-key header support for GenAI API authentication This addresses: - Paste fails to attach screenshot (clipboard) - File upload fails with 500 error when using GenAI API - GenAI datastore upload endpoint support for non-text files
2026-04-09 23:05:44 +00:00
reqwest = { version = "0.12", features = ["json", "stream", "multipart"] }
feat: initial implementation of TFTSR IT Triage & RCA application 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>
2026-03-15 03:36:25 +00:00
regex = "1"
aho-corasick = "1"
uuid = { version = "1", features = ["v7"] }
printpdf = "0.7"
fix: implement native DOCX export without pandoc dependency Replace pandoc-based DOCX export with native Rust implementation using docx-rs crate. DOCX export now works out of the box without requiring users to install external tools. Changes: - Added docx-rs dependency to Cargo.toml - Implemented export_docx() in exporter.rs - Removed pandoc subprocess calls from docs.rs - Uses same markdown parsing as PDF export - Handles titles, headings, and normal text with appropriate styling Tested: - Rust compilation ✓ - Rust formatting ✓ - TypeScript types ✓ Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-04-03 17:53:36 +00:00
docx-rs = "0.4"
feat: initial implementation of TFTSR IT Triage & RCA application 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>
2026-03-15 03:36:25 +00:00
sha2 = { version = "0.10", features = ["std"] }
hex = "0.4"
anyhow = "1"
thiserror = "1"
tracing = "0.1"
tracing-subscriber = { version = "0.3", features = ["env-filter"] }
chrono = { version = "0.4", features = ["serde"] }
futures = "0.3"
async-trait = "0.1"
base64 = "0.22"
fix: UI visibility issues, export errors, filtering, and audit log enhancement - Fix download icons (PDF/DOCX) not visible in dark theme by adding text-foreground class - Fix "Read-only file system" error by using Downloads directory for exports with proper fallback - Fix Search button visibility in History page by changing variant and adding icon - Fix domain-only filtering in History page by adding missing filter.domain handling - Enhance audit log to capture full transmitted data (provider details, messages, content previews) - Add dirs crate dependency for cross-platform directory detection - Add success/error feedback for document exports with file path display - Update Security page to display pretty-printed JSON audit details Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-04-03 13:37:47 +00:00
dirs = "5"
feat: implement OAuth2 token exchange and AES-256-GCM encryption Phase 2.2: OAuth2 flow - Part 1 (Token exchange + encryption) Implemented: - OAuth2 authorization code exchange with PKCE * Real HTTP POST to token endpoint * Parses access_token, refresh_token, expires_in, token_type * Calculates expires_at timestamp - AES-256-GCM token encryption * Uses TFTSR_ENCRYPTION_KEY env var (or dev default) * Random nonce per encryption (12 bytes) * Base64-encoded output with nonce prepended * Proper key derivation (32 bytes) - Updated credential storage * store_pat() now encrypts tokens before DB storage * get_pat() decrypts tokens on retrieval * Stores both token_hash (audit) and encrypted_token (actual) Dependencies added: - mockito 1.7.2 (dev) - HTTP mocking for tests - aes-gcm 0.10 - AES-256-GCM encryption - rand 0.8 - Cryptographically secure RNG TDD tests (20 passing with --test-threads=1): - OAuth exchange: success, missing token, HTTP error, network error - Encryption: roundtrip, different nonces, invalid data, wrong key - PAT storage: store/retrieve, nonexistent service, replacement Note: Tests require single-threaded execution due to env var test isolation. This is acceptable for CI/CD.
2026-04-03 19:32:17 +00:00
aes-gcm = "0.10"
rand = "0.8"
feat: add OAuth2 Tauri commands for integration authentication Phase 2.2: OAuth2 flow - Part 2 (Tauri commands) Implemented: - initiate_oauth command * Generates PKCE challenge * Creates state key for OAuth session * Stores verifier in global OAuth state * Returns authorization URL for Confluence/ADO * ServiceNow uses basic auth (not OAuth2) - handle_oauth_callback command * Retrieves and removes verifier from state * Exchanges authorization code for access token * Encrypts and stores token in DB * Logs audit event for successful OAuth - OAuthInitResponse type for frontend * auth_url: Full OAuth authorization URL * state: Session key for callback matching - Global OAUTH_STATE storage (lazy_static) * Thread-safe HashMap for PKCE verifiers * Temporary storage during OAuth flow * Automatically cleaned up after exchange Service configuration: - Confluence: auth.atlassian.com OAuth2 - Azure DevOps: login.microsoftonline.com OAuth2 - ServiceNow: Basic auth (not OAuth2) Client IDs from env vars: - CONFLUENCE_CLIENT_ID - ADO_CLIENT_ID Dependencies added: - lazy_static 1.4 - Global static initialization TDD tests (3 passing): - OAuth state storage and retrieval - Multiple key management - OAuthInitResponse serialization Commands registered in lib.rs generate_handler![] Next: Local HTTP callback server for OAuth redirects
2026-04-03 19:50:13 +00:00
lazy_static = "1.4"
feat: implement OAuth2 callback server with automatic token exchange Phase 2.2: OAuth2 flow - Part 3 (Callback server) COMPLETE ✅ Implemented: - Local HTTP server on localhost:8765 using warp * GET /callback?code=...&state=... - OAuth redirect handler * GET /health - Health check endpoint * Graceful shutdown with oneshot channel - Automatic callback handling * Server auto-starts on first initiate_oauth call * Background task listens for OAuth redirects * Automatically exchanges code for token * Stores encrypted token in database * Logs audit event for each successful OAuth - Updated initiate_oauth command * Starts callback server if not running * Stores (service, verifier) tuple in OAuth state * Returns auth URL to open in browser/webview - Updated handle_oauth_callback_internal * Accepts AppState reference (not State) * Called automatically by callback server * Exchanges code, encrypts token, stores in DB - Beautiful success/error HTML pages * Green checkmark on success * Auto-closes window after 3 seconds * Clear error messages on failure - Global state management * OAUTH_STATE: Maps state key -> (service, verifier) * CALLBACK_SERVER_SHUTDOWN: Holds shutdown channel * Thread-safe with Mutex wrappers Dependencies added: - warp 0.3 - Lightweight HTTP framework TDD tests (7 passing with --test-threads=1): Callback server tests: * Health endpoint verification * Callback parameter parsing * Missing/partial parameter handling * Graceful shutdown Integration command tests: * OAuth state storage and retrieval * Multiple key management * OAuthInitResponse serialization COMPLETE OAUTH2 FLOW: 1. User calls initiate_oauth("confluence") 2. Callback server starts (if not running) 3. Frontend receives auth URL 4. User opens URL in browser/webview 5. User authorizes, redirected to localhost:8765/callback?code=... 6. Callback server receives redirect 7. Token exchanged automatically 8. Token encrypted and stored in DB 9. Success page shown to user 10. Window auto-closes Next: Frontend components (AuthWindow, Settings UI, CSP updates)
2026-04-03 19:59:39 +00:00
warp = "0.3"
fix(security): harden secret handling and audit integrity Remove high-risk defaults and tighten data handling across auth, storage, IPC, provider calls, and capabilities so sensitive data is better protected by default. Also update README/wiki security guidance and add targeted tests for the new hardening behaviors. Made-with: Cursor
2026-04-05 04:37:05 +00:00
urlencoding = "2"
feat: add image attachment support with PII detection - Add image_attachments table to database schema (migration 013) - Implement image upload, list, delete, and clipboard paste commands - Add image file PII detection with user approval workflow - Register image attachment commands in Tauri IPC - Update TypeScript types and frontend components - Add unit tests for image attachment functionality - Update README and wiki documentation
2026-04-09 01:03:34 +00:00
infer = "0.15"
fix(integrations): security and correctness improvements - Add url canonicalization for deduplication (strip fragments/query params) - Add WIQL injection escaping for Azure DevOps work item searches - Add CQL injection escaping for Confluence searches - Add MAX_EXPANDED_QUERIES constant for consistency - Fix logging to show expanded_query instead of search_url - Add input validation for empty queries - Add url crate dependency for URL parsing All 142 tests pass.
2026-04-15 00:55:32 +00:00
url = "2.5.8"
feat(upload): add safe file extension validation and binary text extraction - Add extension allowlist (SAFE_TEXT_EXTENSIONS + SAFE_BINARY_EXTENSIONS) rejecting unsupported file types at both upload_log_file and upload_log_file_by_content entry points - Add extract_text_content() with PDF text extraction via lopdf and DOCX extraction via zip+quick-xml - Binary files (PDF/DOCX) get extracted text written to .extracted.txt for downstream PII detection - Expand frontend file input accept list and add collapsible supported-formats disclosure element - Add 11 unit tests covering allowlist logic and extraction paths
2026-05-31 18:50:59 +00:00
lopdf = "0.31"
zip = "0.6"
quick-xml = "0.36"
feat(mcp): add MCP Server Support with TDD implementation Adds full Model Context Protocol (MCP) server management, enabling the AI assistant to discover and call tools from external MCP servers during triage conversations. Backend (Rust): - rmcp 1.7.0 dependency (client + stdio + Streamable HTTP transports) - Migration 018: mcp_servers, mcp_tools, mcp_resources tables with CHECK constraints for transport_type, auth_type, discovery_status - src/mcp/ module: models, store, client, adapter, discovery, commands, transport/{stdio,http} - AppState gains mcp_connections: Arc<TokioMutex<HashMap<...>>> - .setup() hook auto-discovers enabled servers at startup - 8 new Tauri commands wired into invoke_handler - execute_mcp_tool_call: PII scan + mandatory audit_log before execution - Auth values encrypted at rest via integrations::auth::encrypt_token(); scrubbed before any frontend response Frontend: - MCPServers.tsx settings page (/settings/mcp) with server list, status badges, Discover Now, Add/Edit modal, enable/disable toggle - tauriCommands.ts: McpServer, McpTool, McpServerStatus types + 8 cmds - App.tsx: Plug icon, /settings/mcp route, sidebar nav entry Tests (TDD): 15 new tests, all green - 5 migration tests (written before migration, red → green) - 5 store CRUD + encryption tests - 5 adapter sanitization + conversion tests Verification: 185/185 Rust, 94/94 Vitest, clippy -D warnings: 0
2026-05-23 21:23:48 +00:00
rmcp = { version = "1.7.0", features = [
"client",
"transport-child-process",
"transport-streamable-http-client-reqwest",
] }
feat(ai): add tool-calling and integration search as AI data source This commit implements two major features: 1. Integration Search as Primary AI Data Source - Confluence, ServiceNow, and Azure DevOps searches execute before AI queries - Search results injected as system context for AI providers - Parallel search execution for performance - Webview-based fetch for HttpOnly cookie support - Persistent browser windows maintain authenticated sessions 2. AI Tool-Calling (Function Calling) - Allows AI to automatically execute functions during conversation - Implemented for OpenAI-compatible providers and Custom REST provider - Created add_ado_comment tool for updating Azure DevOps tickets - Iterative tool-calling loop supports multi-step workflows - Extensible architecture for adding new tools Key Files: - src-tauri/src/ai/tools.rs (NEW) - Tool definitions - src-tauri/src/integrations/*_search.rs (NEW) - Integration search modules - src-tauri/src/integrations/webview_fetch.rs (NEW) - HttpOnly cookie workaround - src-tauri/src/commands/ai.rs - Tool execution and integration search - src-tauri/src/ai/openai.rs - Tool-calling for OpenAI and Custom REST provider - All providers updated with tools parameter support Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-04-06 18:22:02 +00:00
feat: initial implementation of TFTSR IT Triage & RCA application 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>
2026-03-15 03:36:25 +00:00
[dev-dependencies]
tokio-test = "0.4"
feat: implement OAuth2 token exchange and AES-256-GCM encryption Phase 2.2: OAuth2 flow - Part 1 (Token exchange + encryption) Implemented: - OAuth2 authorization code exchange with PKCE * Real HTTP POST to token endpoint * Parses access_token, refresh_token, expires_in, token_type * Calculates expires_at timestamp - AES-256-GCM token encryption * Uses TFTSR_ENCRYPTION_KEY env var (or dev default) * Random nonce per encryption (12 bytes) * Base64-encoded output with nonce prepended * Proper key derivation (32 bytes) - Updated credential storage * store_pat() now encrypts tokens before DB storage * get_pat() decrypts tokens on retrieval * Stores both token_hash (audit) and encrypted_token (actual) Dependencies added: - mockito 1.7.2 (dev) - HTTP mocking for tests - aes-gcm 0.10 - AES-256-GCM encryption - rand 0.8 - Cryptographically secure RNG TDD tests (20 passing with --test-threads=1): - OAuth exchange: success, missing token, HTTP error, network error - Encryption: roundtrip, different nonces, invalid data, wrong key - PAT storage: store/retrieve, nonexistent service, replacement Note: Tests require single-threaded execution due to env var test isolation. This is acceptable for CI/CD.
2026-04-03 19:32:17 +00:00
mockito = "1.2"
feat: initial implementation of TFTSR IT Triage & RCA application 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>
2026-03-15 03:36:25 +00:00
[profile.release]
opt-level = "s"
strip = true
chore: fix version update implementation - Replace npm ci with npm install in CI - Remove --locked flag from cargo clippy/test - Add cargo generate-lockfile after version update - Update update-version.mjs with semver validation - Add build.rs for Rust-level version injection
2026-04-13 21:34:48 +00:00
fix: add --locked to cargo commands and improve version update script - Add --locked to fmt, clippy, and test commands in CI - Remove updateCargoLock() and rely on cargo generate-lockfile - Add .git directory existence check in update-version.mjs - Use package.json as dynamic fallback instead of hardcoded 0.2.50 - Ensure execSync uses shell: false explicitly
2026-04-13 22:54:16 +00:00
feat(ai): add devops-incident-responder agent with domain auto-detection - Implement AgentRegistry system with devops-incident-responder agent - Add domain detection based on conversation keywords - Inject devops-incident-responder as primary system prompt - Auto-switch domain prompts silently when context shifts - Fix version update script to handle JSON format correctly - Always display version in bottom-left corner - Add release notes fallback to git commits if CHANGELOG empty This implements the full devops-incident-responder agent as the primary system prompt, with domain-specific SME prompts layered on top based on conversation content analysis. The version display bug is fixed by removing the collapsed condition, and release notes now have a fallback mechanism.
2026-04-30 00:41:47 +00:00
Reference in New Issue Copy Permalink