The HaaS shift — Harness-as-a-Service and what to build vs buy — step 8 of 9

Write recommend_harness(team) that takes a team profile and returns the recommended runtime as a string. The team dict has:

• team_size (int)
• latency_critical (bool)
• vertical_constraints (bool) — strict domain/regulatory needs
• language (str — e.g. "typescript", "python")

Decision rules (apply in order):

1. Tiny solo dev with no vertical constraints (team_size <= 1 and not vertical_constraints) → "build-your-own" — no runtime needed at this scale.
2. TypeScript shop with no vertical constraints (language == "typescript" and not vertical_constraints) → "vercel-ai-sdk".
3. Python team, latency-critical or vertical-constrained → "build-your-own" (need full control).
4. Python team, otherwise → "claude-agents-sdk" (default for Anthropic-aligned Python work).
5. Anything else with latency-critical → "build-your-own".
6. Anything else → "openai-agents-sdk".

Four teams run for you. Expected output:

ts-startup: vercel-ai-sdk
py-mid: claude-agents-sdk
solo: build-your-own
regulated-fin: build-your-own