chore: release 0.5.0

[plusky]

Version bump for the 0.5.0 release. Per AGENTS.md the bump lands as a normal PR first; the annotated tag then goes on the merge commit and release.yml does the rest (binaries, GitHub release, GHCR image, crates.io).

Why 0.5.0 and not 0.4.1

26 commits since 0.4.0 (2026-08-12), and one of them changes behaviour an operator can be broken by: #105 / #32 makes the http transport deny-by-default — no bearer token and no --insecure-no-auth is a startup refusal before the port is bound. A 0.4.0 http deployment with no token will not come up. Pre-1.0, that belongs in the minor position.

What's in the cycle

Features

• HTTP bearer gate: BUGWARDEN_HTTP_TOKEN / BUGWARDEN_HTTP_READ_TOKEN, deny-by-default, write vs read scope (feat(server): require a bearer token on the http transport #105 / Per-caller authentication on the MCP endpoint #32)
• MCP_ALLOWED_HOSTS and BUGZILLA_USE_AUTH_HEADER from the environment (feat(server): let the environment set allowed hosts and the auth header #104)
• audit / diagnostics export to an OTLP collector; a configured collector is load-bearing (feat: export audit records and diagnostics to an OTLP collector #121 / Document shipping the audit log to an OTel collector (+ examples/otel-collector.yaml) #31)
• published container image ghcr.io/plusky/bugwarden (multi-arch, distroless) (feat: ship a container image on ghcr.io #106)

Fixes

• unparsable --allowed-hosts is a startup error; ::1 is a matchable authority (fix(server): refuse unparsable allowed-hosts at startup #125 / Host-validation hardening: no startup log of effective state, and unparsable entries silently deny all #117)
• SIGTERM so docker stop is a graceful shutdown (fix(server): handle SIGTERM so docker stop is graceful #122 / main.rs handles only SIGINT: as PID 1 a docker stop takes the 13s SIGKILL path #114)
• tool schemas normalized for Gemini/Vertex clients, including nested draft-2020-12 positions (fix(server): normalize tool schemas for gemini/vertex clients #119, fix(server): recurse portable_schema into all draft-2020-12 positions #126)
• I12 transport tests no longer aim at recycled ports (test: stop aiming I12 transport tests at recycled ports #124)

Docs / test / build

• I12 refuse address recorded as 127.0.0.1:1 (docs: record the I12 refuse address as 127.0.0.1:1 #128)
• toolchain pin 1.97.1; Alpine rust image matching it
• h2 0.4.16 (RUSTSEC-2026-0258)
• rust-cache pinned to the v2.9.2 release commit

What this PR touches

File	Change
Cargo.toml	[workspace.package] version → 0.5.0
crates/bugwarden/Cargo.toml	the bugwarden-core dependency pins version as well as path, so it moves in lockstep
Cargo.lock	both workspace crates
crates/bugwarden/man/bugwarden.1	regenerated — the man page embeds the version

The completions carry no version string and are unchanged, which rust-assets-drift confirms.

The bugwarden-core version requirement is still not single-sourced; it has to be bumped by hand every release. It fails the build loudly rather than silently resolving a stale core.

Verification

cargo fmt --check, both clippy invocations, cargo test --workspace --all-targets --locked (550 passed, 0 failed), and cargo deny check all pass. Assets regenerated from the clap CLI and re-diffed.

After merge: annotated tag 0.5.0 on the merge commit (no v prefix). First GHCR push will be private; visibility has to be flipped to public once in Package settings (Danger Zone) — that is a one-way UI step, not part of this PR.