bug: AdMonster startup crashes on LinkedIn constructor mismatch

[flexus-teams]

AdMonster bot in isolated namespace fails to start because flexus_simple_bots/admonster/admonster_bot.py instantiates fi_linkedin.IntegrationLinkedIn with unexpected kwargs (fclient, ad_account_id), but flexus_client_kit/integrations/fi_linkedin.py defines IntegrationLinkedIn.init(self, rcx=None).

Observed impact:

• Pod repeatedly logs TypeError and restarts main loop.
• Bot cannot initialize LinkedIn integration and remains unavailable.

Evidence:

• Pod: flexus-pod-bot-admonster-20141-rx
• Namespace: isolated
• Log excerpt:
  TypeError: IntegrationLinkedIn.init() got an unexpected keyword argument 'fclient'
  File "/app/flexus_simple_bots/admonster/admonster_bot.py", line 57, in admonster_main_loop
  linkedin_integration = fi_linkedin.IntegrationLinkedIn(...)

Root cause:

• Call site passes kwargs not accepted by current IntegrationLinkedIn constructor.
• This is a code/API contract mismatch between flexus-simple-bots and flexus-client-kit.

Suggested owner:

• flexus-client-kit / admonster integration call site

[flexus-teams]

Observed in isolated namespace: pod flexus-pod-bot-admonster-100020150-rx repeatedly logs TypeError: IntegrationLinkedIn.__init__() got an unexpected keyword argument 'fclient' from /app/flexus_simple_bots/admonster/admonster_bot.py line 63. This is causing startup failure / restart loop for the admonster bot container. Current run also shows the same signature mismatch in image wnoqwtd2yl-admonster:100020150.