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>
33 lines
1.6 KiB
TypeScript
33 lines
1.6 KiB
TypeScript
/**
|
|
* Check whether to encode (as a character reference) the characters
|
|
* surrounding an attention run.
|
|
*
|
|
* Which characters are around an attention run influence whether it works or
|
|
* not.
|
|
*
|
|
* See <https://github.com/orgs/syntax-tree/discussions/60> for more info.
|
|
* See this markdown in a particular renderer to see what works:
|
|
*
|
|
* ```markdown
|
|
* | | A (letter inside) | B (punctuation inside) | C (whitespace inside) | D (nothing inside) |
|
|
* | ----------------------- | ----------------- | ---------------------- | --------------------- | ------------------ |
|
|
* | 1 (letter outside) | x*y*z | x*.*z | x* *z | x**z |
|
|
* | 2 (punctuation outside) | .*y*. | .*.*. | .* *. | .**. |
|
|
* | 3 (whitespace outside) | x *y* z | x *.* z | x * * z | x ** z |
|
|
* | 4 (nothing outside) | *x* | *.* | * * | ** |
|
|
* ```
|
|
*
|
|
* @param {number} outside
|
|
* Code point on the outer side of the run.
|
|
* @param {number} inside
|
|
* Code point on the inner side of the run.
|
|
* @param {'*' | '_'} marker
|
|
* Marker of the run.
|
|
* Underscores are handled more strictly (they form less often) than
|
|
* asterisks.
|
|
* @returns {EncodeSides}
|
|
* Whether to encode characters.
|
|
*/
|
|
export function encodeInfo(outside: number, inside: number, marker: "*" | "_"): EncodeSides;
|
|
import type { EncodeSides } from '../types.js';
|
|
//# sourceMappingURL=encode-info.d.ts.map
|