P1: bob bot uses obsolete subscription argument

Start with flexus_client_kit/ckit_ask_model.py:87-120 and the subscription setup in ckit_bot_exec.py, especially subscribe_and_produce_callbacks. Compare the client subscription shape with the backend schema, then verify that flexus-pod-bot-bob-30005-rx no longer exits with the unknown-argument error or enters CrashLoopBackOff.

Original Logs

20260504 14:49:40.392 fclnt [INFO] FlexusClient service_name=bob_30005_r_ api_key=None http://backend-v1-service.flexus.svc/v1/jailed-bot
20260504 14:49:40.393 stexe [INFO] Connecting ws://backend-v1-service.flexus.svc/v1/jailed-bot
20260504 14:49:40.462 btexe [ERROR] 🛑 That looks bad, my key doesn't work: {'message': "403: Whoops your key didn't work (2).", 'locations': [{'line': 2, 'column': 3}], 'path': ['bot_confirm_exists']}
20260504 14:51:40.622 stexe [ERROR] 🛑 3 exceptions in 5 min, exiting
gql.transport.exceptions.TransportQueryError: {'message': "Unknown argument 'want_emsg_types' on field 'Subscription.bot_threads_calls_tasks'. Did you mean 'want_erp_tables' or 'want_messages'?", 'locations': [{'line': 12, 'column': 5}]}

Error Summary

The bob bot pod flexus-pod-bot-bob-30005-rx in isolated is in CrashLoopBackOff. It repeatedly reconnects to the backend, but the subscription fails because the GraphQL schema no longer accepts want_emsg_types on Subscription.bot_threads_calls_tasks.

Stacktrace

gql.transport.exceptions.TransportQueryError: {'message': "Unknown argument 'want_emsg_types' on field 'Subscription.bot_threads_calls_tasks'. Did you mean 'want_erp_tables' or 'want_messages'?", 'locations': [{'line': 12, 'column': 5}]}

Root Cause

• File: flexus_client_kit/ckit_ask_model.py:87-120
• Function: subscription setup in ckit_bot_exec.py / subscribe_and_produce_callbacks
• Why: the bot image is sending a stale GraphQL subscription shape that still includes want_emsg_types, but the backend schema only exposes want_messages / want_erp_tables now. This is a code/package mismatch and causes the bot to exit after repeated transport errors.
• Git blame: manual inspection only; the failing line is in the deployed client-kit image, not a cluster issue.

Affected

• Pods: flexus-pod-bot-bob-30005-rx
• Namespace: isolated
• Occurrences: repeated every restart