DashboardcraftPrefer explicit, fail-closed publish wo…

Prefer explicit, fail-closed publish workflow design

Category: preference
Confidence: 0.80
ID: 01a07c40-6865-7dc9-a7fa-1465ca010e52
Project ID: e16af391-c497-4837-b681-c849a5514499
Cross-project: No
Recalled in other projects: 0
Source session: 1Okgn0vvN7hdZmhlc
Created: 2026-09-07 14:23:10
Updated: 2026-09-07 14:23:10

Content

For 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.

Move to: