faq: keep the drafts copy of the plan in step with The-Nook

Byte-identical to The-Nook drafts/faq-from-objections.md at b86a980b. The plan now
names the rule-3 patch and FRE-334, the Chief of Staff's withdrawal ask.

Source issue: FRE-326.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

marketing/drafts/faq-from-objections.md

@@ -308,7 +308,8 @@ check.
 1. **Sentry starts unconditionally with `sendDefaultPii = true`** (`Sources/NookApp/main.swift:272-278`).
    That is crash and error reporting with personal identifiers, not "anonymous usage telemetry".
 2. **The licence/trial call sends `IOPlatformUUID` and the Mac's device name** (`LicenseService.swift:254`,
-   `:305`), on launch, not only at trial start.
+   `:305`). Precision from the verdict: the identifiers ride on activation, not on every launch — a
+   licensed Mac's launch call is `/status` with the key only (`:290-295`).
 3. **With the phone link on, prompt and reply text transit `nook-relay.freno.me`, sealed end to end**
    (`docs/sidecar-frames.md`). The relay can route the payload but cannot read it; the live answer
    still says no prompt text leaves the device.
@@ -385,8 +386,11 @@ page title stay unchanged.
 change, not an objection-mining change. It should be its own reviewed edit — and E1 no longer promises
 it.
 
-**Patch artifact:** `freno-dev/marketing/drafts/faq-page.patch`, regenerated for this revision (a
-proposal, not applied). The page file itself is untouched until the gates below are satisfied.
+**Patch artifacts:** `freno-dev/marketing/drafts/faq-page.patch`, regenerated for this revision, and
+`freno-dev/marketing/drafts/positioning-privacy-withdrawal.patch` for the rule-3 strike step 3 needs
+to land with it (both proposals, neither applied). The page file and `positioning.md` are untouched
+until the gates below are satisfied; `faq-page.patch` re-checked against `freno-dev` master
+`c1c498e` on 2026-10-29 and applies cleanly.
 
 ---
 
@@ -396,7 +400,7 @@ proposal, not applied). The page file itself is untouched until the gates below
 |---|---|---|---|
 | 1. CTO verifies the claims and evidence pointers in E1–E8 | CTO | **done 2026-10-29** | [FRE-329](/FRE/issues/FRE-329), verdict in its `faq-verdict` document: E1/E7 verified as written, E2/E6 verified after one sentence each, E3/E4/E5/E8 corrected above, **no entry cut**. Applied in this revision. |
 | 2. Human approves this revision | Sponsor | target 2026-10-31 | The draft moves from `marketing/drafts/` to `marketing/approved/`, or the confirmation card on FRE-326 is accepted. The card names the privacy withdrawal, which is part of the same page edit. |
-| 2b. Withdrawal of the false privacy answer and of `positioning.md` rule 3 | Chief of Staff | target 2026-10-31 | A CoS decision, recorded on this issue. If the CoS declines, the seven non-privacy entries can still ship; the privacy answer does not stay up and does not get replaced. |
+| 2b. Withdrawal of the false privacy answer and of `positioning.md` rule 3 | Chief of Staff — asked in [FRE-334](/FRE/issues/FRE-334) | target 2026-10-31 | A CoS decision, recorded on this issue. If the CoS declines, the seven non-privacy entries can still ship; the privacy answer does not stay up and does not get replaced. |
 | 3. Apply the page patch, strike rule 3 + its approved-claims row, commit on `freno-dev` | CMO | 2026-11-03 | The patch applies cleanly; the site's own suite passes; the diff contains only the FAQ entries, the page comment/description, and the `positioning.md` strike. One commit, so the page and the rule move together. |
 | 4. Merge to `freno-dev/master` (the publish) | Sponsor or Chief of Staff | 2026-11-05 | A human merge; Vercel deploys. No agent pushes to master. |
 | 5. Verify the live page | CMO | 2026-11-05 | `https://nook.freno.me/faq` returns 200 and shows the eight entries with no privacy answer; the text matches the approved draft, sentence for sentence. |