davidrs 0.1.1

Changed

• The README now starts with installation, a complete HTTP function and
  direct links to the guide, examples, agent skill and security reporting.
• The introduction describes runtime boundaries without unmeasured latency
  or cost claims.
• The agent skill's references name VerifierConfig::with_required_claim
  and say that an or_else tenant is checked against membership.

Fixed

• A token whose key is being fetched by a concurrent JWKS refresh waits for
  that refresh instead of being refused with UnknownKey.
• A fields exclusion outside what the request keeps no longer leaves an
  empty object in the response or marks its ancestors as wanted.
• A header name repeated on a Failure or by an Admission, such as
  set-cookie, keeps every value on the response.
• sdk_config reads the credentials again each time the SDK resolves them,
  so a value that changes while the function is warm is used.
• OpenAPI tools send a null field of a flattened JSON body as null
  instead of dropping it, so a JSON Merge Patch can clear a field.
• Producer::fail ends the stream: nothing sent afterwards, and no later
  deadline error, follows the failure, and the producer is cancelled.
• An MCP message with "id": null is refused with -32600, since MCP
  forbids a null request id; it was accepted as a notification and never
  answered.
• Keywords beside a $ref in an OpenAPI document apply together with its
  target in the published tool schemas: a constraint the target also sets
  goes under allOf, and properties and required are merged.
• Invocation::invoked_arn is None for a value that is not an ARN, such
  as the function-arn placeholder cargo lambda watch sends.
• An OpenAPI call sends one Authorization header: when an authorization
  header is configured with OpenApi::header, it replaces the caller's
  token that OpenApi::forward_caller_token would send.
• The debug log line of a refused (4xx) request records the step that
  refused it (kind) instead of the HTTP status, so two refusals with the
  same code from different steps can be told apart.
• A scheme name sent alone in Authorization, such as Basic or NTLM
  with no credentials, leaves the request anonymous on a route that
  verifies bearer tokens, instead of being refused with
  ERROR_INVALID_TOKEN.
• On an Application Load Balancer with multi-value headers, source_ip
  reads the last X-Forwarded-For value, the one the load balancer
  appends, instead of the first line, which a client can choose to pick
  its own rate-limit key.