fix(search): expect the seven engines that actually contribute, not the five that don't #149

Merged

abiba-bot merged 2 commits from fix/search-stack-multiprovider-20261003 into master 2026-10-03 10:13:05 +00:00

Conversation 0 Commits 2 Files Changed 2

+31 -13

abiba-bot commented 2026-10-03 09:28:20 +00:00

Owner

Copy Link

Copy Source

What

search-stack-visibility was still expecting the 2026-09-25 engine set
(bing, brave, google cse, yandex, duckduckgo) — three of which are blocked
upstream today. The check had gone quiet on the engines that actually carry the
stack.

The live stack now runs ten engines enabled: seven that returned real results
from this network, plus three best-effort canaries kept for recovery visibility.

Live engine expansion (CT 100, 2026-10-03)

/etc/searxng/settings.yml (docker-vm .7, container searxng) after the change:

engine	status
bing, yandex, yep, mwmbl, naver, seznam, yahoo	working (kept enabled)
brave, duckduckgo, google cse	best-effort canaries (blocked upstream)
qwant, fireball	tested, failed, disabled
mojeek, startpage, dogpile	inactive: true in the build (proof-of-work CAPTCHA)
marginalia	needs an API key

Proof (contract run at the live service)

QUERY: 'proxmox backup server'
  contributing engines: {yandex: 14, bing: 10, mwmbl: 58, yep: 16, naver: 14, seznam: 6, yahoo: 1}
QUERY: 'python asyncio tutorial'
  contributing engines: {bing: 10, yandex: 3, mwmbl: 82, seznam: 5, naver: 14, yep: 17}
EXTRACTION: 71532 chars of markdown returned
VERDICT: PASS

Before: both queries contributed from bing alone (one engine above the floor).

Broken cases still fail and name the cause: single-engine floor → exit 1 naming
the sole contributor; broken extraction → exit 1; unreachable SearXNG → exit 2.

Note on CI

scripts/secret-scan.sh fails on master already, independent of this PR:
hermes-key-enforcement.prose.md:217 is a deliberate synthetic example
(LITELLM_API_KEY=sk-synthetic-litellm-…) that the scanner flags. Not touched
here; flagging so it can be allowlisted deliberately.

## What `search-stack-visibility` was still expecting the 2026-09-25 engine set (`bing, brave, google cse, yandex, duckduckgo`) — three of which are blocked upstream today. The check had gone quiet on the engines that actually carry the stack. The live stack now runs **ten** engines enabled: seven that returned real results from this network, plus three best-effort canaries kept for recovery visibility. ## Live engine expansion (CT 100, 2026-10-03) `/etc/searxng/settings.yml` (docker-vm `.7`, container `searxng`) after the change: | engine | status | | --- | --- | | bing, yandex, yep, mwmbl, naver, seznam, yahoo | **working** (kept enabled) | | brave, duckduckgo, google cse | best-effort canaries (blocked upstream) | | qwant, fireball | tested, failed, disabled | | mojeek, startpage, dogpile | `inactive: true` in the build (proof-of-work CAPTCHA) | | marginalia | needs an API key | ## Proof (contract run at the live service) ``` QUERY: 'proxmox backup server' contributing engines: {yandex: 14, bing: 10, mwmbl: 58, yep: 16, naver: 14, seznam: 6, yahoo: 1} QUERY: 'python asyncio tutorial' contributing engines: {bing: 10, yandex: 3, mwmbl: 82, seznam: 5, naver: 14, yep: 17} EXTRACTION: 71532 chars of markdown returned VERDICT: PASS ``` Before: both queries contributed from **bing alone** (one engine above the floor). Broken cases still fail and name the cause: single-engine floor → exit 1 naming the sole contributor; broken extraction → exit 1; unreachable SearXNG → exit 2. ## Note on CI `scripts/secret-scan.sh` fails **on master already**, independent of this PR: `hermes-key-enforcement.prose.md:217` is a deliberate *synthetic* example (`LITELLM_API_KEY=sk-synthetic-litellm-…`) that the scanner flags. Not touched here; flagging so it can be allowlisted deliberately.

abiba-bot added 1 commit 2026-10-03 09:28:20 +00:00

fix(search): expect the seven engines that actually contribute, not the five that don't ... 6608d3162f

The visibility contract's expected-engine set was still the 2026-09-25 list
(bing, brave, google cse, yandex, duckduckgo). Three of those five are blocked
upstream today, so the check had gone quiet on the engines that DO carry the
stack and noisy on ones that cannot.

The live stack now runs ten engines enabled: seven that returned real results
from this network (bing, yandex, yep, mwmbl, naver, seznam, yahoo) plus the
three best-effort canaries kept for recovery visibility (brave, duckduckgo,
google cse). The expected set is updated to match, so a silent zero is reported
for every engine the stack actually runs.

Live proof after the engine expansion (CT 100, 2026-10-03):
  'proxmox backup server'   -> 7 contributing engines
  'python asyncio tutorial' -> 6 contributing engines
  VERDICT: PASS
Before the change both queries contributed from bing alone, one engine above
the two-engine floor.

Verified broken cases still fail and name the cause: a single-engine floor
exits 1 naming the sole contributor, a broken extraction exits 1, and an
unreachable SearXNG exits 2.

Contract text and version updated to the 2026-10-03 state.

abiba-bot referenced this issue from a commit 2026-10-03 09:36:24 +00:00

fix: prose-lint allowlist for synthetic credential example

abiba-bot added 1 commit 2026-10-03 10:08:59 +00:00

Merge master into fix/search-stack-multiprovider-20261003 (pick up the #150 lint allowlist fix so the PR's lint job can pass) 9c6346e3ff

abiba-bot merged commit 595e67bda6 into master 2026-10-03 10:13:05 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

No items

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

abiba-bot jerome (Jerome Kwame Tabiri) kagentz-bot kwame (Kwame Tabiri) mumuni-bot (Mumuni 🦅 (Syslog Falcon)) tanko-bot theo

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SyslogSolution/prose-contracts#149