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> |
||
|---|---|---|
| .. | ||
| dist | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
@jridgewell/resolve-uri
Resolve a URI relative to an optional base URI
Resolve any combination of absolute URIs, protocol-realtive URIs, absolute paths, or relative paths.
Installation
npm install @jridgewell/resolve-uri
Usage
function resolve(input: string, base?: string): string;
import resolve from '@jridgewell/resolve-uri';
resolve('foo', 'https://example.com'); // => 'https://example.com/foo'
| Input | Base | Resolution | Explanation |
|---|---|---|---|
https://example.com |
any | https://example.com/ |
Input is normalized only |
//example.com |
https://base.com/ |
https://example.com/ |
Input inherits the base's protocol |
//example.com |
rest | //example.com/ |
Input is normalized only |
/example |
https://base.com/ |
https://base.com/example |
Input inherits the base's origin |
/example |
//base.com/ |
//base.com/example |
Input inherits the base's host and remains protocol relative |
/example |
rest | /example |
Input is normalized only |
example |
https://base.com/dir/ |
https://base.com/dir/example |
Input is joined with the base |
example |
https://base.com/file |
https://base.com/example |
Input is joined with the base without its file |
example |
//base.com/dir/ |
//base.com/dir/example |
Input is joined with the base's last directory |
example |
//base.com/file |
//base.com/example |
Input is joined with the base without its file |
example |
/base/dir/ |
/base/dir/example |
Input is joined with the base's last directory |
example |
/base/file |
/base/example |
Input is joined with the base without its file |
example |
base/dir/ |
base/dir/example |
Input is joined with the base's last directory |
example |
base/file |
base/example |
Input is joined with the base without its file |