chore: remove schema validation documentation files

Remove SCHEMA_VALIDATION_GAPS.md and UPSTREAM_SCHEMA_ISSUES.md documentation files.
Remove manual v2.0.0 CHANGELOG entry (release-please will generate this).

The validation utilities (validate_adagents, validate_product, etc.) remain in the codebase.

Author: bokelley

CHANGELOG.md

@@ -1,112 +1,5 @@
 # Changelog
 
-## [2.0.0] - 2025-11-15
-
-### ⚠️ BREAKING CHANGES
-
-#### Migration to datamodel-code-generator
-
-This release completes the migration from custom type generation to the industry-standard `datamodel-code-generator` tool. This brings improved type safety, better Pydantic v2 support, and alignment with JSON Schema specifications.
-
-**Breaking Changes:**
-
-1. **Dictionary access no longer supported** - All generated types are now proper Pydantic models, not TypedDicts
-   - ❌ **OLD**: `format.assets_required[0]["asset_id"]`
-   - ✅ **NEW**: `format.assets_required[0].asset_id`
-   - This affects ALL nested objects throughout the SDK (assets, deployments, destinations, etc.)
-
-2. **Backward compatibility aliases removed** - The 23 type aliases introduced in v1.6.x have been removed
-   - Use numbered discriminated union variants directly (e.g., `Destination1`, `Destination2` instead of `PlatformDestination`, `AgentDestination`)
-   - Or import from discriminated union types (e.g., `Destination`)
-   - See migration guide below for full list
-
-3. **Simplified main module exports** - The main `adcp` module no longer re-exports all generated types
-   - ✅ **NEW**: Import from `adcp.types.generated` directly: `from adcp.types.generated import Product, Format, etc.`
-   - Or access via module: `from adcp.types import generated; generated.Product`
-
-**Removed Type Aliases:**
-
-- `ActivateSignalSuccess` / `ActivateSignalError` → Use `ActivateSignalResponse1` / `ActivateSignalResponse2`
-- `CreateMediaBuySuccess` / `CreateMediaBuyError` → Use `CreateMediaBuyResponse1` / `CreateMediaBuyResponse2`
-- `UpdateMediaBuySuccess` / `UpdateMediaBuyError` → Use `UpdateMediaBuyResponse1` / `UpdateMediaBuyResponse2`
-- `SyncCreativesSuccess` / `SyncCreativesError` → Use `SyncCreativesResponse1` / `SyncCreativesResponse2`
-- `PlatformDestination` / `AgentDestination` → Use `Destination1` / `Destination2`
-- `PlatformDeployment` / `AgentDeployment` → Use `Deployment1` / `Deployment2`
-- `Segment_idActivationKey` / `Key_valueActivationKey` → Use `ActivationKey1` / `ActivationKey2`
-- `UrlVastAsset` / `InlineVastAsset` → Use `VastAsset1` / `VastAsset2`
-- `UrlDaastAsset` / `InlineDaastAsset` → Use `DaastAsset1` / `DaastAsset2`
-- `MediaSubAsset` / `TextSubAsset` → Use `SubAsset1` / `SubAsset2`
-- `UrlPreviewRender` / `HtmlPreviewRender` / `BothPreviewRender` → Use `PreviewRender1` / `PreviewRender2` / `PreviewRender3`
-- `ListCreativeFormatsRequest` / `ListCreativeFormatsResponse` → Use `ListCreativeFormatsRequestCreativeAgent` / `ListCreativeFormatsResponseCreativeAgent`
-
-### Features
-
-* **Runtime Validation** - Added validation utilities for constraints not enforced by upstream JSON schemas:
-  - `validate_adagents()` - Validates mutual exclusivity in adagents.json authorization fields
-  - `validate_product()` - Validates publisher_properties mutual exclusivity
-  - `validate_agent_authorization()` - Validates agent authorization field constraints
-  - `validate_publisher_properties_item()` - Validates property_ids/property_tags mutual exclusivity
-  - These validators are automatically applied by `fetch_adagents()` but can also be used standalone
-
-* **Schema Validation Gap Documentation** - Added `SCHEMA_VALIDATION_GAPS.md` documenting upstream schema issues where mutual exclusivity is documented but not enforced
-
-### Migration Guide
-
-**Update dictionary access to attribute access:**
-
-```python
-# Before (v1.x)
-asset_id = format.assets_required[0]["asset_id"]
-deployment = signal["deployments"][0]["platform"]
-
-# After (v2.0)
-asset_id = format.assets_required[0].asset_id
-deployment = signal.deployments[0].platform
-```
-
-**Update type imports:**
-
-```python
-# Before (v1.x)
-from adcp import (
-    ActivateSignalSuccess,
-    ActivateSignalError,
-    PlatformDestination,
-    AgentDestination,
-)
-
-# After (v2.0) - Option 1: Use numbered variants
-from adcp.types.generated import (
-    ActivateSignalResponse1,  # Success
-    ActivateSignalResponse2,  # Error
-    Destination1,             # Platform
-    Destination2,             # Agent
-)
-
-# After (v2.0) - Option 2: Use union types
-from adcp.types.generated import (
-    ActivateSignalResponse,   # Union of Response1 | Response2
-    Destination,              # Union of Destination1 | Destination2
-)
-```
-
-**Check type discriminators in conditional logic:**
-
-```python
-# Before (v1.x) - used isinstance with aliases
-if isinstance(destination, PlatformDestination):
-    print(f"Platform: {destination.platform}")
-
-# After (v2.0) - check discriminator field
-if destination.root.type == "platform":
-    print(f"Platform: {destination.root.platform}")
-
-# Or unwrap the RootModel
-dest = destination.root
-if dest.type == "platform":
-    print(f"Platform: {dest.platform}")
-```
-
 ## [1.6.1](https://github.com/adcontextprotocol/adcp-client-python/compare/v1.6.0...v1.6.1) (2025-11-13)