5 Commits

Author	SHA1	Message	Date
Shaun Arman	4c4ca40146	fix: UI contrast issues and ARM64 build failure ... **UI Fixes (TDD approach - tests first, then implementation):** - Resolution steps: improved text contrast (text-foreground vs muted) - DocEditor preview: added text-foreground class for readability - History page: fixed domain display (category field) with better contrast - Audit Log: added expandable rows with View/Hide buttons to show transmitted data - Dashboard & buttons: already had proper contrast with outline variant - Export document: fixed missing title/content parameters in command signature **Tests Added (13 new tests, all passing):** - tests/unit/resolution.test.tsx - resolution steps contrast - tests/unit/docEditor.test.tsx - preview mode and export buttons - tests/unit/exportDocument.test.ts - export parameters validation - tests/unit/history.test.tsx - domain display and filtering - tests/unit/dashboard.test.tsx - refresh button visibility - tests/unit/auditLog.test.tsx - data visibility and expandable rows - tests/unit/setup.ts - added @testing-library/jest-dom matchers **CI Fix:** - Removed platform label from ARM64 build step (native agent, old Docker) **Test Results:** - Frontend: 38/38 passing ✅ - Backend: 64/64 passing ✅ - TypeScript: no errors ✅ Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-03 08:05:58 -05:00
Shaun Arman	47af97b68e	feat: close issues, restore history, auto-save resolution steps ... - db.rs: add get_issue_messages command (joins ai_conversations + ai_messages) - tauriCommands.ts: fix updateIssueCmd to pass updates as nested object (was spreading inline — Rust expects {issueId, updates}); fix addFiveWhyCmd parameter names to match Rust (stepOrder, whyQuestion, answer, evidence); add getIssueMessagesCmd and IssueMessage interface - Dashboard: X button on each open issue row to close (mark resolved) inline - Triage: restore conversation history from DB when revisiting existing issues; detect close intent patterns and mark issue resolved + navigate home; auto-save resolution step via addFiveWhyCmd when AI advances why level - tests: add issueActions.test.ts covering IPC arg structure and close intent	2026-03-31 12:50:39 -05:00
Shaun Arman	944b14e5c4	fix: dashboard shows — while loading, exposes errors, adds refresh button ... Stat cards showed 0 immediately on mount because openCount was computed from an empty issues array before the async loadIssues call resolved. Now shows — during load, a red error banner if the backend call fails, and a Refresh button. useEffect dependency changed to [] (fires once on mount, not on every loadIssues reference check).	2026-03-31 08:55:05 -05:00
Shaun Arman	ebf60d17c6	fix: navigate to /logs after issue creation, fix dashboard category display ... - NewIssue: navigate to /issue/:id/logs so log upload step is not skipped - Dashboard: use issue.category instead of issue.domain (field name matches Rust) - tests: add historyStore tests covering open count logic and field mapping	2026-03-31 08:26:25 -05:00
Shaun Arman	8839075805	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-14 22:36:25 -05:00