From d47da3622001aa3da4204a1fc7c8a21431867d57 Mon Sep 17 00:00:00 2001
From: Alexey Shalaev <75322386+AlexeyShalaev@users.noreply.github.com>
Date: Sun, 6 Sep 2026 23:03:54 +0300
Subject: [PATCH] fix: retry gating, native override reporting and connection
 metrics

The work landed in #20. Its squash subject lost the Conventional Commit prefix --
my mistake on the merge, not the author's -- so release-please skipped the merge
and these fixes would never have reached a release. This commit carries the
record. It changes no code: #20 is already on master.

* retry.methods could not narrow at all. The gate was a disjunction of two
  permissions, so neither half could refuse: a DELETE stayed retryable after an
  operator removed it from the list, and an explicit idempotent=False was
  ignored. It now reads a flag that contradicts the method's RFC default as the
  call site deciding, and one that merely restates it as deferring to
  retry.methods.
* ConfigApplicationReport.native_overrides was always empty, though two guides
  promised it listed the accepted passthrough per slot. Every adapter fills it.
* conn_metrics had no consumer, so Attempt.conn was always None and aiohttp's
  DNS, connect, pool-wait and reuse timings reached nothing. Both engines fill
  it and the emitter puts the timings on the call span.
* redact_headers is exported from the package root, beside the
  DEFAULT_SENSITIVE_HEADERS constant it is the only use for.