v0.1.1 — provider-compatible verified search

What changed

v0.1.1 replaces the legacy web_search tool only for search-capable DeepSeek Harness agents and adds a bounded current-source workflow:

• mounts the 60-second time context proposed in Discussion #344;
• exposes verified_search(query, allowed_domains?);
• sends an absolute-date/current-version/first-party evidence instruction to the auxiliary DeepSeek search turn;
• passes the native allowed_domains field;
• filters returned structured sources locally by exact hostname or subdomain before applying the result cap;
• reports filteredOut and leaves the claim unresolved when no usable evidence remains;
• tolerates nullable provider metadata and server-tool error objects;
• drops provider prose and preserves only structured source metadata and citation excerpts.

Live conformance evidence

Tested against DeepSeek Harness 0.1.0-rc.6 and the real DeepSeek Anthropic-compatible Messages endpoint on 2026-08-14.

For an allowed_domains: ["api-docs.deepseek.com"] query, the provider returned 7 out-of-scope structured sources despite receiving the native allowlist. The plugin removed all 7 locally, retained 8 matching api-docs.deepseek.com sources, and reported the count. Because the retained results contained no citation excerpts, the agent disclosed that the requested current model-name claim remained unresolved instead of filling it from memory.

Verification

• 45 unit and lifecycle tests
• TypeScript check and prebuilt-artifact reproducibility
• tag CI: Ubuntu and Windows on Node 22.19 and Node 24 (4/4 green)
• clean DSH_HOME install from #v0.1.1
• clean-profile Web composition readback and HTTP 200 boot smoke
• real DeepSeek provider call through the Harness headless composition

Limits

allowed_domains is a postcondition over returned structured source hostnames. It is not a privacy, compliance, retrieval, redirect, network-egress, or freshness boundary. Search snippets and date/page-age labels remain untrusted provider metadata. The default Harness composition still has no safe full-page fetch path, so missing excerpts must lower confidence.

Search queries are stored in durable Harness session data; do not put secrets or private data in a query.

v0.1.0 is superseded and should not be used.

dsh-plugin-verified-search v0.1.0 (superseded)

Warning

Superseded — do not install this version. A credentialed DeepSeek conformance test found that real structured results may contain null source metadata. v0.1.0 treats that shape as a string and fails during normalization. Use v0.1.1 or newer once published.

What this release changes - replaces inherited web_search with verified_search only for search-capable agents; - mounts the rc.6 dsh-time-context fix corresponding to Discussion #344; - adds first-party allowed_domains passes with Harness-side structured-source enforcement; - requires absolute-date/current-version verification and preserves citation excerpts; - records credential-free native-search requests with a persistence-known session event; - hardens URL, response-size, lifecycle, rollback, and prompt-injection boundaries. ## Verification - 37/37 unit and lifecycle tests pass; - Ubuntu and Windows, Node 22.19 and 24 CI matrix pass; - fresh rc.6 profile install/composition/HTTP boot pass; - Git installation was verified from commit aa778a96b07fee1aa563a885994751ac71d942f2; - packaged archive contains 8 expected files. This is a compatibility layer for Harness 0.1.0-rc.6, not a guarantee that the provider index or ranking is always current. Search queries are durable session data and must not contain secrets.