v0.7.2

v0.7.2 — typed non-200 successes

v0.7.2 fixes a silent typing gap in the generator: a route whose success status
is not literally 200 lost its declared response type. The fix is additive — a
bundle whose successes are all 200 is byte-identical; only silently-untyped
non-200 routes gain their declared schema. The release also ships a
clean-auditing Homebrew formula.

• The success response binds from the declared 2xx. wavefront-bundle add
  picked the success schema from the literal "200" response key only, while the
  per-status error collection deliberately skips all 2xx — so a route whose
  success is 201/202 (FastAPI emits the schema under the route's status_code,
  e.g. 202 for an async endpoint) fell through both collectors and silently
  bound the synthetic Empty, dropping its type. The success now binds from the
  declared 2xx; if a hand-authored spec declares several 2xx for one operation,
  the numerically-lowest wins, deterministically. A declared 2xx with no content
  at all (a 204, or a bare description-only entry) is genuinely bodyless and
  still binds Empty; a 2xx declaring only non-JSON content is still rejected
  (#143 closed).

• Clean-auditing Homebrew formula. The formula rendered at release time now
  passes brew test-bot's tap-syntax audit: the redundant version line is
  dropped (inferable from the URL), the dual license is declared as
  any_of: ["MIT", "Apache-2.0"], and macOS-on-Intel resolves a URL for
  brew readall while depends_on arch: :arm64 keeps the formula
  Apple-Silicon-only on macOS (#142).

• fix: bind the success response_message from the declared 2xx (#144)

• release: emit a clean-auditing Homebrew formula (#142)