docs(api): make the reference examples internally consistent

[ysyneu]

Every item here is a contradiction a reader can see on the rendered page.

Example	Was	Now
ServiceMap fleet	request filters degraded/stale; response returns one active host, while coverage says returned: 2 and counts one degraded + one stale	two hosts, one degraded and one stale — matching both the filter and every count
preset-severity create	returns priority: 3 for a rule the list example shows at priority: 1	priority: 2, and list now orders by creation, so priority and creation order agree
preset-severity history/list	total: 4 beside 2 items; the version=1 "empty" snapshot is timestamped after a rule that already existed	three snapshots on one timeline (two creates, then a disable), total: 3, each snapshot holding the state its own call was about to change
error-ingestion history/list	total: 3 beside 1 item; the snapshot already carried the update it was supposed to precede	two snapshots, total: 2, the pre-update state where it belongs
resource/info	order_id encodes 2026-06-15 for a resource created_at 2025-06-15; billing window not anchored at created_at	order id matches the creation date; window is the 30-day span from created_at the field descriptions promise
example addresses	private-range	RFC 5737 documentation range, as this corpus already uses elsewhere

No downstream release needed. Examples feed no code generation: the CLI reads only request-side examples (internal/cmd/cligen/main.go:461) and none of those change here. Verified by regenerating the SDK against this spec — only the vendored JSON differs, zero generated Go changes — and the SDK's spec-example round-trip test passes against the new payloads.

Structural verification is unchanged and green: 12 specs parse, EN/ZH operation and schema key sets equal, nav allow-list agrees with the specs both ways, 654 catalog links match their x-mint.href, and counts stay 327 across the declared total, per-module sums, table rows, and the specs themselves.