Migration tooling: golden parity harness + client inventory (Phase 0/2)#1602
Closed
PavelMakarchuk wants to merge 5 commits into
Closed
Migration tooling: golden parity harness + client inventory (Phase 0/2)#1602PavelMakarchuk wants to merge 5 commits into
PavelMakarchuk wants to merge 5 commits into
Conversation
- tools/parity/parity.py: freezes golden response snapshots from a reference deployment (corpus = real partner payloads + synthetic basics) and diffs any candidate endpoint against them with numeric tolerance. Goldens captured from production (calculate_demo) included. Found prod UK breakage (#1601) on first run. - tools/parity/inventory.py: read-only Phase-0 inventory against the prod user-analytics Cloud SQL DB -> per-client compatibility matrix (volumes, countries, channels, errors, variables). Key finding: 100% of 90-day traffic is US; frontier channel is in active use. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Exercises the validation/warnings layer the v2 endpoint hasn't ported yet: partial-month warning, deprecated-input drop+warning, axes sweep. Goldens captured from production. 8 cases total. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
corpus_from_inventory.py turns each top client's real variable usage (requested outputs, entities, period granularity, inferred state) into an executable synthetic case — passing parity on client-<id> means the candidate covers that client's contract. Goldens captured from production for the top 5 clients (CO, WA, CA screener profiles). 13 golden cases total. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Prod returns 400 with an errors list for unknown variables; the v2 experiment doesn't port that validation yet. Golden captured from production; parity.py diff now checks status + error body for expected_status!=200 goldens. 14 cases total. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Tooling for the api-v2 migration (experiment; see plan discussion).
frontierchannel is actively used.First cross-implementation diff against the resurrected v2 household endpoint: 5/5 parity on all partner payloads.
🤖 Generated with Claude Code