Skip to content

chore(client-contract): recapture the served document and re-record at apis 7af2d8dd - #56

Merged
jm-rivera merged 2 commits into
devfrom
chore/recapture-apis-7af2d8dd
Nov 15, 2026
Merged

jm-rivera merged 2 commits into
devfrom
chore/recapture-apis-7af2d8dd

Conversation

@jm-rivera

Copy link
Copy Markdown
Contributor

Recaptures served/openapi.json and served/SOURCE.json from dfo-apis 7af2d8dd and re-records the client-contract scenarios against dev at that commit.

Changes

  • served/openapi.json: adds /api/graph/schema/{usage,terms,check} and /api/{datasets,graph,search}/json-schema with their schemas, drops /api/datasets/schema, /api/search/schema and GraphSchema, and CapabilityCaps gains the schema-check caps.
  • 124 scenarios re-recorded. DAC2a answers now read the bilateral composite, so their specs carry provenance/ONEDAC2aBilateral, the "(bilateral flows)" sentence and new spec ids.
  • refs/ref-one-member.json follows fetch-spec-party-totals-kept.

Testing: tools/validate_client_contract.py passes (147 action rows, 35 client codes, 126 scenarios); tests/test_rules.py and tests/test_analysis_rules.py pass (297).

…t apis 7af2d8dd

The served document gains the graph schema usage, terms and check routes and the per-API json-schema routes, and drops the datasets and search schema routes. DAC2a scenarios now read the bilateral composite, so their specs carry provenance/ONEDAC2aBilateral, the "(bilateral flows)" sentence and new spec ids; refs/ref-one-member.json follows fetch-spec-party-totals-kept. The long-build scenarios start later, as each re-record does.
The two record runs moved the DAC and OECD long-build picks to 1973 and 1974, so the scans start at 1974 and 1975.
@jm-rivera
jm-rivera merged commit 92eb187 into dev Nov 15, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant