Signed in create rule clear

app/(app)/create/SignedInDraftHydration.tsx

@@ -27,8 +27,10 @@ const SYNC_ENABLED = process.env.NEXT_PUBLIC_ENABLE_BACKEND_SYNC === "true";
  * server draft on top would clobber unsaved keystrokes with a stale snapshot.
  *
  * Server draft becomes authoritative only when localStorage is empty — i.e.
- * fresh device, after explicit Save & Exit (which clears localStorage), or
- * after Exit-from-completed clears local state.
+ * fresh device, after explicit Save & Exit (which clears localStorage),
+ * after Exit-from-completed clears local state, or after
+ * {@link prepareFreshCreateFlowEntry} (Create rule / new template entry) clears
+ * local + deletes the server draft when sync is on.
  *
  * Skips when `?syncDraft=1` or transfer-pending — {@link PostLoginDraftTransfer}
  * owns that path.

app/(app)/create/utils/clearCreateFlowPersistedDrafts.ts

@@ -4,17 +4,13 @@ import { clearCoreValueDetailsLocalStorage } from "./coreValueDetailsLocalStorag
 /**
  * Wipe the anonymous in-progress create-flow draft from `localStorage` (both
  * the main `create-flow-anonymous` blob and the separate core-value details
- * key). Intended for call sites that navigate **into** the create flow from
- * outside and want a fresh slate — today that's the marketing "Popular
- * templates" click handler on the home page and the `/templates` index page
- * (when not in-flow). `CreateFlowProvider` reads `localStorage` during its
- * `useState` initializer, so clearing *before* pushing the next route means
- * the provider mounts empty and the Create Community stage starts clean.
+ * key). Clearing *before* `router.push` means `CreateFlowProvider` can read
+ * empty storage on mount.
  *
- * Note: this only touches localStorage. It does **not** delete the
- * authenticated user's server draft (`/api/drafts/me`). Server drafts are
- * loaded deliberately from the profile page, not re-hydrated into the flow
- * on every entry, so there's nothing to wipe here for signed-in users.
+ * For marketing/profile “new rule” entry that should also remove the signed-in
+ * server draft when backend sync is on, use {@link prepareFreshCreateFlowEntry}.
+ *
+ * This helper only touches `localStorage`; it does **not** `DELETE /api/drafts/me`.
  */
 export function clearCreateFlowPersistedDrafts(): void {
   clearAnonymousCreateFlowStorage();

app/(app)/create/utils/prepareFreshCreateFlowEntry.ts

@@ -0,0 +1,23 @@
+import { deleteServerDraft } from "../../../../lib/create/api";
+import { clearAnonymousCreateFlowStorage } from "./anonymousDraftStorage";
+import { clearCoreValueDetailsLocalStorage } from "./coreValueDetailsLocalStorage";
+
+const SYNC_ENABLED =
+  process.env.NEXT_PUBLIC_ENABLE_BACKEND_SYNC === "true";
+
+/**
+ * Call **before** navigating into `/create` from marketing or profile “new rule”
+ * entry points so signed-in + sync matches an anonymous fresh start: wipe
+ * `localStorage` draft keys and, when sync is on, `DELETE /api/drafts/me`.
+ * Anonymous `DELETE` is harmless (401). Await ensures the server draft is gone
+ * before mount so {@link SignedInDraftHydration} does not rehydrate stale work.
+ *
+ * Do **not** use for “Continue draft” — that path should load the server draft.
+ */
+export async function prepareFreshCreateFlowEntry(): Promise<void> {
+  clearAnonymousCreateFlowStorage();
+  clearCoreValueDetailsLocalStorage();
+  if (SYNC_ENABLED) {
+    await deleteServerDraft();
+  }
+}