Dashboard › craft › Require strict validation without norma…
01a07e7f-cccc-7eac-895b-d5ef7c4cf11dFor Publish workflow inputs from issue titles/bodies, paths, repositories, versions, revisions, and workspace names, use explicit narrow validation and fail closed on malformed or ambiguous values. Preserve identities, paths, and casing exactly; never normalize them. Enforce the canonical title grammar through a shared resolver before CI/API side effects, reject unsafe segments such as ., .., __proto__, and leading -, and require canonical, uniquely recognized structured links for revisions.