Exclude internal traffic from public demand summaries - #210
Merged
Merged
Conversation
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.
AG advertised its authenticated empty-search canary as unmet demand because the public capability summary read unfiltered serving-cache events. The A2A capability map and gap scout used the same summary; the scout also built proposals from raw query labels.
Use the existing demand-feed qualification and deduplication rules against one bounded durable snapshot. Counts and recency now include qualifying asks only, with identity-backed and heuristic evidence kept distinct. HTTP and A2A expose measurement coverage and explicitly describe historical asks as potential leads rather than funded jobs. The gap scout derives proposals from those same qualified requests. Existing raw history, prices, payment handling and capability supply filtering remain unchanged.
Validation: 88 focused tests passed. Full local suites passed 2,231 JSON and 2,232 SQLite tests, with 25/24 expected skips respectively, counting separate successful reruns of two loopback-dependent tests that the initial sandbox could not execute. Contract regeneration produced no drift. The initial regression suite reproduced the current failures before implementation; added coverage exercises the actual authenticated empty-search request, mixed-traffic counts and dates, legacy requests, durable retention and scout proposals. The protected CI matrix passed for published head c6a8c8e (run 35574536880). The ship workflow merged b1931c6 and passed its deployment-aware release gate (run 35574520193). The TypeScript simulation verifier also passed locally using the existing matching darwin-arm64 esbuild binary; it exercises synthetic data, not real payments.