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>
22 lines
968 B
JavaScript
22 lines
968 B
JavaScript
"use strict";
|
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
exports.escape = void 0;
|
|
/**
|
|
* Escape all magic characters in a glob pattern.
|
|
*
|
|
* If the {@link windowsPathsNoEscape | GlobOptions.windowsPathsNoEscape}
|
|
* option is used, then characters are escaped by wrapping in `[]`, because
|
|
* a magic character wrapped in a character class can only be satisfied by
|
|
* that exact character. In this mode, `\` is _not_ escaped, because it is
|
|
* not interpreted as a magic character, but instead as a path separator.
|
|
*/
|
|
const escape = (s, { windowsPathsNoEscape = false, } = {}) => {
|
|
// don't need to escape +@! because we escape the parens
|
|
// that make those magic, and escaping ! as [!] isn't valid,
|
|
// because [!]] is a valid glob class meaning not ']'.
|
|
return windowsPathsNoEscape
|
|
? s.replace(/[?*()[\]]/g, '[$&]')
|
|
: s.replace(/[?*()[\]\\]/g, '\\$&');
|
|
};
|
|
exports.escape = escape;
|
|
//# sourceMappingURL=escape.js.map
|