chore(baseline): resync the tui changelog slice, surface facts, and test clippy

[asto18089]

Problem

CodeWhale#56 originally carried three disclosed baseline repairs that do not belong on a topic branch:

• the crates/tui/CHANGELOG.md [Unreleased] slice was missing the DDG→Bing search-degradation entry that the root CHANGELOG.md has carried since docs(changelog): record keyless Bing search tail #39 recorded it (3f8a25eef) for the search degradation merged with build: re-fork Pinvou on v0.9.12 #44 (ff299f94b) — behavior already merged on base, purely a forgotten slice resync;
• the generated web twins still described v0.9.11 (docs/public-surface-facts.json, web/data/latest-published-release.json, web/lib/facts.generated.ts), while web/lib/changelog.generated.ts was missing the new [Unreleased] entry;
• crates/tui/src/core/engine/tests.rs carried a map(|event| Ok(event)) redundant-closure that the master/main and release lint lanes (--all-targets -D warnings) reject.

CONTRIBUTING.md writes changelog entries on main at merge time and asks PRs carrying changelog hunks to strip them; #56 has now stripped all of these (18f7c7b) and this PR is their dedicated home. A single-purpose chore touching only these files also avoids the merge-conflict churn the policy exists to prevent.

Notes

• Pinning v0.9.12 forced the telemetry trust prose and its contract test to
  evolve together (2b1784c): the baseline test interpolated
  latestPublishedRelease.version into a required "published
  release asked first" phrase, which would demand a false claim for 0.9.12
  (it counts by default and never asked). Following the contract's upstream
  evolution, the prose and the roadmap/faq/telemetryLead copies (en + zh) now
  name the historically fixed asking release — "earlier 0.9.11 release asked
  first" — and the test asserts it as a literal. Catalogs regenerated via
  npm run i18n:gt -- export; npm test passes 407/407.
• The facts refresh pins v0.9.12 (published 2026-09-05). v0.9.13 published 2026-09-14, after this refresh was generated; the next release-manager receipts run should bump latestPublishedRelease again. No gate on the pinvou3-clean lane checks these files (the web freshness checks trigger on master/main only), so this PR does not claim to satisfy them.
• A review pass added ead3874: the asking-release prose mirrored across the en/zh dictionaries and the faq/roadmap pages had no test anchor, so a new contract test asserts the fixed phrasing in every face and rejects the interpolated "published 0.9.11" wording, and providerCountDefinition is now version-free ("the providers of any published release") so the same stale-pin drift cannot recur there. npm test passes 408/408 at head.
  No-Issue: baseline housekeeping split from fix(fork): stop naming absent tools in model-facing text #56; no separate issue tracked.

[github-actions]

Thanks @asto18089 for taking the time to contribute.

This repository is observing a maintainer-managed PR intake gate in dry-run mode, so this pull request is staying open. This note helps maintainers prepare the allowlist before any enforcement is considered.

Please read CONTRIBUTING.md for the expected contribution shape. A maintainer can grant recurring PR access by commenting /lgtm on a pull request.

[JensenChen28]

已审查当前 head 对目标分支的实际差异，未发现需要阻塞合入的问题；提交前重新确认 required checks 通过。核对了发布事实、文案及生成内容一致性变更。本轮以静态审查和远端门禁为依据，未在本机运行完整 Rust workspace 或所有平台测试。