Sync the chrome cookies example on the FAA page

[mlw]

Synchronize the FAA cookies example with the one on the cookbook.

Long term we will want to have a more generic example to not need to keep things in sync like this. But patching for now so that the information is correct.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 28d04343-73c3-4c11-994e-15757eee58f1

📥 Commits

Reviewing files that changed from the base of the PR and between 30e5b24 and 1971a79.

📒 Files selected for processing (1)

• docs/docs/features/faa.md

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/docs/features/faa.md

---

📝 Walkthrough

Walkthrough

Updated FAA docs example "Protecting Browser Cookies (Data-centric)": Chrome helper SigningID match changed from com.google.Chrome.helper to com.google.Chrome* (wildcard), and a new macOS 26.3+ process exception for SigningID com.apple.mds with PlatformBinary: true was added.

Changes

Cohort / File(s)	Summary
FAA Documentation docs/docs/features/faa.md	Modified the "Protecting Browser Cookies (Data-centric)" example: changed Chrome process SigningID match from com.google.Chrome.helper to wildcard com.google.Chrome* and added a new com.apple.mds process <dict> entry with SigningID: com.apple.mds and PlatformBinary: true (macOS 26.3+).

Sequence Diagram(s)

(omitted — documentation-only change)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update FAA cookbook rule for macOS 26.3 #778: Adds com.apple.mds exception and Chrome SigningID wildcard to FAA cookie-reader rules, matching these documentation updates.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly references syncing the Chrome cookies example on the FAA page, which aligns with the PR's primary change of updating the documentation example.
Description check	✅ Passed	The description explains the purpose of synchronizing the FAA cookies example with the cookbook example and acknowledges the longer-term plan, clearly relating to the changeset.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch mlw/faa-cookies-example

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

docs/docs/features/faa.md (1)

248-248: Small wording fix: “files system” → “file system”.

Line 248 has a typo in user-facing docs.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/docs/features/faa.md` at line 248, Fix the typo in the user-facing
documentation by replacing the phrase "files system" with "file system" in the
docs/docs/features/faa.md content (search for the exact string "files system" to
locate the occurrence).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@docs/docs/features/faa.md`:
- Line 248: Fix the typo in the user-facing documentation by replacing the
phrase "files system" with "file system" in the docs/docs/features/faa.md
content (search for the exact string "files system" to locate the occurrence).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 46110ddc-225c-4188-8776-165718e026b6

📥 Commits

Reviewing files that changed from the base of the PR and between 8fceee0 and d07a396.

📒 Files selected for processing (1)

• docs/docs/features/faa.md