feat(status): gate status pages behind the statusPages org flag - #1972

🟢 Confidence 10/10 · safe to merge. Follow-up hunks are small and pinned by scene/tool tests; the only contract change, a required pageDraft, is set by all four incident tools.
_{no findings · tests covered · risk medium}

Follow-up to the status-pages rollout: the MCP incident tools now say when the page is a draft, a failed bulk component add closes its panel with an error toast, and a draft page's address renders as text with no Open link. Safe to merge.

• StatusPageIncidentMutationOutput gains a required pageDraft, and renderIncident warns the incident stays private
• The editor drops addFailure: a failed add closes the add panel and toasts, so a retry cannot duplicate
• view-live suppresses the public link and Open button for a draft page

Before merge

• Manual · Set "statuspages": true in the Preview org's Clerk public metadata on the development instance before testing a preview of this stack

Production impact

_{3a56bcc · Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.}