Schemas based on ref get incorrectly replace at bundle time

Describe the bug

A schema referencing another schema via ref will get incorrectly replaced when bundling.

e.g.

Uint64:
  type: string
  example: "1"

GenesisTime:
  $ref: "./primitive.yaml#/Uint64"
  example: "1590832934"
  description: "The genesis_time configured for the beacon node, which is the unix time in seconds at which the Eth2.0 chain began."

...
properties:
  genesis_time:
    $ref: '../../beacon-node-oapi.yaml#/components/schemas/GenesisTime'

will generate

genesis_time:
  type: string
  example: '1'

Expected behavior

I would expect the following to be generated. swagger-cli does.

genesis_time:
  type: string
  example: '1590832934'
  genesis: 'The genesis_time configured for the beacon node, which is the unix time in seconds at which the Eth2.0 chain began.'

Reproduce the issue with the YAML schema and nested $ref example from the report, then compare the bundle output with swagger-cli. Trace the bundling path that resolves refs and verify that the referenced schema's local example and description are preserved in the generated genesis_time schema.