Dashboard › craft › Prefer explicit, fail-closed publish wo…
01a07c40-6865-7dc9-a7fa-1465ca010e52For publish-controller changes, use explicit runnable code and consolidated parser/documentation sources rather than inline YAML/Bash JavaScript or duplicated parsing logic. Treat JSON boundaries deliberately: pass valid JSON strings to JSON.parse and serialize structured GitHub Action outputs for fromJSON consumers. Preserve safety over permissive fallback—when workspace discovery is required, failures must stop execution rather than fall back to a potentially misrouted checkout path. Address validated review findings, update requested dependencies, and avoid unrelated formatter churn.