Fix verify hint listing LLM-hidden assertion tools

[pengdev]

Summary

trailblaze verify's LLM hint told the model it MUST call one of assertVisibleBySelector, assertVisibleWithText, or assertWithAI to confirm an assertion — but the first two are registered @TrailblazeToolClass(surfaceToLlm = false, ...) (one's own source comment reads "DO NOT USE GIVE THIS TOOL TO THE LLM"; the other is @Deprecated). The model can never actually see or call either one.

Result: verify reliably returned exit 1 (FAILED) regardless of what was actually on screen — reproduced on a real Android emulator against claude-sonnet-5, where the failure reasoning showed the model hunting for a tool it could never find, even while correctly describing a genuinely healthy render in the same response.

This swaps the two unreachable names for the two tools actually surfaced to the LLM today — assertVisible and assertWithAi (also fixes a casing typo, "assertWithAI" → "assertWithAi") — and drops the now-stale Oxford comma from the original 3-item list.

Verification

• Confirmed via @TrailblazeToolClass annotations in trailblaze-common that assertVisibleBySelector/assertVisibleWithText are hidden (surfaceToLlm = false) and assertVisible/assertWithAi are not.
• Confirmed assertVisible is genuinely usable in verify mode and still produces a recordable trail (delegates internally to the recordable assertVisibleBySelector), via existing tests StepToolSetVerifyModeTest and StepToolSetDirectToolsTest.
• Swept the repo for any other LLM-facing hint/prompt referencing a hidden tool — found none; this was the only one.
• Built from source (scripts/install-trailblaze-source.sh) and re-ran the same verify assertion against a live Android emulator before and after the fix:
  • Before: exit 1 on both a healthy map render and a genuine negative (Home screen, no map) — same failure both times, reasoning stuck on the nonexistent tool.
  • After: exit 0 on the healthy render ("not blank" correctly confirmed), exit 1 on the negative — this time for the correct reason ("home launcher, no map"), no tool-hallucination in the reasoning.

Test plan

• Read-only source verification of tool visibility annotations
• Existing unit tests (StepToolSetVerifyModeTest, StepToolSetDirectToolsTest) confirm assertVisible behaves correctly in verify mode
• Live end-to-end re-test on an Android emulator with a real Anthropic key, both before and after the fix, both a healthy and a broken render