r""" Condition 1: a telehealth visit needs POS=11 and M1=GT on every CPT/HCPCS row. python tests\test_telehealth_fix.py Reuses the existing `ub_claim.html` / `progress_note.html` fixtures rather than adding new ones — the real note eCW served on 2026-09-07 already documents a Telehealth visit (see `progress_note.html`'s History of Present Illness section, `TELEHEALTH`), and detection never touches the DOM at all, so the negative case is just a plain string. Local headless chromium only, exactly like test_claim_form.py: no proxy, no login, no eCW. This is the bot's first WRITE path, so what matters most here is proven *before* it ever runs against a real claim: * detection matches "telehealth", "telephone", and a standalone "TH" token (case-insensitive for the first two, word-bounded and case-sensitive for "TH" — see claim_form.note_mentions_telehealth's docstring for why) and nothing looser than that — a payer/claim-specific "TeleHealth" or "TELEHEALTH VISIT" must still match, but "MONTH" or "WITH" must not; * the write only ever touches real CPT/HCPCS rows — the blank padding row and the trailing "*" entry row (neither carries a CPTROW_ id, exactly the trap `claim_form.extract()`'s own reader already guards against) must never be touched; * every field is read back after the fill, so a write that silently didn't take is a **visible** assertion failure here, not a silent no-op on a real claim; * Cancel and OK are both wired in this fixture (they are not in ub_claim.html's original form — see the added