[Qiyuanqiii]

Summary

After a workspace search request failed, clicking Search again or pressing Enter with the same keyword left the error visible because the query state did not change. An errored query now refetches when resubmitted unchanged. Successful searches, keyword validation, and the API contract retain their existing behavior.

Stacked on #448 (Qiyuanqiii/workspace-markdown-preview).

Validation

• The button and Enter regression cases both failed on b6e89e8c481bb38293d584a9204b36916528c834 and pass with the fix.
• Explorer and Markdown preview suites: 21 tests passed.
• TypeScript build and Vite production build passed; Vite retains the existing large-chunk warning.
• OCR completed the changed production component with zero findings. Its default rules exclude test files.
• Real Chrome, production renderer, and production API: temporarily abort workspace-search requests, remove the interruption, confirm the API returns 200, and resubmit the unchanged keyword. Before: no new request and the error remains. After: a new request returns 200 and the result appears.
• Go tests, vet, and CLI smoke tests: not run for this frontend-only change.

The PNGs below are committed, unmodified browser captures. Setup and reproduction notes are in the acceptance README.

Before, after the connection recovers and Search is clicked again:

After the same action:

Surface governance

• No Surface is added, promoted, downgraded, deprecated, or removed.
• Registry item(s): N/A — no Surface change.
• Target tier / transition: N/A — no Surface change.
• Entry criteria / decision: N/A — no Surface change.
• Owner: N/A — no Surface change.
• Shared Go Application contract: Unchanged workspace search contract.
• Authority impact: Existing read-only search only.
• Supported platforms: Existing browser and desktop frontends.
• Release / test evidence: Focused tests and browser captures above.
• Compatibility strategy: Existing request shape and query keys.
• Deprecation window: N/A — no Surface change.
• Removal / rollback plan: Revert this commit.

Audit

• No credentials or local runtime data are included.
• Policy, workspace, sandbox, and persistence boundaries were reviewed.
• Acceptance README records the changed behavior and verification.