fix: Call identify hooks during init.

[beekld]

Requirements

• I have added test coverage for new or changed functionality
• I have followed the repository's pull request submission guidelines
• I have validated my changes against all supported platform versions

Related issues

N/A

Describe the solution you've provided

Before this change, beforeIdentify and afterIdentify were only called when identify was called. After this change, they are also called as part of init.

Describe alternatives you've considered

None.

Additional context

I don't think this would be considered a breaking change, but I wouldn't mind a second opinion. The change in behavior is observable by the user, but the new behavior is what was originally intended. So I would consider this a bugfix, and would not expect customers to need to make any changes to their code to deal with the change.

---

Note

Medium Risk
Behavior change: beforeIdentify/afterIdentify hooks now run implicitly during LDClient.init, which could affect apps/plugins that assume hooks only fire on explicit identify calls. The change touches initialization flow across multi-environment instances but is covered by updated and new instrumentation tests.

Overview
Identify hooks now run during LDClient.init. During startup, each environment instance invokes the identify hook series (beforeIdentify via hookRunner.identify, followed by afterIdentify with COMPLETED/ERROR based on startup outcome).

Tests were updated to account for the new implicit identify on init, and a new plugin test ensures identify hooks fire once per configured environment (primary + secondary) and again for explicit identify calls.

^{Written by Cursor Bugbot for commit c02c568. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[kinyoklion]

I also agree this is non-breaking. It was the intended behavior, also the primary consumer of this is also us. For our observability plugins.

[tanderson-ld]

The commit for updating to identify per instance did not contain any unit test changes. Consider seeing if it is trivial to test for the multi instance case where each instance gets its identify hook invoked. If it is not trivial it is not the end of the world to add.

[beekld]

The commit for updating to identify per instance did not contain any unit test changes. Consider seeing if it is trivial to test for the multi instance case where each instance gets its identify hook invoked. If it is not trivial it is not the end of the world to add.

Good idea, added a new test for that.