feat(marketplace): adjust cart and checkout view to marketplace use-case (MS-1158)

apps/automated-tests/tests/e2e/checkout/checkout-guest.spec.ts

@@ -6,7 +6,7 @@ test.describe("Guest checkout", () => {
   test.beforeEach(async ({ productPage, cartPage, checkoutLoginPage }) => {
     await productPage.goto(product.url);
 
-    // Add to bag mutation must finished and set checkoutId cookie, thus
+    // Add to bag mutation must finished and set checkout cookie, thus
     // navigation to cart page is required - the cookie will be set by the time the page loads
     await productPage.addProductToBagAndGoToCart();
 

apps/automated-tests/tests/e2e/checkout/checkout.spec.ts

@@ -6,7 +6,7 @@ test.describe("Logged-in user checkout", () => {
   test.beforeEach(async ({ productPage, cartPage, checkoutLoginPage }) => {
     await productPage.goto(product.url);
 
-    // Add to bag mutation must finished and set checkoutId cookie, thus
+    // Add to bag mutation must finished and set checkout cookie, thus
     // navigation to cart page is required - the cookie will be set by the time the page loads
     await productPage.addProductToBagAndGoToCart();
 

apps/docs/versioned_docs/version-1.15.0/marketplace.mdx

@@ -77,6 +77,12 @@ The marketplace app provides the following vendor-facing features:
 - **Vendor Pages** - Manage vendor profile pages and page status
 - **Customer Management** - View and manage customers
 
+## Vendor onboarding flow
+
+During public vendor sign-up, the marketplace app creates the Saleor vendor profile page and default vendor collection before registering the customer account. The vendor page is created as a draft with `isPublished: false`, then the customer account is linked to that page through the `vendor.id` customer metadata key.
+
+The vendor page is published only after the vendor confirms their Saleor account from the account confirmation link. When confirmation succeeds and Saleor returns an active user, the marketplace app reads the customer's `vendor.id` metadata and updates the linked vendor page with `isPublished: true`.
+
 ## i18n
 
 The marketplace app also uses the shared i18n package described in the [i18n architecture docs](/i18n). It passes `app: "marketplace"` to `@nimara/i18n`'s `createRequestConfig`, so it receives the `common` + `marketplace` message bundles (with locale-specific overrides applied where defined).

apps/marketplace/src/app/(public)/account-confirm/actions.ts

@@ -2,14 +2,33 @@
 
 import { ConfirmVendorAccountDocument } from "@/graphql/generated/client";
 import { executeGraphQL } from "@/lib/graphql/execute";
+import { publishVendorPageForConfirmedAccount } from "@/lib/saleor/vendor-page-publication";
 
 export async function confirmAccount(variables: {
   email: string;
   token: string;
 }) {
-  return executeGraphQL(
+  const result = await executeGraphQL(
     ConfirmVendorAccountDocument,
     "ConfirmVendorAccountMutation",
     variables,
   );
+
+  if (!result.ok) {
+    return result;
+  }
+
+  const user = result.data.confirmAccount?.user;
+
+  if (user?.isActive) {
+    const publishResult = await publishVendorPageForConfirmedAccount(
+      user.email,
+    );
+
+    if (!publishResult.ok) {
+      return publishResult;
+    }
+  }
+
+  return result;
 }