ci: restore .NET capture compliance coverage - #318
Draft
dustinbyrne wants to merge 1 commit into
Draft
Conversation
Contributor
posthog-dotnet Compliance ReportDate: 2026-09-07T20:16:52.234855+00:00 ✅ All Tests Passed!47/47 tests passed Capture Tests✅ 30/30 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💡 Motivation and Context
The compliance adapter omitted capture capabilities, so normal CI discovery ran only the 17 feature flag cases and silently skipped capture.
capture_v0andencoding_gzipcapabilities.Capture, serialization, compression, retries, flag results, and called-events continue through the existing public SDK methods. This is adapter/CI coverage work with no SDK API, default, or release changes.
💚 How did you test it?
Linux/Docker execution is delegated to this PR's CI. Optional V1, dedicated AI capture, and non-gzip codecs are not covered. Existing adapter UUID-response/state-accounting and
force_remote:falselimitations are outside these 47 assertions and unchanged.📝 Checklist
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Implemented with the Pi coding agent using repository file tools, Bash, .NET, Python, Git, and GitHub CLI. A separate read-only agent reviewed the same commit and found no issues. Human review is required. The local agent session is not publicly accessible.