#4497 docs(help): point verification at read-only commands, not bare find

Summary

The root help listed find among verification commands, but bare find clicks by default, so an agent checking a field after fill tapped it. Root help, help workflow, help manual-qa, help validate, help react-native, the MCP server guide, and the skill card now point verification at the read-only commands (wait, is, get, the settled diff); where find stays, they say it acts unless its action is exists. The help-conformance scorer and case matchers share one parseFindArgs-based check that accepts only find … exists, with counterexamples for bare and mutating find. find's default action is unchanged.

12 files touched. Fixes #4485.

Validation

• Tested SHA 955ebd06db. Review rounds:
  • Round 1: workflow, react-native and validate help; strict matcher; counterexamples.
  • Round 2: escaped quotes in a quoted query.
  • Round 3: a concrete find text "..." exists example.
  • Round 4: find verification is classified with parseFindArgs instead of a regex grammar.
  • Round 5: an unsupported find action scores false; focused find-verification test.
  • Round 6: the TS command validator parses find commands, so the scorers stay plain JS.
• pnpm exec vitest run --project unit-core src/commands/schema/ src/mcp: 332 passed. Root help still fits the first 30 lines, and the workflow topic stays under its byte budget.
• pnpm exec vitest run scripts/__tests__/help-conformance-expectation-falsification.test.ts scripts/__tests__/help-conformance-topic-coverage.test.ts scripts/__tests__/help-conformance-sample-outputs.test.ts: 62 passed.
• pnpm check:quick: pass.
• Docs/help only: no runtime paths change, so device runs do not apply. CI owns the full gate.

🤖 Generated with Claude Code