[Testing] Repair stale command-palette locator in headed manual audit

[Chris0Jeky]

Observed failure

The documented npm run test:e2e:audit:headed path fails deterministically in manual-audit.spec.ts at the command-palette search step. The palette is open and healthy, but the test waits 45 seconds for the obsolete placeholder Type a command or search...; production has used Type a command or search boards and cards... since commit 6fe147b4.

The same user journey is already located robustly in smoke.spec.ts through getByRole('combobox', { name: 'Command palette search' }), matching the accessible product contract introduced before this audit drift was detected.

Observed on exact candidate 7f8f2137 over main 6cdc8fd1. The core capture → review → explicit apply → board → provenance journey and later advanced capture/board/filter cases passed before this single failure.

Scope

• replace the placeholder-coupled manual-audit locator with the stable accessible role/name contract
• keep the product placeholder and command behavior unchanged
• add no new UI or abstraction
• classify any subsequent full-audit failure independently rather than hiding it

Acceptance criteria

• the command-palette audit case passes against a fresh isolated synthetic E2E database
• npm run test:e2e:audit:headed completes green, or every remaining failure is separately root-caused and tracked
• the existing command-palette smoke path remains green
• changed-file lint and git diff --check pass

Evidence classification

This is a pre-existing deterministic QA-harness defect, not a product navigation failure and not a flaky timeout.