fix: satisfy SDK compliance harness 0.8.0

[marandaneto]

Problem

The SDK compliance workflow and local harness need to use SDK test harness release 0.8.0, with reusable GitHub workflow calls pinned to the release commit SHA instead of a mutable tag/branch. Running the updated harness exposed SDK/adapter compliance gaps in this repository.

Changes

• Pins the reusable SDK compliance workflow to PostHog/posthog-sdk-test-harness commit be8b8d5a3f94a249659844e94832e874f049c1e4.\n- Uses ghcr.io/posthog/sdk-test-harness:0.8.0 for local Docker harness runs / workflow harness version inputs.\n- Updates SDK compliance adapter and/or SDK behavior needed to pass the 0.8.0 compliance contract.

Tests

• SDK compliance Docker harness passed locally with project posthog_dotnet_compliance; unit tests passed.

[github-actions]

posthog-dotnet Compliance Report

Date: 2026-06-30 06:19:33 UTC
Duration: 2333ms

✅ All Tests Passed!

16/16 tests passed

---

Feature_Flags Tests

✅ 16/16 tests passed

View Details

Test	Status	Duration
Request Payload.Request With Person Properties Device Id	✅	249ms
Request Payload.Flags Request Uses V2 Query Param	✅	131ms
Request Payload.Flags Request Hits Flags Path Not Decide	✅	112ms
Request Payload.Flags Request Omits Authorization Header	✅	111ms
Request Payload.Token In Flags Body Matches Init	✅	113ms
Request Payload.Groups Round Trip	✅	117ms
Request Payload.Groups Default To Empty Object	✅	111ms
Request Payload.Person Properties Distinct Id Auto Populated When Caller Omits It	✅	110ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False	✅	111ms
Request Payload.Disable Geoip Omitted Defaults To False	✅	113ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key	✅	110ms
Request Lifecycle.No Flags Request On Init Alone	✅	5ms
Request Lifecycle.No Flags Request On Normal Capture	✅	116ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests	✅	219ms
Request Lifecycle.Mock Response Value Is Returned To Caller	✅	114ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event	✅	216ms

[greptile-apps]

Comments Outside Diff (1)

1. tests/UnitTests/Features/FeatureFlagsTests.cs, line 2374-2404 (link)

   Missing test for DisableGeoIp = true

   The new DisableGeoIp property on AllFeatureFlagsOptions is only exercised indirectly by the existing CallsDecideWithFlagKeyToEvaluate fact (which validates the default geoip_disable: false value). There is no test verifying that passing DisableGeoIp = true results in "geoip_disable": true in the /flags request body. Given the team's preference for parameterised tests, this case is worth adding alongside the existing assertion — a [Theory] with both false and true inputs would cover the full contract.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

_{Reviews (1): Last reviewed commit: "chore: add SDK compliance harness 0.8.0" | Re-trigger Greptile}

[marandaneto]

Addressed Greptile feedback about DisableGeoIp = true coverage in ed6c8e7: CallsDecideWithFlagKeyToEvaluate is now parameterized for both false and true and asserts the serialized geoip_disable request value.

[greptile-apps]

_{Reviews (2): Last reviewed commit: "fix: keep flags api key field" | Re-trigger Greptile}