[Cloudflare One] Document local emergency disconnect

[jiulingz]

Summary

Adds documentation for local emergency disconnect feature (RM-29186) landing in 2026.5.0. This feature allows organizations to trigger an emergency disconnect on the device itself, without network access.

Documentation checklist

• Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
• The change adheres to the documentation style guide.
• Files which have changed name or location have been allocated redirects.

[jiulingz]

/bonk review

[csujedihy]

/bonk review

[ask-bonk]

Testing review submission.

[ask-bonk]

Test line 50

[ask-bonk]

Test line 280

[ask-bonk]

Test line 370

[ask-bonk]

3 issues need fixing before merge — one broken link (cannot inline-suggest because the line sits between diff hunks), one style guide violation, and one formatting fix.

CRITICAL

• emergency-disconnect.mdx:~380 — Broken internal link anchor. The heading changed to ### Clear External Emergency Disconnect, so the link [turn off External Emergency Disconnect](#clear-external-emergency-disconnect-state) should point to #clear-external-emergency-disconnect.

MEDIUM

• emergency-disconnect.mdx:370 — Use "turn off" instead of "disable" per style guide; also use imperative mood ("push" not "pushing").
• emergency-disconnect.mdx:280 — Config key and boolean value need backticks per text formatting rules.

LOW

• emergency-disconnect.mdx:3 — Description (38 chars) is below the 50-character minimum.

Note: The PR body leaves the changelog checkbox unchecked. For a new feature landing in 2026.5.0, consider adding a changelog entry so customers can discover it via RSS and Discord.

[ask-bonk]

Submitted the review on PR #31120. Here's what I found:

3 issues need fixing before merge:

• CRITICAL — Broken internal link in emergency-disconnect.mdx (~line 380). The heading was renamed to ### Clear External Emergency Disconnect, but the link still points to the old anchor #clear-external-emergency-disconnect-state. It should be #clear-external-emergency-disconnect.
• MEDIUM — Style guide violation in emergency-disconnect.mdx (line 370): "disable" should be "turn off", and "pushing" should be "push" (imperative mood).
• MEDIUM — Missing backticks in emergency-disconnect.mdx (line 280): emergency_disconnect and false should both be wrapped in backticks.
• LOW — Description frontmatter is only 38 characters (minimum is 50).

I posted inline suggestions for the 3 commentable issues. The broken link couldn't be inline-suggested because the line sits between GitHub diff hunks, so I described it in the review summary.

I also noted that the changelog checkbox is unchecked in the PR body — for a new feature landing in 2026.5.0, consider adding a changelog entry.

github run

[jiulingz]

/bonk review

[csujedihy]

/bonk review

[ask-bonk]

Thanks for addressing the previous round of feedback. All three fixes have been applied correctly:

• ✅ Description expanded past the 50-character minimum.
• ✅ Config key and boolean value wrapped in backticks.
• ✅ Broken anchor link fixed (#clear-external-emergency-disconnect).
• ✅ Redirect updated to point to the External Emergency Disconnect section anchor.

I have one remaining suggestion to keep a procedure step fully in imperative mood (line 370). Otherwise this looks ready to merge.

[ask-bonk]

Submitted the review on PR #31120. Here's a summary:

Acknowledged fixes from the previous round:

• ✅ Description expanded past the 50-character minimum
• ✅ Config key and boolean value wrapped in backticks
• ✅ Broken anchor link fixed (#clear-external-emergency-disconnect)
• ✅ Redirect updated to point to the External Emergency Disconnect section anchor

One remaining suggestion:

• emergency-disconnect.mdx:370 — Suggested rephrasing the step to keep it fully in imperative mood: use "remove ... and push" as the leading verbs instead of burying the actions in a "by removing ... and pushing" clause.

Otherwise, the PR looks solid and ready to merge after that minor tweak.

github run

[cloudflare-docs-bot]

Review

❌ Review failed for commit a7b8e07. This is usually a transient error — it will retry on the next push.