pre-call-brieflisted

# Pre-call brief Fifteen minutes of manual research, replaced by one call. Before the user writes or dials, hand them the company's live hiring picture: what is open, how fast it is moving, what has been stuck, and what changed recently. ## Ask for it like this - "Brief me on Anaplan before my 3pm call" - "What is company 1950 hiring right now?" - "Prep me for outreach to this list of five companies" ## How it works One endpoint does the heavy lifting: ``` GET /v1/companies/{company_id}/pre-action-brief ``` Header `X-API-Key` from `$REQBEAT_API_KEY`; never print the key. The response carries: `pulse` (open req count, velocity, direction, surge, weekly momentum), `first_hires` by function with dates, `repost_pain` (stuck roles), `top_reqs` (titles, countries, first_seen, boards), `ats_migrations`, and a provenance block with `as_of`. No `company_id` yet? Resolve it first with `GET /v1/reqs/search?role=...&geo=...` or the keyless MCP tool `who_is_hiring_for`. Company name and HQ come from `GET /v1/companies/{id}/enrichment`. ## Output format Five lines, in this order, each with its date: 1. **Motion:** open reqs, direction, surge yes/no, this week vs last (from momentum buckets). 2. **What they want:** top 3 roles with first_seen dates and source boards. 3. **Pain:** stuck reposts, if any. This is the door-opener line. 4. **Stage signals:** first hires in a function, ATS migration if present. 5. **Talking point:** one sentence the user can open with, built only from