## What
Mock `/api/nodes/search` at the Playwright level in
`test-home-coverage-e2e.js` so the home-coverage E2E search-suggestions
step renders deterministically.
## Why
The `step('search input renders suggestions for a 1-char query', …)`
block was previously softened to a no-op (`pickAnyPubkey` + a
`console.log('SKIP …')`) because the live fetch path flakes on cold CI:
`home.js`'s `setupSearch` wraps `/api/nodes/search` in a try/catch that
swallows network errors, so the dropdown's `.open` class never gets
added and the `waitForSelector('.home-suggest.open')` hung.
Per the triage fix path on #1313, install
`page.route('**/api/nodes/search**', …)` to fulfill a deterministic JSON
body and restore the real assertions.
## Red → Green
- **Red commit `d062b35`** — adds the assertion (type into
`#homeSearch`, wait for `.home-suggest.open`, assert ≥ 1 `.suggest-item`
AND that `HomeFlakeFix-1313` is among the rendered names) **without**
the `page.route` mock. The live fixture nodes don't include that
sentinel name → `assert(names.includes(FIXTURE_NAME))` fires
deterministically. This proves the test is meaningful and reaches the
assertion (no build/import error).
- **Green commit `9fc265a`** — installs the `page.route` handler
returning `{ nodes: [{ public_key: <real fixture pubkey>, name:
'HomeFlakeFix-1313', role: 'companion' }] }`. The dropdown renders the
sentinel name → assertion passes. A real fixture pubkey is reused (via
`pickAnyPubkey`) so downstream steps that hit `/api/nodes/<pk>/health`
still see a valid backend response.
E2E assertion added: `test-home-coverage-e2e.js:115-133`.
## Scope
Test-only. No production code changed. Bonus suggestion in the issue
body about adding a visible error state to `home.js`'s search catch
branch is out of scope here — file separately if desired.
Closes#1313
---------
Co-authored-by: mc-bot <bot@openclaw.local>
## Summary
Master CI failing on `test-home-coverage-e2e.js` (from #1303). Two flaky
tests blocking all downstream PRs:
- search suggestions timeout (5s too tight)
- "Full health" click hits stale element handle
## Fix (test-only)
- Wait for `#homeSearch` visible before fill; raise suggestions wait 5s
→ 15s; accept `.suggest-loading` intermediate state
- Switch Full health click to locator (auto-retries on detach);
pre-click waitForFunction for non-zero bounding rect; force-click
fallback
No production code touched. PII preflight clean.
---------
Co-authored-by: Kpa-clawbot <bot@kpa-clawbot.local>
Co-authored-by: clawbot <bot@openclaw.local>
## Summary
Adds Playwright E2E coverage for `public/home.js` and
`public/path-inspector.js` per the umbrella issue #1297 B5 page-modules
batch. Both files were flagged in the 2026-05-19 frontend coverage audit
as page modules with only 1 E2E mention — well below the >=50% statement
coverage target.
## Files added
- `test-home-coverage-e2e.js` — 12 steps exercising:
- first-time chooser → `showChooser` + `setLevel`
- experienced-user render → `renderHome` + `loadStats`
- search → suggestions → claim → `setupSearch` + `addMyNode`
- My Mesh card render + click → `loadHealth` detail
- card remove → localStorage cleared
- level toggle → checklist accordion expand
- `test-path-inspector-coverage-e2e.js` — 10 steps exercising:
- page chrome (input/submit/help text)
- all 4 validation branches (empty, non-hex, odd-length, mixed lengths)
- Enter-key submit + URL `?prefixes=` replacement
- valid prefixes → results/no-results render
- candidate row toggle + Show on Map → `#/map` hand-off
- deep-link `?prefixes=2c` auto-fill + auto-submit
Both wired into `.github/workflows/deploy.yml` after the #1279 entries.
## Why the existing `test-path-inspector-e2e.js` is not enough
The existing file uses the `@playwright/test` runner (`npx playwright
test …`). CI's `e2e-test` step runs every coverage test as `node
test-*-e2e.js` directly — the `@playwright/test`-style file is never
invoked by CI and contributes zero to the frontend coverage roll-up.
## TDD note
Per AGENTS.md exemption: pure coverage tests on existing UI surfaces, no
production code modified (`git diff origin/master --stat` shows only the
two new test files plus the workflow wiring). Zero behavior change → no
red-then-green commit required.
## Verified
- Both tests pass locally against a fresh Go server backed by
`test-fixtures/e2e-fixture.db` (12/12 + 10/10).
- Preflight (`bash ~/.openclaw/skills/pr-preflight/scripts/run-all.sh
origin/master`): all gates clean.
Refs #1297
Co-authored-by: iavor-bot <bot@corescope>
Kpa-clawbot