…es on json_schema

JsonSchema previously accepted `examples` only via `extra="allow"`, leaving
it untyped, undocumented, and invisible to type checkers. Declare it as
Optional[List[JsonType]] so the JSON Schema `examples` keyword is a
first-class, validated field.

Supports PR #88 (OpenAPI converter examples parsing), which currently
relies on the extra-field fallback.

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

…misses-examples-on-params

…misses-examples-on-params

…schema-examples-field

feat(core): add explicit examples field to JsonSchema

Issue 2 — replace the blind cast on http_method with an explicit guard.
OpenAPI allows operations (options/head/trace) that HttpCallTemplate's
Literal type rejects; these are now skipped with a warning instead of
crashing conversion via a Pydantic ValidationError. A shared
SUPPORTED_HTTP_METHODS constant backs both the operation-loop filter and
the per-operation check, so the cast is now truthful rather than assumed.

Issue 3 — make example handling consistent across params, request bodies,
and responses. Examples that appear at the schema level (not just the media
type / parameter object) are now collected via _merge_examples and surfaced
in the normalized JSON Schema 'examples' keyword, and the raw OpenAPI
'example'/'examples' keys are stripped before the schema is spread onto the
property so they no longer leak through as untyped extra fields. This lines
up with the explicit examples field added to JsonSchema in core (#91).

Adds tests for unsupported-method skipping and schema-level example
normalization.

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

…xamples-on-params

fix: OpenAPI Converter was not parsing examples for request parameters

Publishes the OpenAPI examples parsing work: the explicit JsonSchema
`examples` field (core) and the converter changes that normalize examples
and validate HTTP methods (http).

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