Examples

Runnable modules that prove the public Lenso authoring path.

Use these examples when you want working module code instead of a blank scaffold. They prove that a module can be wired into a host and verified through smoke checks.

The examples repository is LioRael/lenso-examples.

Install

git clone https://github.com/LioRael/lenso-examples
cd lenso-examples
pnpm install

Run the smokes

pnpm smoke

For host-level verification, run:

pnpm host-api-smoke

Support Ticket

The support-ticket module is the agent-ready proof point. It turns this prompt into a real module:

Build a support ticket module for a Lenso app.

It includes ticket data, HTTP routes, an admin action, a runtime escalation function, Console-visible metadata, and host API smokes.

Use Agent Development for the full prompt-to-check workflow.

pnpm smoke:support-ticket
pnpm host-api-smoke:support-ticket

Account Profile

The account-profile module is the follow-on proof. It depends on auth while owning profile, organization, and membership data.

pnpm smoke:account-profile
pnpm host-api-smoke:account-profile

Which example to read

Read support-ticket first when you want the full agent-ready module loop.
Read account-profile when you want to see a module depend on auth while owning its own product data.

Local host install

Run the support-ticket service, package it, then install the generated module release from a generated host:

pnpm start:support-ticket
pnpm service-package:support-ticket
lenso module release inspect dist/lenso-service/support-suite-provider/modules/support-ticket/lenso.module-release.json
lenso module install dist/lenso-service/support-suite-provider/modules/support-ticket/lenso.module-release.json \
  --base-url http://127.0.0.1:4110/lenso/service/v1

After the provider is installed, use an environment-aware service release plan for package upgrades:

lenso service env add staging \
  --service support-suite-provider \
  --target kubernetes \
  --namespace lenso-staging \
  --image ghcr.io/acme/support-suite-provider:0.4.0 \
  --public-base-url https://support-staging.example.com

lenso service release plan support-suite-provider \
  dist/lenso-service/support-suite-provider/lenso.service-package.json \
  --env staging \
  --output .lenso/support-suite-provider.staging.release-plan.json
lenso service policy check .lenso/support-suite-provider.staging.release-plan.json --fail-on breaking
lenso service deploy export support-suite-provider \
  --env staging \
  --target kubernetes \
  --output-dir examples/support-ticket/kubernetes/staging
lenso service release apply .lenso/support-suite-provider.staging.release-plan.json --env staging

Console Services shows release risk, provider history, deployment environments, Kubernetes rollout observations, and drift from .lenso/service-releases.json and .lenso/service-deployments.json.

Restart the host and open /console to confirm the module appears.