Add read-only Meta enforcement monitoring routes

[pcauhi]

Summary

• document direct routes for Meta Business Support, Facebook Account Status, Identity Confirmation, and Support Inbox
• capture the /support/ redirect trap and the canonical Support Inbox route
• distinguish similarly named Business Support tabs and add safe read-only boundaries

Verification

• verified the documented routes and visible anchors against a logged-in Chrome session
• confirmed the Support Inbox category URL patterns and item_id link shape
• no Meta settings, support cases, appeals, verification flows, or business assets were changed

---

Summary by cubic

Adds a read-only guide for monitoring Facebook/Meta enforcement surfaces with verified direct routes and safe navigation. Clarifies the Support Inbox redirect trap and sets clear boundaries to avoid creating cases or changing settings.

• New Features
  • Documented direct URLs for Business Support Home (user/business), Account Status, Identity Confirmation, and Support Inbox tabs.
  • Explained the Support Inbox route trap and how to find the canonical link from the profile menu.
  • Listed stable on-page anchors to capture and noted non-interactive restriction cards.
  • Outlined support-case checks and strict read-only boundaries (no appeals, verification, or settings changes).

^{Written for commit a8f72ea. Summary will update on new commits.}

[browser-harness-review]

✅ Skill review passed

Reviewed 1 file(s) — no findings.

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="domain-skills/facebook/enforcement-monitoring.md">

<violation number="1" location="domain-skills/facebook/enforcement-monitoring.md:15">
P2: The documented URLs are internally inconsistent with the skill's own 'Support Inbox route trap' warning. The trap section tells agents to use the no-slash form `support?ref=contextual` because `support/` (with trailing slash) 'can redirect to `/hacked`', yet the Direct routes table and the Support-case checks section prescribe the slash form for `support/?tab_type=APPEALS`, `support/?tab_type=REPORTS`, and `support/?item_id=...`. An agent following the doc to construct tab/item URLs may hit exactly the redirect the skill warns against. Please either align all Support Inbox URLs to one consistent form or explicitly state why the slash-before-query form is safe for `?tab_type=`/`?item_id=` while the bare `support/` form is not.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: The documented URLs are internally inconsistent with the skill's own 'Support Inbox route trap' warning. The trap section tells agents to use the no-slash form support?ref=contextual because support/ (with trailing slash) 'can redirect to /hacked', yet the Direct routes table and the Support-case checks section prescribe the slash form for support/?tab_type=APPEALS, support/?tab_type=REPORTS, and support/?item_id=.... An agent following the doc to construct tab/item URLs may hit exactly the redirect the skill warns against. Please either align all Support Inbox URLs to one consistent form or explicitly state why the slash-before-query form is safe for ?tab_type=/?item_id= while the bare support/ form is not.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At domain-skills/facebook/enforcement-monitoring.md, line 15:

<comment>The documented URLs are internally inconsistent with the skill's own 'Support Inbox route trap' warning. The trap section tells agents to use the no-slash form `support?ref=contextual` because `support/` (with trailing slash) 'can redirect to `/hacked`', yet the Direct routes table and the Support-case checks section prescribe the slash form for `support/?tab_type=APPEALS`, `support/?tab_type=REPORTS`, and `support/?item_id=...`. An agent following the doc to construct tab/item URLs may hit exactly the redirect the skill warns against. Please either align all Support Inbox URLs to one consistent form or explicitly state why the slash-before-query form is safe for `?tab_type=`/`?item_id=` while the bare `support/` form is not.</comment>

<file context>
@@ -0,0 +1,59 @@
+| Facebook Account Status | `https://www.facebook.com/account_status` |
+| Identity Confirmation | `https://www.facebook.com/id/hub/` |
+| Facebook Support Inbox | `https://www.facebook.com/support?ref=contextual` |
+| Support Inbox — alerts/appeals | `https://www.facebook.com/support/?tab_type=APPEALS` |
+| Support Inbox — reports | `https://www.facebook.com/support/?tab_type=REPORTS` |
+
</file context>