validate-scenarios

To lint scenarios for missing fields and taxonomy violations, validate the scenarios array against the required fields and tag taxonomy defined in your source-of-truth files. The process cross-checks data to surface actionable errors and warnings.

Checking for unsanitized credentials in data files involves applying defined rules to scan for sensitive data within your scenarios. The validation surfaces credential leaks as findings without auto-fixing them, ensuring publish-ready data.

When trigger and action types are undocumented in scenarios, the validation process flags these inconsistencies by cross-checking them against the documentation mapping. It reports these discrepancies as errors or warnings to guide remediation.

You cannot fully validate scenario data without running a build process, because the validation concludes by executing npm run build. This step verifies that the marketplace data is healthy and the application compiles successfully.

Scenario validation does not automatically fix credential leaks. It surfaces sensitive data findings using defined rules and guides remediation, requiring explicit user requests before applying any auto-fixes to the data.