v0.2.1 — employer search matches whole words

Employer search was returning wrong companies. Fixed.

search_layoff_notices(company="Ford") returned 219 notices whose top hits were Stanford Health Care, Hanford, Medford. The matcher tested substring containment against the company fields, so any employer name that merely contained your string came back as a match.

Measured on the live 61,345-row archive across 30 realistic employer queries:

query	before	after	false rows removed
Ford	219	67	152 (69% of results were wrong)
Apple	107	65	42
Intel	121	100	21
Amazon	211	203	8
Walmart / United Airlines / Tesla	—	unchanged	0

Across all 30 queries: 336 of 4,310 returned rows (7.8%) were false matches, and 8 of the 30 queries were affected.

What changed

• search_layoff_notices, employer_layoff_history and agency_revisions now match on whole words: every word of your query must appear as a complete word in the notice's company, company_canonical or company_dba. united airlines still matches United Airlines, Inc.; ford no longer matches Stanford.
• This is the same rule the paid WARN Watch alert matcher has always used, so the two can no longer disagree about what "Ford" means.
• Responses now carry company_match_rule, and a zero-hit search returns similar_company_names — real canonical names that contain your string — so an agent retries with a working string instead of reporting that the archive has no such employer.
• Tool schemas state the matching rule, so a model reads it before calling.

No breaking changes to tool names, arguments or response shape. Install is unchanged.

Data: 61,345 notices, 48 states, 1988 to today, rebuilt daily, CC BY 4.0, no API key.