Add notebook pattern validation and standardize setup cells

[petermuehlbacher]

Summary

• New CI check: docs-site/scripts/validate-notebook-patterns.py validates all 18 case study notebooks enforce three patterns:
  1. Conditional %pip install everyrow (via try/except ImportError)
  2. Conditional EVERYROW_API_KEY setup (via if not in os.environ)
  3. All everyrow op calls (merge, screen, dedupe, rank, agent_map) wrapped in async with create_session(name="...") as session: with session.get_url() for observability
• All 18 notebooks fixed: Inserted standardized setup cells and wrapped bare everyrow op calls in create_session contexts
• CI integration: Added validation step to deploy-docs.yaml workflow

Test plan

• uv run python docs-site/scripts/validate-notebook-patterns.py — all 18 notebooks pass
• Verify CI pipeline runs the new validation step on PR

🤖 Generated with Claude Code

[sentry]

Bug: The call to await client.__aexit__() is incorrect as it's missing the three required arguments for an async context manager, which will cause a TypeError on exit.
_{Severity: HIGH}

Suggested Fix

The __aexit__ method should be called with the standard three None arguments to signify a clean exit from the context manager. Change await client.__aexit__() to await client.__aexit__(None, None, None) in src/everyrow/session.py.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: docs/case_studies/dedupe-crm-company-records/notebook.ipynb#L20-L26

Potential issue: The `__aexit__` method in `src/everyrow/session.py` is called without
any arguments. The async context manager protocol requires `__aexit__` to be called with
three arguments: `exc_type`, `exc_val`, and `exc_tb`. The `AuthenticatedClient` forwards
this call to the underlying `httpx.AsyncClient`, whose `__aexit__` method will raise a
`TypeError` because it's missing the required positional arguments. This will cause an
unhandled exception whenever a session is created and closed using the `create_session`
context manager, such as when `single_agent()` is called without an explicit session.

_{Did we get this right? 👍 / 👎 to inform future reviews.}