iVendNextDevelopers Request a sandbox

Kit defect — tell us a piece of the kit does not do what its recipe says

For: an iVendNext Partner, a licensed customer's IT team or the CitiXsys Consulting Team who followed a kit recipe and got a wrong answer, an error or nothing. These forms are for onboarded members (who can file). Reference: the recipes (../recipes/) and the tools they name (../tools/).

A defect is a gap between what a kit piece says it does and what it does. Two short answers and the piece with its version let us repeat it.

When to use it

The kit pieces (name one in the first line of the form): event feed client · manifest · Wasm kit · MCP server · design kit · sign-in recipe · scale-profile kit · money kit · self-check.

Use another form if: the page is wrong and the kit is right → recipe or document gap; you want the kit to do something new → extension-point request or sample request.

The form

# Kit defect: <one-line title>

Kit piece and version: <The kit piece, and the version it prints or the date you downloaded it.>

## 1. What you did
<The steps from a clean start, as you typed them.>

## 2. What you expected, and what happened
<What you expected, and where it says so (the recipe step, or the kit's own output). Then what you saw. Paste the output, with secrets removed.>

- [ ] It touches a sale, a price or a payment

What we may ask you next, in the issue

How often it happens · the smallest input that still shows it (we may ask you to attach it) · your language, runtime and sandbox or staging site, and the date you made it · what it costs you (blocks the build, wrong answer, passes something it should refuse, refuses something it should pass) · any workaround.

What happens after you send it

This page in the kit