Lovable integration context

Find version-matched Lockerverse integration instructions in the installed SDK.

Admin copy prompts contain public resource identity and a minimum SDK version. Use the existing project package manager to install or upgrade the matching @lockerverse/react and @lockerverse/sdk pair without downgrading newer installed releases. Record the resolved old versions before installation. Then read:

1. node_modules/@lockerverse/react/MIGRATIONS.md and SDK_RULES.md in the same package. Apply all applicable upgrade steps, including skipped releases.
2. node_modules/@lockerverse/react/guides/integration.md
3. The resource guide: guides/auctions.md, guides/payment-widgets.md, guides/events.md, or guides/signup.md in that same package.

Persist the short host-root AGENTS.md section described in SDK_RULES.md. Lovable workspace knowledge can carry the same pointer for projects that have not received the file yet. Keep detailed rules in the installed SDK, and preserve all unrelated host instructions. This also covers later dependency updates that do not start from Copy Prompt.

The installed files are authoritative for that release. They are generated from the maintained documentation below, so this handoff page does not keep a second copy of implementation rules. Keep the resource identity and requested mode from the admin prompt. In particular, integrationMode: "hosted-checkout" requires the hosted payment modal, not a conversion to native SDK checkout.

• Shared integration rules
• Auctions
• Payment widget host integration, catalog, payment, and payment primitives
• Events
• Signup

Use live examples only after checking their environment notices. The live auction example uses production. Auction result review and State Lab use simulation data. Do not create live bids, payments, or signup submissions during an implementation check.