Post-fix 96-Q eval (54.8% factual) surfaced 8 failures on room-rent /
sub-limit / cap questions where the bot's reply omitted the specific
room category ("Single Private", "Twin Sharing", "General Ward").
That's 19% of remaining failures.

Root cause: the policy table with the structured cap is ONE chunk in
Chroma, but at top_k=5 it loses to other relevant prose chunks
(definitions, sub-limit prose elsewhere in the doc) → the LLM never
sees the table → can only paraphrase from looser context → misses
the row categories.

Fix: when the query matches a table-cell trigger pattern, raise
effective_top_k to 10 for that query only. Trigger regex covers:

• room rent / sub-limit / sub-limits
• copay / co-pay
• cap on / capped at / sum insured limit
• single private / twin sharing / general ward
• no-claim bonus / NCB

Verified the regex fires on the eval's failing questions and ignores
generic waiting-period queries (which retrieve fine at top_k=5).

Combined with KI-046 (refusal precision on adversarial OOS questions,
+12pp expected), this addresses ~45% of remaining failures. Fresh
eval will land the actual lift number.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>