docs(ios): retire three refusal notes that outlived their refusals

packages/zig/src/bridge_mobile_display.zigmodified+4-3

Changes to packages/zig/src/bridge_mobile_display.zig

		⋯599 linesShow the 599 lines above this hunk@@ -600,9 +600,10 @@ fn applyBadge(count: i64) !i64 {
600	600	/// what happened rather than swallowing it.
601	601	///
602	602	/// The completion handler is `nullable` in the header, so nil is legal and no
603		-/// block is needed. Note that `requestAuthorizationWithOptions:`, which Swift
604		-/// also calls, is *not* nullable there — passing nil to that one crashes, which
605		-/// is part of why authorization is not attempted here.
	603	+/// block is needed. `requestAuthorizationWithOptions:`, which the spec also
	604	+/// calls, is *not* nullable there — passing nil to that one crashes, which is
	605	+/// why it needs a real block. It has one now: `requestBadgeAuthorization`
	606	+/// above asks before this writes, so this function no longer runs unasked.
606	607	fn setBadgeThroughNotificationCenter(count: c_long) bool {
607	608	const UNCenterClass = objc.objc_getClass("UNUserNotificationCenter") orelse return false;
608	609	const sel_current = objc.sel_registerName("currentNotificationCenter") orelse return false;