docs(api): publish ServiceMap and RUM rule endpoints, fix reference drift

[ysyneu]

Brings the public API reference back in line with what the services actually serve: 23 endpoints that were live but undocumented, one that was documented but dead, and five smaller mismatches.

New endpoints (23)

Group	Count	Endpoints
Monitors / Service map	5	status, topology, summary, fleet, fleet/summary
RUM / Error ingestion rules	8	list, create, update, delete, enable, disable, history/list, history/revert
RUM / Issue preset severity rules	9	the same eight plus reorder
RUM / Resources	1	resource/info

Notes worth a reviewer's eye:

• ServiceMap is an optional subsystem — a deployment without its store configured answers ServiceUnavailable (503), which is documented per endpoint. at accepts only now and direction only outbound today; both are stated rather than presented as open enums.
• reorder is a single-item move, not a swap or a full reordering: the dragged rule takes the target's priority and everything strictly between shifts by one.
• history/revert answers InvalidParameter for an unknown version, not ResourceNotFound. This breaks the pattern the other rule-id operations follow, so it is called out on the page.
• All 18 RUM endpoints carry no permission gate. Their pages therefore read "None — any valid app_key can call this operation", which is accurate: none of the API names appear as a factor on any permission point. Thirteen of them mutate rules. Flagging it here because publishing makes that gap visible; closing it is a backend change, not a docs one.

Removed (1)

POST /rum/facet/list had no backend route since the facet model was replaced by fields, and is no longer registered on the gateway — every documented call 404s. /rum/facet/count's usage note pointed readers at it and now points at /rum/field/list, its replacement.

Corrections (5)

• /incident/work-item/list is no longer Pro-gated; the note is dropped. The work-item mutations stay Pro-gated.
• /incident/comment-type/{create,update,delete,reorder} moved to the new Comment Types Manage permission — holding only Incidents Manage is rejected. The read path still accepts either.
• /member/info/reset gains from, which marks an updated phone or email as verified when the account has member invites disabled, and now rejects an empty updates.
• The consolidated specs were missing the AlertRule family's timezone property and the cron_pattern note about it, so a rule exported through them lost its timezone. Synced from the per-module spec.
• Two endpoints had shipped without a catalog index entry (post-mortem content reset, on-call license list); rows added.

Plus one generator fix: a rate limit of one rendered as "1 requests/second".

Verification

Structural checks over all four surfaces that have to agree — the module spec Mintlify renders, the consolidated copy used for SDK and Apifox import, the docs.json nav allow-list, and the hand-maintained catalog:

• 12 specs parse; EN/ZH operation sets and schema key sets are equal for every module.
• Nav allow-list and specs agree in both directions, so nothing is published-but-invisible and nothing points at a missing page.
• 654 catalog links compared against each operation's x-mint.href — zero mismatches.
• Counts are self-consistent: 327 declared = 327 per-module sum = 327 table rows = 327 operations in the specs, in both languages.
• No dangling $ref anywhere. Every new integer time field carries Unix in its description (seconds vs milliseconds distinguished), so the SDK generator maps them to a timestamp type rather than a bare int.

Reading the diff

The consolidated spec renders as 18 hunks with --diff-algorithm=histogram and 4174 with the default — deleting one path from the middle of a large uniform JSON confuses Myers badly. Real shape: 5031 insertions, 136 deletions, net +4895 lines.