Patch and optionally submit a first-party homeowners or umbrella intake.

Applies top-level intake edits for the consumer-prefill follow-up API. Authenticate with Authorization: Bearer <intake_access_token> from the latest consumer-prefill follow-up response. Use this after gathering context-backed answers; for homeowners, recover core shopper and occupancy facts from user-controlled context first, then let Coverage Cat carry estimated home-editor fields into one final review card. After a homeowners application is submitted, this same patch route can answer messy carrier or shopper follow-up in-thread with message_reply; when GET /api/intake/{uid}/issues shows conversation.reply_pending, echo the answer here and pass reply_to_message_id from that conversation payload when Coverage Cat returned one. For umbrella, use the staged review turn to send the bundled shopper-owned details and any corrections, then set confirm_submission: true on that same final turn. Use canonical umbrella count corrections such as umbrella_details.motorized_vehicle_count, never send vehicles rows on this pre-submit patch, and omit top-level field_estimates unless you are certain each field path matches a current umbrella review field. Until that final submit happens, say explicitly that the application is not submitted yet, ask for any remaining items in plain English, and present gathered details plus remaining items as short labeled bullets or sections rather than a prose paragraph. If any shown value is estimated, mark each estimated bullet label or value with *, include the short note * = estimated once above and once below the list, and do not prefix every estimated line with [Estimated]. If the staged review shows a wrong estimated umbrella count from context, patch the canonical umbrella_details.* count field before you show the final review. Coverage Cat will not resume or expose a prior consumer umbrella draft based on email alone. Continue an existing consumer draft only through the issued uid plus the current hidden MCP session or latest intake_access_token handoff. Normalize shopper birthdays from MM-DD-YYYY to YYYY-MM-DD before you send them. Reserve a single human interruption for the final review-and-submit step, keep umbrella credit consent out of this turn, and keep offer selection and post-choose bind continuation on the dedicated /select, /bind, and /attach routes.