feat(dibbs,exclusions,sbir): add SDK support + refresh stale contract

The vendored API contract had gone stale by seven resources — it tracked 25
against Tango's current 32 — so both the conformance and shape-coverage checks
were validating against out-of-date truth. They could not see DIBBS, exclusions,
SBIR, or budget/accounts at all. Refreshing it surfaced those six unimplemented
endpoint families plus 72 additional fields on existing resources.

Add full SDK support for the six families Tango shipped in v4.16-v4.18:
list_/get_ pairs for dibbs rfqs, rfps and awards, exclusions, and SBIR topics and
solicitations, with all 85 filter params, shape schemas, ShapeConfig defaults,
and new DibbsRfq/DibbsRfp/DibbsAward/Exclusion/SbirTopic/SbirSolicitation models.
Documents the two API behaviors that bite: is_open / is_currently_excluded are
derived at query time (filter with open/active instead), and DIBBS
total_contract_price is the order total repeated per line item — never sum it.

Fix the conformance checker's false stale-param reports. It resolved SDK args to
API params only through an explicit api_param_mapping dict, so methods expressing
the translation as tuple tables looked like they exposed ~55 params the API
rejects. They do not — list_budget_accounts correctly sends apportioned__gte and
account_title__icontains. The checker now understands both tuple forms across
Assign, AnnAssign and inline for-iterables, with api_param_mapping still winning.
That let budget/accounts be conformance-checked for the first time; its real
missing lookup variants are baselined. Also allowlists budget/accounts `search`,
which the endpoint honors but the contract omits (verified live).

Verified: 450 tests pass, mypy clean, ruff clean, conformance passes with 0
errors, shape-coverage gate at 0, and all 12 new methods exercised against the
live API (list + detail round-trip for each family).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: vdavez

CHANGELOG.md

@@ -8,6 +8,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 
 ### Added
+- **DIBBS, exclusions, and SBIR/STTR endpoint support.** Six endpoint families
+  Tango shipped in v4.16–v4.18 had no SDK support at all — no models, no methods.
+  Added `list_dibbs_rfqs`/`get_dibbs_rfq`, `list_dibbs_rfps`/`get_dibbs_rfp`,
+  `list_dibbs_awards`/`get_dibbs_award`, `list_exclusions`/`get_exclusion`,
+  `list_sbir_topics`/`get_sbir_topic`, and
+  `list_sbir_solicitations`/`get_sbir_solicitation`, with all 85 filter params,
+  shape schemas, and `ShapeConfig` defaults. New models: `DibbsRfq`, `DibbsRfp`,
+  `DibbsAward`, `Exclusion`, `SbirTopic`, `SbirSolicitation`.
+
+  Two API behaviors are worth knowing. `is_open` (DIBBS) and
+  `is_currently_excluded` (exclusions) are derived at query time, so filter with
+  the `open` / `active` kwargs rather than shaping on those fields. And DIBBS
+  `total_contract_price` is the *order* total repeated on every line item —
+  never sum it across rows; deduplicate on award + delivery-order number first.
 - **Reverse shape-coverage: the SDK now captures every field and expand the API
   returns.** The conformance check only validated one direction — that the SDK's
   shape constants reference *allowed* fields. Nothing checked the reverse, so the
@@ -33,6 +47,29 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   Regenerate the overlay with `scripts/generate_shape_overlay.py` (from the vendored
   contract + `contracts/observed_shape_types.json`, no API key); refresh the type
   observations with `scripts/probe_shape_types.py` (maintainer-run, needs a key).
+
+### Fixed
+- **Refreshed the vendored API contract, which had gone stale by seven
+  resources.** It tracked 25 resources against Tango's current 32, so the
+  conformance and coverage checks were validating against out-of-date truth and
+  could not see DIBBS, exclusions, SBIR, or `budget/accounts` at all. Refreshing
+  it also surfaced 72 additional fields on existing resources, now covered.
+  Nested routes are keyed with a slash (`budget/accounts`), which silently broke
+  the old `budget_accounts` mapping — both keys are now accepted.
+- **`check_filter_shape_conformance.py` no longer reports false stale params.**
+  It resolved SDK arguments to API params only through an explicit
+  `api_param_mapping` dict, so methods that express the translation as tuple
+  tables — `("account_title__icontains", account_title)` and
+  `range_filters = (("apportioned", apportioned, apportioned_gte, ...))` — looked
+  like they exposed dozens of params the API rejects. They do not:
+  `list_budget_accounts` correctly sends `apportioned__gte`, `fiscal_year__lte`,
+  and `account_title__icontains`. The checker now understands both tuple forms
+  (in `Assign`, `AnnAssign`, and inline `for` iterables), with an explicit
+  `api_param_mapping` still taking precedence. This let `budget/accounts` be
+  conformance-checked for the first time; its genuinely missing lookup variants
+  (`agency_code__in`, `bureau_name__icontains`, …) are now baselined.
+
+### Added
 - **Contract-first conformance system.** The canonical API filter/shape
   contract is now vendored at `contracts/filter_shape_contract.json` (refresh
   with the new `scripts/refresh_contract.py`), so the conformance check runs

contracts/conformance_baseline.json

@@ -1,12 +1,35 @@
 {
   "_comment": "Accepted SDK coverage gaps vs the API contract. Params listed here downgrade from error to warning in scripts/check_filter_shape_conformance.py. Each entry is tracked backlog: remove it in the same PR that adds the param to the SDK. Run the checker with --suggest for ready-to-paste typed parameter scaffolds.",
   "missing_filters": {
-    "contracts": ["key"],
-    "entities": ["cage"],
-    "forecasts": ["id"],
-    "idvs": ["key"],
-    "opportunities": ["opportunity_id"],
-    "otas": ["key"],
-    "otidvs": ["key"]
+    "contracts": [
+      "key"
+    ],
+    "entities": [
+      "cage"
+    ],
+    "forecasts": [
+      "id"
+    ],
+    "idvs": [
+      "key"
+    ],
+    "opportunities": [
+      "opportunity_id"
+    ],
+    "otas": [
+      "key"
+    ],
+    "otidvs": [
+      "key"
+    ],
+    "budget/accounts": [
+      "agency_code__in",
+      "bea_category__in",
+      "bureau_name__icontains",
+      "bureau_name__in",
+      "federal_account_symbol__in",
+      "fiscal_year__in",
+      "subfunction_code__in"
+    ]
   }
 }