suites/

Package finalizer removes what a cloud suite run left behind in the shared organisation.

Package cloudconsole contains APIP cloud control-plane and data-plane steps.

Package aiworkspacecli holds the steps that drive the ap CLI's ai-workspace commands against platform-api, the control plane the CLI treats as its AI Workspace server.

Package apcli drives the ap CLI binary.

Package apiportal holds steps that create real subscription, application, and API-key artifacts through api-portal's own REST API — the product that issues subscription tokens and API keys, which reach platform-api (and from there the gateway) as signed webhook events.

Package common contains reusable integration-suite step mechanics.

Package platformapi holds steps for both directions of the platform-api <-> gateway relationship: control_plane.go asserts against artifacts a gateway-controller pushes up to the control plane, and secret_deploy.go creates and deploys artifacts through the control plane's own REST API for the gateway to pull down.

Package platformgateway contains platform-gateway-specific integration steps.

Package steps holds suite-wide UI lifecycle and step definitions for godog features driving a real browser on the block's network.

Package aiworkspace contains AI Workspace-specific UI bindings.

Package apiportal contains API Portal-specific UI step definitions.

Package managementportal holds the Management Portal (API Control Plane) UI step definitions: signing in as either organization, preparing control-plane resources, and asserting what the console shows.

Package uivalue resolves framework placeholders, such as ${UNIQUE:name}, in UI step arguments, keeping each placeholder stable across the steps of one scenario.