Call the last create-flow action Publish so it reads as putting a rule on the web, not locking it forever.

Co-authored-by: Cursor <cursoragent@cursor.com>

tests/components/FinalReviewPage.test.tsx

@@ -79,7 +79,7 @@ describe("FinalReviewScreen", () => {
     render(<FinalReviewScreen />);
     expect(
       screen.getByText(
-        /Here's what other people will see. Make sure everything looks good before you finalize everything. Once the rule is finalized, you must use one of your decision-making mechanisms to edit it again./i,
+        /Here's what other people will see. Make sure everything looks good before you publish. Once the rule is published, you must use one of your decision-making mechanisms to edit it again./i,
       ),
     ).toBeInTheDocument();
   });
@@ -1004,6 +1004,18 @@ function FinalReviewEditPublishedWithStateProbe({
 }
 
 describe("FinalReviewScreen — edit published title and description", () => {
+  it("renders edit-published lockup copy", () => {
+    render(<FinalReviewScreen variant="editPublished" />);
+    expect(
+      screen.getByRole("heading", { name: "Edit your CommunityRule" }),
+    ).toBeInTheDocument();
+    expect(
+      screen.getByText(
+        /Update what others see on your public rule. Save & Exit or Publish applies changes to your published CommunityRule./i,
+      ),
+    ).toBeInTheDocument();
+  });
+
   it("does not expose click-to-edit title or description on default final review", () => {
     render(
       <FinalReviewWithFlowState