Distinguish main matches from related suggestions and ship 0.1.9

This commit is contained in:
karl committed 2026-10-14 12:45:32 +02:00
1 parent a8ba594d0e
commit b0bdfc7816
40 files changed
+2463 -185

No files matched your search

+86 -2
View File
@@ -5,8 +5,8 @@ Windows uninstall/reinstall path, alongside a modest media relevance improvement
No intermediate release or push is permitted. This report distinguishes actual
native observations from process, source and automated frontend checks.
Current delivery is 0.1.8. See the final startup-writer correction and corrected
Windows/Linux package sections below for authoritative hashes and checks.
Current installed correction is 0.1.9. Its package checks below supersede the
0.1.8 startup-writer delivery; earlier sections retain their historical evidence.
Earlier local candidates are retained as historical prechecks and were not
published. Final native capture/input remains unavailable; process startup,
accessibility observation and software screenshots do not replace that gate.
@@ -264,6 +264,47 @@ Final evidence: `.searchi/qa/linux-final-018-lockfix-build.json`, matching build
log, and `.searchi/qa/linux-final-018-lockfix-startup.json`. All owned Linux
build/test/startup processes have finished. No package was published here.
## Linux 0.1.9 graded-result package validation
The renewed semantic-evidence change was frozen with current tracked and
nonignored new source, tests, fixtures/policy and built frontend: 685 files,
source HEAD `a8ba594d0e7e6ba15c3ebb38c48aab8a6a8258ea` plus documented
uncommitted changes. Source archive SHA-256:
`c6fa2f6ec66a153318907ce5f3eb6ba820ece3d059247989260be073750dde32`.
Raw per-file manifest: `.searchi/qa/linux-final-019-source.json`.
CLI/extraction release compilation, desktop release compilation and **56 Linux
desktop tests** passed (zero ignored, 5.55 seconds). Current extraction provenance,
normal Google/speech runtimes and loader resolution were verified. No GPU
execution was performed; the packages retain normal hardware detection and
CPU fallback.
| Artifact | Bytes | SHA-256 |
| --- | ---: | --- |
| `searchi_0.1.9_amd64.deb` | 177,702,778 | `8865da4994cc0e120c7962ffe04e25bd9535042ce9dc21c26306302efc57d3dc` |
| `searchi-headless_0.1.9_linux-x86_64.tar.xz` | 110,104,160 | `f02bf5350c7b23dfecbcd58125cf9d505fb6d40044a849ad770851ed90026f08` |
Actual startup of the extracted final Debian bytes passed on WSLg `:0` with an
isolated profile, automatic indexing disabled and CPU/software rendering. Its
bundled Google worker ran `--device cpu --role query --threads 1`; the desktop
was alive. All 29 speech records and desktop dependencies were verified, and the
owned process group was terminated. No UI interaction retry was attempted.
The headless archive was extracted with all **60 package records** verified.
Genuine CPU CLI and MCP searches used an existing owned one-source speech index,
without reindexing or new fixture tuning. A known spoken-topic query returned one
main match; an absent spaceship query returned zero main matches and one related
suggestion. CLI/MCP match kinds agreed, MCP emitted explicit evidence and counts,
and the genuine Google worker reported query role, 512-token context and one CPU
thread. This tiny package boundary proof is not independent quality validation,
an absence guarantee or a performance benchmark.
Raw evidence: `.searchi/qa/linux-final-019-build.json`, matching build log,
`.searchi/qa/linux-final-019-headless-build.json`,
`.searchi/qa/linux-final-019-startup.json` and
`.searchi/qa/linux-final-019-headless-smoke.json`. All owned processes finished;
no public release or push was performed by this validation agent.
## Final startup writer correction
The preceding local 0.1.8 packages remained unpublished prechecks. An actual
@@ -318,3 +359,46 @@ Google query worker was observed on CPU with query role and one thread, alongsid
bounded background workers. The app is left running for Karl; device discovery
continues in the background. No final native input pass is claimed.
Receipts: `.searchi/qa/lean-final-fixed-install/result.json` and `index-check.json`.
## Windows input access boundary
The current native input failure is `GetCursorPos` returning `0x80070005`
(access denied), not a filesystem or build approval rejection. Microsoft
documents that [GetCursorPos](https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-getcursorpos)
requires `WINSTA_READATTRIBUTES` on the window station and the current input
desktop. Broad workspace access does not establish those conditions for the
native automation helper. The precise failing permission/desktop condition
has not been independently established. No security settings were bypassed
and no unchanged failed input attempt was repeated for 0.1.9.
The remaining manual Windows check is: press Ctrl+Shift+Space, type a query,
navigate main results, expand/collapse Related suggestions, open the selected
source, hide/show through Escape and the tray, and inspect the native glass
opacity setting. Linux native graphical interaction remains a separate check.
Actual CPU retrieval and software-rendered frontend checks do not replace
these open integration checks.
## Windows 0.1.9 installed correction
The normal Windows installer is 101,821,254 bytes, SHA-256
`ebdec4de6501b6f1cf35cb19ffb7e10adebdab039bffe6bd04ccc39f70d63272`.
Installation exited zero; installed executable SHA-256
`7079d7dff83138601f7f87153f7cec1032ccd9debd9c19f8810bc4c36efdd17a`
matches the extracted installer. Current extraction-helper provenance passed.
Settings bytes were preserved, a consistent SQLite backup was saved, and the
VM CPU launcher and desktop/login shortcuts were restored. Retained-index
`quick_check` returned `ok`; this is not a fresh full-discovery qualification.
The installed app responds and its normal Google worker is resident with CPU,
query role and one thread. The packaged Windows CLI using that installed worker
searched the existing real-Google document/media fixture: one main supplier PDF
and six related suggestions, with the mountain still accessible as related.
This is functional package evidence, not the blind quality benchmark. A genuine
Windows CLI/MCP test separately passed document/code queries and cited source
reads. Windows desktop checks passed 56 tests (one explicitly ignored); Linux
desktop checks passed 56. Workspace strict all-target Clippy and formatting
passed, as did 66 frontend tests and the actual UI capture checks.
Receipts: `.searchi/qa/evidence-019-install/`,
`.searchi/qa/evidence-019-windows-real-mcp.log` and the Linux 0.1.9 receipts above.
The installed app is left running. Native input remains unchecked.