fix(llma): use distinct_id from outer context if not provided

[ethanporcaro]

Related to #443

Right now, the LLM analytics wrappers accept a posthog_distinct_id parameter, but override any existing distinct_id, even if the parameter is None.

The utility functions pass

ph_client.capture(
                    distinct_id=posthog_distinct_id or posthog_trace_id,
...

However, if posthog_distinct_id is None (default) it will default to the posthog_trace_id, even if an ID exists on the outer context.

This PR modifies the logic to do the following:

• If a custom distinct_id is passed by parameter, it is used in identify_context
• If no context exists (meaning the above never happened, and no existing context is available), identify with the trace_id.
• Call ph_client.capture without the distinct_id parameter, so that it uses whatever was set from the above steps.

Let me know if any changes are needed or if I should implement this differently.

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[ethanporcaro]

Some of these failed tests are passing on my machine. Do the tests set an outer distinct_id?

[ethanporcaro]

Nevermind, I realize I was running them incorrectly. I think I found the issue and will push a commit soon

[ethanporcaro]

Should be good to go

[andrewm4894]

Thanks for the contribution @ethanporcaro! Great bug find — the outer context distinct_id was indeed being ignored.

I pushed a commit on top with a few tweaks:

1. Fixed $process_person_profile bug — The personless check (posthog_distinct_id is None) didn't account for outer context distinct_id, so events from users who set identify_context() in an outer scope would be incorrectly marked as personless. Changed to use a has_person_distinct_id flag that checks both the explicit param and the context.

2. Fixed typo — "district_id" → "distinct_id" in comments.

3. Added test coverage — 4 new tests covering the key scenarios:

   • No distinct_id provided → uses trace_id, marked personless
   • Explicit posthog_distinct_id param → uses it, creates person profile
   • Outer context identify_context() → uses outer context id, creates person profile
   • Both explicit param and outer context → explicit param wins

[ethanporcaro]

Awesome, thanks for the help