# Lemon Squeezy upload checklist

This is the practical seller handoff for **SmartCut64 Personal**. It is written
for a first-time software publisher and deliberately distinguishes draft-store
work from a live commercial launch.

## Current Lemon Squeezy state

- Seller: **LINEKERPANDI LIMITED**
- Store ID: `448537`
- Test product ID / default variant ID: `1278355` / `1998551`
- Live product ID / default variant ID: `1304562` / `2040403`
- Product: **SmartCut64 Personal**
- Currency and price: **GBP 4.99**, one-time founding-user offer
- Licence-key generation: enabled
- Activation limit: 2 computers
- Test product visibility: published in the isolated test storefront
- Live product visibility: **Draft** (not publicly purchasable)
- Seller identity/KYC: verified
- Live-store activation: approved and Live Mode available on 2026-08-20
- Receipt and confirmation copy: configured with download, licence activation,
  and `support@linekerpandi.com` guidance

No password, API token, webhook secret, private entitlement key, or signing
credential belongs in this document, Lemon Squeezy, Git, or a customer file.

## Safe work before public launch

1. Upload `assets/smartcut64-store-card-1600x1200.png` as draft product media.
2. Use `docs/PRODUCT_LISTING.md` as the product-copy approval draft.
3. The approved test product was copied to Live Mode on 2026-08-20 and returned
   to Draft. Keep it in Draft until the production lifecycle and external
   release gates pass.
4. Keep the public website private until its purchase/download links point to a
   fully tested live product.
5. Use the signed commercial candidate only for internal installation,
   compatibility, and delivery tests until the external launch gates pass.

The current candidate contains the production public entitlement key and
service URL and has passed the exact paid release gate. The production Worker
shell is nevertheless intentionally fail-closed because the entitlement
private key and live webhook secret are not configured. The approved live IDs
are recorded in the ignored production Worker configuration.
Uploading it as a live product now would leave buyers unable to obtain a clean-
export entitlement.

## Build the exact final upload set

The following sequence has been exercised for the current candidate and must be
repeated after any source change and once more after the production bridge and
external launch gates are complete:

1. Configure the release with the production entitlement public modulus and
   the seller-controlled HTTPS licensing-service URL.
2. Generate a paid release-test entitlement bound to the release machine.
3. Run the complete commercial gate:

   `powershell -ExecutionPolicy Bypass -File scripts/release-gate.ps1 -PaidTestLicense <path>`

4. Sign and verify the three first-party executables and installer:

   `powershell -ExecutionPolicy Bypass -File scripts/sign-release-artifact.ps1 -BuildDir build/windows-ucrt-gui-release`

5. Re-run the portable and installer gates after signing.
6. From a clean, committed source tree, create a non-overwriting staging folder:

   `powershell -ExecutionPolicy Bypass -File scripts/prepare-store-upload.ps1`

7. Open `README-FIRST.txt` and the generated JSON manifest. The script
   intentionally leaves `live_upload_allowed` as `false`: automation cannot
   grant legal or business approval. Complete
   `SELLER-COMMERCIAL-SIGNOFF.md` for those exact hashes before live upload.

## Files for the final Lemon product

Upload these four release files from one verified final staging folder:

1. `SmartCut64-1.0.3-win64.exe` — recommended Windows installer
2. `SmartCut64-1.0.3-win64.zip` — portable build
3. `SmartCut64-1.0.3-source.zip` — exact corresponding source and dependency
   source archives required by the GPL/LGPL delivery
4. `SmartCut64-1.0.3-SHA256SUMS.txt` — integrity manifest for all three archives

Use `smartcut64-store-card-1600x1200.png` as product media. The `SELLER-*`
files and `README-FIRST.txt` are operator notes, not customer downloads.

## Required test purchase sequence

Run these in Lemon's test mode against the exact final files and test bridge:

1. Successful purchase and first activation
2. Second-computer activation
3. Third-computer rejection with a useful message
4. Deactivation and transfer to another computer
5. Perpetual offline operation after activation, including after an extended
   simulated service outage
6. Wrong email, wrong product, malformed key, timeout, and rate-limit handling
7. Refund and disabled-key webhook revocation
8. Receipt links for installer, portable ZIP, source ZIP, and checksums
9. Evaluation export visibly watermarked throughout every video segment
10. Paid export clean, playable, and reported as the expected smart-copy or
    boundary-recode path

Current test-mode evidence covers repeat activation, items 1-4, wrong-email
handling, signed refund-webhook revocation, deployed rate limiting, and the
paid-entitlement delivery gate. Receipt/source downloads, the documented
perpetual offline operation, support reset, and exact uploaded-file delivery stay
open until the staged files can be attached to an approved Lemon product.

Repeat the purchase/refund path once in live mode with a controlled real order
before announcing the product, then retain the order, webhook, entitlement,
hash, signature, and playback evidence as the release record.

## Help and website

SmartCut64 already has original, clean-room documentation:

- Bundled guide: `docs/USER_GUIDE.md`, available in the app from
  **Help > Contents** and packaged for offline use
- Product/help site source: `website/`
- Help-site sections: getting started, cutting and preview, smart rendering,
  formats, profiles, licensing, support, and release readiness

The documentation may describe familiar workflow concepts and factual project
compatibility, but must not copy VideoReDo help wording, screenshots, artwork,
or source. Keep the independent-product and third-party-trademark disclaimer.

## Gates that require a person or external organization

- Production Cloudflare private-key/live-ID secret entry,
  seller-controlled domain configuration, monitoring, and recovery evidence
- The final controlled Lemon Squeezy live payment/refund
- Two independently verified offline backups of the production entitlement key
- Independent GPL/LGPL and customer-terms review
- Trademark/copyright clearance for the name and artwork
- Qualified codec-patent advice for each sales territory and distribution model
- Optional Application Verifier run that requires Windows elevation/UAC

Until those gates are evidenced, SmartCut64 is a signed engineering candidate,
not an approved product for public sale.
