hyperping 1.9.0: CLI script rename hyp->hyperping; incident chunking/…

…guard; partial-batch errors; documented 1.8.x breaking changes

hyperping 1.8.1: statuspage v2-shape fix; maintenance statuspage-coun…

…t guard + create_maintenance_windows()

Release v1.8.0

Security-focused release closing audit findings.

- base_url / mcp_url validation rejects http://, userinfo, query, fragment
  by default. allow_insecure=True opt-in for local-dev with warning.
- HyperpingAPIError.response_body recursively redacted at construction.
- MCP transport no longer stores raw server text on error paths.
- _endpoint_breakers map LRU-bounded at 1024 entries.

See CHANGELOG.md and Upgrade Notes for migration guidance.

Release 1.7.0

ci: audit runtime deps only in publish workflow (#24)

The 1.6.0 publish run failed at the pip-audit step on two CVEs in `pip`
itself, even though `pip` is not a runtime dependency of the published
`hyperping` wheel. The root cause was that pip-audit was scanning the
entire venv (which uv populates with build/dev tooling including pip)
instead of the dependency closure that users actually install.

Switch the publish-time audit to operate on a freshly exported
runtime-only requirements file (`uv export --no-dev --no-emit-project`).
This audits exactly what `pip install hyperping` would resolve to, and
silences env-only noise without ignoring real CVE IDs.

Local check:
    $ uv export --no-dev --no-emit-project --no-hashes \
        --format requirements.txt -o /tmp/req.txt
    $ uv run pip-audit -r /tmp/req.txt
    No known vulnerabilities found

ci.yml's audit step is `continue-on-error: true` and is unaffected; can
be tightened the same way in a follow-up.

feat: add MCP-discovered API endpoints (reporting, observability, on-…

…call, integrations)