# 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.

## Current integration checkpoint (2026-10-12)

- `cargo test --workspace --locked`: 41 default tests passed after final core integration. Four asset-dependent
  or explicit benchmark tests remain opt-in; a default pass does not run them.
- Native desktop tests: 7 passed with SEARCHI_FORCE_CPU=1 and WebView2 GPU disabled.
- Frontend: 7 async-state tests passed, Prettier passed, TypeScript/Vite build passed.
- Genuine Google CPU reference/window test passed separately: five DigUp reference
  vectors had cosine similarity above 0.999; actual multilingual retrieval and
  tokenizer tail-window coverage passed. MiniLM evidence below is historical.
- Repository description/topics were read back after update; the branded avatar
  upload returned HTTP 204 and the repository API returned its avatar URL.
- New desktop styling is in progress. `design-qa.md` records the visual gate as
  blocked because browser bootstrap and native screen capture are unavailable.
  No visual match or complete UI interaction verification is claimed.

Final UI integration: the branded compact launcher, local Inter/Fluent assets,
themes and motion implementation passed frontend build, formatting, and seven
state tests. Native launch succeeded; accessibility text showed real controls
and a warmed Google CPU worker. UI input and screenshots remain blocked by
Windows access/capture errors, as recorded in design-qa.md. Workspace formatting
and strict all-target Clippy passed. The fixed full-corpus first-input report
is in crates/searchi-core/benchmarks/results/windows-cpu-full-candidate-first-final.json;
all 40 measured filename inputs were below 50 ms in that run.

The active parallel development branches of work may add tests or change counts
after this checkpoint. Run the documented checks again after integration.

## Historical foundation evidence

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: `GetCursorPos` access denied, then monitor capture error
  `0x80070057`. 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.json` for 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.