wfctl validate: unknown module type "auth.m2m" — missing from schema registry

[intel352]

Summary

wfctl validate (v0.3.47) reports auth.m2m as an unknown module type, even though it is a core engine type used for OAuth2 M2M authentication.

$ wfctl validate --plugin-dir plugins workflow/api/base.yaml
error: 1 config(s) failed validation

modules[3].type: unknown module type "auth.m2m"

Context

auth.m2m is registered at runtime in the engine (used since v0.3.10 for client_credentials, JWT-bearer grants, token introspection/revocation, JWKS, trusted keys, etc.), but it is not in coreModuleTypes or the schema registry that wfctl uses for validation.

This is the same class of issue as #305 (step types missing from wfctl), which was resolved in v0.3.36.

Expected behavior

wfctl validate should recognize auth.m2m as a valid module type.

Workaround

wfctl validate --skip-unknown-types passes validation.