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>
81 lines
2.4 KiB
TypeScript
81 lines
2.4 KiB
TypeScript
export declare enum FileType {
|
|
Unknown = 0,
|
|
File = 1,
|
|
Directory = 2,
|
|
SymbolicLink = 3
|
|
}
|
|
export interface UnixPermissions {
|
|
readonly user: number;
|
|
readonly group: number;
|
|
readonly world: number;
|
|
}
|
|
/**
|
|
* Describes a file, directory or symbolic link.
|
|
*/
|
|
export declare class FileInfo {
|
|
name: string;
|
|
static UnixPermission: {
|
|
Read: number;
|
|
Write: number;
|
|
Execute: number;
|
|
};
|
|
type: FileType;
|
|
size: number;
|
|
/**
|
|
* Unparsed, raw modification date as a string.
|
|
*
|
|
* If `modifiedAt` is undefined, the FTP server you're connected to doesn't support the more modern
|
|
* MLSD command for machine-readable directory listings. The older command LIST is then used returning
|
|
* results that vary a lot between servers as the format hasn't been standardized. Here, directory listings
|
|
* and especially modification dates were meant to be human-readable first.
|
|
*
|
|
* Be careful when still trying to parse this by yourself. Parsing dates from listings using LIST is
|
|
* unreliable. This library decides to offer parsed dates only when they're absolutely reliable and safe to
|
|
* use e.g. for comparisons.
|
|
*/
|
|
rawModifiedAt: string;
|
|
/**
|
|
* Parsed modification date.
|
|
*
|
|
* Available if the FTP server supports the MLSD command. Only MLSD guarantees dates than can be reliably
|
|
* parsed with the correct timezone and a resolution down to seconds. See `rawModifiedAt` property for the unparsed
|
|
* date that is always available.
|
|
*/
|
|
modifiedAt?: Date;
|
|
/**
|
|
* Unix permissions if present. If the underlying FTP server is not running on Unix this will be undefined.
|
|
* If set, you might be able to edit permissions with the FTP command `SITE CHMOD`.
|
|
*/
|
|
permissions?: UnixPermissions;
|
|
/**
|
|
* Hard link count if available.
|
|
*/
|
|
hardLinkCount?: number;
|
|
/**
|
|
* Link name for symbolic links if available.
|
|
*/
|
|
link?: string;
|
|
/**
|
|
* Unix group if available.
|
|
*/
|
|
group?: string;
|
|
/**
|
|
* Unix user if available.
|
|
*/
|
|
user?: string;
|
|
/**
|
|
* Unique ID if available.
|
|
*/
|
|
uniqueID?: string;
|
|
constructor(name: string);
|
|
get isDirectory(): boolean;
|
|
get isSymbolicLink(): boolean;
|
|
get isFile(): boolean;
|
|
/**
|
|
* Deprecated, legacy API. Use `rawModifiedAt` instead.
|
|
* @deprecated
|
|
*/
|
|
get date(): string;
|
|
set date(rawModifiedAt: string);
|
|
}
|