Getting Started

Purpose

Orient a new user to the local V6 Storefront and its verified public entry points.

Eligible Users and Roles

Guests, customers, and creators. Administrator tasks use a separate port-3007 fixture.

Prerequisites

• Local V6 Storefront available at http://localhost:3006.
• A safe synthetic account only when testing signed-in functions.
• No real credentials, payment details, or personal data in screenshots.

How to Open This Feature

Open http://localhost:3006; the root storefront entry leads to the public shop surface.

Step-by-Step Instructions

Step 1: Open the Shop

Navigate to /shop and confirm the storefront heading and public content render.

Step 2: Check a Mobile Layout

At 390px width, confirm the page remains usable without horizontal overflow.

Step 3: Choose a Supported Area

Use the header to reach public discovery, account access, cart, or creator surfaces. The source inventory contains 34 V6 page routes, but routes not individually operated remain Inferred.

Possible States

Publicly Available

Public catalog content loads without a signed-in account.

Authentication Required

Protected destinations redirect a guest to sign-in and preserve the intended destination where verified.

Unavailable or Blocked

Dependency failures should expose recovery rather than fabricate success. Admin operation is Blocked without the port-3007 fixture.

Input Rules and Limits

Do not enter secrets or real personal information. Route-specific input constraints are documented in the corresponding feature guide; unverified limits remain Not Tested.

Common Problems and Recovery

• If a protected route redirects to sign-in, authenticate with an authorized synthetic account.
• If an API-dependent page is unavailable, preserve work and retry only after service recovery.
• If /search redirects to /search/test, treat it as an open product decision.

Important Warnings

Do not treat source inventory as proof that every route, role, or state passed. Do not operate real financial transactions.

What Happens Next

Continue to the role-appropriate guide and verify the expected state after navigation and refresh.

Current closing evidence includes 382/382 V6 unit tests, 22/22 accessibility E2E tests, passing V6 and root typechecks, a passing targeted V6 production build, and 27/27 worker-events tests. The full storefront rerun has not completed, so no result is claimed.