karl
a9b6592330
Core CI / core (ubuntu-latest) (push) Failing after 1m22s
Core CI / core (macos-latest) (push) Canceled after 0s
Core CI / core (windows-latest) (push) Canceled after 0s
Core CI / desktop (ubuntu-latest) (push) Successful in 3m46s
Core CI / desktop (macos-latest) (push) Canceled after 0s
Core CI / desktop (windows-latest) (push) Canceled after 0s
2.2 KiB
2.2 KiB
Validation evidence
Development host: Windows VM, x86_64 MSVC, Rust stable 1.99.0. All local tests run on CPU; no GPU provider is configured.
Initial foundation checks (2026-10-12):
cargo test --workspace: CLI parser/executable checks and engine retrieval, lifecycle, exclusions, filters, migration and concurrent-reader checks passed.cargo clippy --workspace --all-targets -- -D warnings: passed.- Rust formatting applied; final formatting verification follows integration.
- Desktop TypeScript/Vite build passed; npm audit reported zero vulnerabilities.
- Initial Windows desktop native check, embedded app build, strict Clippy and two desktop tests passed (index gate recovery and guarded source opening).
- Desktop launched with WebView2
--disable-gpu. UI automation could not capture the window:GetCursorPosaccess denied, then monitor capture error0x80070057. Visual layout and end-to-end UI interactions remain unverified. - Real Python CPU ONNX embedding proof completed on 8 documents / 6 queries:
5/6 top-1 accuracy, 6/6 recall@3. The strict top-1 quality gate is not met.
See
tools/semantic-proof/windows-cpu-result.jsonfor raw timings and rankings. This tiny fixture is not evidence of large-corpus performance. - Native Rust CPU embedding adapter compiled, passed its three unit tests and the explicit local-model smoke test. The smoke reproduced the same 5/6 top-1 limitation. Default CI omits this asset-dependent test; it must be executed separately with provisioned local artifacts.
- Integrated workspace validation: 19 default tests passed; 1 local-model test is opt-in. Rust formatting and strict Clippy passed after lockfile refresh.
- PDF/DOCX fixture tests include matching source locations, corrupt replacement, encrypted PDF behavior and compressed-input limits.
Not yet established: production latency targets, semantic inference, desktop runtime behavior, Linux/macOS execution, installer signing or upgrades. CI configuration is source configuration, not evidence that remote jobs ran. Gitea workflows require matching Windows, Linux and macOS runners; runner availability has not been established. GitHub workflows are also supplied for future mirroring, but do not run merely because code was pushed to Gitea.