PR Custody

fix(meta): expose messaging_type/tag on Instagram + dedupe across Meta Send API actions

@singhbharath03checks n/achecks…fix/meta-send-api-messaging-window → master5 files · +87 −52review: @zen-agentupdated 4w ago

▸Description

Bug: INSTAGRAM_SEND_TEXT_MESSAGE (and INSTAGRAM_SEND_IMAGE) fail in production with status 403 — error_subcode 2534022: "This message is sent outside of allowed window." The actions had no way to set messaging_type=MESSAGE_TAG + tag=HUMAN_AGENT, the only escape from Meta's 24-hour reply window.
Fix: Introduce mercury/utils/meta_messaging.py with MessagingType / MessageTag enums, a MessagingWindowMixin (defaulted fields + validator), and an apply_messaging_window(payload, request) helper. Route Instagram's two send actions and Facebook's two send actions through it.
Dedupe: Facebook previously implemented this surface twice inline — send_message.py used a model_validator, send_media_message.py raised mid-execute(). Both now share the same primitive. The mid-execute raise in send_media_message.py is gone; validation happens at request-construction time.

Scenario	Before	After
Instagram default reply within 24h	works (`RESPONSE` implicit)	works (`RESPONSE` explicit, no behavior change)
Instagram reply outside 24h	403 / 2534022 — no surface to fix	caller can pass `messaging_type=MESSAGE_TAG`, `tag=HUMAN_AGENT`
`MESSAGE_TAG` without `tag`	(Instagram) hit API and 400; (FB) raised inline	pydantic `ValidationError` before any HTTP work
Facebook callers passing `messaging_type="RESPONSE"` etc.	works	works (string → enum coercion)
Invalid string like `messaging_type="bogus"`	would have failed at the API	now fails at pydantic

ruff check + ruff format --check: pass
nox -s chk_app -- apps/instagram (ruff + mypy 1.13): pass
nox -s chk_app -- apps/facebook (ruff + mypy 1.13): pass
nox -s chk (full repo, every app + mercury core + tests): all checks passed
Mercury runtime parse/schema checks across all 4 actions:
- default (no messaging_type) — parses + serializes correctly
- MESSAGE_TAG without tag — raises at RequestWrapper.parse() boundary
- MESSAGE_TAG + HUMAN_AGENT — parses; payload contains both fields
- Facebook string inputs ("RESPONSE", "ACCOUNT_UPDATE", etc.) — coerce cleanly to enums
- LLM-facing tool schema (RequestWrapper.schema()) contains messaging_type, tag, MESSAGE_TAG, HUMAN_AGENT for all four actions
No existing tests under tests/*instagram* / tests/*facebook* / tests/*meta_messaging* to regress.

Smoke-test the production failing call via run.py against a connected Instagram Business account with a stale PSID (>24h since last user message):
- Confirm default call still 403s with error_subcode=2534022 (reproduces the bug)
- Confirm {"messaging_type": "MESSAGE_TAG", "tag": "HUMAN_AGENT"} succeeds (requires Human Agent app permission)
Smoke-test INSTAGRAM_SEND_IMAGE with the same MESSAGE_TAG / HUMAN_AGENT params
Verify Facebook FACEBOOK_SEND_MESSAGE regression: existing string messaging_type="RESPONSE" callers continue to succeed
Verify Facebook FACEBOOK_SEND_MEDIA_MESSAGE regression: existing callers using messaging_type + tag continue to succeed

🤖 Generated with Claude Code

loading diff…